On 09/20/2010 01:59 PM, Michael S. Tsirkin wrote:
You can also initiate the unplug from the OS without the ACPI event
ever happening. I suspect that in our current implementation, that
means that we'll automatically delete the device which may have
strange effects on management tools.
So it probably makes sense for our interface to present the same
procedure. What do you think?
Regards,
Anthony Liguori
We seem to have two discussions here. you speak about how an ideal hot plug
interface will look. This can involve new commands etc.
I speak about fixing existing ones so qemu and/or guest won't crash.
To be fair, existing qemu won't crash if you do:
(qemu) device_del <device>
Use info_qtree to notice when device goes away
(qemu) netdev_del <backend>
You're trying to come up with a workaround for the fact that libvirt is
making bad assumptions. That's wrong. We either need to fix libvirt to
not make bad assumptions or we need to provide better interfaces for
libvirt to use if the current interfaces aren't desirable.
Regards,
Anthony Liguori
This requires fixing existing commands, unless we can't
fix them at all - which is demonstrably not the case.
