Public bug reported: When I try to start a virtual machine (x86_64 guest on a x86_64 host that has 32GB memory, using kvm_amd module, both host and guest running linux-2.6.39 kernels) with "qemu-system-x86_64 -cpu host -smp 2 -m 4096 ...", shortly after the guest kernel starts, qemu aborts with a message "Bad ram offset 11811c000".
With e.g. "-m 3500" (or lower), the virtual machine runs fine. I experience this both using qemu-kvm 0.14.1 and a recent version from git commit 525e3df73e40290e95743d4c8f8b64d8d9cbe021 Merge: d589310 75ef849 Author: Avi Kivity <a...@redhat.com> Date: Mon Jul 4 13:36:06 2011 +0300 ** Affects: qemu Importance: Undecided Status: New ** Tags: memory ram -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/809912 Title: qemu-kvm -m bigger 4096 aborts with 'Bad ram offset' Status in QEMU: New Bug description: When I try to start a virtual machine (x86_64 guest on a x86_64 host that has 32GB memory, using kvm_amd module, both host and guest running linux-2.6.39 kernels) with "qemu-system-x86_64 -cpu host -smp 2 -m 4096 ...", shortly after the guest kernel starts, qemu aborts with a message "Bad ram offset 11811c000". With e.g. "-m 3500" (or lower), the virtual machine runs fine. I experience this both using qemu-kvm 0.14.1 and a recent version from git commit 525e3df73e40290e95743d4c8f8b64d8d9cbe021 Merge: d589310 75ef849 Author: Avi Kivity <a...@redhat.com> Date: Mon Jul 4 13:36:06 2011 +0300 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/809912/+subscriptions