From: Aurelien Jarno <aurelien@aurel32.net>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH] Fix segfault with ram_size > 4095M without kvm
Date: Tue, 23 Feb 2010 18:02:15 +0100 [thread overview]
Message-ID: <4B840A17.9050809@aurel32.net> (raw)
In-Reply-To: <20100223151314.GN17350@us.ibm.com>
Ryan Harper a écrit :
> Currently, x86_64-softmmu qemu segfaults when trying to use > 4095M memsize.
> This patch adds a simple check and error message (much like the 2047 limit on
> 32-bit hosts) on ram_size in the control path after we determine we're
> not using kvm
>
> Upstream qemu-kvm is affected if using the -no-kvm option; this patch address
> the segfault there as well.
It looks like workarounding the real bug. At some point both
i386-softmmu (via PAE) and x86_64-softmmu were able to support > 4GB of
memory. I remember adding the support long time ago, and testing it with
32GB of emulated RAM.
> Signed-off-by: Ryan Harper <ryanh@us.ibm.com>
> ---
> vl.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/vl.c b/vl.c
> index db7a178..a659e98 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -5760,6 +5760,12 @@ int main(int argc, char **argv, char **envp)
> fprintf(stderr, "failed to initialize KVM\n");
> exit(1);
> }
> + } else {
> + /* without kvm enabled, we can only support 4095 MB RAM */
> + if (ram_size > (4095UL << 20)) {
> + fprintf(stderr, "qemu: without kvm support at most 4095 MB RAM can be simulated\n");
> + exit(1);
> + }
> }
>
> if (qemu_init_main_loop()) {
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2010-02-23 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 15:13 [PATCH] Fix segfault with ram_size > 4095M without kvm Ryan Harper
2010-02-23 17:02 ` Aurelien Jarno [this message]
2010-02-23 20:30 ` [Qemu-devel] " Alexander Graf
2010-02-23 21:07 ` Anthony Liguori
2010-02-23 21:24 ` Aurelien Jarno
2010-02-23 22:55 ` Ryan Harper
2010-03-04 21:27 ` Aurelien Jarno
2010-03-04 21:34 ` Ryan Harper
2010-03-06 21:31 ` Aurelien Jarno
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=4B840A17.9050809@aurel32.net \
--to=aurelien@aurel32.net \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.ibm.com \
/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