For importing Scaleway images, extension needs to be '.qcow2'
See: https://www.scaleway.com/en/docs/compute/instances/how-to/snapshot-import-export-feature/
> Make sure that the QCOW / QCOW2 image file you want to import,
> uses the file extension .qcow or .qcow2 to avoid issues while importing the image.
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
This variable allows to override the disk extension which is initially
based on the DISK_FORMAT.
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
In case of sysext of zfs-kmod, pkg_setup() calls linux-info_get_any_version()
of eclass/linux-info.eclass with MERGE_TYPE=binary and
LINUX_INFO_BINARY_RESET=0. That results in KV_FULL and KV_OUT_DIR being
unset, which is not what we want. So set LINUX_INFO_BINARY_RESET=1 to
avoid such side effect.
Without setting them, build_sysext complains like below, i.e. it tries to find
System.map of a wrong Kernel version 6.6.21, when it should find a newer
version like 6.6.23. That results in subsequent zfs CI tests failing due to
missing files like System.map and module deps.
```
System.map for kernel 6.6.21-flatcar was not found, may be due to the
built kernel sources no longer being available and lacking the fallback:
```
Suggested-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
After making flatcar_production_pxe.vmlinuz a symlink to
flatcar_production_image.vmlinuz the signature creation didn't work
because the target could not be found.
As we do with the generic image, download the kernel from bincache, too,
before starting the VM image build.
The move to symlinking to the qemu-uefi image also resulted in the
qemu-uefi image being referenced in the qemu-bios and qemu-uefi-secure
scripts instead of referencing the image symlinks. Same for the VM name
shown in the qemu window title.
When generating the qemu scripts, use the original qemu image name and
VM name.
The arm64 kernel didn't have TPM support for the qemu TPM2 TIS software TPM.
This moves the TPM TIS kernel module enablement to the common config of both
architectures.
Authored-by: Kai Lueke <kailuke@microsoft.com>
Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
