From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 67061] [BISECTED][Nested]L2 guest boot up fail(kvm on kvm).
Date: Mon, 10 Mar 2014 19:51:38 +0000 [thread overview]
Message-ID: <bug-67061-28872-SQUXggVKU4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-67061-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=67061
Thilo Fromm <kontakt@thilo-fromm.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kontakt@thilo-fromm.de
--- Comment #3 from Thilo Fromm <kontakt@thilo-fromm.de> ---
This bug may have been fixed in 3.13.6.
I was affected by this bug, too - I use nested virtualization a lot, mainly for
system testing purposes. I was able to reproduce the issue on all 3.13 kernels
so far; my hardware is a Intel Core i7-2640M.
Kernel release 3.13.6 fixed the issue for me. Looking at the changelog at
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.13.6, I guess the fix
was in commit 92cb6f3c5533832aa70a7dc9326ef21270169583 " kvm, vmx: Really fix
lazy FPU on nested guest".
The issue is discussed on the kvm-devel mailing list:
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/119328 leading to the
fix: http://permalink.gmane.org/gmane.linux.kernel.stable/82043.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-03-10 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 2:56 [Bug 67061] New: [Nested]L2 guest boot up fail(kvm on kvm) bugzilla-daemon
2013-12-16 2:57 ` [Bug 67061] " bugzilla-daemon
2013-12-18 14:25 ` [Bug 67061] [BISECTED][Nested]L2 " bugzilla-daemon
2014-03-10 19:51 ` bugzilla-daemon [this message]
2014-03-11 7:47 ` 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-67061-28872-SQUXggVKU4@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