summaryrefslogtreecommitdiffstats
path: root/conf/machine/include/meta-intel.inc
diff options
context:
space:
mode:
authorPatrick Ohly <patrick.ohly@intel.com>2017-01-20 15:54:54 (GMT)
committerCalifornia Sullivan <california.l.sullivan@intel.com>2017-01-24 22:31:06 (GMT)
commit5130e819ca8aef8111ac3581520402ea46566666 (patch)
tree86cb1ba54a5626ebb371658fc6c9f2a54ed5c51f /conf/machine/include/meta-intel.inc
parent72402b08c571809f3b2f3cfdc2d1eb0e72109a64 (diff)
downloadmeta-intel-5130e819ca8aef8111ac3581520402ea46566666.tar.gz
meta-intel: enable qemu and select more suitable virtual machine options
Although the machines definitions in meta-intel are meant to target real hardware, begin able to start the resulting images under qemu is nevertheless useful for testing. Doing that via runqemu depends on a per-image runqemu.conf that describes how to run qemu for the image. Ineriting qemuboot.bbclass in image recipes with QB_ variables set for the current architecture via overrides creates that file. The new qemuboot-intel.inc was copied from OE-core's qemuboot-x86.inc and adapted to the three common machines in meta-intel: $ diff ../openembedded-core/meta/conf/machine/include/qemuboot-x86.inc conf/machine/include/qemuboot-intel.inc 3,5c3,5 < QB_SYSTEM_NAME_x86 = "qemu-system-i386" < QB_CPU_x86 = "-cpu qemu32" < QB_CPU_KVM_x86 = "-cpu kvm32" --- > QB_SYSTEM_NAME_intel-core2-32 = "qemu-system-i386" > QB_CPU_intel-core2-32 = "-cpu coreduo" > QB_CPU_KVM_intel-core2-32 = "-cpu kvm32" 7,9c7,13 < QB_SYSTEM_NAME_x86-64 = "qemu-system-x86_64" < QB_CPU_x86-64 = "-cpu core2duo" < QB_CPU_KVM_x86-64 = "-cpu kvm64" --- > QB_SYSTEM_NAME_intel-corei7-64 = "qemu-system-x86_64" > QB_CPU_intel-corei7-64 = "-cpu Nehalem" > QB_CPU_KVM_intel-corei7-64 = "-cpu kvm64" > > QB_SYSTEM_NAME_intel-quark = "qemu-system-i386" > QB_CPU_intel-quark = "-cpu coreduo" > QB_CPU_KVM_intel-quark = "-cpu kvm32" For performance reasons, runqemu uses virtio for the boot disk. The kernel therefore must have the necessary drivers enabled. This may also be useful when running a meta-intel machine image on other virtual platforms and therefore the default kernel configuration gets changed to enable virtio. However, OE-core's qemu.inc also enables various other tweaks for running under qemu, like deriving the wired Ethernet address from the kernel boot parameters. This is probably less desirable for a meta-intel machine and thus not enabled in the new qemu-intel.inc. The downside is that the resulting images then come up without assigned IP address when used under qemu. Distros which want that feature can still add it to their images by copying settings from OE-core's qemu.inc. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Diffstat (limited to 'conf/machine/include/meta-intel.inc')
-rw-r--r--conf/machine/include/meta-intel.inc7
1 files changed, 7 insertions, 0 deletions
diff --git a/conf/machine/include/meta-intel.inc b/conf/machine/include/meta-intel.inc
index fd0a792..21587fb 100644
--- a/conf/machine/include/meta-intel.inc
+++ b/conf/machine/include/meta-intel.inc
@@ -36,3 +36,10 @@ EFI_PROVIDER ?= "rmc-boot"
36 36
37# Add general MACHINEOVERRIDE for meta-intel 37# Add general MACHINEOVERRIDE for meta-intel
38MACHINEOVERRIDES =. "intel-x86-common:" 38MACHINEOVERRIDES =. "intel-x86-common:"
39
40# Definition of (more or less) suitable virtual machines.
41require conf/machine/include/qemuboot-intel.inc
42
43# Ensure that the extra tools needed by qemu are built when building images
44# and tweak machine definition to make the result more usable under qemu.
45require conf/machine/include/qemu-intel.inc