fix(qemu-coreos-arm64): fix several issues and refactoring
* rework machine conf to only build necessary stuff * in *.wks file switch from ondisk to use-uuid the solves an issue that during boot the user data partition could not be mounted because user data was set to mmcblk1 in fstab but actually was sda * kenrel options were missing for dmcrypt to create secure storage. those are now added to all machines using linux-yocto source and use the meta-belden-coreos-bsp layer
This commit is contained in:
parent
d57a9b7a70
commit
e18d9b87a8
|
|
@ -6,9 +6,9 @@
|
||||||
require conf/machine/qemu-generic-arm64.conf
|
require conf/machine/qemu-generic-arm64.conf
|
||||||
MACHINEOVERRIDES =. "qemu-generic-arm64:"
|
MACHINEOVERRIDES =. "qemu-generic-arm64:"
|
||||||
|
|
||||||
IMAGE_FSTYPES += "wic.xz wic.bmap"
|
COREOS_IMAGE_GENERATE_INSTALLER = "0"
|
||||||
|
|
||||||
WKS_FILE = "qemu-efi-coreos-generic.wks.in"
|
WKS_FILE = "qemu-efi-coreos-generic.wks.in"
|
||||||
QB_DRIVE_TYPE = "/dev/sd"
|
|
||||||
|
|
||||||
EFIBOOTGUARD_TIMEOUT ?= "0"
|
EFIBOOTGUARD_TIMEOUT ?= "0"
|
||||||
require conf/machine/include/coreos-generic-features/efi.inc
|
require conf/machine/include/coreos-generic-features/efi.inc
|
||||||
|
|
|
||||||
|
|
@ -0,0 +1,4 @@
|
||||||
|
CONFIG_BLK_DEV_DM=y
|
||||||
|
CONFIG_KEYS=y
|
||||||
|
CONFIG_ENCRYPTED_KEYS=y
|
||||||
|
CONFIG_DM_CRYPT=y
|
||||||
|
|
@ -0,0 +1,2 @@
|
||||||
|
# Set kernel config needed by secure-storage
|
||||||
|
SRC_URI += "file://secure-storage.cfg"
|
||||||
|
|
@ -2,11 +2,11 @@
|
||||||
# long-description: Creates a partitioned EFI disk image that the user
|
# long-description: Creates a partitioned EFI disk image that the user
|
||||||
# can directly dd to boot media.
|
# can directly dd to boot media.
|
||||||
|
|
||||||
part --source efibootguard-efi --label efi --part-type=EF00 --ondisk mmcblk1 --offset 20480S --size 64M --extra-space 0 --overhead-factor 1
|
part --source efibootguard-efi --label efi --part-type=EF00 --use-uuid --offset 20480S --size 64M --extra-space 0 --overhead-factor 1
|
||||||
part / --source rootfs --fstype=ext4 --label rootfs0 --ondisk mmcblk1 --size ${WKS_PART_ROOT_SIZE} --extra-space 0 --overhead-factor 1
|
part / --source rootfs --fstype=ext4 --label rootfs0 --use-uuid --size ${WKS_PART_ROOT_SIZE} --extra-space 0 --overhead-factor 1
|
||||||
part --fstype=ext4 --label rootfs1 --ondisk mmcblk1 --size ${WKS_PART_ROOT_SIZE} --extra-space 0 --overhead-factor 1
|
part --fstype=ext4 --label rootfs1 --use-uuid --size ${WKS_PART_ROOT_SIZE} --extra-space 0 --overhead-factor 1
|
||||||
part --source efibootguard-boot --label ebg0 --part-type=0700 --sourceparams "args=coreos.root=rootfs0,watchdog=${EFIBOOTGUARD_TIMEOUT},revision=2,kernel=${COREOS_KERNEL_FILENAME};KERNEL.EFI" --ondisk mmcblk1 --align 1024 --size 128M --extra-space 0 --overhead-factor 1
|
part --source efibootguard-boot --label ebg0 --part-type=0700 --sourceparams "args=coreos.root=rootfs0,watchdog=${EFIBOOTGUARD_TIMEOUT},revision=2,kernel=${COREOS_KERNEL_FILENAME};KERNEL.EFI" --use-uuid --align 1024 --size 128M --extra-space 0 --overhead-factor 1
|
||||||
part --source efibootguard-boot --label ebg1 --part-type=0700 --sourceparams "args=coreos.root=rootfs1,watchdog=${EFIBOOTGUARD_TIMEOUT},revision=1,kernel=${COREOS_KERNEL_FILENAME};KERNEL.EFI" --ondisk mmcblk1 --align 1024 --size 128M --extra-space 0 --overhead-factor 1
|
part --source efibootguard-boot --label ebg1 --part-type=0700 --sourceparams "args=coreos.root=rootfs1,watchdog=${EFIBOOTGUARD_TIMEOUT},revision=1,kernel=${COREOS_KERNEL_FILENAME};KERNEL.EFI" --use-uuid --align 1024 --size 128M --extra-space 0 --overhead-factor 1
|
||||||
${WKS_PART_USERDATA} --ondisk mmcblk1 --size ${WKS_PART_USERDATA_SIZE} --extra-space 0 --overhead-factor 1
|
${WKS_PART_USERDATA} --use-uuid --size ${WKS_PART_USERDATA_SIZE} --extra-space 0 --overhead-factor 1
|
||||||
|
|
||||||
bootloader --ptable gpt
|
bootloader --ptable gpt
|
||||||
Loading…
Reference in New Issue