[Xen-bugs] [Bug 416] New: xm block-list != xm list --long != reality

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

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

           Summary: xm block-list != xm list --long != reality
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: sean@xxxxxxxxx


xm block-list seems to only record the adds of devices, and xm list --long never
seems to change once block devices are added.  If you do the following sequence
of actions:

1. Boot a domain with no /dev/hdc or /dev/hdd
2. xm block-attach DomainName file://some/iso/loop.iso /dev/hdc ro
3. mount /dev/hdc /mnt/cdrom
4. xm block-attach DomainName file://some/iso/loop.iso /dev/hdd ro
5. xm block-detach DomainName hdd-device-id (*)

* The help says you can use symbolic name, but you can't.  Use block-list to
figure out what the hdd-device-id is.

You will end up with "xm block-list" showing both the hdc and hdd devices, and
"xm list --long DomainName" showing neither.  Given that hdc is mounted and
working in DomU, it clearly is still attached.  So we are in a bad possition
that 2 tools commands are inconsistant with each other, and neither actually
reflects reality.


xen info::::::::::::::::::::::::::::::::::::::::::
xen_major              : 3
xen_minor              : 0
xen_extra              : -devel
xen_caps               : xen-3.0-x86_32
platform_params        : virt_start=0xfc000000
xen_changeset          : Thu Nov 17 10:10:52 2005 +0100 7855:0adacfa2e33f
cc_compiler            : gcc version 3.4.3 (Mandrakelinux 10.2 3.4.3-7mdk)
cc_compile_by          : sdague
cc_compile_domain      : (none)
cc_compile_date        : Thu Nov 17 10:34:14 EST 2005

-- 
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