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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
