All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mikko.rapeli@linaro.org, poky@lists.yoctoproject.org
Subject: Re: [poky] [PATCH v2] genericarm64.conf: fix qemu testing with testimage.bbclass
Date: Wed, 11 Mar 2026 13:16:50 +0000	[thread overview]
Message-ID: <fdd873c3c1a95ce400b8733aad5c7ae2320f4df7.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260311125406.259842-1-mikko.rapeli@linaro.org>

On Wed, 2026-03-11 at 14:54 +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.
> 
> 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.
> 
> TEST_RUNQEMUPARAMS needs snapshot since default genericarm64 image
> is a compressed wic.zst and nographic to run qemu without connected
> display which is better on headless build machines.
> 
> With these set, default genericarm64 core-image-sato boots correctly
> with testimage.bbclass and all oeqa runtime tests pass on an x86_64
> build machine:
> 
> $ bitbake core-image-sato && bitbake -c testimage core-image-sato
> ...
> SUMMARY:
> core-image-sato () - Ran 75 tests in 229.248s
> core-image-sato - OK - All required tests passed (successes=24,
> skipped=51, failures=0, errors=0)
> NOTE: Tasks Summary: Attempted 1558 tasks of which 1556 didn't need to
> be rerun and all succeeded.
> 
> To boot qemu manually (add "slirp" if tap networking not setup):
> 
> $ runqemu nographic snapshot core-image-sato
> 
> Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> ---
>  meta-yocto-bsp/conf/machine/genericarm64.conf | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> v2: dropper slirp from TEST_RUNQEMUPARAMS
> 
> v1: https://lists.yoctoproject.org/g/poky/message/13854
> 
> diff --git a/meta-yocto-bsp/conf/machine/genericarm64.conf b/meta-yocto-bsp/conf/machine/genericarm64.conf
> index 2b1ce4bdd02b..d6839d16a515 100644
> --- a/meta-yocto-bsp/conf/machine/genericarm64.conf
> +++ b/meta-yocto-bsp/conf/machine/genericarm64.conf
> @@ -73,5 +73,9 @@ QB_TCPSERIAL_OPT ?= "-device virtio-serial-pci -chardev socket,id=virtcon,port=@
>  # Virtio networking
>  QB_TAP_OPT ?= "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=no"
>  
> +# default to nographic to work on headless build machines using testimage.bbclass, snapshot for wic.zst image type
> +TEST_RUNQEMUPARAMS ?= "nographic snapshot"
> +# basic qemu testimage.bbclass support
> +TESTIMAGEDEPENDS:append = " qemu-native:do_populate_sysroot qemu-helper-native:do_populate_sysroot qemu-helper-native:do_addto_recipe_sysroot"
>  # If we're running testimage then we're in a qemu, so ensure u-boot is build
>  TESTIMAGEDEPENDS:append = " u-boot:do_deploy"

I'll try again.

nographic does not make sense here, genericarm64 supports graphics as
far as I know. The limitations of the test environment should not be
hardcoded into the machine definition.

There are patches which I sent recently against master which fix that
issue in a better way and will mean this is not needed. I am therefore
not going to take that as it is confusing, incorrect and not actually
needed.

Cheers,

Richard






  reply	other threads:[~2026-03-11 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 12:54 [PATCH v2] genericarm64.conf: fix qemu testing with testimage.bbclass Mikko Rapeli
2026-03-11 13:16 ` Richard Purdie [this message]
2026-03-11 13:25   ` [poky] " Mikko Rapeli

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=fdd873c3c1a95ce400b8733aad5c7ae2320f4df7.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mikko.rapeli@linaro.org \
    --cc=poky@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.