Re: [PATCH 0/5] Add iso9660 image support for ISAR

[Uladzimir Bely <ubely@ilbers.de>]

On Tue, 2025-01-21 at 11:42 +0000, 'MOESSBAUER, Felix' via isar-users
wrote:
> On Tue, 2025-01-21 at 11:24 +0100, Jan Kiszka wrote:
> > On 21.01.25 11:12, Felix Moessbauer wrote:
> > > This series adds support to create hybrid iso9660 images for ISAR
> > > which can be used as live images for booting from USB sticks or
> > > DVDs. Currently, only syslinux and EFI (grub) bootloaders are
> > > supported.
> > > 
> > > Best regards,
> > > Felix Moessbauer
> > > 
> > > Felix Moessbauer (5):
> > >   Import isoimage-isohybrid from oe
> > >   wic: add ISAR version of isohybrid-efi plugin
> > >   move squashfs imagetype class from CIP to ISAR
> > >   add qemuamd64 target for hybrid iso9660 image
> > >   add kas menu target for qemuamd64-iso machine
> > > 
> > >  kas/machine/Kconfig                           |  14 +
> > >  kas/machine/qemuamd64-iso.yaml                |   7 +
> > >  meta-isar/classes/squashfs.bbclass            |  48 ++
> > >  meta-isar/conf/machine/qemuamd64-iso.conf     |  29 +
> > >  .../multiconfig/qemuamd64-iso-bookworm.conf   |   4 +
> > >  .../lib/wic/canned-wks/isohybrid-efi.wks.in   |   2 +
> > >  meta/classes/image.bbclass                    |   2 +-
> > >  .../plugins/source/isoimage-isohybrid-isar.py | 535
> > > ++++++++++++++++++
> > >  8 files changed, 640 insertions(+), 1 deletion(-)
> > >  create mode 100644 kas/machine/qemuamd64-iso.yaml
> > >  create mode 100644 meta-isar/classes/squashfs.bbclass
> > >  create mode 100644 meta-isar/conf/machine/qemuamd64-iso.conf
> > >  create mode 100644 meta-isar/conf/multiconfig/qemuamd64-iso-
> > > bookworm.conf
> > >  create mode 100644 meta-isar/scripts/lib/wic/canned-
> > > wks/isohybrid-
> > > efi.wks.in
> > >  create mode 100644 meta/scripts/lib/wic/plugins/source/isoimage-
> > > isohybrid-isar.py
> > > 
> > 
> > I suspect we still missing a hook-up into the isar test suite,
> > aren't
> > we?
> 
> Probably yes, but I can't provide that as I'm not familiar with the
> testsuite. What we need is a test that builds the target and checks
> if
> systemctl is-system-running reports "running".
> 

I tried to check the image (build with kas) under qemu and it fails for
me. My steps (some of them are definitely worth adding to Isar):

1. Some local modifications:

- Added to "start_vm.py" `amd64-iso` "machine"

- Fixed machine in multiconfig/qemuamd64-iso-bookworm.conf (see my
comments to patch 4)

- Added to kas/isar.yaml:

```
local_conf_header:
  bbmulticonfig: |
    BBMULTICONFIG += "${MACHINE}-${BASE_DISTRO_CODENAME}"
```

No we can run "start_vm.py" that uses multiconfigs parsing inside.

2. Building the image

Configured `kas-container` menu and run build:
 - machine: qemuamd64-iso
 - distro: debian
 - user `root` enabled


3. Running the image with start_vm.py

# Workaround for bitbake reusing kas' relative paths in
conf/bblayers.conf
ln -s . repo


# Run qemu on the host
. isar-init-build-env
../testsuite/start_vm.py -a amd64-iso -d bookworm -i isar-image-base


After logging in, `systemd is-system-running` shows "starting" that is
changed to "degraded" after a while.



> Felix
> 
> > 
> > Jan
> > 
> 

-- 
Best regards,
Uladzimir.



-- 
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/5be064d5e26c6cf44ea5a9a18088b651d3d14772.camel%40ilbers.de.