windows 2019, virtio configuration

[puzon]

Hi.
I have few vm's with Windows 2019 std. Everytime i add some hardware like cdrom (on proxmox hardware), shutdown vm and start it again - Red hat virtio network driver is down (screenshot). I need to uninstall it (on windows side), add it again and do all network manual configuration for this.
I try add bridge_hw to vmbr interface - no effect.
i try to update redhat drivers - no effect

thanks for help.
Proxmox 6.4-13, windows 2019 with all updates,

 

[Moayad]

What version of virtio that you are using?

 

[puzon]

0.1.208
Redhat Virtio Ethernet adapter:
Driver date: 30.08.2021
Driver version: 100.85.104.20800

as i mention - it was updated from previous version (from 2020 as far as i remember).

 

[Moayad]

I can't reproduce it on my side. could you please post the VM config qm config <VMID> and the output of pveversion -v

 

[puzon]

Sure.

agent: 1
balloon: 2048
bootdisk: virtio0
cores: 4
cpu: IvyBridge
hotplug: disk,network,usb,memory,cpu
machine: q35
memory: 8192
name: REP-VM102-AD
net0: virtio=16:34:E5:61:79:D7,bridge=vmbr1,firewall=1
numa: 1
onboot: 1
ostype: win10
parent: przed_upd_ad2
sata2: none,media=cdrom
scsihw: virtio-scsi-pci
smbios1: uuid=3574280a-8ec0-442c-a2cc-96488c72944b
sockets: 1
tablet: 1
vga: virtio
virtio0: pool01:vm-102-disk-0,cache=writeback,size=240G
virtio1: pool01:vm-102-disk-5,backup=0,cache=writeback,iothread=1,size=15000G
virtio4: pool01:vm-102-disk-4,backup=0,cache=writeback,iothread=1,size=15000G
vmgenid: 300448c7-a395-4f19-bd9b-09e7dd387c7a

proxmox-ve: 6.4-1 (running kernel: 5.4.157-1-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)
pve-kernel-5.4: 6.4-11
pve-kernel-helper: 6.4-11
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.157-1-pve: 5.4.157-1
pve-kernel-5.4.140-1-pve: 5.4.140-1
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.101-1-pve: 5.4.101-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
ceph: 14.2.22-pve1
ceph-fuse: 14.2.22-pve1
corosync: 3.1.5-pve2~bpo10+1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve4~bpo10
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.22-pve2~bpo10+1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-4
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.13-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-1
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.3-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.6-pve1~bpo10+1

 

[Moayad]

Have you tried to add additional NIC to the Windows VM?

 

[puzon]

No. i need just one - why?

 

[Moayad]

Hi,

No. i need just one - why?

It's just for testing

 

[puzon]

Sorry for delay - tested and after stop vm, move it to another host and start again - both networks fail. need to uninstall (under windows), rescan and made all configs.