From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 64801] Nested Virtualisation with KVM on Intel and AMD processors: L2 unreachable
Date: Mon, 11 Nov 2013 20:47:08 +0000 [thread overview]
Message-ID: <bug-64801-28872-gXv867lDcD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-64801-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=64801
--- Comment #1 from josef <2005@kuarepoti-dju.net> ---
On the AMD Athlon II X2 240e machine, the results from above have now basically
been reproduced with the L0 test image. Again, it was able to boot into L2, but
not into L3. When attempting to do so, kvm outputs "vcpu0 unhandled rdmsr:
0xc0000103". Afterwards, it just hangs and can be interrupted.
Now there are four different machines with four different error symptomes.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2013-11-11 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 15:47 [Bug 64801] New: Nested Virtualisation with KVM on Intel and AMD processors: L2 unreachable bugzilla-daemon
2013-11-11 20:47 ` bugzilla-daemon [this message]
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-64801-28872-gXv867lDcD@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