Thanks - is there an easy way for you to test utopic with the 1.2.5 libvirt build (which should be building right now)?
Meanwhile I"ll try a few combinations to see if I can track down what changed to cause this. I do maintain that what you are doing is fundamentally racy. I assume qemu is being or is supposed to be started with -no-reboot, so that the qemu process exits. But by waiting for 'vm.isActive()' to become 0, you can always to a race where the vm is stopped and restarted between your calls. Would it be possible for you to get the pid of the qemu process and simply wait for it to exit? That should be race-proof with qemu -no- reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329254 Title: VMs do not become inactive during the reboot on saucy and later hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1329254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
