From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nk1yX-0008F7-Vg for qemu-devel@nongnu.org; Tue, 23 Feb 2010 16:07:26 -0500 Received: from [199.232.76.173] (port=40695 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nk1yX-0008Ev-Hw for qemu-devel@nongnu.org; Tue, 23 Feb 2010 16:07:25 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Nk1yV-0002Mf-SB for qemu-devel@nongnu.org; Tue, 23 Feb 2010 16:07:25 -0500 Received: from mail-vw0-f45.google.com ([209.85.212.45]:51084) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Nk1yV-0002MX-Kq for qemu-devel@nongnu.org; Tue, 23 Feb 2010 16:07:23 -0500 Received: by vws11 with SMTP id 11so575941vws.4 for ; Tue, 23 Feb 2010 13:07:23 -0800 (PST) Message-ID: <4B844388.9080705@codemonkey.ws> Date: Tue, 23 Feb 2010 15:07:20 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Fix segfault with ram_size > 4095M without kvm References: <20100223151314.GN17350@us.ibm.com> <4B840A17.9050809@aurel32.net> <8B153AFB-E0D5-406A-A360-389A8A9C9D69@suse.de> In-Reply-To: <8B153AFB-E0D5-406A-A360-389A8A9C9D69@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Ryan Harper , qemu-devel@nongnu.org, Aurelien Jarno , kvm@vger.kernel.org On 02/23/2010 02:30 PM, Alexander Graf wrote: > On 23.02.2010, at 18:02, Aurelien Jarno wrote: > > >> 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. >> > Sounds like a perfect candidate for -stable then. For HEAD I agree that finding the cause would be the way to go. > No, it's wrong. A good candidate for -stable would be something that fixes the SEGV :-) Regards, Anthony Liguori > Alex-- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >