Will this work in the case of a system boot? I know if we load the kernel
directly to memory and boot, we can pass kernel command line through QEMU.
However many boards I have worked with in the past (and still do) do a system
level boot that starts with BIOS/Firmware, goes into a second stage loader
(grub/u-boot) and then starts the kernel. How would these parameters end up
going to the kernel in that case, or are they silently ignored? Is silently
ignored on a system boot the behavior we want?
--Mark
On 3/1/24 9:05 AM, M. Seben via lists.openembedded.org wrote:
From: michal seben <[email protected]>
Allow to set runqemu bootparams option using TEST_EXTRABOOTPARAMS
variable. This option can be used .e.g. to mask service only for
testimage task.
Signed-off-by: michal seben <[email protected]>
---
meta/classes-recipe/testimage.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/testimage.bbclass
b/meta/classes-recipe/testimage.bbclass
index ad040ee8f0..6e2800e3c3 100644
--- a/meta/classes-recipe/testimage.bbclass
+++ b/meta/classes-recipe/testimage.bbclass
@@ -47,6 +47,8 @@ TESTIMAGE_FAILED_QA_ARTIFACTS +=
"${@bb.utils.contains('DISTRO_FEATURES', 'ptest
# TEST_QEMUBOOT_TIMEOUT can be used to set the maximum time in seconds the
launch code will wait for the login prompt.
# TEST_OVERALL_TIMEOUT can be used to set the maximum time in seconds the
tests will be allowed to run (defaults to no limit).
# TEST_QEMUPARAMS can be used to pass extra parameters to qemu, e.g. "-m
1024" for setting the amount of ram to 1 GB.
+# TEST_EXTRABOOTPARAMS can be used to set the 'bootparams' option for the
runqemu script
+# e.g. "systemd.mask=NetworkManager-wait-online.service" to mask particular
service
# TEST_RUNQEMUPARAMS can be used to pass extra parameters to runqemu, e.g.
"gl" to enable OpenGL acceleration.
# QEMU_USE_KVM can be set to "" to disable the use of kvm (by default it is
enabled if target_arch == build_arch or both of them are x86 archs)
@@ -358,7 +360,7 @@ def testimage_main(d):
try:
# We need to check if runqemu ends unexpectedly
# or if the worker send us a SIGTERM
- tc.target.start(params=d.getVar("TEST_QEMUPARAMS"),
runqemuparams=d.getVar("TEST_RUNQEMUPARAMS"))
+ tc.target.start(params=d.getVar("TEST_QEMUPARAMS"),
extra_bootparams=d.getVar("TEST_EXTRABOOTPARAMS"),
runqemuparams=d.getVar("TEST_RUNQEMUPARAMS"))
import threading
try:
threading.Timer(int(d.getVar("TEST_OVERALL_TIMEOUT")), handle_test_timeout,
(int(d.getVar("TEST_OVERALL_TIMEOUT")),)).start()
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196641):
https://lists.openembedded.org/g/openembedded-core/message/196641
Mute This Topic: https://lists.openembedded.org/mt/104665175/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
