Created attachment 705893 [details] logs Description of problem: I tried to deactivate a disk while the vm was doing a live storage migration on one of its other disks. I got a CanDoAction in engine: 2013-03-06 01:08:43,791 WARN [org.ovirt.engine.core.bll.HotUnPlugDiskFromVmCommand] (ajp-/127.0.0.1:8702-3) CanDoAction of action HotUnPlugDiskFromVm failed. Reasons:VAR__ACTION__HOT_UNPLUG,VAR__TYPE__VM_DISK,ACTION_TYPE_FAILED_VM_STAT looking at the log, the VM's status is illegal because vdsm is moving it to Pause during extend: 2013-03-06 01:08:40,835 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (QuartzScheduler_Worker-37) VM FGFG 8770aef8-5b0a-4b81-9ac0-866884cef95c moved from Up --> Paused Version-Release number of selected component (if applicable): SF9 vdsm-4.10.2-10.0.el6ev.x86_64 libvirt-0.10.2-18.el6_4.eblake.2.x86_64 How reproducible: race Steps to Reproduce: 1. try to unplug a disk once the lvextend has moved the vm to pause 2. 3. Actual results: we fail with CanDoAction Expected results: since we change the vm status a lot during live migrate, if lvextend bug is not fixed we should at least create a flow for status change during lvextend (such as retries). Additional info: logs
Fede, any reason to prevent hotunplug while VM is in pause?
(In reply to comment #1) > Fede, any reason to prevent hotunplug while VM is in pause? I checked the qemu/libvirt code and it looks like there's no limitation about hot-plugging/hot-unplugging when the VM is suspended. I also successfully tested it a couple of times (qemu-1.2.2-6.fc18/libvirt-0.10.2.3-1.fc18). If there's any limitation in VDSM (I don't think there is), it should be removed (maybe cloning this bug). As far as this issue is concerned the canDoAction can be modified accordingly.
http://gerrit.ovirt.org/#/c/12986/
Please note the incongruity with bug 918798 comment 8. Fine by me to enable it but qemu should try to solve its issue.
sf13.1 Can hotplug/unplug/attach disk while VM is paused.
3.2 has been released