From: Launchpad Bug Tracker <809912@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 809912] Re: qemu-kvm -m bigger 4096 aborts with 'Bad ram offset'
Date: Wed, 04 Jan 2017 04:17:52 -0000 [thread overview]
Message-ID: <20170104041752.27545.39427.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20110713143335.13610.27004.malonedeb@chaenomeles.canonical.com
[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
prev parent reply other threads:[~2017-01-04 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 14:33 [Qemu-devel] [Bug 809912] [NEW] qemu-kvm -m bigger 4096 aborts with 'Bad ram offset' Lutz Vieweg
2011-11-04 12:51 ` [Qemu-devel] [Bug 809912] " Craig S
2016-11-04 15:58 ` Thomas Huth
2017-01-04 4:17 ` Launchpad Bug Tracker [this message]
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=20170104041752.27545.39427.malone@loganberry.canonical.com \
--to=809912@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.