linux/poky.git/scripts/runqemu, branch master-next

runqemu: resize rootfs image to power of 2 for SD or pflash

2025-11-07T13:15:35+00:00

QEMU requires that SD and pflash images are sized to be a power of 2 (e.g., 32M, 64M, etc). So, if the image being used is not a power of 2 and it's being used for SD or pflash, increase it to the next power of 2 size via the truncate command. This might not be an actual spec requirement, and is being investigated in https://gitlab.com/qemu-project/qemu/-/issues/1754 (From OE-Core rev: 4e2f75f89843d629d9e0b9d3f7a68414091f2b70) Signed-off-by: Jon Mason Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

runqemu: remove setting of mem on kernel command line for certain systems

2025-11-07T13:15:35+00:00

Some emulated hardware will not boot if mem is set on the kernel command line (all of the Raspberry Pi machines seemed to fail with this set, possibly many others). Also, it is not necessary if the device tree file is present, as that _should_ have the memory size specified in it. Add a check for QB_DTB and don't set mem in the kernel command line if present. (From OE-Core rev: cf3524dbd536c206a49e06da8bb1067900fdc777) Signed-off-by: Jon Mason Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

scripts/runqemu: raise an error when bitbake was not found

2025-10-09T09:58:07+00:00

Running 'scrupts/runqemu' without bitbake in PATH causes the following error: ``` Traceback (most recent call last): File "/home/rg/temp_stuff/oe_2/./scripts/runqemu", line 1807, in main config.check_args() ~~~~~~~~~~~~~~~~~^^ File "/home/rg/temp_stuff/oe_2/./scripts/runqemu", line 624, in check_args s = re.search('^DEPLOY_DIR_IMAGE="(.*)"', self.bitbake_e, re.M) File "/usr/lib/python3.13/re/__init__.py", line 177, in search return _compile(pattern, flags).search(string) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^ TypeError: expected string or bytes-like object, got 'NoneType' ``` This patch adds a more helpful error message to inform the user that bitbake was not found, e.g. because oe-init-build-env was not sourced. This is an example of the new error message after the patch: ``` runqemu - ERROR - In order for this script to dynamically infer paths kernels or filesystem images, you either need bitbake in your PATH or to source oe-init-build-env before running this script. Dynamic path inference can be avoided by passing a *.qemuboot.conf to runqemu, i.e. `runqemu /path/to/my-image-name.qemuboot.conf` Bitbake is needed to run 'bitbake -e', but it is not found in PATH. Please source the bitbake build environment. ``` CC: Richard Purdie CC: Alexander Kanavin (From OE-Core rev: 0c10a78796fbdfaa5be4a824c0c9f5cb97c88046) Signed-off-by: Richard Grünert Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

scripts/runqemu: remove the code block that works around the missing bitbake environment

2025-10-09T09:58:07+00:00

As confirmed by the previous patch this code path is never taken and can be removed. (From OE-Core rev: b931f74442e9f2fba95600ba056a5bd898c23b5a) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

runqemu: ensure that bitbake environment is either returned, or an exception is raised

2025-10-09T09:58:07+00:00

This eliminates the other remaining code path where environment getter returns 'nothing'. This and the previous patch were tested in a-full, and no errors occurred [1], which means the code paths that make use of the function returning nothing are never actually executed and can be cleaned up (in the following patch). The rationale is that if environment getter cannot obtain the environment, it should report that and not sweep the issue under the carpet; it's up to the caller to handle that situation, or make pre-emptive checks that avoid calling the environment getter when it is bound to fail. [1] https://lists.openembedded.org/g/openembedded-core/message/223651 (From OE-Core rev: 8197be4dd336be2f8a646916223922da61c5b9b1) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

runqemu: add erofs filesystem types

2025-09-22T21:09:48+00:00

runqemu does not recognize erofs, erofs-lz4, and erofs-lz4hc as filesystem types. Add them to start from an erofs filesystem without needing the full path. (From OE-Core rev: 8d5654d21c021964794c84f594748f376c2b39fc) Signed-off-by: Thomas Witte Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

runqemu: fix special characters bug

2025-08-07T11:11:16+00:00

Fix the bug in runqemu that happens when the file path contains the specific words such as 'vmlinux', e.g. /home/frank/vmlinux. runqemu - ERROR - wic doesn't need kernel (From OE-Core rev: 3c186fe7741adecb0887e36c8a9164a58fc16437) Signed-off-by: Libo Chen Signed-off-by: Richard Purdie

runqemu: refactor a duplicated cleanup statement

2025-08-07T11:11:16+00:00

Refactor using a "finally:" instead of a duplicated statement inside and outside of the try/except block. (From OE-Core rev: c92399c355d1333eff37ea799832a8890acd0d74) Signed-off-by: Yoann Congal Signed-off-by: Richard Purdie

runqemu: use "zstd -o" to preserve sparse images

2025-08-07T11:11:16+00:00

wic images can be sparse. Using "zstd -o" preserves the sparse state of the image and should decrease decompression time. Suggested-by: Adrian Freihofer (From OE-Core rev: 27d156d85f13131ea4c5d766ddaa2d18b88d7577) Signed-off-by: Yoann Congal Signed-off-by: Richard Purdie

scripts/runqemu: Update the fstypes list with newly supported compressed images types

2025-08-06T21:32:41+00:00

Update the interal list of types within runqemu with the newly added compression formats it supports. This fixes autodetection of qemuboot file locations. (From OE-Core rev: 46b9a1c74df00f76f7c19b5ed27e6a569aaabb5e) Signed-off-by: Richard Purdie