Bug 1019 - runqemu custom append options do not always work
Summary: runqemu custom append options do not always work
Status: RESOLVED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 1.0
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.1
Assignee: Scott Garman
QA Contact:
URL:
Whiteboard: Pull request submitted on 2011-09-03
Depends on:
Blocks:
 
Reported: 2011-05-02 15:29 UTC by Scott Garman
Modified: 2011-09-06 09:35 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments
Allows additional kernel command line options to be easily provided (666 bytes, patch)
2011-05-18 04:58 UTC, Gary Thomas
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Garman 2011-05-02 15:29:37 UTC
Darren demonstrated some issues with the runqemu script when he tried to specify kernel command line options. It appears that the --append options are listed before the default kernel --append options when the qemu utility is run, and there is some overriding behavior going on.

Fixing this may be as simple as moving custom --append options to the end of the qemu command string.
Comment 1 Gary Thomas 2011-05-18 04:58:49 UTC
Created attachment 159 [details]
Allows additional kernel command line options to be easily provided

The attached patch is a reasonable fix for this problem by specifying
SCRIPT_KERNEL_OPT="additional kernel command line options" when the
script is run.

There are already such options for this script such as "SERIAL_LOGFILE"
If you want to use a different name for SCRIPT_KERNEL_OPT, that's fine,
but please make it easier to specify such kernel options.

Note: a very strong argument for this is a simple ability to suppress
the psplash boot screen (for debugging).  Without this option, one has
to edit the runqemu scripts, just to add 'psplash=false' when booting.
Comment 2 Scott Garman 2011-09-03 15:54:03 UTC
It turns out Otavio Salvador fixed this bug by adding the undocumented bootparams option. So I added documention for this option in the usage screen and made use of a similar method for passing custom qemu options. Pull request pending on oe-core.