From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 72381] [Nested] L1 call trace when create windows 7 guest as L2 guest.
Date: Mon, 24 Mar 2014 17:38:41 +0000 [thread overview]
Message-ID: <bug-72381-28872-VO2AqLXihX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-72381-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=72381
Paolo Bonzini <bonzini@gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bonzini@gnu.org
--- Comment #1 from Paolo Bonzini <bonzini@gnu.org> ---
What guest kernel is this? Can you try pairing 3.13.6 with 94b3ffcd (first
3.13.6 in the host, then 3.13.6 in the guest)?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-03-24 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 7:43 [Bug 72381] New: [Nested] L1 call trace when create windows 7 guest as L2 guest bugzilla-daemon
2014-03-24 17:38 ` bugzilla-daemon [this message]
2014-03-26 8:38 ` [Bug 72381] " bugzilla-daemon
2014-08-08 5:35 ` bugzilla-daemon
2014-08-08 5:36 ` bugzilla-daemon
2014-08-08 5:38 ` bugzilla-daemon
2014-08-08 5:38 ` 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-72381-28872-VO2AqLXihX@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