Re: [Bug 1925496] Re: nvme disk cannot be hotplugged after removal

[Max Reitz <mreitz@redhat.com>]

On 28.04.21 12:12, Klaus Jensen wrote:
> On Apr 28 09:31, Oguz Bektas wrote:
>>> My understanding is that this is the expected behavior. The reason is
>>> that the drive cannot be deleted immediately when the device is
>>> hot-unplugged, since it might not be safe (other parts of QEMU could
>>> be using it, like background block jobs).
>>>
>>> On the other hand, the fact that if the drive is removed explicitly
>>> through QMP (or in the monitor with drive_del), the drive id is
>>> remains "in use". This might be a completely different bug that is
>>> unrelated to the nvme device.
>>
>> using the same commands I can hot-plug and hot-unplug a scsi disk like
>> this without issue - this behavior only appeared on nvme devices.
>>
> 
> Kevin, Max, can you shed any light on this?
> 
> Specifically what the expected behavior is wrt. to the drive when 
> unplugging a device that has one attached?
> 
> If the scsi disk is capable of "cleaning up" immediately, then I suppose 
> that some steps are missing in the nvme unrealization.

I’m not very strong when it comes to question for guest devices, but 
looking into the QAPI documentation, it says that when DEVICE_DELETED is 
emitted, it’s safe to reuse the device ID.  Before then, it isn’t, 
because the guest may yet need to release the device.

So the questions that come to my mind are:
- Do nvme guest devices have a release protocol with the guest, so that 
it just may take some time for the guest to release the device?  I.e. 
that this would be perfectly normal and documented behavior?
(Perhaps this just isn’t the case for scsi, or the guest just releases 
those devices much quicker)

- Did Oguz always wait for the DEVICE_DELETED event before reusing the 
ID?  Sounds like it would be a bug if reusing the ID after getting that 
event failed.

Max