public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "ubely@ilbers.de" <ubely@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>
Cc: "Bezdeka, Florian" <florian.bezdeka@siemens.com>,
	"Kowalsky, Clara" <clara.kowalsky@siemens.com>
Subject: Re: [PATCH 0/5] Add iso9660 image support for ISAR
Date: Thu, 23 Jan 2025 07:53:53 +0000	[thread overview]
Message-ID: <1cb68152e8701d76ff895ffae27463a88053e32f.camel@siemens.com> (raw)
In-Reply-To: <5be064d5e26c6cf44ea5a9a18088b651d3d14772.camel@ilbers.de>

On Wed, 2025-01-22 at 17:11 +0300, Uladzimir Bely wrote:
> 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"

Hi, I'll add this in the v2 as well.

> 
> - 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.

Please do a systemctl list-units --failed and paste the output here.
I tested with the following (manual) qemu cmdline and there it
correctly worked:

qemu-system-x86_64 -m 1G -snapshot -serial mon:stdio \
    -netdev user,id=net,hostfwd=tcp:127.0.0.1:22222-:22 \
    -cdrom build/tmp/deploy/images/qemuamd64-iso/isar-image-base-
debian-bookworm-qemuamd64-iso.wic \
    -cpu host -smp 4 -machine q35,accel=kvm:tcg \
    -bios /usr/share/ovmf/OVMF.fd -global ICH9-LPC.noreboot=off \
    -device virtio-net-pci,netdev=net -nographic

Best regards,
Felix Moessbauer

> 
> 
> 
> > Felix
> > 
> > > 
> > > Jan
> > > 
> > 
> 

-- 
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany


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

  parent reply	other threads:[~2025-01-23  7:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21 10:12 'Felix Moessbauer' via isar-users
2025-01-21 10:12 ` [PATCH 1/5] Import isoimage-isohybrid from oe 'Felix Moessbauer' via isar-users
2025-01-21 10:12 ` [PATCH 2/5] wic: add ISAR version of isohybrid-efi plugin 'Felix Moessbauer' via isar-users
2025-01-21 10:12 ` [PATCH 3/5] move squashfs imagetype class from CIP to ISAR 'Felix Moessbauer' via isar-users
2025-01-21 10:12 ` [PATCH 4/5] add qemuamd64 target for hybrid iso9660 image 'Felix Moessbauer' via isar-users
2025-01-22 12:22   ` Uladzimir Bely
2025-01-22 13:35   ` Uladzimir Bely
2025-01-21 10:12 ` [PATCH 5/5] add kas menu target for qemuamd64-iso machine 'Felix Moessbauer' via isar-users
2025-01-22 12:25   ` Uladzimir Bely
2025-01-21 10:24 ` [PATCH 0/5] Add iso9660 image support for ISAR 'Jan Kiszka' via isar-users
2025-01-21 11:42   ` 'MOESSBAUER, Felix' via isar-users
2025-01-21 13:17     ` 'Jan Kiszka' via isar-users
2025-01-22 14:11     ` Uladzimir Bely
2025-01-22 15:02       ` Uladzimir Bely
2025-01-23  7:53       ` 'MOESSBAUER, Felix' via isar-users [this message]
2025-01-23  8:49       ` 'MOESSBAUER, Felix' via isar-users

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=1cb68152e8701d76ff895ffae27463a88053e32f.camel@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=clara.kowalsky@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=ubely@ilbers.de \
    /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