[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-bugs] [Bug 321] New: xm block-detach fails to detach a device by name



http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=321

           Summary: xm block-detach fails to detach a device by name
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: lge@xxxxxxxxxx
                CC: pl@xxxxxxxxxx


Changeset: 7344

After creating a domain with disk = [ 'phy:/dev/ram0,hda1,w' ], xm block-detach
fails to detach the device by name (hda1). I am able to detach the device using
device ID (769). 05_block-destroy_byname_pos.test of xmtest fails because of
this reason. 

Here is the return status and output after running block-detach command:

status =256
output:
Traceback (most recent call last):
  File "/usr/sbin/xm", line 10, in ?
    main.main(sys.argv)
  File "/tmp/xen-unstable.hg/dist/install/usr/lib/python/xen/xm/main.py", line
712, in main
    handle_xend_error(argv[1], args[0], ex)
  File "/tmp/xen-unstable.hg/dist/install/usr/lib/python/xen/xm/main.py", line
176, in handle_xend_error
    raise ex
xen.xend.XendProtocol.XendError: Exception: invalid literal for int(): hda1

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.