2025 2012-02-22 15:26:59 +0000 runqemu scripts should attempt sane defaults for unknown machines 2023-03-30 15:24:05 +0000 1 1 7 Build System, Metadata & Runtime Meta-yocto meta-yocto unspecified All Multiple RESOLVED WONTFIX Low enhancement Future 1 dvhart unassigned bluelightning jessica.zhang jon.mason poky.bs.watcher poky.watcher randy.macleod scott.a.garman sgw song.liu --- --- Yes (doc changes required) oldest_to_newest 18713 0 dvhart 2012-02-22 15:26:59 +0000 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. 74428 1 bluelightning 2017-06-21 07:36:31 +0000 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. 95242 2 randy.macleod 2023-03-30 15:24:05 +0000 We could guess about this required options but we could easily be wrong. Better to be deterministic.