Il 16/04/2013 09:57, Stefan Hajnoczi ha scritto: > So it sounds like unplug will not block and there is no guarantee the > memory is actually unplugged when the monitor command completes. The > memory region is only released when the last reference count holder lets > go. > > This means that pending I/O to a hung NFS mount can delay the actual > unplug for unbounded time (by default the kernel NFS client keeps > retrying and does not fail the I/O request). The user will be able to > issue additional monitor commands and see that memory is not yet > unplugged?
I think "info mtree" would provide information. We can add an event too, similar to the recently added DEVICE_DELETED. Paolo
