Public bug reported:
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,
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: libvirt (Ubuntu Focal)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Confirmed
** Affects: libvirt (Ubuntu Jammy)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Confirmed
** Also affects: libvirt (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: New => Fix Released
** Changed in: libvirt (Ubuntu Focal)
Status: New => Confirmed
** Changed in: libvirt (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu Focal)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: libvirt (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: libvirt (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu Jammy)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Description changed:
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
+ $ virsh list
+ Id Name State
+ -------------------------
+ 1 test-vm running
- $ sudo systemctl restart libvirtd.service
+ $ 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'
+ $ 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
+ Id Name State
+ --------------------
- $ virsh list --all
- Id Name State
- --------------------------
- - test-vm shut off
+ $ 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,
+ $ pgrep -af qemu-system-x86_64 | cut -d, -f1
+ 2638 /usr/bin/qemu-system-x86_64 -name guest=test-vm,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059272
Title:
libvirt domain is not listed/managed after libvirt restart with
messages "internal error: no monitor path" and "Failed to load config
for domain"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2059272/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
