Re: [poky] [PATCH] genericarm64.conf: fix qemu testing with testimage.bbclass

Richard Purdie <[email protected]> Wed, 11 Mar 2026 11:53:25 +0000
Newsgroups org.yoctoproject.lists.poky
Message-ID <f3f3d82f4f70370b4904d65467748210e5cd1c84.camel@linuxfoundation.org>
On Wed, 2026-03-11 at 13:36 +0200, Mikko Rapeli via lists.yoctoproject.org =
wrote:
> genericarm64 machine has supported qemu for a long time but
> the default build config failed with testimage.bbclass to boot
> and run oeqa runtime tests.

The key question is whether genericarm64 is meant for real hardware or
qemu.

When you run testimage against an image, the assumption has been it
would be a real hardware setup, not a qemu one. If you wanted qemu,
you'd have used qemuarm64.

These changes are basically turning genericarm64 into qemuarm64 :/.

> TESTIMAGEDEPENDS needs qemu utilities so that they are correctly
> installed to image sysroot. For qemu machines these are set in
> testimage.bbclass but remain unset for non-qemu machines like
> genericarm64.

This is going to be annoying if you're trying to test real hardware
with testimage. I can see the arguments both ways. This is one of the
differences between the two machines though and I'm not sure it makes
sense to make them match.

> TEST_RUNQEMUPARAMS needs snapshot since default genericarm64 image
> is a compressed wic.zst, nographic to run qemu without connected
> display which is better on headless build machines, and slirp which
> also works on much broader set of build machines than the default
> tap networking.

You shouldn't need to use nographic with the changes I'm proposing to
how runqemu is working, even on a headless system.

slirp, is a preference thing and I'd like to stay consistent between
the qemu setups. It is not the default.

snapshot is probably the one setting I think we should have as default
for the reason you mention.


Cheers,

Richard