[PATCH 0/4] Fix qemu riscv64 and arm64 ubuntu resolute targets

[PATCH 0/4] Fix qemu riscv64 and arm64 ubuntu resolute targets

['Felix Moessbauer' via isar-users]

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(-)

-- 
2.55.0

-- 
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/20261015211527.3143702-1-felix.moessbauer%40siemens.com.

[PATCH 1/4] sdimage-efi: use uuid for boot partition to support virtio disks

['Felix Moessbauer' via isar-users]

When providing the image via virtio, the disk identifiers are vda
instead of sda. To support this case (needed for qemu testing), we also
assing a uuid to this partition.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta-isar/scripts/lib/wic/canned-wks/sdimage-efi-sd.wks | 2 +-
 meta-isar/scripts/lib/wic/canned-wks/sdimage-efi.wks    | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta-isar/scripts/lib/wic/canned-wks/sdimage-efi-sd.wks b/meta-isar/scripts/lib/wic/canned-wks/sdimage-efi-sd.wks
index 7fe2953f..de542f44 100644
--- a/meta-isar/scripts/lib/wic/canned-wks/sdimage-efi-sd.wks
+++ b/meta-isar/scripts/lib/wic/canned-wks/sdimage-efi-sd.wks
@@ -2,7 +2,7 @@
 # long-description: Creates a partitioned EFI disk image without any swap that
 # the user can directly dd to boot media.
 
-part /boot --source bootimg-efi-isar --sourceparams "loader=systemd-boot" --ondisk sda --label efi --part-type EF00 --align 1024
+part /boot --source bootimg-efi-isar --sourceparams "loader=systemd-boot" --ondisk sda --label efi --part-type EF00 --align 1024 --use-uuid
 
 part / --source rootfs --ondisk sda --fstype ext4 --mkfs-extraopts "-T default" --label platform --align 1024 --use-uuid --exclude-path boot/
 
diff --git a/meta-isar/scripts/lib/wic/canned-wks/sdimage-efi.wks b/meta-isar/scripts/lib/wic/canned-wks/sdimage-efi.wks
index 80c3a535..14bf10b1 100644
--- a/meta-isar/scripts/lib/wic/canned-wks/sdimage-efi.wks
+++ b/meta-isar/scripts/lib/wic/canned-wks/sdimage-efi.wks
@@ -2,7 +2,7 @@
 # long-description: Creates a partitioned EFI disk image without any swap that
 # the user can directly dd to boot media.
 
-part /boot --source bootimg-efi-isar --sourceparams "loader=grub-efi" --ondisk sda --label efi --part-type EF00 --align 1024
+part /boot --source bootimg-efi-isar --sourceparams "loader=grub-efi" --ondisk sda --label efi --part-type EF00 --align 1024 --use-uuid
 
 part / --source rootfs --ondisk sda --fstype ext4 --mkfs-extraopts "-T default" --label platform --align 1024 --use-uuid --exclude-path boot/
 
-- 
2.55.0

-- 
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/20261015211527.3143702-2-felix.moessbauer%40siemens.com.

[PATCH 2/4] qemuarm64: add support for ubuntu resolute

['Felix Moessbauer' via isar-users]

The ubuntu resolute target has an efi-only kernel. By that, the existing
qemuarm64 target that does direct kernel boot cannot boot the image,
leading to the long-standing CI error.

We fix this by providing creating an efi image and provide a
corresponding efiboot cmdline for QEMU for this target on
resolute.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta-isar/conf/machine/qemuarm64.conf | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/meta-isar/conf/machine/qemuarm64.conf b/meta-isar/conf/machine/qemuarm64.conf
index 4b76e5c1..5ade722d 100644
--- a/meta-isar/conf/machine/qemuarm64.conf
+++ b/meta-isar/conf/machine/qemuarm64.conf
@@ -9,8 +9,13 @@ KERNEL_NAME ?= "arm64"
 KERNEL_NAME:ubuntu ?= "generic"
 
 IMAGE_FSTYPES ?= "ext4"
+# the ubuntu kernel is an EFI zboot image, so it can only boot via UEFI from wic
+IMAGE_FSTYPES:resolute ?= "wic"
 ROOTFS_EXTRA ?= "128"
 
+IMAGER_BOM:wic += "${GRUB_BOOTLOADER_INSTALL}"
+IMAGER_INSTALL:wic += "${GRUB_BOOTLOADER_INSTALL}"
+
 QEMU_ROOTFS_DEV ?= "vda"
 
 QEMU_ARCH ?= "aarch64"
@@ -18,6 +23,8 @@ QEMU_MACHINE ?= "virt"
 QEMU_CPU ?= "cortex-a57"
 # TODO: start_vm doesn't support multiline vars
 QEMU_DISK_ARGS ?= "-drive file=##ROOTFS_IMAGE##,if=none,format=raw,id=hd0 -device virtio-blk-device,drive=hd0"
+# virtio-rng is required, cortex-a57 has no CPU RNG and systemd blocks on getrandom()
+QEMU_DISK_ARGS:resolute ?= "-drive file=##ROOTFS_IMAGE##,if=none,format=raw,id=hd0 -device virtio-blk-device,drive=hd0 -device virtio-rng-pci -bios /usr/share/qemu-efi-aarch64/QEMU_EFI.fd"
 
 MACHINE_SERIAL ?= "ttyAMA0"
 BAUDRATE_TTY ?= "115200"
-- 
2.55.0

-- 
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/20261015211527.3143702-3-felix.moessbauer%40siemens.com.

[PATCH 3/4] qemuriscv64: add support for ubuntu resolute

['Felix Moessbauer' via isar-users]

The ubuntu resolute target also has an efi-only kernel and is built
for the RAV23 machine (with vector extensions), while the debian
targets are built for rv64.

We now provide the corresponding QEMU args, so this target can be
bootet. For efi booting, this means using an EDK2 on pflash and the
default builtin OpenSBI as bios.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta-isar/conf/machine/qemuriscv64.conf | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/meta-isar/conf/machine/qemuriscv64.conf b/meta-isar/conf/machine/qemuriscv64.conf
index a2a5de9b..283404ce 100644
--- a/meta-isar/conf/machine/qemuriscv64.conf
+++ b/meta-isar/conf/machine/qemuriscv64.conf
@@ -10,18 +10,26 @@ KERNEL_NAME ?= "riscv64"
 KERNEL_NAME:ubuntu ?= "generic"
 
 IMAGE_FSTYPES ?= "ext4"
+# the ubuntu kernel is an EFI zboot image, so it can only boot via UEFI from wic
+IMAGE_FSTYPES:resolute ?= "wic"
 ROOTFS_EXTRA ?= "128"
 
-# grub-efi is incompatible with targets riscv64, thus no sdimage-efi default
-WKS_FILE ?= "qemuriscv"
+# grub-efi has no riscv64 target, so use the systemd-boot variant
+WKS_FILE ?= "sdimage-efi-sd"
+IMAGER_BOM:wic += "${SYSTEMD_BOOTLOADER_INSTALL}"
+IMAGER_INSTALL:wic += "${SYSTEMD_BOOTLOADER_INSTALL}"
 
 QEMU_ROOTFS_DEV ?= "vda"
 
 QEMU_ARCH ?= "riscv64"
 QEMU_MACHINE ?= "virt"
 QEMU_CPU ?= "rv64"
+# ubuntu riscv64 is built for RVA23
+QEMU_CPU:resolute ?= "rva23s64"
 # TODO: start_vm doesn't support multiline vars
 QEMU_DISK_ARGS ?= "-drive file=##ROOTFS_IMAGE##,if=none,format=raw,id=hd0 -device virtio-blk-device,drive=hd0"
+# EDK2 on pflash, OpenSBI as bios; virtio-rng is required as rv64 has no CPU RNG
+QEMU_DISK_ARGS:resolute ?= "-drive file=##ROOTFS_IMAGE##,if=none,format=raw,id=hd0 -device virtio-blk-device,drive=hd0 -device virtio-rng-pci -drive if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/qemu-efi-riscv64/RISCV_VIRT_CODE.fd"
 
 MACHINE_SERIAL ?= "ttyS0"
 BAUDRATE_TTY ?= "115200"
-- 
2.55.0

-- 
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/20261015211527.3143702-4-felix.moessbauer%40siemens.com.

[PATCH 4/4] testsuite: re-enable riscv64 and arm64 ubuntu resolute tests

['Felix Moessbauer' via isar-users]

As the ubuntu resolute images are now using efiboot, we also add the
corresponding QEMU and OVMF packages to the test container.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 testsuite/citest.py             | 21 ++++-----------------
 testsuite/dockerdata/Dockerfile |  4 +++-
 testsuite/dockerdata/version    |  2 +-
 3 files changed, 8 insertions(+), 19 deletions(-)

diff --git a/testsuite/citest.py b/testsuite/citest.py
index c5996830..d068ca11 100644
--- a/testsuite/citest.py
+++ b/testsuite/citest.py
@@ -446,21 +446,14 @@ class CrossTest(CIBaseTest):
         ]
 
         self.init()
-        try:
-            self.perform_build_test(targets)
-        except exceptions.TestFail:
-            self.cancel('KFAIL')
+        self.perform_build_test(targets)
 
-    # TODO: broken because of moving to UEFI
     def test_run_arm64_resolute(self):
         """
         :avocado: tags=startvm
         """
         self.init()
-        try:
-            self.vm_start('arm64', 'resolute')
-        except exceptions.TestFail:
-            self.cancel('KFAIL')
+        self.vm_start('arm64', 'resolute')
 
     def test_cross_debsrc(self):
         targets = [
@@ -548,10 +541,7 @@ class CrossTest(CIBaseTest):
         ]
 
         self.init()
-        try:
-            self.perform_build_test(targets)
-        except exceptions.TestFail:
-            self.cancel('KFAIL')
+        self.perform_build_test(targets)
 
     def test_run_riscv64_trixie(self):
         """
@@ -568,10 +558,7 @@ class CrossTest(CIBaseTest):
         :avocado: tags=startvm,riscv64
         """
         self.init()
-        try:
-            self.vm_start('riscv64', 'resolute', image='isar-image-ci')
-        except exceptions.TestFail:
-            self.cancel('KFAIL')
+        self.vm_start('riscv64', 'resolute', image='isar-image-ci')
 
     def test_cross_forky(self):
         targets = [
diff --git a/testsuite/dockerdata/Dockerfile b/testsuite/dockerdata/Dockerfile
index d4698aea..3ca5472d 100644
--- a/testsuite/dockerdata/Dockerfile
+++ b/testsuite/dockerdata/Dockerfile
@@ -11,7 +11,9 @@ RUN sudo pip3 --proxy=$https_proxy install --break-system-packages \
               avocado-framework==${AVOCADO_VERSION} \
               avocado-framework-plugin-varianter-yaml-to-mux==${AVOCADO_VERSION} && \
     sudo apt-get update && \
-    sudo apt-get install -y -f --no-install-recommends qemu-system ovmf python3-apt busybox squid && \
+    sudo apt-get install -y -f --no-install-recommends \
+        qemu-system qemu-efi-aarch64 qemu-efi-riscv64 ovmf \
+        python3-apt busybox squid && \
     sudo apt-get clean && \
     sudo rm -rf $(pip3 cache dir) /var/lib/apt/lists/* /tmp/* /var/tmp/* && \
     sudo sh -c 'echo "max_filedescriptors 1048576" > /etc/squid/conf.d/docker.conf'
diff --git a/testsuite/dockerdata/version b/testsuite/dockerdata/version
index b8626c4c..7ed6ff82 100644
--- a/testsuite/dockerdata/version
+++ b/testsuite/dockerdata/version
@@ -1 +1 @@
-4
+5
-- 
2.55.0

-- 
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/20261015211527.3143702-5-felix.moessbauer%40siemens.com.

Re: [PATCH 4/4] testsuite: re-enable riscv64 and arm64 ubuntu resolute tests

[Zhihang Wei]

On 10/15/26 23:15, 'Felix Moessbauer' via isar-users wrote:
> As the ubuntu resolute images are now using efiboot, we also add the
> corresponding QEMU and OVMF packages to the test container.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>   testsuite/citest.py             | 21 ++++-----------------
>   testsuite/dockerdata/Dockerfile |  4 +++-
>   testsuite/dockerdata/version    |  2 +-
>   3 files changed, 8 insertions(+), 19 deletions(-)
>
> diff --git a/testsuite/citest.py b/testsuite/citest.py
> index c5996830..d068ca11 100644
> --- a/testsuite/citest.py
> +++ b/testsuite/citest.py
> @@ -446,21 +446,14 @@ class CrossTest(CIBaseTest):
>           ]
>   
>           self.init()
> -        try:
> -            self.perform_build_test(targets)
> -        except exceptions.TestFail:
> -            self.cancel('KFAIL')
> +        self.perform_build_test(targets)
>   
> -    # TODO: broken because of moving to UEFI
>       def test_run_arm64_resolute(self):
>           """
>           :avocado: tags=startvm
>           """
>           self.init()
> -        try:
> -            self.vm_start('arm64', 'resolute')
> -        except exceptions.TestFail:
> -            self.cancel('KFAIL')
> +        self.vm_start('arm64', 'resolute')
>   
>       def test_cross_debsrc(self):
>           targets = [
> @@ -548,10 +541,7 @@ class CrossTest(CIBaseTest):
>           ]
>   
>           self.init()
> -        try:
> -            self.perform_build_test(targets)
> -        except exceptions.TestFail:
> -            self.cancel('KFAIL')
> +        self.perform_build_test(targets)
>   

It was set to KFAIl because of an issue on ubuntu tar, see 11b921c6. It's
still failing now in rootful, I'll check whether this is still an issue on
rootless mode. If so, we can disable them on rootful mode.

Zhihang

>       def test_run_riscv64_trixie(self):
>           """
> @@ -568,10 +558,7 @@ class CrossTest(CIBaseTest):
>           :avocado: tags=startvm,riscv64
>           """
>           self.init()
> -        try:
> -            self.vm_start('riscv64', 'resolute', image='isar-image-ci')
> -        except exceptions.TestFail:
> -            self.cancel('KFAIL')
> +        self.vm_start('riscv64', 'resolute', image='isar-image-ci')
>   
>       def test_cross_forky(self):
>           targets = [
> diff --git a/testsuite/dockerdata/Dockerfile b/testsuite/dockerdata/Dockerfile
> index d4698aea..3ca5472d 100644
> --- a/testsuite/dockerdata/Dockerfile
> +++ b/testsuite/dockerdata/Dockerfile
> @@ -11,7 +11,9 @@ RUN sudo pip3 --proxy=$https_proxy install --break-system-packages \
>                 avocado-framework==${AVOCADO_VERSION} \
>                 avocado-framework-plugin-varianter-yaml-to-mux==${AVOCADO_VERSION} && \
>       sudo apt-get update && \
> -    sudo apt-get install -y -f --no-install-recommends qemu-system ovmf python3-apt busybox squid && \
> +    sudo apt-get install -y -f --no-install-recommends \
> +        qemu-system qemu-efi-aarch64 qemu-efi-riscv64 ovmf \
> +        python3-apt busybox squid && \
>       sudo apt-get clean && \
>       sudo rm -rf $(pip3 cache dir) /var/lib/apt/lists/* /tmp/* /var/tmp/* && \
>       sudo sh -c 'echo "max_filedescriptors 1048576" > /etc/squid/conf.d/docker.conf'
> diff --git a/testsuite/dockerdata/version b/testsuite/dockerdata/version
> index b8626c4c..7ed6ff82 100644
> --- a/testsuite/dockerdata/version
> +++ b/testsuite/dockerdata/version
> @@ -1 +1 @@
> -4
> +5

-- 
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/b77ce26f-f9bc-4597-b15f-d8e15f8ffc35%40ilbers.de.

Re: [PATCH 4/4] testsuite: re-enable riscv64 and arm64 ubuntu resolute tests

['Moessbauer, Felix' via isar-users]

On Mon, 2026-10-26 at 17:49 +0100, Zhihang Wei wrote:
> On 10/15/26 23:15, 'Felix Moessbauer' via isar-users wrote:
> > As the ubuntu resolute images are now using efiboot, we also add the
> > corresponding QEMU and OVMF packages to the test container.
> > 
> > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> > ---
> >   testsuite/citest.py             | 21 ++++-----------------
> >   testsuite/dockerdata/Dockerfile |  4 +++-
> >   testsuite/dockerdata/version    |  2 +-
> >   3 files changed, 8 insertions(+), 19 deletions(-)
> > 
> > diff --git a/testsuite/citest.py b/testsuite/citest.py
> > index c5996830..d068ca11 100644
> > --- a/testsuite/citest.py
> > +++ b/testsuite/citest.py
> > @@ -446,21 +446,14 @@ class CrossTest(CIBaseTest):
> >           ]
> >   
> >           self.init()
> > -        try:
> > -            self.perform_build_test(targets)
> > -        except exceptions.TestFail:
> > -            self.cancel('KFAIL')
> > +        self.perform_build_test(targets)
> >   
> > -    # TODO: broken because of moving to UEFI
> >       def test_run_arm64_resolute(self):
> >           """
> >           :avocado: tags=startvm
> >           """
> >           self.init()
> > -        try:
> > -            self.vm_start('arm64', 'resolute')
> > -        except exceptions.TestFail:
> > -            self.cancel('KFAIL')
> > +        self.vm_start('arm64', 'resolute')
> >   
> >       def test_cross_debsrc(self):
> >           targets = [
> > @@ -548,10 +541,7 @@ class CrossTest(CIBaseTest):
> >           ]
> >   
> >           self.init()
> > -        try:
> > -            self.perform_build_test(targets)
> > -        except exceptions.TestFail:
> > -            self.cancel('KFAIL')
> > +        self.perform_build_test(targets)
> >   
> 
> It was set to KFAIl because of an issue on ubuntu tar, see 11b921c6. It's
> still failing now in rootful, I'll check whether this is still an issue on
> rootless mode. If so, we can disable them on rootful mode.

I saw that comment, but was not able to reproduce it. I also don't see
why rootless and privileged builds should be any different in this
regard.

It's probably because I'm testing this on top of the "More build time
reductions" series, which also always generates the source package from
the -native variant.

Will look into it. For now, you can also just merge patches 1-3.

Felix

> 
> Zhihang
> 
> >       def test_run_riscv64_trixie(self):
> >           """
> > @@ -568,10 +558,7 @@ class CrossTest(CIBaseTest):
> >           :avocado: tags=startvm,riscv64
> >           """
> >           self.init()
> > -        try:
> > -            self.vm_start('riscv64', 'resolute', image='isar-image-ci')
> > -        except exceptions.TestFail:
> > -            self.cancel('KFAIL')
> > +        self.vm_start('riscv64', 'resolute', image='isar-image-ci')
> >   
> >       def test_cross_forky(self):
> >           targets = [
> > diff --git a/testsuite/dockerdata/Dockerfile b/testsuite/dockerdata/Dockerfile
> > index d4698aea..3ca5472d 100644
> > --- a/testsuite/dockerdata/Dockerfile
> > +++ b/testsuite/dockerdata/Dockerfile
> > @@ -11,7 +11,9 @@ RUN sudo pip3 --proxy=$https_proxy install --break-system-packages \
> >                 avocado-framework==${AVOCADO_VERSION} \
> >                 avocado-framework-plugin-varianter-yaml-to-mux==${AVOCADO_VERSION} && \
> >       sudo apt-get update && \
> > -    sudo apt-get install -y -f --no-install-recommends qemu-system ovmf python3-apt busybox squid && \
> > +    sudo apt-get install -y -f --no-install-recommends \
> > +        qemu-system qemu-efi-aarch64 qemu-efi-riscv64 ovmf \
> > +        python3-apt busybox squid && \
> >       sudo apt-get clean && \
> >       sudo rm -rf $(pip3 cache dir) /var/lib/apt/lists/* /tmp/* /var/tmp/* && \
> >       sudo sh -c 'echo "max_filedescriptors 1048576" > /etc/squid/conf.d/docker.conf'
> > diff --git a/testsuite/dockerdata/version b/testsuite/dockerdata/version
> > index b8626c4c..7ed6ff82 100644
> > --- a/testsuite/dockerdata/version
> > +++ b/testsuite/dockerdata/version
> > @@ -1 +1 @@
> > -4
> > +5

-- 
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/e978f99f9448f18985435095d6c6049d07276f9d.camel%40siemens.com.

Re: [PATCH 0/4] Fix qemu riscv64 and arm64 ubuntu resolute targets

[Zhihang Wei]

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.