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 17:24:10 +0200 Message-ID: <518D111A.2070604@siemens.com> References: <518D0E54.7000004@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: Kashyap Chamarthy Return-path: Received: from thoth.sbs.de ([192.35.17.2]:28547 "EHLO thoth.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753487Ab3EJPYN (ORCPT ); Fri, 10 May 2013 11:24:13 -0400 In-Reply-To: <518D0E54.7000004@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: 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