public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH] start_vm.py: support running images built with kas on host
Date: Thu, 23 Jan 2025 18:17:51 +0300	[thread overview]
Message-ID: <20250123151758.18098-1-ubely@ilbers.de> (raw)

Script start_vm.py internally calls bitbake (bb.tinfoil) to set
some qemu parameters from the build environment. If the image
was build in kas, build/conf/bblayers.conf includes path that don't
fit host machine.

Also, current implementation relies on appropriate BBMULTICONFIG
value set in local.conf.

The patch adds workarounds that cover both cases mentioned above.

Configuring and building the image:

```
./kas/kas-container menu
./kas/kas-container build
```

Running the image with start_vm.py:

```
. isar-init-build-env
../testsuite/start_vm.py -a amd64 -d bookworm -i isar-image-base
```

Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
 kas/isar.yaml         |  4 ++++
 testsuite/start_vm.py | 10 ++++++++++
 2 files changed, 14 insertions(+)

diff --git a/kas/isar.yaml b/kas/isar.yaml
index 16ce8b42..d15bdbe1 100644
--- a/kas/isar.yaml
+++ b/kas/isar.yaml
@@ -17,3 +17,7 @@ bblayers_conf_header:
   standard: |
     BBPATH = "${TOPDIR}"
     BBFILES ?= ""
+
+local_conf_header:
+  bbmulticonfig: |
+    BBMULTICONFIG += "${MACHINE}-${BASE_DISTRO_CODENAME}"
diff --git a/testsuite/start_vm.py b/testsuite/start_vm.py
index 0b9a52d6..f39e53a1 100755
--- a/testsuite/start_vm.py
+++ b/testsuite/start_vm.py
@@ -135,7 +135,17 @@ def sb_cleanup():
     os.remove(os.path.basename(OVMF_VARS_PATH))
 
 
+def kas_paths_workaround():
+    # "repo" simlink pointing to the isar dir makes kas-generated
+    # ${TOPDIR}/../repo/ paths in local.conf work outside of kas container
+    isar_dir = os.path.realpath(f'{os.path.dirname(__file__)}/..')
+    if not os.path.exists(f'{isar_dir}/repo'):
+        os.symlink('.', f'{isar_dir}/repo')
+
+
 def start_qemu(arch, build, distro, image, out, pid, enforce_pcbios):
+    kas_paths_workaround()
+
     cmdline, vm_ctx = format_qemu_cmdline(
         arch, build, distro, image, out, pid, enforce_pcbios
     )
-- 
2.45.2

-- 
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/20250123151758.18098-1-ubely%40ilbers.de.

             reply	other threads:[~2025-01-23 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 15:17 Uladzimir Bely [this message]
2025-01-23 15:27 ` '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=20250123151758.18098-1-ubely@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.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