Bug 2025 - runqemu scripts should attempt sane defaults for unknown machines
Summary: runqemu scripts should attempt sane defaults for unknown machines
Status: RESOLVED WONTFIX
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: All Multiple
: Low enhancement
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-02-22 15:26 UTC by Darren Hart
Modified: 2023-03-30 15:24 UTC (History)
9 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darren Hart 2012-02-22 15:26:59 UTC 
When building for certain real machines, it can still useful to test the results in qemu. Currently, runqemu and runqemu-internal must have several things specified for every machine, and if not, abort with an error.

Instead, it would be nice if it would at least attempt to run with sane defaults:

FS=ext3
KERNEL={bzImage,uImage,etc.}-$MACHINE.bin

The qemu${ARCH} might be guessable from the KERNEL image, and if not, an ARCH= option might be a reasonable addition.

As for the QEMUOPTIONS, perhaps a serial port for output rather than VGA if that is easier to deal with.
Comment 1 Paul Eggleton 2017-06-21 07:36:31 UTC 
This should in theory be easier with the newly rewritten runqemu that uses the QB_* variables - we could presumably set defaults for these on a per-architecture basis.
Comment 2 Randy MacLeod 2023-03-30 15:24:05 UTC 
We could guess about this required options but we could easily be wrong.
Better to be deterministic.