11:06 a.m.
The problem isn’t with Ovirt 4.4.x, it’s the underlying red hat/centos 8 stream OS that no
longer supports the Emulex. So if you have an existing system, it should be easy enough to
switch to the EL Repo kernels and the proceed with the 4.4.10 updates. It’s a bigger
headache if you’re installing fresh, in which case using a different OS that supports
kernel drivers for your hardware should work.
Unless you’re using Ovirt Node, in which case I don’t think there’s a good solution for
that short of spinning your own with a custom kernel.
On Apr 14, 2022, at 12:57 AM, Thomas Kamalakis <thkam(a)hua.gr>
wrote:
Thanks Darrell
I think I understand your point, but it looks to me like such a bother to have to do
things like this. I will try starting from 4.4.9.
Could a solution be to install Debian and run kvm to install the ovirt-node? I guess
you waste some resources doing this but maybe worth it if you can skip all this kernel
business.
BR
Thomas
On Wed, Apr 13, 2022 at 10:35 PM Darrell Budic <budic(a)onholyground.com
<mailto:budic@onholyground.com>> wrote:
I hit this too, RH appears to have limited the supported PCI ids in their be2net and no
longer includes the Emulex OneConnect in the list of supported IDs. I switched to the EL
repo mainline kernels to resolve the issue on existing systems, it was a bit more fun on
systems needing new installs of 8.x. I think I settled on installing an older system,
switching kernels, and then upgrading to current.
Good luck,
-Darrell
> On Apr 13, 2022, at 12:12 AM, thkam(a)hua.gr <mailto:thkam@hua.gr> wrote:
>
> Hi
>
> We have a large number of HP servers where we use Ovirt and we are having problems
upgrading the nodes to Ovirt 4.4.10
>
> More specifically the servers have the Emulex OneConnect 10Gb NICs and what we did
in previous Ovirt node installations was to download the driver rpm (e.g.
kmod-be2net-12.0.0.0-8.el8_5.elrepo.x86_64.rpm) and then install it using "rpm -ivh
... " and carrying out "modprobe be2net"
>
> For 4.18.0-365 we could not find a separate rpm but it looks like this was included
in kernel-modules-4.18.0-365.el8.x86_64.rpm
(https://centos.pkgs.org/8-stream/centos-baseos-x86_64/kernel-modules-4.18...
<https://centos.pkgs.org/8-stream/centos-baseos-x86_64/kernel-modules-4.18...>)
which is already installed. "modprobe be2net" produces no errors but the network
interfaces do not show up in "ip -a" even after reboot.
>
> Are we missing something here, or is our infrastructure unusable with 4.4.10?
Things were working for 4.4.9.
>
> Thanks!
> _______________________________________________
> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-leave(a)ovirt.org
<mailto:users-leave@ovirt.org>
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
<https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
<https://www.ovirt.org/community/about/community-guidelines/>
> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AFSJ76ZGLMM...
<https://lists.ovirt.org/archives/list/users@ovirt.org/message/AFSJ76ZGLMM...
--
Dr. Thomas Kamalakis
Professor and Dean of the School of Digital Technology
Department of Informatics and Telematics, Harokopio University of Athens, Greece
Omirou 9, Tavros, Athens, GR17778, Tel: +302109549406,
Web: https://galaxy.hua.gr/~thkam <https://galaxy.hua.gr/~thkam>;, Github:
https://github.com/thomaskamalakis/ <https://github.com/thomaskamalakis/>