[Qemu-devel] [Bug 809912] [NEW] qemu-kvm -m bigger 4096 aborts with 'Bad ram offset'

[Qemu-devel] [Bug 809912] [NEW] qemu-kvm -m bigger 4096 aborts with 'Bad ram offset'

[Lutz Vieweg]

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 <avi@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 <avi@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

[Qemu-devel] [Bug 809912] Re: qemu-kvm -m bigger 4096 aborts with 'Bad ram offset'

[Craig S]

After updating from the QEMU that came with Ubuntu 11.04 to
070411-1ubuntu2 version, I am seeing the bad ram offset error, also.  If
I drop the memory for the guest (which is Windows 7 Pro 64-bit) from 4
GB to 3300MB, the error goes away.

Host machine has an AMD Opteron 6128 with 32GB RAM and is running the 64
bit version of Ubuntu 11.04 updated to current versions as of November

-- 
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 <avi@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

[Qemu-devel] [Bug 809912] Re: qemu-kvm -m bigger 4096 aborts with 'Bad ram offset'

[Thomas Huth]

Can you still reproduce this issue with the latest version of QEMU?

** Changed in: qemu
       Status: New => Incomplete

-- 
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:
  Incomplete

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 <avi@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

[Qemu-devel] [Bug 809912] Re: qemu-kvm -m bigger 4096 aborts with 'Bad ram offset'

[Launchpad Bug Tracker]

[Expired for QEMU because there has been no activity for 60 days.]

** Changed in: qemu
       Status: Incomplete => Expired

-- 
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:
  Expired

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 <avi@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