From c0c0c1f8c6f1a2770d1fcab47353144adab6d81f Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Wed, 5 Feb 2025 03:42:53 -0700 Subject: [PATCH] Update Workflows/Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md --- .../Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Workflows/Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md b/Workflows/Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md index 81ad51c..0d4548c 100644 --- a/Workflows/Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md +++ b/Workflows/Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md @@ -13,7 +13,7 @@ Some high-level things to do to fix this are listed below, as well as commands t - The display driver needs switched to `SPICE` - The operating system needs to have the bootloader and storage drivers regenerated, see the instructions below: - Boot from a Rocky Linux 9.5 installation ISO in the broken Rocky Linux VM - - Select "Troubleshooting" in the boot menu + - Select "Troubleshooting -->" in the boot menu - Select "Rescue a Rocky Linux Operating System" - Press through the prompt with value `1` to select the automatic mounting of the detected operating system of the virtual machine - Press **** to enter the shell, then run the following commands to fix the booting issues