From: Jan Kiszka <jan.kiszka@siemens.com>
To: Kashyap Chamarthy <kashyap.cv@gmail.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted.
Date: Fri, 10 May 2013 17:24:10 +0200 [thread overview]
Message-ID: <518D111A.2070604@siemens.com> (raw)
In-Reply-To: <518D0E54.7000004@siemens.com>
On 2013-05-10 17:12, Jan Kiszka wrote:
> On 2013-05-10 15:00, Kashyap Chamarthy wrote:
>> Heya,
>>
>> This is on Intel Haswell.
>>
>> First, some version info:
>>
>> L0, L1 -- both of them have same versions of kernel, qemu:
>>
>> =====
>> $ rpm -q kernel --changelog | head -2
>> * Thu May 09 2013 Josh Boyer - 3.10.0-0.rc0.git23.1
>> - Linux v3.9-11789-ge0fd9af
>
> Please recheck with kvm.git, next branch.
Hmm, looks like your branch already contains the patch I was thinking of
(03b28f8).
You could try if leaving shadow VMCS off makes a difference, but I bet
that is unrelated. You get that backtrace in L1, correct? I'll have to
see if I can reproduce it.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-05-10 15:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 13:00 [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted Kashyap Chamarthy
[not found] ` <CAOaxAcZ1uyx-RrmDEiZhG2H8H5zTCK9iz1nHJKEJwUfhn=vZHA@mail.gmail.com>
2013-05-10 14:41 ` Kashyap Chamarthy
2013-05-10 15:12 ` Jan Kiszka
2013-05-10 15:24 ` Jan Kiszka [this message]
2013-05-10 15:39 ` Kashyap Chamarthy
2013-05-10 15:46 ` Kashyap Chamarthy
2013-05-10 16:33 ` Jan Kiszka
2013-05-10 17:40 ` Nakajima, Jun
2013-05-10 18:09 ` Jan Kiszka
2013-05-10 21:37 ` Kashyap Chamarthy
2013-05-11 6:55 ` Kashyap Chamarthy
2013-05-12 8:32 ` Gleb Natapov
2013-05-12 12:30 ` Kashyap Chamarthy
2013-05-12 12:38 ` Gleb Natapov
2013-05-12 12:42 ` Kashyap Chamarthy
2013-05-12 12:59 ` Abel Gordon
2013-05-12 13:06 ` Kashyap Chamarthy
2013-05-12 13:31 ` Kashyap Chamarthy
2013-05-12 13:33 ` Kashyap Chamarthy
2013-05-12 15:52 ` Gleb Natapov
2013-05-12 16:52 ` Kashyap Chamarthy
2013-05-13 6:31 ` Jan Kiszka
2013-05-13 6:39 ` Gleb Natapov
2013-05-13 6:45 ` Ren, Yongjie
2013-05-13 6:57 ` Jan Kiszka
2013-05-13 7:06 ` Gleb Natapov
2013-05-12 13:48 ` Abel Gordon
2013-05-12 15:35 ` Gleb Natapov
2013-05-12 16:29 ` Kashyap Chamarthy
2013-05-10 21:37 ` Kashyap Chamarthy
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=518D111A.2070604@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kashyap.cv@gmail.com \
--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