Yes, I have just retraced and found the bug. This is my negligence. Reviewed-by: Arthur Chunqi Li <yzt...@gmail.com>
On Sun, Aug 4, 2013 at 8:08 PM, Gleb Natapov <g...@redhat.com> wrote: > After commit 21feb4eb64e21f8dc91136b91ee886b978ce6421 tr base is zeroed > during vmexit. Set it to L1's HOST_TR_BASE. This should fix > https://bugzilla.kernel.org/show_bug.cgi?id=60679 > > Signed-off-by: Gleb Natapov <g...@redhat.com> > diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c > index b533cf8..7d31e7b 100644 > --- a/arch/x86/kvm/vmx.c > +++ b/arch/x86/kvm/vmx.c > @@ -8261,7 +8261,7 @@ static void load_vmcs12_host_state(struct kvm_vcpu > *vcpu, > seg.base = vmcs12->host_gs_base; > vmx_set_segment(vcpu, &seg, VCPU_SREG_GS); > seg = (struct kvm_segment) { > - .base = 0, > + .base = vmcs12->host_tr_base, > .limit = 0x67, > .selector = vmcs12->host_tr_selector, > .type = 11, > -- > Gleb. -- Arthur Chunqi Li Department of Computer Science School of EECS Peking University Beijing, China -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
