Hi, how can I see who''s who?: # xm block-list vm1 Vdev BE handle state evt-ch ring-ref BE-path 768 0 0 4 11 1036 /local/domain/0/backend/vbd/9/768 832 0 0 3 12 1037 /local/domain/0/backend/vbd/9/832 # xm block-list vm3 Vdev BE handle state evt-ch ring-ref BE-path 768 0 0 4 11 1036 /local/domain/0/backend/vbd/10/768 832 0 0 3 12 1037 /local/domain/0/backend/vbd/10/832 If I want to detach the CD-ROM drive to enable media change, what''s the correct device? Did someone forget a translation for "768"? 768 is 0x300, and /dev/hda has major 3, minor 0. Considering that "xm" is a python program, shouldn''t it translate the numbers to something more useful? Likewise why not allow device names for "block- detach" as well? Regards, Ulrich _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Did someone forget a translation for "768"? 768 is 0x300, and /dev/hda has > major 3, minor 0. Considering that "xm" is a python program, shouldn''t it > translate the numbers to something more useful? Likewise why not allow > device names for "block- detach" as well?True, but this would only work for Linux guests, because other OSes will have a different idea of what a vdev number means to them. Doing this decoding would need the tools to be aware of the kind of guest OS running to provide sensible naming (or fall back to numbers) - doable, though. An easier route might be to simply allow disks to be named by the user in the config file. It''d be a relatively simple patch, adding an extra component to the disk description. You could file it as a wishlist in the bug tracker. HTH, Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Seemingly Similar Threads
- HVM creation problem
- XM create issue: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
- XM create issue: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
- Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working
- Attach CDROM to windows