From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [nVMX with: v3.9-11789-ge0fd9af] Stack trace when L2 guest is rebooted. Date: Fri, 10 May 2013 20:09:22 +0200 Message-ID: <518D37D2.4060805@siemens.com> References: <518D0E54.7000004@siemens.com> <518D111A.2070604@siemens.com> <518D216C.90107@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Kashyap Chamarthy , "kvm@vger.kernel.org" To: "Nakajima, Jun" Return-path: Received: from david.siemens.de ([192.35.17.14]:20757 "EHLO david.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751271Ab3EJSJj (ORCPT ); Fri, 10 May 2013 14:09:39 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 2013-05-10 19:40, Nakajima, Jun wrote: > On Fri, May 10, 2013 at 9:33 AM, Jan Kiszka wrote: >> On 2013-05-10 17:39, Kashyap Chamarthy wrote: >>> On Fri, May 10, 2013 at 8:54 PM, Jan Kiszka 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