No Network on VM after Migration from Hyper-V

[kevinbrown1980]

Hi, I'm trying to move my home lab from Hyper-V to Proxmox but I'm running into issues migrating the VMs.

I rebuilt a webserver as a container in Proxmox and it works as it should but when I try to migrate the VMs across they all loose internet connection. I've followed the process of migration from a few guides on the forums (Export from Hyper-V - Import to Proxmox - Convert to QCOW etc) but no matter what type of NIC I put on them they don't have any connection.

Has anyone come across this before? or can anyone help please?

Thanks in advance!

 

[apoc]

Hm. When you configure an e1000 nic this should work right away. At least when we talk about win2012 and newer.
For virtio NICs you need the appropriate drivers to be installed first otherwise those don't get detected, as there are no inbuilt drivers in windows.

 

[kevinbrown1980]

Thanks for the advice tburger, I've gone through changing the NIC to all of the options and neither worked, the VMs are a mixture of Linux and Server 2019 if that makes any difference.

I will give it another try though just in case.

 

[apoc]

No it shouldn't.
If you change the nic to e1000: does the OS recognise the NIC? E.g. connect to the virtual Console and have you checked the NIC is seen there?
Linux has virtio drivers in the kernel since a long time. Only windows is "problematic".

 

[kevinbrown1980]

OK so, the Linux machines are Gen 1 in Hyper-V, they don't recognise the NIC at all.
The Windows Machines are Gen 2 in Hyper-V so are UEFI, they don't boot at all.

Do you think they need rebuilding?

 

[apoc]

Interesting. I would not have expected that.
Windows: if they are uefi, you need to setup the vms in proxmox as uefi as well.
Linux actually should have drivers for any of those NICs. Are you sure the NICs aren't recognised? Or is it potentially showing as a new nic and the configuration does not work?