From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 43068] New: Operation restricted to levels L0-2 - kerneloops when booting L3
Date: Sat, 7 Apr 2012 17:36:23 GMT [thread overview]
Message-ID: <bug-43068-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=43068
Summary: Operation restricted to levels L0-2 - kerneloops when
booting L3
Product: Virtualization
Version: unspecified
Kernel Version: 3.2.0-2-amd64
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
ReportedBy: 2005@kuarepoti-dju.net
Regression: No
Created an attachment (id=72845)
--> (https://bugzilla.kernel.org/attachment.cgi?id=72845)
Kernel oops backtrace
Trying to run KVM with a high level of nesting works fine for the first two
levels of virtual machines (L1 and L2) but leads to the attached oops when
attempting to boot into L3.
The host system has 24 Xeon X5675 cores running Ubuntu 12.04 with kernel
3.2.0-21-generic. The nested VMs are restricted to one of these core. They all
run resized clones of a Debian wheezy (testing) image with kernel
3.2.0-2-amd64.
In the Turtles paper, nested virtualisation has been presented to support Ln
and includes L3 in the diagrams but the evaluation only went up to L2. The
kernel documentation nested-vmx.txt doesn't list this as a restriction but
doesn't mention L3 or higher either. Hence, it is not clear if the
implementation is supposed to support L3 at all, at the moment or in the
foreseeable future.
--
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:[~2012-04-07 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 17:36 bugzilla-daemon [this message]
2012-04-07 17:37 ` [Bug 43068] Operation restricted to levels L0-2 - kerneloops when booting L3 bugzilla-daemon
2012-04-08 8:18 ` bugzilla-daemon
2013-02-11 12:28 ` 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-43068-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