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/chroot-environment-linux.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,7 +94,7 @@ This article describes how to troubleshoot the chroot environment on a rescue vi
94
94
1. Detach the disk from the rescue VM, and then perform a disk swap with the original VM.
95
95
1. Start the original VM, and check its connectivity.
96
96
97
-
## RHEL/Centos/Oracle 6.x && Oracle 8.x && RHEL/Centos 7.x with RAW partitions
97
+
## RHEL/Centos/Oracle 6._x_ && Oracle 8._x_ && RHEL/Centos 7._x_ with RAW partitions
98
98
99
99
1. Stop or deallocate the affected VM.
100
100
1. Create a rescue VM image of the same OS version in the same resource group (RSG) and location by using a managed disk.
@@ -158,7 +158,7 @@ This article describes how to troubleshoot the chroot environment on a rescue vi
158
158
1. Detach the disk from the rescue VM, and then perform a disk swap with the original VM.
159
159
1. Start the original VM, and check its connectivity.
160
160
161
-
## RHEL/Centos 7.x & 8.X with LVM
161
+
## RHEL/Centos 7._x_ & 8._x_ with LVM
162
162
163
163
> [!NOTE]
164
164
> If your original VM includes Logical Volume Manager (LVM) on the OS Disk, create the rescue VM by using the image with raw partitions on the OS Disk.
0 commit comments