On 10/28/14 12:34 AM, Manuel Bouyer wrote:
On Mon, Oct 27, 2014 at 04:39:01PM -0700, Jeff Rizzo wrote:On 10/27/14 4:10 PM, Jeff Rizzo wrote:Given that these are in use on Amazon EC2 instances, I'm going to work around the problem in a similar fashion for now.I just looked a little more closely at the existing workaround, and now I'm not sure what the right thing to do is - should I set x86_xsave_features to 0 for Xen in general?As it shows up on Intel CPUs too, I guess it's a reasonable woraround for now.
I can confirm that if I set x86_xsave_features to 0 for Xen, the problem AMIs boot on the problem CPUs. I will commit the change later today.