Fresh Windows 10 install stuck loading Redhat VirtIO network

IsThisThingOn

New Member
Nov 26, 2021
8
0
1
122
Hi everyone

I am using pve-manager/7.1-6, latest Windows 10 H2 and virtio 0.1.208.
I followed this guide: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices
but the VM gets stuck when I try to load the network drivers. Balloning and iSCSI drivers work.

After installing Windows 10 without any network, guest agent installation gets stuck at installing virtio-win-drivers.
If I try to install the driver by opening device manager and selecting NetKVM\W10\amd64 it also gets stuck.
 
Last edited:

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
7,595
905
163
33
Vienna

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,502
893
163
Please post your:

> pveversion -v

and:

> qm config VMID

and your physical hardware (CPU and Mainboard)
 

IsThisThingOn

New Member
Nov 26, 2021
8
0
1
122
Saw your post to late and already purged the VM for a new one. Setting it up in English right now.

Code:
proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve)
pve-manager: 7.1-6 (running version: 7.1-6/4e61e21c)
pve-kernel-5.13: 7.1-4
pve-kernel-helper: 7.1-4
pve-kernel-5.11: 7.0-10
pve-kernel-5.4: 6.4-5
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
pve-kernel-5.4.128-1-pve: 5.4.128-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-15
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.4-3
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3

Intel(R) Xeon(R) E-2224 on a hpe proliant microserver gen10 plus
 
Jan 13, 2021
3
0
1
40
Just ran into the same problem. Does anyone know if there are any updates here? I sadly need a native German Win10 because the Software to be used in there is very sensitive to this (had lots of problems on native machines with english setup in the past....). Language pack did not help back then.

proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-12
pve-kernel-5.13: 7.1-9
pve-kernel-5.13.19-6-pve: 5.13.19-14
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-3
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-7
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1

agent: 1
boot: order=scsi0;ide2;net0;ide3
cores: 4
ide2: local:iso/Win10_21H2_German_x64.iso,media=cdrom,size=5760336K
ide3: local:iso/virtio-win-0.1.215.iso,media=cdrom,size=528322K
memory: 8192
meta: creation-qemu=6.1.0,ctime=1647202026
name: jtl-win10
net0: virtio=62:84:AE:DE:7F:39,bridge=vmbr0,firewall=1
numa: 1
ostype: l26
scsi0: local-zfs:vm-100-disk-0,discard=on,size=100G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=0bf231f6-1b4c-49a8-8ac9-32b39cea604b
sockets: 1
vmgenid: cc0714d6-08d4-431f-b0c0-11faf6848e81

the install is stuck for some time and then fails with this error ->
 

Attachments

  • Screenshot from 2022-03-13 21-35-57.png
    Screenshot from 2022-03-13 21-35-57.png
    86.7 KB · Views: 4
Last edited:

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!