[Xen-bugs] [Bug 420] New: block-attach after block-detach in the same device does not work and does not report failure

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

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

           Summary: block-attach after block-detach in the same device does
                    not work and does not report failure
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: mfb@xxxxxxxxxx


As exposed by "05_attach_and_dettach_device_repeatedly_pos" and
"09_attach_and_dettach_device_check_data_pos" if I try to attach a block device
after detach that it will fail without reporting any error.

Here is an example:

$xm block-attach my-domU phy:ram3 hda1 w

$xm block-list my-domU
(769 ((virtual-device 769) (backend-id 0) (state 4) (backend
/local/domain/0/backend/vbd/114/769) (ring-ref 8) (event-channel 6)))

$xm block-detach my-domU 769

$xm block-list my-domU
(769 ((virtual-device 769) (backend-id 0) (state 6) (backend
/local/domain/0/backend/vbd/114/769) (ring-ref 8) (event-channel 6)))

$xm block-attach my-domU phy:ram3 hda1 w

$xm block-list my-domU
(769 ((virtual-device 769) (backend-id 0) (state 1) (backend
/local/domain/0/backend/vbd/114/769) (ring-ref 8) (event-channel 6)))

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