forked from coreos/fedora-coreos-config
-
Notifications
You must be signed in to change notification settings - Fork 0
/
platforms.yaml
177 lines (177 loc) · 6.87 KB
/
platforms.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
# This file specifies image customizations that are specific to particular
# architecture/platform pairs. It is applied (indirectly, via
# /boot/coreos/platforms.json) by create_disk.sh and gf-set-platform at
# build time and coreos-installer at install time (if --platform is
# specified).
#
# Currently this is used to configure the default console. For any
# arch/platform pairs not specified, GRUB and the kernel will apply their
# own defaults. Note that coreos-installer install --console will
# completely override any GRUB commands specified here.
#
# s390x doesn't use GRUB and requires running zipl after updating kargs,
# so it can't be added to this file without additional development work.
#
# All architectures, platforms, and fields are optional.
aarch64:
aws:
# https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-to-serial-console.html#sc-considerations
# It appears there's no screenshot support on ARM
grub_commands:
- serial --speed=115200 efi0
- terminal_input serial_efi0
- terminal_output serial_efi0
kernel_arguments:
- console=ttyS0,115200n8
azure:
# https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-machines/serial-console-linux
# https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-machines/boot-diagnostics
# Have GRUB write only to console, which gets copied to the serial port.
# If we use serial (serial efi0; terminal_output console serial_efi0)
# we get doubled output.
kernel_arguments:
- console=tty0
- console=ttyAMA0,115200n8
openstack:
# Graphical console primary, serial console available for logging
# https://docs.openstack.org/diskimage-builder/latest/elements/bootloader/README.html
# https://issues.redhat.com/browse/OCPBUGS-2926
grub_commands:
- serial --speed=115200
- terminal_input serial console
- terminal_output serial console
kernel_arguments:
- console=ttyAMA0,115200n8
- console=tty0
packet:
# https://metal.equinix.com/developers/docs/resilience-recovery/serial-over-ssh/#limitations
grub_commands:
- serial --speed=115200
- terminal_input serial
- terminal_output serial
kernel_arguments:
- console=ttyAMA0,115200
qemu:
# The kernel successfully autodetects a serial console, but we still
# want GRUB to use one
grub_commands:
- serial --speed=115200
- terminal_input serial console
- terminal_output serial console
ppc64le:
openstack:
# Graphical console primary, serial console available for logging
# petitboot doesn't understand GRUB console commands
# https://docs.openstack.org/diskimage-builder/latest/elements/bootloader/README.html
# https://issues.redhat.com/browse/OCPBUGS-2926
kernel_arguments:
- console=hvc0
- console=tty0
qemu:
# petitboot doesn't understand GRUB console commands, but we need to
# pass console kargs
# https://github.com/coreos/coreos-assembler/pull/2400#discussion_r701412417
kernel_arguments:
- console=hvc0
- console=tty0
x86_64:
aws:
# https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-to-serial-console.html#sc-considerations
# https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_GetConsoleScreenshot.html
grub_commands:
- serial --speed=115200
- terminal_input serial console
- terminal_output serial console
kernel_arguments:
- console=tty0
- console=ttyS0,115200n8
azure:
# https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-machines/serial-console-linux
# https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-machines/boot-diagnostics
# Have GRUB write only to console, which gets copied to the serial port.
# If we use serial we get doubled output.
kernel_arguments:
- console=tty0
- console=ttyS0,115200n8
gcp:
# Four serial ports are available; we use the first one
# https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-using-serial-console
# https://cloud.google.com/compute/docs/troubleshooting/capturing-vm-screenshots
grub_commands:
- serial --speed=115200
- terminal_input serial console
- terminal_output serial console
kernel_arguments:
- console=tty0
- console=ttyS0,115200n8
ibmcloud:
# Docs suggest 9600 bps, but that doesn't seem reasonable
# https://cloud.ibm.com/docs/vpc?topic=vpc-create-linux-custom-image#kernel-args
# https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_console&interface=ui
grub_commands:
- serial --speed=115200
- terminal_input serial console
- terminal_output serial console
kernel_arguments:
- console=tty0
- console=ttyS0,115200n8
kubevirt:
# No official docs on this for kubevirt. Requested some:
# https://github.com/kubevirt/kubevirt/issues/9400
# The web UI displays the VNC console first, so go with
# graphical console primary, serial console secondary.
grub_commands:
- serial --speed=115200
- terminal_input serial console
- terminal_output serial console
kernel_arguments:
- console=ttyS0,115200n8
- console=tty0
openstack:
# Graphical console primary, serial console available for logging
# https://docs.openstack.org/diskimage-builder/latest/elements/bootloader/README.html
# https://issues.redhat.com/browse/OCPBUGS-2926
grub_commands:
- serial --speed=115200
- terminal_input serial console
- terminal_output serial console
kernel_arguments:
- console=ttyS0,115200n8
- console=tty0
packet:
# https://metal.equinix.com/developers/docs/resilience-recovery/serial-over-ssh/#limitations
grub_commands:
- serial --unit=1 --speed=115200
- terminal_input serial
- terminal_output serial
kernel_arguments:
- console=ttyS1,115200n8
qemu:
# https://github.com/coreos/fedora-coreos-tracker/issues/954
grub_commands:
- serial --speed=115200
- terminal_input serial console
- terminal_output serial console
kernel_arguments:
- console=tty0
- console=ttyS0,115200n8
virtualbox:
# Graphical console primary, serial console available for logging
# https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-virtualbox/#_troubleshooting_first_boot_problems
grub_commands:
- serial --speed=115200
- terminal_input serial console
- terminal_output serial console
kernel_arguments:
- console=ttyS0,115200n8
- console=tty0
vmware:
# Graphical console primary, serial console available for logging
# https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-vmware/#_troubleshooting_first_boot_problems
grub_commands:
- serial --speed=115200
- terminal_input serial console
- terminal_output serial console
kernel_arguments:
- console=ttyS0,115200n8
- console=tty0