qemu 6.0 breaks libvirt <7.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
qemu (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
With qemu 6.0 you'll see issues with hotplug on attach-device (there are more cases than the examples show)
attach-device hotplug-rng.xml+ uvt-kvm ssh --insecure impish-kvm 'virsh -c qemu:///system attach-device impish-2nd-hotplug hotplug-rng.xml'
error: Failed to attach device from hotplug-rng.xml
error: internal error: unable to execute QEMU command 'object-add': Parameter 'props' is unexpected
attach-device hotplug-mem64.xml+ uvt-kvm ssh --insecure impish-kvm 'virsh -c qemu:///system attach-device impish-2nd-hotplug hotplug-mem64.xml'
error: Failed to attach device from hotplug-mem64.xml
error: internal error: unable to execute QEMU command 'object-add': Parameter 'size' is missing
This is due to qemu
https:/
It was reported and discussed in
https:/
It is intentional and will stay that way, so higher layers need to adapt.
https:/
https:/
https:/
That means >=7.2 is needed for qemu 6.0
Impish will eventually have that, but I think we need to add a Breaks to qemu d/control to ensure partial upgrades are not crashing unexpectedly.
Related branches
- Lucas Kanashiro (community): Approve
- Canonical Server packageset reviewers: Pending requested
- Canonical Server: Pending requested
-
Diff: 6801 lines (+6016/-43)19 files modifieddebian/changelog (+4449/-4)
debian/control (+96/-22)
debian/control-in (+67/-13)
debian/patches/build-most-modules-statically-hack.diff (+1/-1)
debian/patches/series (+6/-0)
debian/patches/ubuntu/define-ubuntu-machine-types.patch (+823/-0)
debian/patches/ubuntu/enable-svm-by-default.patch (+34/-0)
debian/patches/ubuntu/lp-1929926-target-s390x-Fix-translation-exception-on-illegal-in.patch (+101/-0)
debian/patches/ubuntu/pre-bionic-256k-ipxe-efi-roms.patch (+62/-0)
debian/qemu-block-extra.postinst (+59/-0)
debian/qemu-kvm-init (+89/-0)
debian/qemu-system-common.install (+1/-0)
debian/qemu-system-common.qemu-kvm.default (+8/-0)
debian/qemu-system-common.qemu-kvm.service (+16/-0)
debian/qemu-system-gui.install (+2/-0)
debian/qemu-system-x86.NEWS (+80/-0)
debian/qemu-system-x86.README.Debian (+47/-0)
debian/rules (+61/-3)
debian/run-qemu.mount (+14/-0)
CVE References
Changed in libvirt (Ubuntu): | |
status: | New → Triaged |
Changed in qemu (Ubuntu): | |
status: | New → Triaged |
tags: | added: libvirt-21.10 qemu-21.10 |
This bug was fixed in the package libvirt - 7.4.0-0ubuntu3
---------------
libvirt (7.4.0-0ubuntu3) impish; urgency=medium
* d/t/smoke-lxc: skip if cgroup v1&v2 are present (systemd 248
was not enough)
libvirt (7.4.0-0ubuntu2) impish; urgency=medium
* d/t/smoke-lxc: skip before systemd 248 due to a known bug (LP: #1934966)
libvirt (7.4.0-0ubuntu1) impish; urgency=medium
* Merge v7.4.0 from upstream, Fix-cross- building- of-dtrace- probes. patch let-image- label-setting- loop-over- backing- files.patch Revert- remote- Add-libvirtd- dependency- to-virt- gue.patch clients. install: completions no more are symlinked to vsh
among a lot of new features and fixes this closes a few of issues
reported against Ubuntu
- Toleration for qemu >=6.0 handling of props (LP: #1932264)
- Persistent vfio-ccw device assignments (LP: #1887929)
- Drop patches that are upstream in v7.4.0
- d/p/b/meson-
- d/p/b/apparmor-
- d/p/r/systemd-
- d/p/u/lp-1913266-*: add vsock options to be usable with s390x
- d/p/u/lp-1921754-*: EPYC-Rome-v2
- d/p/u/lp-1921880-*: EPYC-Milan
- d/libvirt-
- Revert "disable firewalld support (universe dependency)"
This does not add a runtime dependency and while firewalld isn't in
main that way users can install and use it from universe.
(LP: #1928113)
- d/libvirt0.symbols: bump symbol versions for 7.4.0
- d/rules: disable the now auto-built vstorage backend
- not-installed: split daemon man pages are no yet installed
-- Christian Ehrhardt <email address hidden> Thu, 08 Jul 2021 14:20:53 +0200