[SOLVED] How do I prepare for this upgrade.

[godsavethequ33n]

I feel that right out the gate I might be lacking details so let me know what what else you might need from me.

I plan on dropping in a a new PCI card and I know it is going to shift addressing/naming and ultimately mess with my PCI passthrough, my NIC config (which is PCI), and whatever else I may have setup but forgotten about.

I believe I will loose network connectivity so I will need local access to make necessary changes to the /etc/interfaces (i think?) so I can get back to the WebUI and update the VMs I have PCI passthrough setup for.

Is there anything I can do to prep for this or make it more seamless?

 

[Dunuin]

Prepare your WebKVM or keyboard+display. Put in the PCI card, use the keyboard+display to edit your /etc/network/interfaces to match the new NIC name. Do a systemctrl restart networking and then your WebUI+SSH should be working again to fix PCI passthrough and so on.

 

[Neobin]

And disable auto-start, if you have it enabled now, at least for the VM(s) with PCI(e)-passthrough (better for all VMs and LXCs) before you install the new device.

 

[godsavethequ33n]

Thanks for the direction - Both of you! Much appreciated.

So my plan should look something like:

1. Have local Keyboard+Display ready
2. Backup current /etc/network/interface config
3. Disable auto start for VMs/LXCs
4. Shut down PM
5. Drop in new PCI device
6. Power on PM
7. Via local Keyboard+Display discover new NIC name.
8. Update /etc/network/interfaces/ with new NIC name.
9. Run 'systemctrl restart networking'
10. WebUI should be up - at this time update any PCI passthrough devices with new addresses via WebUI and start VMs/LXCs accordingly.

 

[Dunuin]

Thanks for the direction - Both of you! Much appreciated.

So my plan should look something like:

1. Have local Keyboard+Display ready
2. Backup current /etc/network/interface config
3. Disable auto start for VMs/LXCs
4. Shut down PM
5. Drop in new PCI device
6. Power on PM
7. Via local Keyboard+Display discover new NIC name.
8. Update /etc/network/interfaces/ with new NIC name.
9. Run 'systemctrl restart networking'
10. WebUI should be up - at this time update any PCI passthrough devices with new addresses via WebUI and start VMs/LXCs accordingly.

Jup, I would do it like that.
The reason why you shouldn't enable auto start of VMs with passthrough is that PVE could then passthrough a wrong device. Maybe it will passthrough something wrong like the RAM controller and not a NIC/GPU like intended and then autostarting a VM would crash the system each time you boot up your server before you would be able to edit your passthrough. You then would need to boot in rescue mode so VMs won't autostart and fix stuff in CLI.

And backing up guests using PBS/Vzdump + the "/etc" folder is also always a good idea. I don't think you will need them but its always good to have a recent backup.

 

[godsavethequ33n]

Jup, I would do it like that.
The reason why you shouldn't enable auto start of VMs with passthrough is that PVE could then passthrough a wrong device. Maybe it will passthrough something wrong like the RAM controller and not a NIC/GPU like intended and then starting a VM would crash the system each time you boot up your server before you would be able to edit your passthrough. You then would need to boot in rescue mode so VMs won't autostart and fix stuff in CLI.

I am 100% with you on that. It would cause issues with one of my VMs where I am passing through a PCI SATA Controller. Could end up a hot mess if it was passed through elsewhere or completely missing from its intended VM. So yes I defiantly understand the reasoning for this and I thank you for the suggestion!