Thanks for the test, that ensures it still is in 5.2 Unfortunately since a few days that isn't the very most recent version [1] as 6.0 release two weeks ago. I don't have a 6.0 version ready as Ubuntu package yet that I could ask you to try.
Usually for an upstream bug report (which IMHO is the right next step) you'd want to have confirmed that the last release is affected as well. So the question IMHO should now be - how do we get you a qemu 6.0 to try. And if confirmed there the next step would be getting in touch with upstream at https://gitlab.com/qemu-project/qemu/-/issues How comfortable (or not) would you feel building your own qemu for a test? It should be something like: $ git clone git://git.qemu.org/qemu.git $ sudo vim /etc/apt/sources.list # edit sources.list to have "# deb-src" lines no more commented out $ sudo apt update $ sudo apt build-dep qemu $ cd qemu $ mkdir build $ cd build # you should need almost nothing for your test, so the following (or similar) should give you a quick build $ ../configure --disable-werror --disable-user --disable-linux-user --disable-docs --disable-guest-agent --disable-sdl --disable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt --disable-bluez --disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi --disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir --disable-seccomp --disable-glusterfs --disable-tpm --disable-numa --disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs --disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma --disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock --disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user --disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs --disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat --disable-qed --disable-parallels --disable-sheepdog --disable-avx2 --disable-nettle --disable-gnutls --disable-capstone --enable-tools $ make $ sudo make install The above is untested writeup from memory (except the configure line, but that was for a different version) so expect some slight modifications to be needed. You can then replace the qemu in your system (back it up) at /usr/bin/qemu-system-x86_64 with that new built version for a try. I'm currently rather busy, so the delay until I can provide a 6.0 might be a bit. But if you are unable to build your own you can surely wait for that to be ready. Or - also an alternative - you can report it upstream despite not having tested in on 6.0 yet. They might ask for it then, but chances are that someone more familiar with acpi or bhyve immediately recognizes it and can help. If you happen to do so please leave me a link to the issue here so I'm able to track it. [1]: https://wiki.qemu.org/Planning/6.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876678 Title: Ubuntu 20.04 KVM / QEMU Failure with nested FreeBSD bhyve To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1876678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
