From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Bernhard M. Wiedemann" Subject: nested VMX + unrelated qemu bug Date: Thu, 14 Jul 2011 17:22:52 +0200 Message-ID: <4E1F09CC.6030708@lsmod.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from delta2.zq1.de ([78.46.32.14]:48544 "EHLO delta.zq1.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754724Ab1GNPcB (ORCPT ); Thu, 14 Jul 2011 11:32:01 -0400 Received: from delta.zq1.de (localhost [127.0.0.1]) by delta.zq1.de (Postfix) with ESMTP id 6BD5D173465 for ; Thu, 14 Jul 2011 17:22:52 +0200 (CEST) Received: from [10.8.0.245] (suse1.zq1.de [10.8.0.245]) by delta.zq1.de (Postfix) with ESMTPS for ; Thu, 14 Jul 2011 17:22:52 +0200 (CEST) Sender: kvm-owner@vger.kernel.org List-ID: Hi, I tried nested VMX on Xeon E5630 and it worked really well with the Kernel from avi's git and 0.14.0 (with modprobe kvm-intel nested=1) but in the process I found that qemu built from git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git crashed when started with -m 3600 or more while booting into openSUSE-11.3 where 0.14.0 worked well (even with 5GB) ./x86_64-softmmu/qemu-system-x86_64 -drive file=opensuse-113-64.img,if=virtio,boot=on -m 3600 -serial stdio -vnc :9 Could not open option rom 'extboot.bin': No such file or directory doing fast boot Creating device nodes with udev Trying manual resume from /dev/vda1 Invoking userspace resume from /dev/vda1 resume: libgcrypt version: 1.4.4 Trying manual resume from /dev/vda1 Invoking in-kernel resume from /dev/vda1 Waiting for device /dev/vda2 to appear: ok fsck from util-linux-ng 2.17.2 [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/vda2 /dev/vda2: recovering journal /dev/vda2: clean, 62553/230608 files, 449938/922112 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/vda2 mount -o rw,acl,user_xattr -t ext4 /dev/vda2 /root Bad ram offset 1009cc000 Aborted Ciao Bernhard M. Wiedemann