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.
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.