summaryrefslogtreecommitdiffstats
path: root/src/config
diff options
context:
space:
mode:
authorMichael Brown2017-01-24 14:47:03 +0100
committerMichael Brown2017-01-24 14:47:03 +0100
commit90fc2f273a32793e0d0413d7adbf7bc43b995914 (patch)
tree87f622788d430250cd3b4c5795bff073317265e3 /src/config
parent[netdevice] Allow MTU to be changed at runtime (diff)
downloadipxe-90fc2f273a32793e0d0413d7adbf7bc43b995914.tar.gz
ipxe-90fc2f273a32793e0d0413d7adbf7bc43b995914.tar.xz
ipxe-90fc2f273a32793e0d0413d7adbf7bc43b995914.zip
[cloud] Show CPU vendor and model in example cloud boot scripts
Some problems arise only when running on a specific CPU type (e.g. non-functional timer interrupts as observed in Azure AMD instances). Include the CPU vendor and model within the sample cloud boot scripts, to assist in debugging such problems. Signed-off-by: Michael Brown <mcb30@ipxe.org>
Diffstat (limited to 'src/config')
-rw-r--r--src/config/cloud/aws.ipxe1
-rw-r--r--src/config/cloud/gce.ipxe1
-rw-r--r--src/config/cloud/settings.h4
3 files changed, 6 insertions, 0 deletions
diff --git a/src/config/cloud/aws.ipxe b/src/config/cloud/aws.ipxe
index d857d71d..2c96e388 100644
--- a/src/config/cloud/aws.ipxe
+++ b/src/config/cloud/aws.ipxe
@@ -1,6 +1,7 @@
#!ipxe
echo Amazon EC2 - iPXE boot via user-data
+echo CPU: ${cpuvendor} ${cpumodel}
ifstat ||
dhcp ||
route ||
diff --git a/src/config/cloud/gce.ipxe b/src/config/cloud/gce.ipxe
index 95330d71..88e12b56 100644
--- a/src/config/cloud/gce.ipxe
+++ b/src/config/cloud/gce.ipxe
@@ -1,6 +1,7 @@
#!ipxe
echo Google Compute Engine - iPXE boot via metadata
+echo CPU: ${cpuvendor} ${cpumodel}
ifstat ||
dhcp ||
route ||
diff --git a/src/config/cloud/settings.h b/src/config/cloud/settings.h
index e69de29b..34deeb07 100644
--- a/src/config/cloud/settings.h
+++ b/src/config/cloud/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