** Changed in: linux (Ubuntu Precise)
Status: New = Won't Fix
--
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
Title:
FreeBSD Guest crash on boot due to xsave instruction issue
Status
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
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
Testing with the identified patch doesn't solve the issue, in addition
looking at the cpu flags (core2duo +xsave) this may not be a valid
configuration since xsave assumes additional features will be there
(instead of creating an older cpu model with xsave.) Therefore I believe
this is a
I should have refreshed my browser before commenting. : ) Thanks Jesse
and Paolo.
--
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
Title:
FreeBSD Guest crash on boot due to xsave instruction
As a workaround use the 'host' cpu type so the proper bits are enabled:
-cpu host,+xsave
--
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
Title:
FreeBSD Guest crash on boot due to xsave
$ git tag --contains 56c103ec040b1944c8866f79aa768265c0dd2986
v3.15-rc1
The patch in question is already in 3.16 / Utopic.
I can reproduce this easily in Trusty.
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status:
Thanks for reporting this bug. Given the lkml.org fix, I assume this is
in fact a kernel bug, so assigning it as such.
This is presumably fix-released in utopic, but SRU-able to precise and
trusty's backport kernels. I'm not clearn on how that process works, so
leaving it like this.
** Also
** 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
