From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <t.f.g.geelen@gmail.com>, <openembedded-core@lists.openembedded.org>
Cc: "Alex Kanavin" <alex.kanavin@gmail.com>
Subject: Re: [OE-core] [PATCH V2] qemurunner: Improve qmp module detection PKG_CONFIG_SYSROOT_DIR for qmp module path
Date: Thu, 08 Jan 2026 12:31:53 +0100 [thread overview]
Message-ID: <DFJ6AGZNL99N.VPY6DN6VPCWK@bootlin.com> (raw)
In-Reply-To: <20260107202553.2965393-3-t.f.g.geelen@gmail.com>
On Wed Jan 7, 2026 at 9:25 PM CET, Tom Geelen via lists.openembedded.org wrote:
> Instead of using logfile to detect where qmp is located we can use PKG_CONFIG_SYSROOT_DIR, passed via ENV to the launch function as this will point to the image recipe for which launch is called.
>
> Signed-off-by: Tom Geelen <t.f.g.geelen@gmail.com>
> ---
Hi Tom,
Thanks for your patch.
This is failing on the autobuilder, with the following error:
2026-01-08 10:20:15,532 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/qemux86-tc/build/layers/openembedded-core/meta/lib/oeqa/utils/commands.py", line 390, in runqemu
qemu.start(params=qemuparams, ssh=ssh, runqemuparams=runqemuparams, launch_cmd=launch_cmd, discard_writes=discard_writes)
File "/srv/pokybuild/yocto-worker/qemux86-tc/build/layers/openembedded-core/meta/lib/oeqa/targetcontrol.py", line 179, in start
raise RuntimeError("%s - FAILED to start qemu - check the task log and the boot log" % self.pn)
RuntimeError: core-image-minimal - FAILED to start qemu - check the task log and the boot log
...
DEBUG: Using kvm for runqemu
ERROR: qemurunner: qmp module missing, please ensure it's installed in /../recipe-sysroot-native/usr/lib/qemu-python (No module named 'qmp')
https://autobuilder.yoctoproject.org/valkyrie/#/builders/28/builds/2925
https://autobuilder.yoctoproject.org/valkyrie/#/builders/5/builds/2931
https://autobuilder.yoctoproject.org/valkyrie/#/builders/28/builds/2925
https://autobuilder.yoctoproject.org/valkyrie/#/builders/66/builds/2975
Can you have a look at these issues?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-01-08 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 20:25 [PATCH V2] qemurunner: Improve qmp module detection PKG_CONFIG_SYSROOT_DIR for qmp module path Tom Geelen
2026-01-07 20:52 ` Alexander Kanavin
2026-01-08 11:31 ` Mathieu Dubois-Briand [this message]
2026-01-08 14:52 ` [OE-core] " Tom Geelen
2026-01-08 17:34 ` Mathieu Dubois-Briand
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=DFJ6AGZNL99N.VPY6DN6VPCWK@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=t.f.g.geelen@gmail.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