From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 60679] L2 can't boot up when creating L1 with '-cpu host' qemu option
Date: Tue, 13 Aug 2013 07:35:37 +0000 [thread overview]
Message-ID: <bug-60679-28872-z4b7IWytCM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60679-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60679
Jay Ren <yongjie.ren@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |CODE_FIX
--- Comment #1 from Jay Ren <yongjie.ren@intel.com> ---
the following commit fixed the bug:
commit 205befd9a5c701b56f569434045821f413f08f6d
Author: Gleb Natapov <gleb@redhat.com>
Date: Sun Aug 4 15:08:06 2013 +0300
KVM: nVMX: correctly set tr base on nested vmexit emulation
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
Reported-by: Yongjie Ren <yongjie.ren@intel.com>
Reviewed-by: Arthur Chunqi Li <yzt356@gmail.com>
Tested-by: Yongjie Ren <yongjie.ren@intel.com>
Signed-off-by: Gleb Natapov <gleb@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-08-13 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 6:33 [Bug 60679] New: L2 can't boot up when creating L1 with '-cpu host' qemu option bugzilla-daemon
2013-08-13 7:35 ` bugzilla-daemon [this message]
2013-08-13 7:35 ` [Bug 60679] " bugzilla-daemon
2013-08-13 7:36 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-60679-28872-z4b7IWytCM@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.