在 6/19/2017 6:49 PM, Kevin Wolf 写道:
'info block' shows nothing, but we can't add drive who's id
is'drive-virtio-disk1' too.
Yes, the old BlockBackend is only fully freed when the guest actually
unplugs the device. Specifically, we would have to free the QemuOpts
in DriveInfo that keeps the ID
Am 19.06.2017 um 12:27 hat Xie Changlong geschrieben:
> 在 6/19/2017 3:27 PM, Kevin Wolf 写道:
> >Am 18.06.2017 um 09:21 hat Xie Changlong geschrieben:
> >>In device hot-remove scenario, if we don't probe acpiphp module on
> >>the guest, 'device_del' will never emit DEVICE_DELETED event(because
>
在 6/19/2017 3:27 PM, Kevin Wolf 写道:
Am 18.06.2017 um 09:21 hat Xie Changlong geschrieben:
In device hot-remove scenario, if we don't probe acpiphp module on
the guest, 'device_del' will never emit DEVICE_DELETED event(because
guest will not write to __EJ0) . So we can confirm that hot-remove
Am 18.06.2017 um 09:21 hat Xie Changlong geschrieben:
> In device hot-remove scenario, if we don't probe acpiphp module on
> the guest, 'device_del' will never emit DEVICE_DELETED event(because
> guest will not write to __EJ0) . So we can confirm that hot-remove
> failed. But IIUC, there is no
Resend
在 6/18/2017 3:21 PM, Xie Changlong 写道:
Hi all
In device hot-remove scenario, if we don't probe acpiphp module on the
guest, 'device_del' will never emit DEVICE_DELETED event(because guest
will not write to __EJ0) . So we can confirm that hot-remove failed. But
IIUC, there is no event
Hi all
In device hot-remove scenario, if we don't probe acpiphp module on the
guest, 'device_del' will never emit DEVICE_DELETED event(because guest
will not write to __EJ0) . So we can confirm that hot-remove failed. But
IIUC, there is no event such as DEVICE_ADDED, so
1) How can we confirm
