Am 30.03.2012 13:17, schrieb Paolo Bonzini: > We do not want jobs to keep a device busy for a possibly very long > time, and management could become confused because they thought a > device was not even there anymore. So, cancel long-running jobs > as soon as their device is going to disappear. > > Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Shouldn't management tools know what jobs they have running? We can take this for now, but once we switch to blockdev-add/del, management tools will have to be explicit about the BlockDriverState deletion (and I think the right semantics there is that it fails if jobs are still running). Kevin
