There's a race condition on libvirtd shutdown that might cause the domain status XML file(s) to lose the '<monitor path=...'> tag/field.
This causes an error on libvirtd startup, and the domain is not listed/managed, despite it is still running.
$ virsh list Id Name State ------------------------- 1 test-vm running
$ sudo systemctl restart libvirtd.service
$ journalctl -b -u libvirtd.service | tail ... ... libvirtd[2789]: internal error: no monitor path ... libvirtd[2789]: Failed to load config for domain 'test-vm'
$ virsh list Id Name State --------------------
$ virsh list --all Id Name State -------------------------- - test-vm shut off
$ pgrep -af qemu-system-x86_64 | cut -d, -f1 2638 /usr/bin/qemu-system-x86_64 -name guest=test-vm,
There's a race condition on libvirtd shutdown
that might cause the domain status XML file(s)
to lose the '<monitor path=...'> tag/field.
This causes an error on libvirtd startup, and
the domain is not listed/managed, despite it
is still running.
$ virsh list ------- ------- -----
Id Name State
------
1 test-vm running
$ sudo systemctl restart libvirtd.service
$ journalctl -b -u libvirtd.service | tail
...
... libvirtd[2789]: internal error: no monitor path
... libvirtd[2789]: Failed to load config for domain 'test-vm'
$ virsh list ------- -------
Id Name State
------
$ virsh list --all ------- ------- ------
Id Name State
------
- test-vm shut off
$ pgrep -af qemu-system-x86_64 | cut -d, -f1 qemu-system- x86_64 -name guest=test-vm,
2638 /usr/bin/