No Network Adapter in fresh Windows Server after Upgrade to Proxmox 7

have to use win svr in the home/work lab, :( hit this hurldle also and followed this thread
- PVE Ver 7.0-8
- WIndows ISO (known working) - Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO
- machine type q35

qm config:
boot: order=ide0;ide2;net0
cores: 2
ide0: local-ssd-raid1:vm-105-disk-0,size=40G
ide2: local-wvc-nas:iso/Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO,media=cdrom
machine: pc-q35-6.0
memory: 4096
name: SVR1
net0: virtio=26:3D:1D:50:62:99,bridge=vmbr1,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=2bb253a6-6b29-4197-829c-4900ab26030a
sockets: 2
vmgenid: 0a3edca8-6a87-48c8-b68e-0c0d35b10f9a

No network adapters listed in the OS... Looking for solutions.

Just loading Server 2019 and Server 2022 as review
- 17763.737.190906-2324.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us_1.iso
- 20348.169.210806-2348.fe_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso

Will report on 2019 and 2022.
 
Setup
- PVE Ver 7.0-8
- WIndows ISO (known working) - Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO
qm config:
boot: order=ide0;ide2;net0
cores: 2
ide0: local-ssd-raid1:vm-105-disk-0,size=40G
ide2: local-wvc-nas:iso/Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO,media=cdrom
machine: pc-q35-6.0
memory: 4096
name: SVR1
net0: virtio=26:3D:1D:50:62:99,bridge=vmbr1,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=2bb253a6-6b29-4197-829c-4900ab26030a
sockets: 2
vmgenid: 0a3edca8-6a87-48c8-b68e-0c0d35b10f9a

Result
No network adapters listed in the OS
---

Setup
- PVE Ver 7.0-8
- 17763.737.190906-2324.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us_1.iso = Windows Server 2019
qm config:
boot: order=ide0;ide2;net0
cores: 2
ide0: local-ssd-raid1:vm-106-disk-0,size=40G
ide2: local-wvc-nas:iso/17763.737.190906-2324.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us_1.iso,media=cdrom
machine: pc-q35-6.0
memory: 4096
name: SVR2019
net0: virtio=FE:0A:34:1C:69:98,bridge=vmbr1,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=2a456ee8-0be1-4a4a-8a97-5ee72b23c5f9
sockets: 2
vmgenid: 4a77344a-01d3-42d6-8e0e-2aa4b13d4bf5

Result
No network adapters listed in the OS

Setup
- PVE Ver 7.0-8
- 17763.737.190906-2324.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us_1.iso = Windows Server 2019\
- switched net adapter type to e1000
qm config:
boot: order=ide0;ide2;net0
cores: 2
ide0: local-ssd-raid1:vm-106-disk-0,size=40G
ide2: local-wvc-nas:iso/17763.737.190906-2324.rs5_release_svc_refresh_SERVER_EVAL_x64FRE_en-us_1.iso,media=cdrom
machine: pc-q35-6.0
memory: 4096
name: SVR2019
net0: e1000=FE:0A:34:1C:69:98,bridge=vmbr1,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=2a456ee8-0be1-4a4a-8a97-5ee72b23c5f9
sockets: 2
vmgenid: 4a77344a-01d3-42d6-8e0e-2aa4b13d4bf5

Result

Adapter found ..... e1000 is the fix for me.

---

Setup
- PVE Ver 7.0-8
- 20348.169.210806-2348.fe_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso = Windows Server 2022
- switched net adapter to an e1000 for this test.
qm config:
boot: order=ide0;ide2;net0
cores: 2
ide0: local-ssd-raid1:vm-105-disk-0,size=40G
ide2: local-wvc-nas:iso/20348.169.210806-2348.fe_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso,media=cdrom
machine: pc-q35-6.0
memory: 4096
name: SVR2019
net0: e1000=CE:45:B5:48:8A:30,bridge=vmbr1,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=cbda461c-18f4-4f55-b953-0e2679ccc901
sockets: 2
vmgenid: 78ccb0f4-de17-4230-a652-bcd45711e365

Result
Network adapter dsicovered!
 
My freshly installed Win10pVM (from a correct Win10_21H1_German_x64.iso) on a PVE7.0-13 non-production-repro / Xeon E3-1275 v6 / Chipset C236 (fujitsu D3417-B2, no IOmmu in BIOS configurable) recognized the configured network-adapter, but did not use it, an error was shown in the Win10-device-manager. I even could not configure any network ip-adress etc. Thanx to this thread, I changed the machine-modell from pc-i440fx-6.0 to pc-q35-v6.0, but the VM did not start. Then I reinstalled the Win10pVM with machine-modell pc-q35-v6.0 and now Win10 uses the network-adapter. I installed virtio-win-gt-x64, reconfigured hd and network to virtio-drivers, rebooted Win10 and now the Win10VM runs smoothly!
 
Last edited:
Hi,
I'm having much the same issue.
While installing fresh Win10Pro of various Builds works fine, also the migration of linux based VMs from VMWare, the migration of existing Win2k16 servers does not.
The servers report the ethernet adapter as working with the newest drivers, but the network center doesn't show a single adapter.

Switching from pc-i440fx to q35 crashed the VMs for good ("inaccessible boot device" although the hds are still the same).

As we tested this migration a few weeks ago with the latest proxmox 6.4 and it worked quite well it seems an issue with px7.

Unfortunately we upgraded all nodes in the cluster to 7 before the final migration step because of an issue with some hardware. Everything (old and new Linux VMs, new Win10 VMs) works as it should, only the key VMs do not.

Any ideas?
 
Just a reminder: After changing network configurations of a node like adding a bridge, You do have to push the button "Apply Configuration".

It was introduced to execute several changes at once - very helpfull, but sometimes an unnoticed stumbeling block in the hurry of daily labor, because node-network is the only config with such an "apply all changes at once" button. Without leads to error messages like "network adaptor does not exists" (or similar).
 
Wolfgang Leithner said:
Hi,
I'm having much the same issue.
While installing fresh Win10Pro of various Builds works fine, also the migration of linux based VMs from VMWare, the migration of existing Win2k16 servers does not.
The servers report the ethernet adapter as working with the newest drivers, but the network center doesn't show a single adapter.

Switching from pc-i440fx to q35 crashed the VMs for good ("inaccessible boot device" although the hds are still the same).

As we tested this migration a few weeks ago with the latest proxmox 6.4 and it worked quite well it seems an issue with px7.

Unfortunately we upgraded all nodes in the cluster to 7 before the final migration step because of an issue with some hardware. Everything (old and new Linux VMs, new Win10 VMs) works as it should, only the key VMs do not.

Any ideas?
Click to expand...
Maybe running the MergeIDE_v3 Script to prepare Windows before migrating might help?
 
Hi
I can confirm, that the english iso is working, and the german one not. I had it even setup on q35.
 
ziraxas said:
Hi
I can confirm, that the english iso is working, and the german one not. I had it even setup on q35.
Click to expand...
Please set the Machine version to 5.1 as a workaround (for German Windows and report back.
 
  • Like
Reactions: zaphyre and ITT
That's because Windows is acting arbitrary and a big enough change in HW can trigger a reset/reinstallation of some device drivers, and changing machine versions may be enough for that, depending on the initial machine version the VM was created and other, more arcane things.
Sometimes one can try to force that by reinstalling it over the device manager, but that is not always a guaranteed solution either.
 
  • Like
Reactions: ITT
here too: pm 7.1-6 VM Windows Server 2016 q35 and 5.1 Networking works

Thank's
Best regards,
Christian
 
After creating the vms anew with q35 and importing the vmdks via qm importdisk the win servers came up quite nicely. installing the virtio ver 1.0.28 helped also.
 
Hy

we also have the same problem with german win 2k19 u 2k16.

A quick and dirty workaround ist the following. I will try to test more and make the workarount more efficient.
(Maybe its better delete the Nic from Hardware, install the driver, add device and start installation)

* Boot VM with Default (i440fx) 6.0
* Add the Attached 2 Regkeys to registry (Maybe ist better to User Current Control Set)
* install the driver: Pnputil /add-driver d:\netkvm\2k19\amd64\netkmv.inf /install
* reboot the server, maybe use "Stop"
* after Reboot, uninstall the VirtIO Nic if ErrorCode 56 is present
* Install Nic with "Automatisch nach aktualisierter Treibersoftware suchen"

Hope this can help

The Regkeys in the Attaches iso, delete the txt extension


kr
Roland
 

Attachments

  • Like
Reactions: KernelMaker and ciFlorian
What works for me while using German versions:

- setting VM hardware to Q35 v6.0
- install of Windows Server as usual (load drivers from the second ISO/DVD virtual io 208)
- install qemu-agent and missing drivers after first boot to desktop
- shut down the VM and change VM hardware to Q35 v6.1
 
  • Like
Reactions: sysbitnet
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom