If I hack qemuProcessStop() to not kill a vm, kvm keeps running, but the monitor sock fd (13) is closed (presumably because libvirt has disconnected).
This seems to confirm that a race triggered by another virsh list/start action is causing a qemu task which is starting up to get killed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/961217 Title: virsh start domain sometimes fail in oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/961217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
