| Summary: | AB-INT: QEMU: failed to start (riscv) | ||
|---|---|---|---|
| Product: | [QA/Testing] Runtime Testing | Reporter: | Mathieu Dubois-Briand <mathieu.dubois-briand> |
| Component: | oeqa/runtime | Assignee: | Trevor Gamblin <tgamblin> |
| Status: | IN PROGRESS DESIGN --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | Harish.Sadineni, randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | 6.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | AB-INT | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Mathieu Dubois-Briand
2026-08-26 08:20:40 UTC
qemuriscv64-ptest alma8-vk-1 master&master-next completed at 2026-08-23 00:57:16+00:00 https://valkyrie.yocto.io/pub/non-release/20260822-117/testresults/qemuriscv64-ptest/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2231/steps/16/logs/stdio See if it happens again. This issue is reproducible when building an image with KERNEL_DEBUG = "True" on riscv64. runqemu hangs when booting with -bios fw_jump.elf, but boots successfully with fw_dynamic.elf or the default bios. Hope this helps, Trevor. Note that this requires meta-oe to make pahole-native available, otherwise you get: tgamblin@megalith ~/workspace/ypbuilds/poky-qemuriscv64/build $ bitbake core-image-minimal Loading cache: 100% |#################################################################################################################################################################################| Time: 0:00:00 Loaded 1979 entries from dependency cache. NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'pahole-native'. Close matches: pango-native patch-native patchelf-native ERROR: Required build target 'core-image-minimal' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal', 'virtual/kernel', 'pahole-native'] I can't reproduce this anymore. Harish, can you? We've now switched to kernel version 7.2 with the Poky distro by default (see commit: https://git.yoctoproject.org/meta-yocto/commit/?id=3bb1295755628c4facec3a0a2800a9c12345ce00). This issue doesn't occur with the 7.2 kernel, so it looks like it may have been fixed in this version. To reproduce it, set PREFERRED_VERSION_linux-yocto = "6.18%" in local.conf. Note: wrynose is still affected. I have sent a workaround patch to use fw_dynamic.elf for oe-core/wrynose branch. https://lists.openembedded.org/g/openembedded-core/message/245965 We should probably look at the kernel history to see what might've changed it before just going with a workaround. I'll spend some time doing that. It seems that when I compare local builds between 6.18 and 7.2, the kernel build for the latter is reporting CONFIG_PAHOLE_VERSION=0 in the .config file. Still digging... |