From f7559f9d1c10303eab5f0e4e0c6eef7b24171998 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Sun, 20 Apr 2025 23:08:53 -0600 Subject: [PATCH] Update Workflows/Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md --- .../Migrating VMs to ProxmoxVE.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/Workflows/Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md b/Workflows/Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md index 5aecde3..e75a8aa 100644 --- a/Workflows/Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md +++ b/Workflows/Veeam Backup & Replication/Migrating VMs to ProxmoxVE.md @@ -9,8 +9,13 @@ Some high-level things to do to fix this are listed below, as well as commands t - Fix the socket and cores are reversed, so a single socket CPU with 16 cores will appear like 16 sockets with one core each - 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 - The storage controller needs to be switched to `VirtIO iSCSI` -- The VM may need you to switch the network adapter from `VirtIO` to `E1000` if you run `ethtool ens18` and find it's not detecting the link speed, and everything else is missing. -- The display driver needs switched to `SPICE` +- The VM may need you to switch the network adapter from `VirtIO` to `E1000` if you run `ethtool ens18` and find it's not detecting the link speed with `Unknown!`, and everything else is missing. +- Run the following commands to assign the new `ens18` interface as a networking interface for the VM to use: +```sh +nmcli connection add type ethernet ifname ens18 con-name ens18 ipv4.method manual ipv4.addresses 192.168.1.100/24 ipv4.gateway 192.168.3.1 ipv4.dns "1.1.1.1 1.0.0.1" +nmcli connection up ens18 +``` +- The display driver needs switched to `Default` - 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 @@ -22,6 +27,8 @@ Some high-level things to do to fix this are listed below, as well as commands t chroot /mnt/sysroot dracut --force --regenerate-all grub2-mkconfig -o /boot/grub2/grub.cfg +exit +exit ``` After this is done, you can turn off / sudo poweroff the VM and allow the VM to reboot.