Upgrading hardware on a standalone Home VM

superczar

Active Member
Feb 11, 2018
5
1
43
44
I use proxmox for a simple home server
Just a simple x86 machine with 2 SATA drives and 3 NIC running pfsense along with Linux Mint (NAS) and Windows (for RDP/other windows only apps)

I was hoping to upgrade the underlying hardware (again to a regular x86 sytem - i3 7100)
Unfortunately I do not have the luxury of migrating the VMs to another node

I searched around the forums but most related questions are for more complex production setups with hardware RAID or multiple nodes
Hence this question - Once I have moved the disks from the current machine to the new one, what should I do next in order to make sure everything is up and running.
 
Once I have moved the disks from the current machine to the new one, what should I do next in order to make sure everything is up and running.

Normally nothing. If it boots up, everything works as expected. The hardest part is to get it to boot. That's the beauty of Linux for decades. Just move disks, boot up and enjoy.
 
maybe you have to adapt the network config to a new ethX or enpX value
 
maybe you have to adapt the network config to a new ethX or enpX value
you are right.
The system did boot up as expected and even the ip address on the local console showed the same IP address as before
However the ip address was unreachable on the network.
The /etc/udev/rules.d/70-persistent-net.rules file was also empty
Since this was a new install, I ended up reinstalling proxmox
However, for future reference, it would be good to know how to readapt the network config on proxmox 5.
 
link removed
Not sure if that would have solved the problem.
I understand that older versions of proxmox would create a persistent file at /etc/udev/rules.d/70-persistent-net.rules that would associate the NICs MAC with the interface address
In case of a hardware change, you could simply delete that file and reboot for a fresh configuration to be written

the current version however does not have this file anymore (at least at the location mentioned above) so post the bootup, while the network configuration appears to be correct at a physically connected console, the network interface never actually comes up
 
the current version however does not have this file anymore (at least at the location mentioned above) so post the bootup, while the network configuration appears to be correct at a physically connected console, the network interface never actually comes up

Yes, you have to change the network settings to reflect your new network devices (names), that are named corresponding to their physical location on the pci slot basis.