You don't need "+xsave", "-cpu host" just works.
The bug is invalid. You are requesting a CPU that doesn't exist (a
core2duo that supports XSAVE), and the guest's behavior is probably not
going to be well defined.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1285708
Title:
FreeBSD Guest crash on boot due to xsave instruction issue
Status in QEMU:
Invalid
Status in qemu-kvm:
New
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Precise:
Won't Fix
Status in “linux” source package in Trusty:
In Progress
Bug description:
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 -balloon virtio -cpu
core2duo,+xsave
The FreeBSD Guest will kernel crash on boot with the following error:
panic: CPU0 does not support X87 or SSE: 0
When launching the guest without the cpu flags, it works just fine.
This bug has been resolved in source:
https://lkml.org/lkml/2014/2/22/58
Can this fix be included in Precise ASAP!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1285708/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
