Comment 4 for bug 1436561

This can be caused by things other than the hypervisor (udev, blockid, lvm) accessing the device nodes. Running 'fuser' and 'ls -l /block/<dev>/holders' in the case of removal failure can sometimes catch the culprit(s), though sometimes there are gone by the time you check.