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 configuration issue.
The comment above in #4 assumes your host has the correct cpu features, you can
always run something like:
kvm -cpu host,+xsave,check to check if are issues with the host plus
additional features settings. In addition I've been able to use '-cpu
SandyBridge,+xsave' and this also works.
Marking this 'Won't Fix' as there is a clear workaround (use another CPU
model), and this configuration may not be valid.
Thanks
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu)
Status: Fix Released => Invalid
** Changed in: linux (Ubuntu Precise)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu Trusty)
Importance: Medium => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1285708
Title:
FreeBSD Guest crash on boot due to xsave instruction issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1285708/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
