From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 53641] New: nVMX: Windows as L2 guest doesn't work
Date: Mon, 11 Feb 2013 14:47:48 +0000 (UTC) [thread overview]
Message-ID: <bug-53641-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=53641
Summary: nVMX: Windows as L2 guest doesn't work
Product: Virtualization
Version: unspecified
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
ReportedBy: nyh@math.technion.ac.il
Regression: No
While Linux works fine as nested guests (L2), Windows of various versions do
not - which is of course a serious downside of KVM's nested VMX.
I verified this myself - seeing Windows 2000 hang on boot. It was also reported
by others and is not specific to Windows 2000, e.g. the following reports by
Gianluca Cecchi:
http://lists.fedoraproject.org/pipermail/virt/2011-June/002702.html
http://lists.fedoraproject.org/pipermail/virt/2011-November/002959.html
http://comments.gmane.org/gmane.comp.emulators.kvm.devel/82131
At some point during our research prototype, Windows L2 guests *did* work
(including Windows 2000), so it's probably not a big problem, but rather some
sneaky bug.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2013-02-11 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 14:47 bugzilla-daemon [this message]
2013-02-11 14:48 ` [Bug 53641] nVMX: Windows as L2 guest doesn't work bugzilla-daemon
2013-08-30 23:11 ` bugzilla-daemon
2015-03-17 3:53 ` 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-53641-28872@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox