© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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