[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>

diff --git a/src/config/cloud/aws.ipxe b/src/config/cloud/aws.ipxe
index d857d71df44a82525356a1cad9727a5b451368ac..2c96e3888f10a8f94b9151ea474daef28ec2bd8f 100644 (file)
--- 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 95330d718345115d19c70fe54896df0651ef1e6d..88e12b56bd5679713824b6e4a1afbf37e6117e91 100644 (file)
--- 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 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391..34deeb0708f652ab0a514e12bd6934ad7b8649d0 100644 (file)
--- 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