Update Workflows/Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md

Workflows/Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md

@@ -4,6 +4,7 @@ When you migrate virtual machines from Hyper-V (and possibly other platforms) to
 
 ### Fixing Boot Issues
 Some high-level things to do to fix this are listed below:
+
 - Switch the VM processor type to `host`.
 - The socket and core counts are reversed, so a single socket CPU with 16 cores will appear like 16 sockets with one core each, flip these around to correct this issue.
 - The storage controller needs to be set to `VirtIO iSCSI`
@@ -11,6 +12,7 @@ Some high-level things to do to fix this are listed below:
 
 #### Dracut Emergency Shell
 If you start the VM and you reach a "dracut" prompt, then the bootloader got nuked and needs to be regenerated.  Follow the steps below to work through this process:
+
 - Boot from a Rocky Linux 9.5+ installation ISO in the broken Rocky Linux VM
 - Select "**Troubleshooting -->**" in the boot menu
 - Select "**Rescue a Rocky Linux System**"
@@ -28,6 +30,7 @@ exit
 
 ### Fixing Network Issues
 The VM will lose the adapter name of `eth0` and put something else like `ens18` that needs to be reconfigured manually to get networking functional again:
+
 - Type `ethtool ens18`, and if the link speed is `Unknown!`, then poweroff the VM and switch the network adapter from `VirtIO (paravirtualized)` to `Intel E1000`, then boot the VM back up.
 - Run the following commands to assign the new `ens18` interface as a networking interface for the VM to use:
 ```sh