path: root/conf/machine/include/
Commit message (Collapse)AuthorAgeFilesLines
* Add to KERNEL_FEATURES via KERNEL_FEATURES_INTEL_COMMONCalifornia Sullivan2017-05-111-1/+1
| | | | | | | | | | Adding to KERNEL_FEATURES causes the kernel tools to try to add the feature to all kernels, even custom kernels not using the yocto-kernel-cache. By moving it to KERNEL_FEATURES_INTEL_COMMON, it will only affect the kernels the layer supplies. Signed-off-by: California Sullivan <> Signed-off-by: Saul Wold <>
* Add ovmf to EXTRA_IMAGEDEPENDSCalifornia Sullivan2017-03-281-0/+3
| | | | | | | This lets us use ovmf firmware with runqemu without building ovmf manually beforehand. Signed-off-by: California Sullivan <>
* meta-intel: enable qemu and select more suitable virtual machine optionsPatrick Ohly2017-01-241-0/+16
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 was copied from OE-core's and adapted to the three common machines in meta-intel: $ diff ../openembedded-core/meta/conf/machine/include/ conf/machine/include/ 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 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 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 Signed-off-by: Patrick Ohly <> Signed-off-by: California Sullivan <>