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

christian.g

Member
Jun 4, 2020
43
17
13
Hi everyone,

are there any known issues with networking inside Windows VMs and Proxmox 7?

2 days ago i installed a Windows Server 2016 VM without any problems.
Yesterday i did an upgrade of the Proxmox Cluster from latest 6 to 7.0-8.
Today i try to install a Windows Server 2016 VM (same ISO, same procedure, same virtio version 0.1.190) and the VM doesn't recognize the Network adapter although the virtio drivers are installed and Windows says that the device is working fine. Still the network connections panel is empty.
I tried different network devices (e1000, virtio) and machine types (pc-i440fx-5.2, pc-i440fx-6.0)
It doesn't make any sense to me.

Code:
# pveversion

proxmox-ve: 7.0-2 (running kernel: 5.11.22-1-pve)
pve-manager: 7.0-8 (running version: 7.0-8/b1dbf562)
pve-kernel-5.11: 7.0-3
pve-kernel-helper: 7.0-3
pve-kernel-5.4: 6.4-4
pve-kernel-5.11.22-1-pve: 5.11.22-2
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph: 16.2.4-pve1
ceph-fuse: 16.2.4-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.0.0-1+pve6
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-4
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-9
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.1-1
proxmox-backup-file-restore: 2.0.1-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.2-4
pve-cluster: 7.0-3
pve-container: 4.0-7
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-9
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.4-pve1


Code:
# qm config 123

agent: 1
boot: order=virtio0;ide2;net0
cores: 2
ide0: hvshare:iso/virtio-win-0.1.196.iso,media=cdrom,size=486642K
ide2: hvshare:iso/SW_DVD9_Win_Svr_STD_Core_and_DataCtr_Core_2016_64Bit_German_-3_MLF_X21-30352.ISO,media=cdrom
machine: pc-i440fx-5.2
memory: 8192
name: test01
net0: virtio=FA:4C:DC:09:4B:42,bridge=vmbr0,firewall=1,tag=910
numa: 0
onboot: 1
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=6728accf-234d-4a51-abac-8b9934ff5b1a
sockets: 1
virtio0: hdd:vm-123-disk-0,size=50G
vmgenid: b629511a-a4ae-434f-9465-3d04ecba9db6
 

Attachments

  • win2016-net-empty.png
    win2016-net-empty.png
    223.3 KB · Views: 111
Last edited:
  • Like
Reactions: lps90 and Borotes

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,537
920
163
works for me, just installed a fresh win2016 from ISO on latest Proxmox VE 7.0
 

christian.g

Member
Jun 4, 2020
43
17
13
Glad it works for you but it doesn't for me. I didn't change anything except for the upgrade to PVE 7.0.
Any suggestion on how to track this down? Networking on the Nodes and all existing VMs works fine.
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,537
920
163
Glad it works for you but it doesn't for me.
You asked if there are known issues with windows, the answer is no.

You have a vlan tag in your config, maybe you have an issue with vlan.
 

christian.g

Member
Jun 4, 2020
43
17
13
The VLANs do work without any problems on every existing machine.
A wrong configured VLAN should result in no network connectivity but not in the absence of the network card within the VM.
Every VM (Linux and Windows) which did exist prior the upgrade works fine as well as Linux VMs created after the upgrade.
Only newly created Windows VMs (2016 and 10 21H1) are affected, no matter what network device type is selected.

Update:
Windows 10 21H1 seems to work. It just took longer to activate the device.

Update:
I have now cloned an existing Windows 2016 VM, run sysprep and network is working fine. I'm using that one as a template for now.
New Windows 2016 installations still have no network card (also tested different ISOs)
 
Last edited:
  • Like
Reactions: Borotes

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,537
920
163
@tom Which machine type did you use during your test?

Just normal settings, here is my config:

Code:
# qm config 104

agent: 1
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
ide0: iso-templates:iso/virtio-win-0.1.196.iso,media=cdrom,size=486642K
ide2: iso-templates:iso/Win2016-1616-evaluation.ISO,media=cdrom
machine: pc-i440fx-6.0
memory: 4096
name: win2016-pve7
net0: virtio=92:07:07:3F:E2:D3,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsi0: local-lvm:vm-104-disk-0,cache=writeback,discard=on,size=64G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=b999ed35-e405-41c0-aa31-d9c7bf64c973
sockets: 1
vmgenid: ea5954b2-f5a7-4148-86b5-d5734483bac5
 
  • Like
Reactions: Borotes

christian.g

Member
Jun 4, 2020
43
17
13
My observations so far with Windows Server 2016

Fresh installation:
Doesn't work no matter what machine and network card type combination.

Clone of VM created with pc-i440fx-5.1 prior upgrade:
Works only with machine type it was initially created (pc-i440fx-5.1).
Changing the machine type to 5.2 or 6.0 results in the same error as a fresh installation.

Update:
Tested Windows Server 2019: Works without any problems.

So i have the following results:

Working (any machine type): Linux (only tested Debian buster), Windows 10 Pro, Windows Server 2019
Not Working (any machine type): Windows Server 2016

Any ideas?
 
Last edited:
  • Like
Reactions: Borotes

christian.g

Member
Jun 4, 2020
43
17
13
Most windows installation failures are caused by a corrupted installation ISO.
I can rule a corrupted ISO out as i tested 3 different ISOs and also did a fresh download from the MS Evaluation Center.

To rule out a problem with the Cluster nodes i tested the same on a standalone node which was upgraded today from PVE 6 to 7 (different physical Infrastructure and no VLAN).

Same result. Windows Server 2016 (any combination of pc-i440fx-5.1, pc-i440fx-6.0, e1000, virtio) is not able to use the network card. Drivers are installed, in Device Manager the Network card is ready and healthy but the Network connection panel remains empty. No network connectivity.

Code:
# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-1-pve)
pve-manager: 7.0-8 (running version: 7.0-8/b1dbf562)
pve-kernel-5.11: 7.0-3
pve-kernel-helper: 7.0-3
pve-kernel-5.4: 6.4-4
pve-kernel-5.0: 6.0-11
pve-kernel-5.11.22-1-pve: 5.11.22-2
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 14.2.21-1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.0.0-1+pve6
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-4
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-9
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.1-1
proxmox-backup-file-restore: 2.0.1-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.2-4
pve-cluster: 7.0-3
pve-container: 4.0-7
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
pve-zsync: 2.2
qemu-server: 7.0-10
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.4-pve1

Code:
# qm config 100
boot: order=virtio0;ide2;net0
cores: 1
ide0: syno2:iso/virtio-win-0.1.190.iso,media=cdrom,size=489986K
ide2: syno2:iso/Windows_Server_2016_STD_and_DataCt_64Bit_German.ISO,media=cdrom
machine: pc-i440fx-6.0
memory: 8192
name: win2016-test-vm01
net0: virtio=BA:27:B5:28:05:9D,bridge=vmbr0,firewall=1
net1: e1000=FA:C3:7E:40:42:FE,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=acdbbb4a-811e-445e-9d66-1011b323aeac
sockets: 1
virtio0: data:vm-100-disk-0,backup=0,size=32G
vmgenid: 88cb1315-b2de-44b5-972e-07d6b0c08860

Code:
# qm config 101
boot: order=ide0;ide2;net0
cores: 1
ide0: data:vm-101-disk-0,size=32G
ide2: syno2:iso/Windows_Server_2016_STD_and_DataCt_64Bit_German.ISO,media=cdrom
machine: pc-i440fx-5.1
memory: 8192
name: win2016-test-vm02
net0: e1000=BE:AD:8A:AB:D5:AA,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=f78e24a5-3554-41f4-9482-9f62fa78ff8f
sockets: 1
vmgenid: 812a9804-8eda-4d04-b4a7-180514539b96

Did you test on a fresh PVE 7 installation or on an upgraded one?
 
  • Like
Reactions: Borotes

Alternativende

Active Member
Aug 27, 2015
30
1
28
I have exactly the same problems here.

Im trying to install a Windows 20H2 with almost every machine and driver combination available, but with no success.
It just fails, even with IntelE1000 or Realtek devices.

Any suggestions?

Edit:
I have used a fresh installation of Proxmox btw..
 
Last edited:
  • Like
Reactions: Borotes

virusmoere

New Member
Jul 9, 2021
2
2
3
31
Same issue here. Fresh Proxmox 7 and Windows Server 2016 install.

Code:
pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-1-pve)
pve-manager: 7.0-9 (running version: 7.0-9/228c9caa)
pve-kernel-helper: 7.0-4
pve-kernel-5.11: 7.0-3
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.0.0-1+pve6
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-4
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-9
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.1-1
proxmox-backup-file-restore: 2.0.1-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.2-4
pve-cluster: 7.0-3
pve-container: 4.0-8
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-10
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.4-pve1

Code:
qm config 100
agent: 1
bios: ovmf
boot: order=virtio0;ide2
cores: 6
efidisk0: SSD:vm-100-disk-0,size=1M
ide2: local:iso/virtio-win.iso,media=cdrom,size=402812K
machine: pc-i440fx-6.0
memory: 16384
name: testserver
net0: virtio=F2:41:6A:C5:E6:D7,bridge=vmbr0
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=34aceb43-1343-4199-ba0e-f3db4f478610
sockets: 1
vga: virtio
virtio0: SSD:vm-100-disk-1,size=32G
vmgenid: 49326403-9838-49d3-b26e-7ce07394b0fa

2021-07-09 20_41_10-pve-eystrup-01 - Proxmox Virtual Environment and 12 more pages - Personal ...png
 
Last edited:
  • Like
Reactions: Borotes

Riddleuk

Member
Jul 9, 2021
35
0
6
44
After the odessy of issues today I have run into this as an issue as well. I made the bridge but I have no network connection inside any VM I create.

Tried open media vault
Ubuntu server
Windows 10

No networking at all.
 

HibikeChc

New Member
Jul 16, 2021
1
1
1
26
Hello, I also have the same problem when setting up a Windows server 2016 VM with a fresh install of Proxmox VE 7.0.
 
  • Like
Reactions: Borotes

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,537
920
163
Any comment from the Proxmox Team?
I added all my ideas already to this thread. As we do not see this issue in any of our tests, I am out of ideas, there must be something different in your setup.
 

christian.g

Member
Jun 4, 2020
43
17
13
there must be something different in your setup
As you can see, I'm not the only one having this issue and everything worked flawless until the upgrade.

From this thread we can already see that this issue affects
- Cluster setups
- single Node setups
- fresh PVE Installations
- upgraded PVE Installations
- different bare metal Hosts (Hardware)

Corrupted ISOs can be ruled out.
What else could be a source of this issue?

I'm happy to provide more Information, and i guess the others as well, to help you reproduce the issue.
 
  • Like
Reactions: lps90 and Borotes

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,537
920
163
I can rule a corrupted ISO out as i tested 3 different ISOs and also did a fresh download from the MS Evaluation Center.
Did you verify the checksum of the ISO after you moved it to your ISO storage? If yes, how? Did MS provide you checksum which you can compare?
 

Alternativende

Active Member
Aug 27, 2015
30
1
28
I tried two different ISOs which i´ve downloaded from VLSC. Unfortunately i have no access to the machine right now, but i will try it out on a brand new HP DL380 on Monday or Tuesday, next week.
 

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!

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 your own in 60 seconds.

Buy now!