https://bugzilla.kernel.org/show_bug.cgi?id=217574 Sean Christopherson (seanjc@xxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seanjc@xxxxxxxxxx --- Comment #2 from Sean Christopherson (seanjc@xxxxxxxxxx) --- Ya, as Chao alluded to, the problem appears to be that not all CPUs have have the same VMX configuration, which is reflected in the MSRs Chao mentioned. My best guess is that going through a suspend+resume cycle either wipes out a problematic ucode update, or applies a "good" ucode update to all CPUs, and thus resolves the inconsistent VMX configuration across CPUs. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
