From: Marc Zyngier <maz@kernel.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Kenneth Adam Miller <kennethadammiller@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-arm@nongnu.org
Subject: Re: Raspberry Pi?
Date: Wed, 26 Jan 2022 13:48:23 +0000 [thread overview]
Message-ID: <9864ab7ffce7f60d460051fa94f755c5@kernel.org> (raw)
In-Reply-To: <1e98b4ec-3476-387c-9dda-99a13121e22f@amsat.org>
On 2022-01-26 02:59, Philippe Mathieu-Daudé via wrote:
> Hi,
>
> On 26/1/22 00:59, Kenneth Adam Miller wrote:
>> Hello all,
>>
>> I would like to emulate something on a pi so that I don't have to
>> pay as high of a translation penalty since the guest and host will
>> share the same arch. I'm finding that on some forums that people have
>> been having trouble getting QEMU to run on raspberry pi. The posts are
>> kind of old, in 2019.
>>
>> Does anyone know if this has been addressed since then?
>
> What you asks is if you can run an Aarch64 guest (virt machine?) on a
> Raspi4 host, is that right? IIRC it should work straight away using
> "-machine virt,gic-version=host". Cc'ing qemu-arm@ list to verify.
Note that only a RPi-4 will provide any sort of performance, assuming
the OP wants to use KVM as the acceleration backend.
The original RPi has no support for virtualisation (ARM 1176), and
the two following models are deprived of a GIC, making them a bit
useless (we have *some* support code in KVM, but I'm pretty sure it
has bitrot by now).
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2022-01-26 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 23:59 Raspberry Pi? Kenneth Adam Miller
2022-01-26 2:59 ` Philippe Mathieu-Daudé via
2022-01-26 13:48 ` Marc Zyngier [this message]
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=9864ab7ffce7f60d460051fa94f755c5@kernel.org \
--to=maz@kernel.org \
--cc=f4bug@amsat.org \
--cc=kennethadammiller@gmail.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).