From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:55400) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URe4V-0002QK-Gi for qemu-devel@nongnu.org; Mon, 15 Apr 2013 03:43:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1URe4R-00005h-QC for qemu-devel@nongnu.org; Mon, 15 Apr 2013 03:43:27 -0400 Received: from mout.web.de ([212.227.17.11]:60145) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URe4R-0008Vt-H5 for qemu-devel@nongnu.org; Mon, 15 Apr 2013 03:43:23 -0400 Message-ID: <516BAF96.1010402@web.de> Date: Mon, 15 Apr 2013 09:43:18 +0200 From: Jan Kiszka MIME-Version: 1.0 References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2LAVNPGRWXVIKLNIQHMKE" Subject: Re: [Qemu-devel] [qemu-devel] Bug Report: VM crashed for some kinds of vCPU in nested virtualization List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?B?IuadjuaYpeWlhyA8QXJ0aHVyIENodW5xaSBMaT4i?= Cc: qemu-devel@nongnu.org, kvm This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2LAVNPGRWXVIKLNIQHMKE Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2013-04-15 08:24, =E6=9D=8E=E6=98=A5=E5=A5=87 wrote= : > Hi all, > In a nested virtualization environment of qemu+KVM, some emulated CPU (= such > as core2duo) may cause L2 guest crash after booting for a while. Here's= my > configuration: >=20 > Host: > Linux 3.5.7 You should better use latest version from kvm.git [1], branch "next". Otherwise, you risk re-triggering bugs that were fixed in the meantime. > Qemu is the latest version from git repository. > Emulated CPU : core2duo >=20 > L1 guest: > Linux 3.5.7 > Qemu is the latest version from git > Emulated CPU : core2duo >=20 > L2 guest: > Crash at some specific point after running for sometime. >=20 >=20 > Here's the callback trace: >=20 > qemu-system-x86_64 -net nic,vlan=3D0,macaddr=3D00:26:b9:fa:fe:31 -net > tap,vlan=3D0 -vnc :1 -hda vm1.1.img -m 512 -machine pc,accel=3Dkvm -cpu= > core2duo -cdrom ubuntu-12.04.2-server-amd64.iso > TUNSETIFF: Device or resource busy > qemu-system-x86_64: pci_add_option_rom: failed to find romfile > "efi-e1000.rom" > KVM: entry failed, hardware error 0x7 ^^^ As an exercise, you could try to track down what this number means. Hint: there will be two possibilities (unfortunately). > RAX=3D000000000000000f RBX=3Dffff88001f60c740 RCX=3D000000000000038f > RDX=3D0000000000000007 > RSI=3D000000000000000f RDI=3D000000000000038f RBP=3Dffff88001e6ffaf0 > RSP=3Dffff88001e6ffaf0 > R8 =3D000000070000000f R9 =3D0000000000000000 R10=3D0000000000000000 > R11=3D0000000000000000 > R12=3D0000000000000001 R13=3D0000000000000001 R14=3D0000000000000000 > R15=3Dffff88001f617384 > RIP=3Dffffffff8103fe1a RFL=3D00000002 [-------] CPL=3D0 II=3D0 A20=3D1 = SMM=3D0 HLT=3D0 > ES =3D0000 0000000000000000 000fffff 00000000 > CS =3D0010 0000000000000000 ffffffff 00a09b00 DPL=3D0 CS64 [-RA] > SS =3D0018 0000000000000000 ffffffff 00c09300 DPL=3D0 DS [-WA] > DS =3D0000 0000000000000000 000fffff 00000000 > FS =3D0000 0000000000000000 000fffff 00000000 > GS =3D0000 ffff88001f600000 000fffff 00000000 > LDT=3D0000 0000000000000000 000fffff 00000000 > TR =3D0040 ffff88001f611580 00002087 00008b00 DPL=3D0 TSS64-busy > GDT=3D ffff88001f604000 0000007f > IDT=3D ffffffff81dd6000 00000fff > CR0=3D8005003b CR2=3D00000000ffffffff CR3=3D0000000001c0b000 CR4=3D0000= 07f0 > DR0=3D0000000000000000 DR1=3D0000000000000000 DR2=3D0000000000000000 > DR3=3D0000000000000000 > DR6=3D00000000ffff0ff0 DR7=3D0000000000000400 > EFER=3D0000000000000d01 > Code=3D20 89 f9 48 09 c8 5d c3 66 90 55 89 f0 89 f9 48 89 e5 0f 30 <31>= c0 5d > c3 66 90 55 89 f9 48 89 e5 0f 33 89 c7 48 89 d0 48 c1 e0 20 89 f9 48 09= c8 > 5d c3 >=20 >=20 > This bug also appears in Westmere, SandyBridge and Haswell. But Nehalem= , > Penryn and Conroe runs OK. >=20 > Is this problem really a bug or some mistakes in configuration? A bug, most probably. If you are able to reproduce using latest KVM, we would have to look into details. Jan PS: KVM related error reports of QEMU should also go to the KVM list. CC'ing it. [1] https://git.kernel.org/cgit/virt/kvm/kvm.git/ ------enig2LAVNPGRWXVIKLNIQHMKE 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/ iEYEARECAAYFAlFrr5YACgkQitSsb3rl5xQhAACgpazXADzhVkhRsDAlTl6Byotn zjMAoOBEkmmnKXJ7zHzQRZJJj5SH0tmY =wYs0 -----END PGP SIGNATURE----- ------enig2LAVNPGRWXVIKLNIQHMKE--