KVM Windows VMs and losing network connectivity

B

badly_connected

New Member
Jul 9, 2015
3
0
1
Hi,

I have an issue with some Windows Server 2012 VMs that are running on Proxmox 5.1-41 with KVM.
Suddenly the VMS goes "down" and accessing from the console i can see the Windows network icon with an exclamation point indicating that the connection is not reaching internet properly.

The solution for fix this is easy and is enough
1. disable the network card from Windows
2. enable again the card and magically starts to work again.

This is happening on two different proxmox installations running the same version: 5.1-41
The virtual machines are all configured to use a virtual IntelE1000 Network Card and i'm using a bridge network with Proxmox with no strange configuration, just the default vmbr0 interface.

Somebody had the same issue and have suggestions? i'm getting crazy to find a way to fix this.

Thank you
 
change network card to VirlIO.
You can install driver from virtio-win-0.1.141.iso .
I test the "virtio-win-0.1.149.iso " network card driver have same bug like you.
 
Hi,

ah ok happy to be not the only one with this strange issue, ok i will try with Virtio+1.141 drivers, i've downloaded virtio-win-0.1.141.iso i guess is the file you told me.

Thank you so much!
 
Hi

I have the same problem with Proxmox 5.2.3 and Windows 2012 R2. It happens with virtio and E1000 drivers. There is no entry in the Windows-, or Proxmox log, it just looses connectivity and the only way to fix this is to disable/enable the NIC or reboot the VM.

There seems to be a relation between high network-, and maybe also also system load of the VM, but i could not reproduce it.

Any hint to fix this problem is welcome :)

Thanks
Michael


--------------------
SW version :
proxmox-ve: 5.2-2 (running kernel: 4.15.17-3-pve)
pve-manager: 5.2-3 (running version: 5.2-3/785ba980)
pve-kernel-4.15: 5.2-3
pve-kernel-4.15.17-3-pve: 4.15.17-13
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-34
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-9
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-1
openvswitch-switch: 2.7.0-2
proxmox-widget-toolkit: 1.0-19
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-4
pve-firewall: 3.0-12
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-29
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9
----------------------
Windows 2012R2 (6.3.9600 Build 9600)
----------------------
E1000 NIC driver --> Microsoft version 8.4.13.0
----------------------
VirtIO NIC driver --> 0.1.141 (from the so named ISO)
----------------------



badly_connected said:
Hi,

I have an issue with some Windows Server 2012 VMs that are running on Proxmox 5.1-41 with KVM.
Suddenly the VMS goes "down" and accessing from the console i can see the Windows network icon with an exclamation point indicating that the connection is not reaching internet properly.

The solution for fix this is easy and is enough
1. disable the network card from Windows
2. enable again the card and magically starts to work again.

This is happening on two different proxmox installations running the same version: 5.1-41
The virtual machines are all configured to use a virtual IntelE1000 Network Card and i'm using a bridge network with Proxmox with no strange configuration, just the default vmbr0 interface.

Somebody had the same issue and have suggestions? i'm getting crazy to find a way to fix this.

Thank you
Click to expand...
 
  • Like
Reactions: Tmanok
change network card to VirlIO.
You can install driver from virtio-win-0.1.141.iso .
mholoubek said:
Hi

I have the same problem with Proxmox 5.2.3 and Windows 2012 R2. It happens with virtio and E1000 drivers. There is no entry in the Windows-, or Proxmox log, it just looses connectivity and the only way to fix this is to disable/enable the NIC or reboot the VM.

There seems to be a relation between high network-, and maybe also also system load of the VM, but i could not reproduce it.

Any hint to fix this problem is welcome :)

Thanks
Michael


--------------------
SW version :
proxmox-ve: 5.2-2 (running kernel: 4.15.17-3-pve)
pve-manager: 5.2-3 (running version: 5.2-3/785ba980)
pve-kernel-4.15: 5.2-3
pve-kernel-4.15.17-3-pve: 4.15.17-13
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-34
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-9
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-1
openvswitch-switch: 2.7.0-2
proxmox-widget-toolkit: 1.0-19
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-4
pve-firewall: 3.0-12
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-29
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9
----------------------
Windows 2012R2 (6.3.9600 Build 9600)
----------------------
E1000 NIC driver --> Microsoft version 8.4.13.0
----------------------
VirtIO NIC driver --> 0.1.141 (from the so named ISO)
----------------------
Click to expand...
 
it will take a few days to do another load test on this VM and a few more to upgrade the kernel. i'll be back with more information and test results, as soon as i can.

thanks for now
Michael


tom said:
Please test with latest stable kernel (4.15.18-4-pve), any improvement?

And try also latest virtio-win drivers: 0.1.160
Click to expand...
 
Are there any updates on this issue. I have just had a Windows VM on a new proxmox 5.2 install suffer exactly the same symptoms. Loss of network connectivity, only restored by a vm reboot or disable/reenable of NIC.
 
Since my last post, everything is working stable and without any problems. I planed to to load tests on the VM as soon as the NIC fails to work again, but it works for 7 days now. The only thing i did, was to add a new VirtIO device for the VM in Proxmox(driver 0.1.141) and disable the existing E1000 in Windows.
I have no idea what caused the problems or made it work until now ......

tomstephens89 said:
Are there any updates on this issue. I have just had a Windows VM on a new proxmox 5.2 install suffer exactly the same symptoms. Loss of network connectivity, only restored by a vm reboot or disable/reenable of NIC.
Click to expand...
 
I tell you only VirtIO device for the VM(driver 0.1.141) . my vm works for half of year now. E1000 and latest virtio-win drivers in Windows have bug .I am not good at English.
mholoubek said:
Since my last post, everything is working stable and without any problems. I planed to to load tests on the VM as soon as the NIC fails to work again, but it works for 7 days now. The only thing i did, was to add a new VirtIO device for the VM in Proxmox(driver 0.1.141) and disable the existing E1000 in Windows.
I have no idea what caused the problems or made it work until now ......
Click to expand...
 
Hi

As i wrote to you before ..... i had this problems with E1000 and VirtIO NIC and i used the 0.1.141 driver! Now it works and the only difference is, that i have not removed the unused/faulty E1000 NIC from the VM, just deactivated it in the virtual Windows and added a new VirtIO NIC with the same driver than before.
I have no explanation why it works now, but it does and i will post here again as soon as it fails again.


Michael


hitsword said:
I tell you only VirtIO device for the VM(driver 0.1.141) . my vm works for half of year now. E1000 and latest virtio-win drivers in Windows have bug .I am not good at English.
Click to expand...
 
Resurrecting an old thread here, but I'm experiencing the same issue on 6.0 using VirtIO 171 drivers. I just updated all my guests to the VirtIO 173 drivers so I will pay attention if it happens again. Like mholoubek, I believe I've also seen the issue with a windows guest using e1000. I will pay more attention to the specifics if/when I see the issue again. It happens somewhat infrequently and randomly, but it seems like there is a correlation with rebooting the guest such as for windows updates.

I've only seen it with Windows guests. None of my Linux guests have ever experienced it.

Anybody ever experienced this issue while using openVSwitch? I've got a few other proxmox clusters which all use OpenVSwitch, and I've never seen the issue there. Although those run mostly linux guests which means that it would be less likely to see the issue. The host that I've been seeing the issue with now is a single box using a basic linux bridge vmbr0. No vlans, no openvswitch, nothing fancy.
 
Same issues guys.
It seems to crash the Windows network when the network interface is overloaded. Like a backup or a file transferring.
Proxmox 5.3-11. VM Windows 2016
e1000 or VirtIO same problem.
Thanks in Advance!
 
Last edited:
I can confirm this. I also facing the same issue. Windows VMs lose connectivity after some time. I'm using an intel driver before and switch to virtio driver now. I'll keep monitor with this

In windows server event viewer I can see many logs with event ID 10001 and message disconnected.

I'm using OVS bonds with LACP and OVS bridges. There are no logs related to this on OVS logs
 
Update from my environment.
OPenVswitch
Proxmox 6.1-7
Virtio Drivers 173

I just experienced the disconnect issue a couple more times yesterday with a Windows Server 2019 VM. I notice it mostly that *sometimes* on booting up from a reboot the NIC will fail to pass traffic. It seems to happen on *some* reboots, but definitely not all. As in the past. Either rebooting the VM again, or disconnecting the NIC and reconnecting it (either from within windows or from the hardware tab in proxmox) will get the NIC working again.

I have two vms that are configured identically, and were cloned from the same template. One of them experienced the issue twice last night. The other one did not. (both VMs were getting the same application installed on them last night, hence the reboots)

I have tried to reproduce the issue on a 3rd VM (also cloned from the same template) by rebooting it many times this morning. I have been unable to reproduce it this morning. I also tried loading the NIC heavily as Cristiano and Luca reported that it does it when the NIC is under heavy load. I ran an iPerf test from a VM to the hypervisor for 1 hour, passing 11.5-12Gbps the entire time. The network stayed up.
 
I can also confirm this. Two identical windows VMs and one VM getting this network hiccup. I had to restart the network adapter within the windows vm to fix. both using intel NICs
 
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
Back