[SOLVED] Hyper-V VM moved to Proxmox no longer has networking adapter

[marie.o]

A running Windows Server 2016 VM shall move to Proxmox - It boots up on our 7.1.4 Proxmox node just fine, but reports no network connection, even though the definition says to have E1000 NIC, and the E1000 NIC does show up in the device manager without an exclamation mark, but as running.

I've tried the Realtek (which comes up like the Intel one in device manager as working), I have tried the VirtIO one, which comes up in device manager as missing driver, but the driver installation fails with (german) error message

Basically: Error installing driver - The process was returned due to timeout.

Anyone has an idea, how to proceed?

I already tried removing all previous NICs in the device manager, resetted the network with netsh et al.

Still no go.

Any and all help is greatly appreciated as I want to move a dozen or so VMs from Hyper-V to Proxmox to reduce the number of hypervisors in the company.

 

[marie.o]

Just to make sure that it is not related to a not upgraded system, I upgraded the node to 7.2-4 - same results.

 

[marie.o]

More information: Running the VM under Hyper-V Hypervisor inside our Proxmox 7.2-4 node works, but is not really a solution.

Anyone ever experienced something similar?

 

[mijanek]

Yes, that is common issue with german Widows server while using EN version with GER LP works well.
The sollution for you is to change the Machine to Q35-5.1 later versions won‘t work.

See here:

https://forum.proxmox.com/threads/windows-server-2022-deutsch-netzwerk-startet-nicht.102528

 

[marie.o]

Thank you very much, mijanek.

That did the trick. I have to work on my google fu, but I never expected the language to be the cause of issues. I know why I prefer to install server systems in English, but one has to work with what others provided.

Thanks again, and have a great week.

 

[RolandK]

qemu bug: https://gitlab.com/qemu-project/qemu/-/issues/774#note_1178918198