From: Avi Kivity Upon entry to protected mode, we set cr4 to a value derived from cr0 accidentally. Fix. This could cause a guest to crash (though I never observed it). Signed-off-by: Avi Kivity Signed-off-by: Andrew Morton --- drivers/kvm/kvm_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/kvm/kvm_main.c~kvm-virtualization-infrastructure-kvm-fix-guest-cr4-corruption drivers/kvm/kvm_main.c --- a/drivers/kvm/kvm_main.c~kvm-virtualization-infrastructure-kvm-fix-guest-cr4-corruption +++ a/drivers/kvm/kvm_main.c @@ -698,7 +698,7 @@ static void enter_pmode(struct kvm_vcpu vmcs_writel(GUEST_RFLAGS, flags); vmcs_writel(GUEST_CR4, (vmcs_readl(GUEST_CR4) & ~CR4_VME_MASK) | - (vmcs_readl(CR0_READ_SHADOW) & CR4_VME_MASK) ); + (vmcs_readl(CR4_READ_SHADOW) & CR4_VME_MASK)); update_exception_bitmap(vcpu); _