From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 56070658DE for ; Thu, 23 Jul 2020 21:21:53 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2BAD92BAFD for ; Thu, 23 Jul 2020 21:21:53 +0200 (CEST) Received: from ssl1.xaq.nl (ssl1.xaq.nl [IPv6:2001:985:6a0f:64::24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 3DAD32BAF0 for ; Thu, 23 Jul 2020 21:21:51 +0200 (CEST) Received: from x2go.xaq.nl (x2go.utr.xaq.nl [192.168.64.48]) by ssl1.xaq.nl (Postfix) with ESMTPSA id 385627F708 for ; Thu, 23 Jul 2020 21:21:44 +0200 (CEST) Date: Thu, 23 Jul 2020 21:21:43 +0200 From: richard lucassen To: pve-user@lists.proxmox.com Message-Id: <20200723212143.58e743b84615aeb85a031e19@lucassen.org> In-Reply-To: <8e14f866-ef7a-e7d3-1bb1-36a10ea4f9cb@web.de> References: <1506136562.36294.1595313175981.JavaMail.zimbra@zimbra.panservice.it> <20200721104154.0f2188d06a622942fddb7cab@lucassen.org> <20200723102253.b991fc7e31f4e92f54a87500@lucassen.org> <8e14f866-ef7a-e7d3-1bb1-36a10ea4f9cb@web.de> Reply-To: pve-user@lists.proxmox.com Organization: XAQ Systems X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.425 Adjusted score from AWL reputation of From: address KAM_DMARC_NONE 0.25 DKIM has Failed or SPF has failed on the message and the domain has no DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -1.703 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_SOFTFAIL 0.972 SPF: sender does not match SPF record (softfail) Subject: Re: [PVE-User] Problem with Centos 5.X virtio ethernet drivers and last PVE updates X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2020 19:21:53 -0000 On Thu, 23 Jul 2020 12:11:19 +0200 Roland wrote: I run a Debian Lenny VM: # cat /etc/issue.net=20 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: =20 vermagic: 2.6.26-2-686 SMP mod_unload modversions 686=20 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@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. >=20 > so if virtio worked before a proxmox update,=A0 then i would call this a > regression. >=20 > can you tell which proxmox version worked for you with virtio ? >=20 > 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. >=20 > roland >=20 > [root@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 >=20 >=20 > [root@centos5 ~]# cat /etc/redhat-release > CentOS release 5.11 (Final) > [root@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] >=20 > Am 23.07.20 um 10:22 schrieb richard lucassen: > > On Tue, 21 Jul 2020 11:06:27 +0200 > > Michael Rasmussen via pve-user wrote: > > > >> On Tue, 21 Jul 2020 10:41:54 +0200 > >> richard lucassen 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. > > --=20 richard lucassen https://contact.xaq.nl/