Browse Source

[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>
tags/v1.20.1
Michael Brown 7 years ago
parent
commit
90fc2f273a
3 changed files with 6 additions and 0 deletions
  1. 1
    0
      src/config/cloud/aws.ipxe
  2. 1
    0
      src/config/cloud/gce.ipxe
  3. 4
    0
      src/config/cloud/settings.h

+ 1
- 0
src/config/cloud/aws.ipxe View File

@@ -1,6 +1,7 @@
1 1
 #!ipxe
2 2
 
3 3
 echo Amazon EC2 - iPXE boot via user-data
4
+echo CPU: ${cpuvendor} ${cpumodel}
4 5
 ifstat ||
5 6
 dhcp ||
6 7
 route ||

+ 1
- 0
src/config/cloud/gce.ipxe View File

@@ -1,6 +1,7 @@
1 1
 #!ipxe
2 2
 
3 3
 echo Google Compute Engine - iPXE boot via metadata
4
+echo CPU: ${cpuvendor} ${cpumodel}
4 5
 ifstat ||
5 6
 dhcp ||
6 7
 route ||

+ 4
- 0
src/config/cloud/settings.h View File

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

Loading…
Cancel
Save