Ubuntu
libvirt package

[Focal] 'virsh domcapabilities' fails unless 'virsh capabilites' is run first

Bug #1867460 reported by Chris Newcomer
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Fix Released
Undecided
Christian Ehrhardt 

Bug Description

This is affecting my MAAS installation to be able to create VMs through the pods interface.

cnewcome@neuromancer:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu Focal Fossa (development branch)"

cnewcome@neuromancer:~$ virsh domcapabilities
error: failed to get emulator capabilities
error: invalid argument: unable to find any emulator to serve 'x86_64' architecture

cnewcome@neuromancer:~$ virsh capabilities
<capabilities>

...
</capabilities>

cnewcome@neuromancer:~$ virsh domcapabilities
<domainCapabilities>
...
</domainCapabilities>

cnewcome@neuromancer:~$ dpkg -l | grep libvirt
ii gir1.2-libvirt-glib-1.0:amd64 2.0.0-2 amd64 GObject introspection files for the libvirt-glib library
ii libvirt-clients 6.0.0-0ubuntu5 amd64 Programs for the libvirt library
ii libvirt-daemon 6.0.0-0ubuntu5 amd64 Virtualization daemon
ii libvirt-daemon-driver-qemu 6.0.0-0ubuntu5 amd64 Virtualization daemon QEMU connection driver
ii libvirt-daemon-driver-storage-rbd 6.0.0-0ubuntu5 amd64 Virtualization daemon RBD storage driver
ii libvirt-daemon-system 6.0.0-0ubuntu5 amd64 Libvirt daemon configuration files
ii libvirt-daemon-system-systemd 6.0.0-0ubuntu5 amd64 Libvirt daemon configuration files (systemd)
ii libvirt-glib-1.0-0:amd64 2.0.0-2 amd64 libvirt GLib and GObject mapping library
ii libvirt0:amd64 6.0.0-0ubuntu5 amd64 library for interfacing with different virtualization systems
ii python3-libvirt 6.0.0-0ubuntu3 amd64 libvirt Python 3 bindings
cnewcome@neuromancer:~$

Related branches

~paelzer/ubuntu/+source/libvirt:lp-1867460-fix-domcapabilities-focal
Rafael David Tinoco (community): Approve
Canonical Server: Pending requested
Canonical Server packageset reviewers: Pending requested
Diff: 5704 lines (+5514/-0)
31 files modified
debian/changelog (+13/-0)
debian/patches/series (+29/-0)
debian/patches/stable/lp-1868539-bhyve-command-remove-unused-includes.patch (+41/-0)
debian/patches/stable/lp-1868539-daemon-set-default-memlock-limit-for-systemd-service.patch (+94/-0)
debian/patches/stable/lp-1868539-m4-libxl-properly-fail-when-libxl-is-required.patch (+47/-0)
debian/patches/stable/lp-1868539-qemu-Don-t-compare-local-and-remote-hostnames-on-mig.patch (+62/-0)
debian/patches/stable/lp-1868539-qemu-Stop-domain-on-failed-restore.patch (+104/-0)
debian/patches/stable/lp-1868539-qemu-Use-g_autoptr-for-qemuDomainSaveCookie.patch (+140/-0)
debian/patches/stable/lp-1868539-qemu-do-not-revert-to-NULL-bandwidth.patch (+45/-0)
debian/patches/stable/lp-1868539-qemu-preserve-error-on-bandwidth-rollback.patch (+59/-0)
debian/patches/stable/lp-1868539-qemu-save-restore-original-error-when-recovering-fro.patch (+60/-0)
debian/patches/stable/lp-1868539-qemu-use-correct-backendType-when-checking-memfd-cap.patch (+46/-0)
debian/patches/stable/lp-1868539-qemuDomainGetStatsIOThread-Don-t-leak-array-with-0-i.patch (+49/-0)
debian/patches/stable/lp-1868539-qemuDomainSaveImageStartVM-Use-VIR_AUTOCLOSE-for-int.patch (+50/-0)
debian/patches/stable/lp-1868539-qemuDomainSaveImageStartVM-Use-g_autoptr-for-virComm.patch (+40/-0)
debian/patches/stable/lp-1868539-qemuTestParseCapabilitiesArch-Free-binary.patch (+52/-0)
debian/patches/stable/lp-1868539-security-Try-harder-to-run-transactions.patch (+97/-0)
debian/patches/stable/lp-1868539-tests-fix-double-unlock-of-monitor-in-hotplug-test.patch (+64/-0)
debian/patches/stable/lp-1868539-testutils-check-return-value-of-g_setenv.patch (+39/-0)
debian/patches/stable/lp-1868539-testutilsxen-error-out-on-initialization-failure.patch (+42/-0)
debian/patches/stable/lp-1868539-virDomainFSDefFree-Unref-private-data.patch (+52/-0)
debian/patches/stable/lp-1868539-virsystemdtest-do-not-leak-socket-path.patch (+55/-0)
debian/patches/stable/lp-1868539-vz-Fix-return-value-in-error-path.patch (+49/-0)
debian/patches/ubuntu/lp-1853200-cpu_map-Add-decode-element-to-x86-CPU-model-definiti.patch (+741/-0)
debian/patches/ubuntu/lp-1853200-cpu_map-Add-more-noTSX-x86-CPU-models.patch (+695/-0)
debian/patches/ubuntu/lp-1853200-cpu_map-Don-t-use-new-noTSX-models-for-host-model-CP.patch (+129/-0)
debian/patches/ubuntu/lp-1853200-cpu_x86-Honor-CPU-models-decode-element.patch (+59/-0)
debian/patches/ubuntu/lp-1853200-cputest-Add-data-for-Intel-R-Core-TM-i7-8550U-CPU-wi.patch (+2022/-0)
debian/patches/ubuntu/lp-1867460-qemu-fixing-auto-detecting-binary-in-domain-capabili.patch (+115/-0)
debian/patches/ubuntu/lp-1867460-qemu_capabilities-Rework-domain-caps-cache.patch (+325/-0)
debian/patches/ubuntu/lp-1868528-util-virhostcpu-Fail-when-fetching-CPU-Stats-for-inv.patch (+99/-0)
Revision history for this message
Bryce Harrington (bryce) wrote :

I was able to reproduce this in lxc:

$ sudo apt-get install libvirt-clients gir1.2-libvirt-glib-1.0 libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd libvirt-daemon-system libvirt-daemon-system-systemd libvirt-glib-1.0-0 libvirt0 python3-libvirt

triage-focal+20.04:~$ virsh domcapabilities
error: failed to get emulator capabilities
error: invalid argument: unable to find any emulator to serve 'x86_64' architecture

And after running `virsh capabilities` and then again `virsh domcapabilities` it shows valid looking output.

Changed in libvirt (Ubuntu):
status: New → Triaged
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

I was seeing that as well, will look at this as soon as some other high prio breakages are resolved.

Changed in libvirt (Ubuntu):
assignee: nobody → Christian Ehrhardt  (paelzer)
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Repro is easy, right after install:

root@f-dcap-after-cap:~# virsh domcapabilities
error: failed to get emulator capabilities
error: invalid argument: unable to find any emulator to serve 'x86_64' architecture

But if you run cap, then dcap works:
$ virsh capabilities
...
$ virsh domcapabilities
... now it works ...

The situation can be re-created on a system later on via:

$ rm /var/cache/libvirt/qemu/capabilities/*.xml
$ systemctl restart libvirtd
$ virsh domcapabilities
error: failed to get emulator capabilities
error: invalid argument: unable to find any emulator to serve 'x86_64' architecture

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

After an upstream discussion (Thanks danpb !) I'll probably need:

$ git tag --contains c76009313f8068c848cad6cb517daf42e6716bb9
v6.1.0
v6.1.0-rc1
v6.1.0-rc2
$ git tag --contains 6d786f95a366600e7bbae68c1b324a8131f5e2c5
v6.1.0
v6.1.0-rc1
v6.1.0-rc2

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

MP at: https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/380942
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3986/+packages

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

FYI: I combined a few other ongoing issues into the same PPA&MP

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

The PPA build works, just need to ensure the other changes are fine as well before an upload to 20.04.

Changed in libvirt (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

FYI Regression test is fine on this build

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libvirt - 6.0.0-0ubuntu6

---------------
libvirt (6.0.0-0ubuntu6) focal; urgency=medium

  * d/p/ubuntu/lp-1867460-*: fix domcapabilities before capabilities
    and binary autodetection in general (LP: #1867460)
  * d/p/stable/lp-1868539-*: stabilize libvirt by backporting upstream
    fixes (LP: #1868539)
  * d/p/ubuntu/lp-1853200*: add cpu models without hle/rtm features to have
    modern types on kernels with recent security fixes (LP: #1853200)
  * d/p/ubuntu/lp-1868528-*: Fail when fetching CPU Status for invalid CPU
    (LP: #1868528)

 -- Christian Ehrhardt <email address hidden> Fri, 20 Mar 2020 10:34:19 +0100

Changed in libvirt (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.