[PVE-User] Intermittent NIC Connectivity after Host Upgrade to PVE

[JR Richardson]

You might want to update your packages directly and see if the kernel update is present, I'm using community repository and there is definitely a new kernel 4.15.18.-18-pve, since two days ago. I've been updating all my hosts nodes with it, but does still have the win2016 VirtIO NIC issue. So I'm switching all my Win2016 VMs to use the Intel E1000 NIC.

JR


I read the mention of kernel Linux proxmox 4.15.18-18-pve, but I just run the update and my kernel is still Linux proxmox 4.15.18-17-pve. I installation is licensed and I am supposed to have all the updates. I also see a bad problem with the network on Windows using virtio. I get 10% or less of the bandwidth of a physical virtual machine on the same network.


On Fri, Jul 12, 2019 at 7:32 AM JR Richardson <jmr.richardson at gmail.com>
wrote:

> Yes, I was using latest stable, them went to unstable, it worked for a 
> bit until reboot of VM then virtio-win-0.1.171.iso also failed. Intel 
> E1000 NIC seems to be stable with latest PVE kernel update.
>
> JR
>
>
>
> Have you tried virtio drivers 0.1.141 latest stable
>
>
>
> Wolfgang
>
>
>
> -----Urspr ngliche Nachricht-----
> Von: JR Richardson <jmr.richardson at gmail.com>
> Gesendet: Donnerstag 11 Juli 2019 14:02
> An: pve-user at pve.proxmox.com
> Betreff: Re: [PVE-User] Intermittent NIC Connectivity after Host 
> Upgrade to PVE
>
>
> Oddly enough, there was another kernel update yesterday, so I updated 
> and so far the intermittent network connectivity problem seems to have 
> went away.
> Problem appears on kernel: 4.15.18-17-pve but so far not on kernel:
> 4.15.18-18-pve.
>
> The issue with the VirtIO NIC driver is still present on Win2016. 
> Still have to run the Intel NIC on the VM.
>
> I will do some more testing today and follow up.
>
> Thanks.
>
> JR
>
>
> Are you able to boot on a previous kernel and see if the problem returns ?
>
> Gianni
>
> On Wed, 10 Jul 2019 at 16:06, JR Richardson <jmr.richardson at gmail.com>
> wrote:
>
> > Hi All,
> >
> > I recently upgraded a host within a 4 Node Cluster from 
> > pve-manager/5.2-5/eb24855a (running kernel: 4.15.18-1-pve) to
> > pve-manager/5.4-10/9603c337 (running kernel: 4.15.18-17-pve).
> >
> > I had several VMs running on the host node, some Win2016 Servers and 
> > Linux Servers. I migrated the VM off the host node, performed the 
> > upgrade, them migrated the VMs back to the upgraded host. All seemed 
> > to go well, next day I notices the Win2016 servers having 
> > intermittent network connectivity, Linux servers running fine. 
> > Performing continuous pings to Win2016 servers, the NIC were 
> > dropping for 45-60 seconds every hour or so, time was not 
> > consistent. I was using VitIO for NICs.
> >
> > I did windows update and this crashed the NICs, would not come up. I 
> > downloaded the latest virtio-win-0.1.171.iso and updated drivers, 
> > This did restore the NICs n the VMs but still have the network 
> > drops. I switched the VM NICs to Intel E1000 and still have the network drops.
> >
> > I don't see anything in the host node logs or the Win2016 VM logs 
> > indicating why the network drops periodically. Could this be a PVE 
> > kernel issue? I think this is more of a Win2016 issue, maybe the 
> > Intel NIC driver, its using the embedded Windows driver from 2010. 
> > Should I try downloading the latest driver from Intel?
> >
> > Dell R710 host node NICs:
> > Ethernet controller: Broadcom Limited NetXtreme II BCM5709 Gigabit 
> > Ethernet (rev 20) Ethernet controller: Intel Corporation 82576 
> > Gigabit Network Connection (rev 01)
> >
> > The NIC on the host for VMs is Broadcom. But the Linux hosts do not 
> > experience any drops so i don't think this is a host node or host 
> > kernel issue but I'm not sure.
> >
> > I appreciate any guidance.
> >
> > Thanks.
> >
> > JR