Re: [Xen-devel] blktap3: libxl complaining when a domain gets destroyed

[Thanos Makatos <thanos.makatos@xxxxxxxxxx>]

> This is because libxl will wait for the backend to reach state '6'
> (closed). Even if state 6 is not reached libxl will clean up the
> backend path, you should check why blktap3 doesn't set the backend to
> state 6.

At some point during "xl destroy ..." the backend state is set to 5 (assuming 
by libxl?). I get a XenStore watch triggering on this event. So how should I 
handle this event? Setting the backend state to 6 fails with EPERM, which I 
don't understand since I do modify the backend state when going from 
initialised to connected etc.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel