runqemu + multiconfig

runqemu + multiconfig

[Patrick Ohly]

Hello!

runqemu works okay in a multiconfig setup, but one has to be careful
about how one sets MACHINE in the base configuration (aka local.conf):
it has to be done with ?= and not =

Example:

local.conf:
MACHINE ?= "intel-corei7-64"
BBMULTICONFIG = "core2 quark"

conf/multiconfig/quark.conf:
MACHINE = "intel-quark"

conf/multiconfig/core2.conf:
MACHINE = "intel-core2-32"

$ runqemu refkit-image-noswupd dsk intel-core2-32 ovmf
runqemu - INFO - Assuming MACHINE = intel-core2-32
runqemu - INFO - Running MACHINE=intel-core2-32 bitbake -e...
runqemu - INFO - MACHINE: intel-core2-32
runqemu - INFO - DEPLOY_DIR_IMAGE: .../tmp-glibc/deploy/images/intel-core2-32
runqemu - INFO - CONFFILE: .../tmp-glibc/deploy/images/intel-core2-32/...-intel-core2-32.qemuboot.conf

When using MACHINE = "intel-corei7-64" in local.conf, overriding the
MACHINE with "MACHINE=intel-core2-32 bitbake -e..." fails and runqemu
ends up using the image directory of the base configuration:

$ runqemu refkit-image-noswupd dsk intel-core2-32 ovmf
runqemu - INFO - Assuming MACHINE = intel-core2-32
runqemu - INFO - Running MACHINE=intel-core2-32 bitbake -e...
runqemu - INFO - MACHINE: intel-core2-32
runqemu - INFO - DEPLOY_DIR_IMAGE: .../tmp-glibc/deploy/images/intel-corei7-64
Traceback (most recent call last):
....
Exception: Failed to find <image>.qemuboot.conf!

This was with the patch for qemu support in meta-intel and the OVMF
firmware, but should also apply to the normal qemux86/qemux86-64.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.