-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-9.4
-
None
-
libvirt-10.5.0-5.el9
-
Yes
-
Important
-
Regression
-
rhel-sst-virtualization
-
ssg_virtualization
-
24
-
26
-
5
-
Dev ack
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
Pass
-
Not Needed
-
Manual
-
-
s390x
-
None
What were you trying to do that didn't work?
Migrate a VM with ignored feature <acpi/> from a RHEL 9.0 or a RHEL 9.2 host to a RHEL 9.4 host.
Please provide the package NVR for which bug is seen:
Source 1
qemu-kvm-6.2.0-11.el9_0.9.s390x
libvirt-8.0.0-8.6.el9_0.s390x
Source 2
qemu-kvm-7.2.0-14.el9_2.s390x
libvirt-9.0.0-10.el9_2.s390x
Destination
Warning: Permanently added '10.0.160.36' (ED25519) to the list of known hosts.
qemu-kvm-8.2.0-11.el9_4.5.s390x
libvirt-10.0.0-6.6.el9_4.s390x
How reproducible:
100%
Steps to reproduce
- Define and start a VM with
<features><acpi/></features>
- Migrate the VM to a RHEL 9.4 host
Expected results
The migration succeeds.
Actual results
The migration fails.
error: unsupported configuration: machine type 's390-ccw-virtio-rhel9.0.0' does not support ACPI
Additional information
This was called out by bfiuczyn.
The problem is that on the Source host the incorrect configuration is just ignored but it's not ignored on the destination host. Libvirt allows to modify the XML during migration by passing
--xml
. However, this specific example doesn't allow this because the ABI stability check would fail.
I'm not sure if there could be a workaround so setting Major at this point even if it's based on a wrong configuration. People new to s390x might inadvertently add unsupported elements to the domain xml that are ignored leading to this scenario.
- links to
-
RHSA-2024:130953 libvirt bug fix and enhancement update