From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Bin Meng <bmeng.cn@gmail.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
David Hildenbrand <david@redhat.com>,
"Richard W.M. Jones" <rjones@redhat.com>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>,
Alistair Francis <Alistair.Francis@wdc.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: xilinx-zynq-a9: cannot set up guest memory 'zynq.ext_ram'
Date: Fri, 20 Aug 2021 16:09:56 +0200 [thread overview]
Message-ID: <869f8be9-b76f-e315-9591-9c452bedf922@redhat.com> (raw)
In-Reply-To: <CAEUhbmUhKFFxSspve+t2BeppCGPegpb_Z5g-w8M5t-JMLy3Zsg@mail.gmail.com>
Hi Bin,
On 8/20/21 4:04 PM, Bin Meng wrote:
> Hi,
>
> The following command used to work on QEMU 4.2.0, but is now broken
> with QEMU head.
>
> $ qemu-system-arm -M xilinx-zynq-a9 -display none -m 40000000
> -nographic -serial /dev/null -serial mon:stdio -monitor null -device
> loader,file=u-boot-dtb.bin,addr=0x4000000,cpu-num=0
> qemu-system-arm: cannot set up guest memory 'zynq.ext_ram': Cannot
> allocate memory
>
> Any ideas?
Richard hit that recently too.
Can you provide:
cat /proc/sys/vm/overcommit_kbytes
cat /proc/sys/vm/overcommit_memory
cat /proc/sys/vm/overcommit_ratio
and
cat /proc/meminfo
(CommitLimit, Committed_AS)
and OOM messages.
Per David, 'you can trick QEMU in trying to work around
that issue, specifying a memory-backend-ram with "reserve=off"
as guest RAM.'
next prev parent reply other threads:[~2021-08-20 14:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 14:04 xilinx-zynq-a9: cannot set up guest memory 'zynq.ext_ram' Bin Meng
2021-08-20 14:09 ` Philippe Mathieu-Daudé [this message]
2021-08-20 14:22 ` Bin Meng
2021-08-20 14:34 ` David Hildenbrand
2021-08-20 14:39 ` Peter Maydell
2021-08-20 15:31 ` Philippe Mathieu-Daudé
2021-08-20 15:44 ` Igor Mammedov
2021-08-20 15:47 ` David Hildenbrand
2021-08-20 15:53 ` Philippe Mathieu-Daudé
2021-08-20 16:08 ` Igor Mammedov
2021-08-20 16:13 ` Philippe Mathieu-Daudé
2021-08-20 16:03 ` Igor Mammedov
2021-08-20 16:06 ` Philippe Mathieu-Daudé
2021-08-20 16:36 ` Igor Mammedov
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=869f8be9-b76f-e315-9591-9c452bedf922@redhat.com \
--to=philmd@redhat.com \
--cc=Alistair.Francis@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=david@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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;
as well as URLs for NNTP newsgroup(s).