From f11fd49c78b1ec111a4d8ba0f7f4fc493658fafc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=B6rg=20Thalheim?= <joerg@thalheim.io>
Date: Sat, 26 Aug 2023 19:36:49 +0200
Subject: [PATCH] kexec-installer: re-enable kexec-syscall-auto

Seems like GCP changed something about their boot process and the same instance types that failed to kexec, now just works.
This fixes secureboot as well: https://github.com/nix-community/nixos-images/issues/128
---
 nix/kexec-installer/kexec-run.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/nix/kexec-installer/kexec-run.sh b/nix/kexec-installer/kexec-run.sh
index 09d9d33..ea2c7db 100644
--- a/nix/kexec-installer/kexec-run.sh
+++ b/nix/kexec-installer/kexec-run.sh
@@ -52,8 +52,8 @@ done
 
 find . | cpio -o -H newc | gzip -9 >> "$SCRIPT_DIR/initrd"
 
-# Dropped --kexec-syscall-auto because it broke on GCP...
 if ! "$SCRIPT_DIR/kexec" --load "$SCRIPT_DIR/bzImage" \
+  --kexec-syscall-auto \
   --initrd="$SCRIPT_DIR/initrd" --no-checks \
   --command-line "init=$init $kernelParams"; then
   echo "kexec failed, dumping dmesg"