CI: Include microcode for x86 hardware jobs

All the x86 hardware runners are out of date, to varying degrees, in terms of
microcode.

Microcode must be uncompressed and prepended to the initrd in order for Xen to
be able to use it during early boot.

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Anthony PERARD <anthony.perard@vates.tech>
(cherry picked from commit 4a39780faa)
This commit is contained in:
Andrew Cooper committed 2025-05-07 15:28:02 +01:00
1 parent 0258350a63
commit 690655a511
4 files changed
+11 -2

No files matched your search

+1
View File
@@ -306,6 +306,7 @@ alpine-3.18-gcc-debug:
CONFIG_ARGO=y
CONFIG_UBSAN=y
CONFIG_UBSAN_FATAL=y
CONFIG_UCODE_SCAN_DEFAULT=y
CONFIG_XHCI=y
debian-12-x86_64-gcc-debug:
+6
View File
@@ -26,6 +26,9 @@
- project: xen-project/hardware/test-artifacts
job: alpine-3.18-x86_64-rootfs
ref: master
- project: xen-project/hardware/test-artifacts
job: microcode-x86
ref: master
.qemu-arm64:
extends: .test-jobs-common
@@ -247,6 +250,9 @@ xilinx-smoke-dom0-x86_64-gcc-debug-argo:
- project: xen-project/hardware/test-artifacts
job: alpine-3.18-x86_64-rootfs
ref: master
- project: xen-project/hardware/test-artifacts
job: microcode-x86
ref: master
adl-smoke-x86-64-gcc-debug:
extends: .adl-x86-64
+2 -1
View File
@@ -188,7 +188,8 @@ Kernel \r on an \m (\l)
fi
# Dom0 rootfs
cp binaries/rootfs.cpio.gz binaries/dom0-rootfs.cpio.gz
cp binaries/ucode.cpio binaries/dom0-rootfs.cpio.gz
cat binaries/rootfs.cpio.gz >> binaries/dom0-rootfs.cpio.gz
cat binaries/xen-tools.cpio.gz >> binaries/dom0-rootfs.cpio.gz
# test-local configuration
@@ -106,7 +106,8 @@ cd ..
rm -rf rootfs
# Dom0 rootfs
cp binaries/rootfs.cpio.gz binaries/dom0-rootfs.cpio.gz
cp binaries/ucode.cpio binaries/dom0-rootfs.cpio.gz
cat binaries/rootfs.cpio.gz >> binaries/dom0-rootfs.cpio.gz
cat binaries/xen-tools.cpio.gz >> binaries/dom0-rootfs.cpio.gz
if [[ "${TEST}" == argo ]]; then
cat binaries/argo.cpio.gz >> binaries/dom0-rootfs.cpio.gz
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.