All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Kashyap Chamarthy <kashyap.cv@gmail.com>,
	"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 20:09:22 +0200	[thread overview]
Message-ID: <518D37D2.4060805@siemens.com> (raw)
In-Reply-To: <CAL54oT0WKVcDizpMVTwSmNjJz=UMqprZ8rn6jF3-tAkA9jFZeg@mail.gmail.com>

On 2013-05-10 19:40, Nakajima, Jun wrote:
> On Fri, May 10, 2013 at 9:33 AM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> On 2013-05-10 17:39, Kashyap Chamarthy wrote:
>>> On Fri, May 10, 2013 at 8:54 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>>>>
>>>> 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:
>>>>>>
> 
> I tried to reproduce such a problem, and I found L2 (Linux) hangs in
> SeaBIOS, after line "iPXE (http://ipxe.org) ...". It happens with or
> w/o VMCS shadowing (and even without my virtual EPT patches). I didn't
> realize this problem until I updated the L1 kernel to the latest (e.g.
> 3.9.0) from 3.7.0. L0 uses the kvm.git, next branch. It's possible
> that the L1 kernel exposed a bug with the nested virtualization, as we
> saw such cases before.

Hmm, no such issues here ATM although I'm on 3.9 for L1 as well.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2013-05-10 18:09 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
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 [this message]
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=518D37D2.4060805@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=jun.nakajima@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.