From: "Bernhard M. Wiedemann" <bernhardout@lsmod.de>
To: kvm@vger.kernel.org
Subject: nested VMX + unrelated qemu bug
Date: Thu, 14 Jul 2011 17:22:52 +0200 [thread overview]
Message-ID: <4E1F09CC.6030708@lsmod.de> (raw)
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
next reply other threads:[~2011-07-14 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 15:22 Bernhard M. Wiedemann [this message]
2011-07-16 7:53 ` nested VMX + unrelated qemu bug Alexander Graf
2011-07-16 16:26 ` Blue Swirl
2011-07-18 7:23 ` Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E1F09CC.6030708@lsmod.de \
--to=bernhardout@lsmod.de \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox