mirror of
git://git.yoctoproject.org/meta-virtualization.git
synced 2025-07-04 21:05:25 +02:00
d876cfc5bf
OEcore/bitbake are moving to use the clearer ":" as an overrides
separator.
This is pass one of updating the meta-virt recipes to use that
syntax.
This has only been minimally build/runtime tested, more changes
will be required for missed overrides, or incorrect conversions
Note: A recent bitbake is required:
commit 75fad23fc06c008a03414a1fc288a8614c6af9ca
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Sun Jul 18 12:59:15 2021 +0100
bitbake: data_smart/parse: Allow ':' characters in variable/function names
It is becomming increasingly clear we need to find a way to show what
is/is not an override in our syntax. We need to do this in a way which
is clear to users, readable and in a way we can transition to.
The most effective way I've found to this is to use the ":" charater
to directly replace "_" where an override is being specified. This
includes "append", "prepend" and "remove" which are effectively special
override directives.
This patch simply adds the character to the parser so bitbake accepts
the value but maps it back to "_" internally so there is no behaviour
change.
This change is simple enough it could potentially be backported to older
version of bitbake meaning layers using the new syntax/markup could
work with older releases. Even if other no other changes are accepted
at this time and we don't backport, it does set us on a path where at
some point in future we could
require a more explict syntax.
I've tested this patch by converting oe-core/meta-yocto to the new
syntax for overrides (9000+ changes) and then seeing that builds
continue to work with this patch.
(Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
90 lines
3.3 KiB
BlitzBasic
90 lines
3.3 KiB
BlitzBasic
DESCRIPTION = "A minimal xen image"
|
|
|
|
INITRD_IMAGE = "core-image-minimal-initramfs"
|
|
|
|
XEN_KERNEL_MODULES ?= "kernel-module-xen-blkback kernel-module-xen-gntalloc \
|
|
kernel-module-xen-gntdev kernel-module-xen-netback kernel-module-xen-wdt \
|
|
${@bb.utils.contains('MACHINE_FEATURES', 'pci', "${XEN_PCIBACK_MODULE}", '', d)} \
|
|
${@bb.utils.contains('MACHINE_FEATURES', 'acpi', 'kernel-module-xen-acpi-processor', '', d)} \
|
|
"
|
|
|
|
IMAGE_INSTALL += " \
|
|
packagegroup-core-boot \
|
|
packagegroup-core-ssh-openssh \
|
|
${XEN_KERNEL_MODULES} \
|
|
xen-tools \
|
|
qemu \
|
|
"
|
|
|
|
# The hypervisor may not be within the dom0 filesystem image but at least
|
|
# ensure that it is deployable:
|
|
do_build[depends] += "xen:do_deploy"
|
|
|
|
# Networking for HVM-mode guests (x86/64 only) requires the tun kernel module
|
|
IMAGE_INSTALL:append:x86 = "kernel-module-tun"
|
|
IMAGE_INSTALL:append:x86-64 = "kernel-module-tun"
|
|
|
|
# Linux kernel option CONFIG_XEN_PCIDEV_BACKEND depends on X86
|
|
XEN_PCIBACK_MODULE = ""
|
|
XEN_PCIBACK_MODULE:x86 = "kernel-module-xen-pciback"
|
|
XEN_PCIBACK_MODULE:x86-64 = "kernel-module-xen-pciback"
|
|
|
|
LICENSE = "MIT"
|
|
|
|
inherit core-image qemuboot-xen-defaults qemuboot-xen-dtb
|
|
|
|
do_check_xen_state() {
|
|
if [ "${@bb.utils.contains('DISTRO_FEATURES', 'xen', ' yes', 'no', d)}" = "no" ]; then
|
|
die "DISTRO_FEATURES does not contain 'xen'"
|
|
fi
|
|
}
|
|
|
|
addtask check_xen_state before do_rootfs
|
|
|
|
syslinux_iso_populate:append() {
|
|
install -m 0444 ${STAGING_DATADIR}/syslinux/libcom32.c32 ${ISODIR}${ISOLINUXDIR}
|
|
install -m 0444 ${STAGING_DATADIR}/syslinux/mboot.c32 ${ISODIR}${ISOLINUXDIR}
|
|
}
|
|
|
|
syslinux_hddimg_populate:append() {
|
|
install -m 0444 ${STAGING_DATADIR}/syslinux/libcom32.c32 ${HDDDIR}${SYSLINUXDIR}
|
|
install -m 0444 ${STAGING_DATADIR}/syslinux/mboot.c32 ${HDDDIR}${SYSLINUXDIR}
|
|
}
|
|
|
|
grubefi_populate:append() {
|
|
install -m 0644 ${DEPLOY_DIR_IMAGE}/xen-${MACHINE}.gz ${DEST}${EFIDIR}/xen.gz
|
|
}
|
|
|
|
syslinux_populate:append() {
|
|
install -m 0644 ${DEPLOY_DIR_IMAGE}/xen-${MACHINE}.gz ${DEST}/xen.gz
|
|
}
|
|
|
|
SYSLINUX_XEN_ARGS ?= "loglvl=all guest_loglvl=all console=com1,vga com1=115200,8n1"
|
|
SYSLINUX_KERNEL_ARGS ?= "ramdisk_size=32768 root=/dev/ram0 rw console=hvc0 earlyprintk=xen console=tty0 panic=10 LABEL=boot debugshell=5"
|
|
|
|
build_syslinux_cfg () {
|
|
echo "ALLOWOPTIONS 1" > ${SYSLINUX_CFG}
|
|
echo "DEFAULT boot" >> ${SYSLINUX_CFG}
|
|
echo "TIMEOUT 10" >> ${SYSLINUX_CFG}
|
|
echo "PROMPT 1" >> ${SYSLINUX_CFG}
|
|
echo "LABEL boot" >> ${SYSLINUX_CFG}
|
|
echo " KERNEL mboot.c32" >> ${SYSLINUX_CFG}
|
|
echo " APPEND /xen.gz ${SYSLINUX_XEN_ARGS} --- /vmlinuz ${SYSLINUX_KERNEL_ARGS} --- /initrd" >> ${SYSLINUX_CFG}
|
|
}
|
|
|
|
# Enable runqemu. eg: runqemu xen-image-minimal nographic slirp
|
|
WKS_FILE_x86-64 = "directdisk-xen.wks"
|
|
QB_MEM ?= "-m 400"
|
|
QB_DEFAULT_KERNEL ?= "none"
|
|
QB_DEFAULT_FSTYPE ?= "wic"
|
|
QB_DEFAULT_FSTYPE_qemux86-64 = "wic"
|
|
QB_FSINFO ?= "wic:kernel-in-fs"
|
|
QB_SERIAL_OPT = "-serial mon:stdio"
|
|
# qemux86-64 machine does not include 'wic' in IMAGE_FSTYPES, which is needed
|
|
# to boot this image, so add it here:
|
|
IMAGE_FSTYPES:qemux86-64 += "wic"
|
|
# Networking: the qemuboot.bbclass default virtio network device works ok
|
|
# and so does the emulated e1000 -- choose according to the network device
|
|
# drivers that are present in your dom0 Linux kernel. To switch to e1000:
|
|
# QB_NETWORK_DEVICE = "-device e1000,netdev=net0,mac=@MAC@"
|