You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/linux/serial-console-grub-proactive-configuration.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,14 +75,14 @@ If you don't have access to GRUB, watch [this video](https://youtu.be/m5t0GZ5oGA
75
75
76
76
## Configuration methods and challenges
77
77
78
-
By default, not all Linux Azure VMs are configured for GRUB access or to be interrupted by the SysRq commands. Some older distros, such as LES 11, aren't configured to display a sign-in prompt in the Azure Serial Console. The following sections review various Linux distributions and discuss configurations that make GRUB available.
78
+
By default, not all Linux Azure VMs are configured for GRUB access or can be interrupted by the SysRq commands. Some older distros, such as LES 11, aren't configured to display a sign-in prompt in the Azure Serial Console. The following sections review various Linux distributions and discuss configurations that make GRUB available.
79
79
80
80
### How to configure Linux VM to accept SysRq keys
81
81
82
82
By default, the SysRq key is enabled on some newer Linux distros. On other distros, it might be configured for accepting values only for certain SysRq functions.
83
83
On older distros, it might be disabled completely.
84
84
85
-
The SysRq feature is useful for restarting a non-responding VM directly from the Azure Serial Console. It's also helpful to gain access to the GRUB menu. Aalternatively, restarting a VM from another portal window or SSH session might drop your current console connection and end GRUB timeouts that previously displayed the GRUB menu.
85
+
The SysRq feature is useful for restarting a nonresponding VM directly from the Azure Serial Console. It's also helpful to gain access to the GRUB menu. Alternatively, restarting a VM from another portal window or SSH session might drop your current console connection and end GRUB timeouts that previously displayed the GRUB menu.
86
86
87
87
The VM must be configured to accept a value of **1** for the kernel parameter. This setting enables all functions of SysRq or 128 for restart and power off processes.
88
88
@@ -150,7 +150,7 @@ Ubuntu 12.04 allows access to the serial console but doesn't offer the ability t
150
150
151
151
For Ubuntu 12.04 to obtain a **login:** prompt, follow these steps:
152
152
153
-
1. Create a file that's named /etc/init/ttyS0.conf and that contains the following text:
153
+
1. Create a file, and name it /etc/init/ttyS0.conf. The file should contain the following text:
154
154
155
155
```console
156
156
# ttyS0 - getty
@@ -187,13 +187,15 @@ If you don't configure the kernel boot parameter, the Recovery menu is automatic
187
187
188
188
:::image type="content" source="media/serial-console-grub-proactive-configuration/recovery-mode-ubuntu.png" alt-text="Screenshot that shows the Serial console and a recovery mode version selected.":::
189
189
190
-
1. Locate the line that loads the kernel. Replace the last parameter, **nomodeset**, with the destination, as **console=ttyS0**:
190
+
1. Locate the line that loads the kernel:
191
191
192
192
```console
193
193
linux /boot/vmlinuz-4.15.0-1023-azure root=UUID=21b294f1-25bd-4265-9c4e-d6e4aeb57e97 ro recovery nomodeset
194
+
```
194
195
195
-
change to
196
+
Replace the last parameter, **nomodeset**, with the destination, as **console=ttyS0**:
196
197
198
+
```console
197
199
linux /boot/vmlinuz-4.15.0-1023-azure root=UUID=21b294f1-25bd-4265-9c4e-d6e4aeb57e97 ro recovery console=ttyS0
198
200
```
199
201
@@ -250,7 +252,7 @@ GRUB_TIMEOUT=1
250
252
GRUB_TERMINAL_OUTPUT="console"
251
253
```
252
254
253
-
Change these to the following:
255
+
Change these lines to the following lines:
254
256
255
257
```console
256
258
GRUB_TIMEOUT=5
@@ -290,7 +292,7 @@ Alternatively, you can configure GRUB and SysRq by using a single line, either i
290
292
291
293
#### Red Hat 6\.*x* GRUB configuration
292
294
293
-
The file to modify is /boot/grub/grub.conf. The `timeout` value will determine how long GRUB is dispplayed.
295
+
The file to modify is /boot/grub/grub.conf. The `timeout` value determines how long GRUB is displayed.
294
296
295
297
```console
296
298
#boot=/dev/vda1
@@ -303,7 +305,7 @@ terminal serial
303
305
terminal --timeout=5 serial console
304
306
```
305
307
306
-
The last line, *terminal –-timeout=5 serial console*, further increases the **GRUB** timeout value by adding a prompt of five seconds duration that displays the message, **Press any key to continue.**
308
+
The last line, *terminal –-timeout=5 serial console*, further increases the **GRUB** timeout value by adding a five-second prompt that displays the message, **Press any key to continue.**
307
309
308
310
:::image type="content" source="media/serial-console-grub-proactive-configuration/press-any-key-to-continue.png" alt-text="Screenshot that shows console output.":::
This configuration triggers a prompt of five seconds duration on the console that displays the message, **Press any key to continue.**
368
+
This configuration triggers a prompt on the console that displays a five-second message, **Press any key to continue.**
367
369
368
370
It then displays the GRUB menu for an additional five seconds. Press the down arrow to interrupt the counter, and then select a kernel that you want to start. You can make either of the following changes:
0 commit comments