[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 424] New: Frontend directories are not been removed from store on {network, block}-detach
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=424 Summary: Frontend directories are not been removed from store on {network,block}-detach Product: Xen Version: unstable Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Unspecified AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx ReportedBy: mfb@xxxxxxxxxx BugsThisDependsOn: 420 If a device is detached from domU the backend directories are being removed by hotplug scripts, but the frontend ones not. Who is supposed to remove that? 1. The frontend driver/xenbus 2. Hotplug scripts on dom0 I tested the second approach, but as the the frontend device was not unregistered it still watching the frontend nodes on store. After I remove that directory frontend driver rewrite the state node. When frontend device is unregistered I can remove frontend directory from store that nothing changes there (as it should be). So we depend on bug #420. Here is the same text I put on #420 report: --- 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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |