Quite right - our workaround was to switch to using the host
capabilities instead of the compatibility fallback. However, the
decision for a compatibility fallback was automatically made and
included the above combination. I don't know where that bug should sit.
--
You received this bug
** Also affects: qemu-kvm
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1285708
Public bug reported:
When trying to boot a working FreeBSD 9.1/9.2 guest on a kvm/qemu host
with the following command:
kvm -m 256 -cdrom FreeBSD-9.2-RELEASE-amd64-disc1.iso -drive
file=FreeBSD-9.2-RELEASE-amd64.qcow2,if=virtio -net nic,model=virtio
-net user -nographic -vnc :10 -enable-kvm
