Description of problem: Version-Release number of selected component (if applicable): qemu-6.2.0-6.fc36.x86_64 How reproducible: Launching qemu based VMs with a SLIC table can fail. This has been fixed upstream (https://github.com/qemu/qemu/commit/8cdb99af45365727ac17f45239a9b8c1d5155c6d) and I'm simply requesting a backport into fc36 6.2.0 Steps to Reproduce: 1. FC35 system with a VM with a SLIC table from the physical HW (sadly, I very occasionally need to run Windows, but infrequently enough that a VM is preferable to dual booting). This has worked for the last ~10 Fedora versions. 2.Upgrade to Fedora 36 and qemu 6.2.0 3. Same VM image, config, and SLIC table now fail Actual results: VM fails to start with: Error starting domain: internal error: qemu unexpectedly closed the monitor: qxl_send_events: spice-server bug: guest stopped, ignoring ** ERROR:../hw/acpi/aml-build.c:61:build_append_padded_str: assertion failed: (len <= maxlen) Bail out! ERROR:../hw/acpi/aml-build.c:61:build_append_padded_str: assertion failed: (len <= maxlen) Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/object/domain.py", line 1384, in startup self._backend.create() File "/usr/lib64/python3.10/site-packages/libvirt.py", line 1353, in create raise libvirtError('virDomainCreate() failed') libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: qxl_send_events: spice-server bug: guest stopped, ignoring ** ERROR:../hw/acpi/aml-build.c:61:build_append_padded_str: assertion failed: (len <= maxlen) Bail out! ERROR:../hw/acpi/aml-build.c:61:build_append_padded_str: assertion failed: (len <= maxlen Expected results: VM launches successfully Additional info: Initial bug report upstream (not from me): https://gitlab.com/qemu-project/qemu/-/issues/786 Upstream thread: https://lore.kernel.org/qemu-devel/20211227193120.1084176-2-imammedo@redhat.com/ Upstream commit: https://github.com/qemu/qemu/commit/8cdb99af45365727ac17f45239a9b8c1d5155c6d Rebuilding qemu-6.2.0-6.fc36.x86_64 with that single patch resolves the issue.
F36 build: https://koji.fedoraproject.org/koji/taskinfo?taskID=85237776
FEDORA-2022-58f72fadb4 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-58f72fadb4
FEDORA-2022-58f72fadb4 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-1f08855c02 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1f08855c02
FEDORA-2022-1f08855c02 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-1f08855c02` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1f08855c02 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Thank you for the super quick fix! I just wanted to confirm that 2:6.2.0-8.fc36 is confirmed to work for me.
FEDORA-2022-1f08855c02 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.