Some notes based my understanding (and from a brief chat with libvirt/QEMU developers):
- DEVICE_DELETED is the event that QEMU sends to libvirt, *once* the device was removed by the guest, so that libvirt can clean-up. So if we see DEVICE_DELETED that means the device was successfully detached from QEMU's point of view (therefore, from the guest's PoV, too)
- The presence of the '/sys/module/pci_hotplug/' directory in the guest confirms that it is capable of handling hotplug/hotunplug events. (And Lee confirmed on IRC that the CirrOS guest _does_ have this directory)
So, if you _can_ see DEVICE_DELETED, then it sounds like the problem is somewhere _else_ than the guest OS.
Some notes based my understanding (and from a brief chat with libvirt/QEMU developers):
- DEVICE_DELETED is the event that QEMU sends to libvirt, *once* the device was removed by the guest, so that libvirt can clean-up. So if we see DEVICE_DELETED that means the device was successfully detached from QEMU's point of view (therefore, from the guest's PoV, too)
- The presence of the '/sys/module/ pci_hotplug/ ' directory in the guest confirms that it is capable of handling hotplug/hotunplug events. (And Lee confirmed on IRC that the CirrOS guest _does_ have this directory)
So, if you _can_ see DEVICE_DELETED, then it sounds like the problem is somewhere _else_ than the guest OS.