Hyper-V cluster and OpnSense migration?

[cyclone3d]

I've got a 3-node Hyper-V cluster running on Server 2025 Datacenter.

One of the VMs is OpnSense.

Whenever I try migrating the OpnSense server to another host, it loses connection.

I've verified the vswitches are identical between the hosts as well as identical physical switch settings.

It is the only VM that is causing me trouble as of now.

I've also tried rebooting OpnSense, disabling and re-enabling the NICa on the host and also shut and no shutting the ports on the switch.

The only thing left to do for diagnostics is to look at the config through the CLI and verify that it is seeing the same NICs as on the original host, but when it boots, it doesn't say anything about not finding the NICs.

Oh yeah, MAC spoofing is also enabled for the OpnSense VM as was recommended as a possible solution via the interwebs.

 

[CrimsonKnight13]

I generally find Hyper-V to be absolute trash... Have you tested migration with any other hypervisors like Proxmox VE?

 

[Nobu]

Are the hosts on the same network, static IP? They (the VMs) aren't both running at the same time, no other possible IP conflicts?

The host is still up, it's just the opnsense vm that isn't working?

 

[stormy1]

To fix network connection issues after replacing a network card in OPNsense, you must re-bind your logical interfaces (WAN/LAN) to the new physical ports.

I am betting that when it moves the network ports become unbound.
Google the above line to find out how to fix it.

 

[cyclone3d]

Just to update this, I got it figured out later that day.

Had to disable some hardware acceleration for the NICs and also enable MAC spoofing (think that was what it was) and then everything just started working as expected.