On Fri, Feb 12, 2016 at 03:53:06PM +0100, Olaf Hering wrote:
> On Fri, Feb 12, Wei Liu wrote:
>
> > CC'ing other tools maintainer.
> >
> > On Thu, Feb 11, 2016 at 11:37:49AM +0100, Olaf Hering wrote:
> > > How should libxl__initiate_device_generic_remove deal with devices which
> >
> > I think y
On Fri, Feb 12, Wei Liu wrote:
> CC'ing other tools maintainer.
>
> On Thu, Feb 11, 2016 at 11:37:49AM +0100, Olaf Hering wrote:
> > How should libxl__initiate_device_generic_remove deal with devices which
>
> I think you meant libxl__initiate_device_remove. There is no function
> called libxl__
CC'ing other tools maintainer.
On Thu, Feb 11, 2016 at 11:37:49AM +0100, Olaf Hering wrote:
> How should libxl__initiate_device_generic_remove deal with devices which
I think you meant libxl__initiate_device_remove. There is no function
called libxl__initiate_device_generic _remove.
> have no fr
How should libxl__initiate_device_generic_remove deal with devices which
have no frontend driver? Right now it moves "state" from either
XenbusStateInitialising or XenbusStateInitWait to XenbusStateClosing.
Then it expects the backend to move "state" to XenbusStateClosed. This
will never happen, at