bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Nicole Rappe
2025-04-20 23:08:53 -06:00
parent 0ad4cf600e
commit f7559f9d1c
1 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -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 - 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 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 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 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.
- The display driver needs switched to `SPICE` - 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: - 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 - 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
@ -22,6 +27,8 @@ Some high-level things to do to fix this are listed below, as well as commands t
chroot /mnt/sysroot chroot /mnt/sysroot
dracut --force --regenerate-all dracut --force --regenerate-all
grub2-mkconfig -o /boot/grub2/grub.cfg 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. After this is done, you can turn off / sudo poweroff the VM and allow the VM to reboot.