https://bugzilla.kernel.org/show_bug.cgi?id=61971
--- Comment #11 from Paolo Bonzini <[email protected]> --- This is XSAVE -> non-XSAVE migration. Alexander Graf reported to me on IRC that the XSAVE patches we recently committed to kvm/next fixed this for him. xstate_bv is saved as 7 and this check fails on the destination: if (xstate_bv & ~XSTATE_FPSSE) return -EINVAL; I think it is because your CPU has xsave but not xsaveopt. However, those patches introduced regressions that have to be fixed. I'll look at those soon, but your bug should get fixed in 3.13. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
