From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59975) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VPGuH-0004IZ-FL for qemu-devel@nongnu.org; Thu, 26 Sep 2013 15:07:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VPGu6-0007fO-Of for qemu-devel@nongnu.org; Thu, 26 Sep 2013 15:07:21 -0400 Received: from mout.web.de ([212.227.17.12]:53008) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VPGu6-0007et-CN for qemu-devel@nongnu.org; Thu, 26 Sep 2013 15:07:10 -0400 Received: from mchn199C.mchp.siemens.de ([95.157.58.223]) by smtp.web.de (mrweb003) with ESMTPSA (Nemesis) id 0MI5yY-1VQvav1Vde-003tsd for ; Thu, 26 Sep 2013 21:07:07 +0200 Message-ID: <524485D6.2050205@web.de> Date: Thu, 26 Sep 2013 21:07:02 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <5243CF52.6020400@web.de> <52446E5C.6040707@web.de> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TmwjcQpB6n9QHJtBAsuVe4CdOCN42CAhB" Subject: Re: [Qemu-devel] Fwd: Guest VM debug (Int 3 panic) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Hu Yaohui Cc: qemu-devel@nongnu.org, kvm This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --TmwjcQpB6n9QHJtBAsuVe4CdOCN42CAhB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2013-09-26 20:53, Hu Yaohui wrote: > Hi Jan, > I am working on some Nested VM related projects. Some other teammates h= ave > made the modifications to the kvm module.=20 And these modifications cannot cause the misguided INT3? > Most of my work depends on his. > If I could not use Qemu Debug method. Could you please suggest some oth= er > debugging methods to debug the L2 guest OS(printk, hijack kernel functi= on, > or something else)? Remove L0 while debugging L2 and, once it works, move L1/L2 back over L0? Your setup seems to be pretty special with (for us) unknown requirements, so it's hard to suggest what to do best. In any case, you seem to be pretty much "off-track" and may either have to stabilize the whole stack on your own, possibly back-porting essential nVMX fixes from latest versions, or rebase & share your changes so that we can help again. Jan --TmwjcQpB6n9QHJtBAsuVe4CdOCN42CAhB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJEhdoACgkQitSsb3rl5xQqTACfRn1tiWrgK1iYfRtIT4C/IeU0 EgIAnA8kaH/AIvXjkbIMVcv3xKV4E8jp =1dt6 -----END PGP SIGNATURE----- --TmwjcQpB6n9QHJtBAsuVe4CdOCN42CAhB--