From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com
Subject: Re: [PATCH 0/4] Fix qemu riscv64 and arm64 ubuntu resolute targets
Date: Thu, 29 Oct 2026 15:20:36 +0100 [thread overview]
Message-ID: <8726a47b-5782-4b9d-b606-bc6601fca671@ilbers.de> (raw)
In-Reply-To: <20261015211527.3143702-1-felix.moessbauer@siemens.com>
p1-3 were applied to next, thanks.
Zhihang
On 10/15/26 23:15, 'Felix Moessbauer' via isar-users wrote:
> Ubuntu created a mess... The linux-image-generic package ships a PE
> (efi) kernel, which breaks the non-efi setups. As a replacement, the
> linux-image-fb-generic is provided which provides the non-wrapped
> kernel binaries. However, this package is not installable as it has
> broken dependencies (it depends on linux-image-generic, both provide
> the vmlinuz and by that violate the no duplicates rule). Among that,
> the riscv64 variant is now built for the rva23s64 machine (having
> vector extensions) instead of the rv64 machine.
>
> Given that, we directly switch these targets over to EFI and change
> the QEMU cmdlines accordingly. As we now need EFI firmware in QEMU,
> we also add the necessary packages to the test container.
>
> All in all, the non amd64 resolute targets have ever been broken
> and time-outed on CI. We now make them work properly, which also
> reduces the CI time of the -t fast by around 1000 seconds as we no
> longer need to wait for the timeouts.
>
> Best regards,
> Felix Moessbauer
>
> Felix Moessbauer (4):
> sdimage-efi: use uuid for boot partition to support virtio disks
> qemuarm64: add support for ubuntu resolute
> qemuriscv64: add support for ubuntu resolute
> testsuite: re-enable riscv64 and arm64 ubuntu resolute tests
>
> meta-isar/conf/machine/qemuarm64.conf | 7 +++++++
> meta-isar/conf/machine/qemuriscv64.conf | 12 +++++++++--
> .../lib/wic/canned-wks/sdimage-efi-sd.wks | 2 +-
> .../lib/wic/canned-wks/sdimage-efi.wks | 2 +-
> testsuite/citest.py | 21 ++++---------------
> testsuite/dockerdata/Dockerfile | 4 +++-
> testsuite/dockerdata/version | 2 +-
> 7 files changed, 27 insertions(+), 23 deletions(-)
>
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/8726a47b-5782-4b9d-b606-bc6601fca671%40ilbers.de.
prev parent reply other threads:[~2026-10-29 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 21:15 'Felix Moessbauer' via isar-users
2026-10-15 21:15 ` [PATCH 1/4] sdimage-efi: use uuid for boot partition to support virtio disks 'Felix Moessbauer' via isar-users
2026-10-15 21:15 ` [PATCH 2/4] qemuarm64: add support for ubuntu resolute 'Felix Moessbauer' via isar-users
2026-10-15 21:15 ` [PATCH 3/4] qemuriscv64: " 'Felix Moessbauer' via isar-users
2026-10-15 21:15 ` [PATCH 4/4] testsuite: re-enable riscv64 and arm64 ubuntu resolute tests 'Felix Moessbauer' via isar-users
2026-10-26 16:49 ` Zhihang Wei
2026-10-27 8:59 ` 'Moessbauer, Felix' via isar-users
2026-10-29 14:20 ` Zhihang Wei [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=8726a47b-5782-4b9d-b606-bc6601fca671@ilbers.de \
--to=wzh@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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