Re: [Qemu-discuss] qemu-arm chroot memory size

[Peter Maydell]

On 11 November 2014 17:28, Dave Flogeras <address@hidden> wrote:
> I have a qemu-arm chroot, inside of which I am trying to build
> chromium (probably stupid).  At the linking phase, it falls over,
> running out of memory. I am just wondering what the memory limit
> inside of a 32bit arm chroot is (or is that a loaded question)?  The
> host is 64bit with 16GB ram.

On a 64 bit host we can allocate a contiguous 32 bit range
in the virtual address space for the guest's memory, which
means that it should not have any artificial limit on the
memory space. This is the default, but check that you're
not accidentally overriding it by providing a -R command
line option to QEMU or setting QEMU_RESERVED_VA.

[I'm assuming you're using a relatively recent QEMU.]

Don't set QEMU_PAGESIZE or QEMU_STACK_SIZE (the former in
particular is for telling QEMU the host page size, not
anything to do with the guest memory limits).

Note that it is not completely impossible that chromium is
simply too large to link in a 32 bit address space. You
could try using qemu's strace options (or host strace)
to see exactly what the guest is trying to mmap.

thanks
-- PMM