attemt at a more complete debug configuration

.github/workflows/main.yaml

@@ -4,6 +4,7 @@ on:
   push:
     tags:
       - 'v*-hetzner*'
+      - 'v*-debug*'
 
 jobs:
   build_iso:
@@ -18,7 +19,7 @@ jobs:
             isolinux \
             genisoimage
       - name: build cloud/hetzner
-        run: make -C src bin/ipxe.iso CONFIG=cloud EMBED=config/cloud/hetzner.ipxe
+        run: make -C src bin/ipxe.iso CONFIG=hcloud EMBED=config/hcloud/hetzner.ipxe
       - name: Create Release
         id: create_release
         uses: actions/create-release@v1

src/config/hcloud/aws.ipxe

@@ -0,0 +1,8 @@
+#!ipxe
+
+echo Amazon EC2 - iPXE boot via user-data
+echo CPU: ${cpuvendor} ${cpumodel}
+ifstat ||
+dhcp ||
+route ||
+chain -ar http://169.254.169.254/latest/user-data

src/config/hcloud/console.h

@@ -0,0 +1,31 @@
+/*
+ * Console configuration suitable for use in public cloud
+ * environments, or any environment where direct console access is not
+ * available.
+ *
+ */
+
+/* Log to syslog(s) server
+ *
+ * The syslog server to be used must be specified via e.g.
+ * "set syslog 192.168.0.1".
+ */
+#define CONSOLE_SYSLOG
+#define CONSOLE_SYSLOGS
+
+/* Log to serial port
+ *
+ * Note that the serial port output from an AWS EC2 virtual machine is
+ * generally available (as the "System Log") only after the instance
+ * has been stopped.
+ */
+#define CONSOLE_SERIAL
+
+/* Log to partition on local disk
+ *
+ * If all other log mechanisms fail then the VM boot disk containing
+ * the iPXE image can be detached and attached to another machine in
+ * the same cloud, allowing the log to be retrieved from the log
+ * partition.
+ */
+#define CONSOLE_INT13

src/config/hcloud/gce.ipxe

@@ -0,0 +1,8 @@
+#!ipxe
+
+echo Google Compute Engine - iPXE boot via metadata
+echo CPU: ${cpuvendor} ${cpumodel}
+ifstat ||
+dhcp ||
+route ||
+chain -ar http://metadata.google.internal/computeMetadata/v1/instance/attributes/ipxeboot

src/config/hcloud/general.h

@@ -0,0 +1,28 @@
+/* Allow retrieval of metadata (such as an iPXE boot script) from
+ * Google Compute Engine metadata server.
+ */
+// #define HTTP_HACK_GCE
+
+/* Based on https://ipxe.org/buildcfg I've enabled everything that
+ * seems remotely usefull for debugging on Hetzner Cloud
+ */
+
+#define DOWNLOAD_PROTO_HTTPS
+#define NET_PROTO_IPV6
+#define CERT_CMD
+#define CONSOLE_CMD
+#define IMAGE_TRUST_CMD
+#define IPSTAT_CMD
+#define LOTEST_CMD
+#define NEIGHBOUR_CMD
+#define NSLOOKUP_CMD
+#define NTP_CMD
+#define PARAM_CMD
+#define PCI_CMD
+#define PING_CMD
+#define POWEROFF_CMD
+#define PROFSTAT_CMD
+#define REBOOT_CMD
+#define TIME_CMD
+#define VLAN_CMD
+

src/config/hcloud/hetzner.ipxe

@@ -0,0 +1,18 @@
+#!ipxe
+
+echo Hetzner Cloud - iPXE boot via user-data
+echo CPU: ${cpuvendor} ${cpumodel}
+
+# Give user a chance to enter the shell
+prompt --key 0x02 --timeout 2000 Press Ctrl-B for the iPXE shell... || goto no_shell
+shell
+exit
+
+:no_shell
+
+# Perform automated system Boot
+
+ifstat ||
+dhcp ||
+route ||
+chain -ar http://169.254.169.254/latest/user-data

src/config/hcloud/settings.h

@@ -0,0 +1,4 @@
+/* It can often be useful to know the CPU on which a cloud instance is
+ * running (e.g. to isolate problems with Azure AMD instances).
+ */
+#define CPUID_SETTINGS