All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: ryanh@linux.vnet.ibm.com,
	Anthony Liguori <aliguori@linux.vnet.ibm.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	amit.shah@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Fix segfault with ram_size > 4095M without kvm
Date: Sat, 25 Dec 2010 23:35:52 +0100	[thread overview]
Message-ID: <20101225223552.GA9076@volta.aurel32.net> (raw)
In-Reply-To: <20101208162745.60d085db@doriath>

On Wed, Dec 08, 2010 at 04:27:45PM -0200, Luiz Capitulino wrote:
> On Wed, 08 Dec 2010 12:23:12 -0600
> Anthony Liguori <aliguori@linux.vnet.ibm.com> wrote:
> 
> > On 12/08/2010 12:01 PM, Luiz Capitulino wrote:
> > > 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.
> > >
> > > Signed-off-by: Ryan Harper<ryanh@us.ibm.com>
> > > Signed-off-by: Aurelien Jarno<aurelien@aurel32.net>
> > > ---
> > > NOTE: this patch was applied in the v0.12.x branch, but it seems it got
> > >        lost for master
> > >    
> > 
> > No, it was intentional.  We should fix the segv, this is not a known 
> > limitation but rather a bug.
> 
> A TCG bug, I presume?
> 

Do you have more details about this issue and how to reproduce it? 

Support for more than 4GB of memory has been added a few years ago, 
and I am not able to reproduce the problem anymore (I have booted a 
64-bit guest with 6GB of RAM, and make sure the guest use the whole 
memory). I guess TCG itself is fine, but there might be a bug in
the MMU emulation in some cases.

I also noticed that now i386-softmmu has been artificially limited to
2047MB. Tthis configuration used to support up to 64GB of RAM (PAE)
on 64-bit hosts.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel33.net

  parent reply	other threads:[~2010-12-25 22:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 18:01 [Qemu-devel] [PATCH] Fix segfault with ram_size > 4095M without kvm Luiz Capitulino
2010-12-08 18:23 ` [Qemu-devel] " Anthony Liguori
2010-12-08 18:27   ` Luiz Capitulino
2010-12-08 18:30     ` Anthony Liguori
2010-12-25 22:35     ` Aurelien Jarno [this message]
2011-01-04 15:49       ` Ryan Harper
2011-01-05 19:04         ` Ryan Harper
2011-01-06 14:48           ` 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=20101225223552.GA9076@volta.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=amit.shah@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ryanh@linux.vnet.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 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.