[PVE-User] Problem with Centos 5.X virtio ethernet drivers and last PVE updates

richard lucassen mailinglists at lucassen.org
Fri Jul 24 16:01:07 CEST 2020


On Fri, 24 Jul 2020 08:07:34 +0200
Eneko Lacunza via pve-user <pve-user at lists.proxmox.com> wrote:

> What physical network interface make/model in Proxmox node?

# lspci | grep -i ether
02:00.0 Ethernet controller: Broadcom Limited NetXtreme II BCM5709
Gigabit Ethernet (rev 20)

02:00.1 Ethernet controller: Broadcom Limited NetXtreme II BCM5709
Gigabit Ethernet (rev 20)

07:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet
Controller (rev 06)

07:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet
Controller (rev 06)

The MAC adresses point to "Hewlett-Packard" in the MAC database and I'm
at 900km's from these machines so I can't tell you if it is the Intel or
the Broadcom. The loaded kernel modules are e1000e and bnx2.

R.

> El 23/7/20 a las 21:21, richard lucassen escribió:
> > On Thu, 23 Jul 2020 12:11:19 +0200
> > Roland <devzero at web.de> wrote:
> >
> > I run a Debian Lenny VM:
> >
> > # cat /etc/issue.net
> > Debian GNU/Linux 5.0
> >
> > # modinfo virtio_net
> > filename:       /lib/modules/2.6.26-2-686/kernel/drivers/net/virtio_net.ko
> > license:        GPL
> > description:    Virtio network driver
> > alias:          virtio:d00000001v*
> > depends:
> > vermagic:       2.6.26-2-686 SMP mod_unload modversions 686
> > parm:           napi_weight:int
> > parm:           csum:bool
> > parm:           gso:bool
> >
> > Proxmox host version 5.4:
> >
> > # cat /proc/version
> > Linux version 4.15.18-30-pve (root at nora) (gcc version 6.3.0 20170516
> > (Debian 6.3.0-18+deb9u1)) #1 SMP PVE 4.15.18-58 (Fri, 12 Jun 2020
> > 13:53:01 +0200)
> >
> > I upgraded from 4.15.18-27-pve to 4.15.18-30-pve and then the virtio
> > driver became very unstable. This machine has run for many years on
> > multiple versions of Proxmox (IIRC from version 1) without any
> > problem.
> >
> > R.
> >
> >> i see that my centos 5.11 VM should have support for virtio (see
> >> below) and according to https://access.redhat.com/articles/2488201
> >> rhel/centos supports this since 5.3.
> >>
> >> so if virtio worked before a proxmox update,  then i would call
> >> this a regression.
> >>
> >> can you tell which proxmox version worked for you with virtio ?
> >>
> >> i tested centos 5.11 installer on my older pve 6.0-4 (5.0.15-1-pve
> >> kernel) , but it does not find virtual disks.
> >>
> >> roland
> >>
> >> [root at hr-neu ~]# uname -aLinux hr-neu 2.6.18-398.el5 #1 SMP Tue
> >> Sep 16 20:50:52 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux
> >>
> >>
> >> [root at centos5 ~]# cat /etc/redhat-release
> >> CentOS release 5.11 (Final)
> >> [root at centos5 ~]# rpm -q kernel --changelog|grep virtio|grep 446214
> >> - [xen] virtio: include headers in kernel-headers package (Eduardo
> >> Pereira Habkost ) [446214]
> >> - [xen] virtio: add PV network and block drivers for KVM (Mark
> >> McLoughlin ) [446214]
> >> - [xen] virtio: include headers in kernel-headers package (Eduardo
> >> Pereira Habkost ) [446214]
> >> - [xen] virtio: add PV network and block drivers for KVM (Mark
> >> McLoughlin ) [446214]
> >>
> >> Am 23.07.20 um 10:22 schrieb richard lucassen:
> >>> On Tue, 21 Jul 2020 11:06:27 +0200
> >>> Michael Rasmussen via pve-user <pve-user at lists.proxmox.com> wrote:
> >>>
> >>>> On Tue, 21 Jul 2020 10:41:54 +0200
> >>>> richard lucassen <mailinglists at lucassen.org> wrote:
> >>>>
> >>>>> network. There is definitly something wrong somewhere.
> >>>>>
> >>>> The only thing wrong here is that you a running a version of
> >>>> RHEL/CentOS which is in maintenance support 2. This means there
> >>>> will be no more updates except critical bugs. As of March 31,
> >>>> 2017 it is considered in deep freeze!
> >>> I know. But sometimes you need to keep an old version and a good
> >>> way to handle this is to run such an old version in a virtual
> >>> environment. A vhost supplies virtual hardware and apparently this
> >>> virtual hardware has changed. This is not A Good Thing IMHO.
> >>>
> >>> It runs well under subversion 27 of the pve kernel but has stopped
> >>> under version 30. So I think this is a bug as I do not expect
> >>> design changes between subversion 27 and 30.
> >>>
> >>> R.
> >>>
> >
> 
> 


-- 
richard lucassen
https://contact.xaq.nl/



More information about the pve-user mailing list