May 2025 - AlmaLinux Users - AlmaLinux List Archives

Re: Virtualbox fail with new almalinux kernel
by John Thompson 22 May '25

22 May '25

On 5/22/25 11:45, John Thompson via AlmaLinux Users wrote: > My almalinux-9.6 just updated to kernel 5.14.0-570.12.1.el9_6.x86_64 #1 > and Virtualbox can no longer load my virtual machines, failing with this > error: > > VirtualBox can't operate in VMX root mode. Please disable the KVM kernel > extension, recompile your kernel and reboot > > Anybody else seeing this? Following up on this, using rmmod to unload the kvm and kvm_intel kernel modules allows VirtualBox to load my virtual machines, but that still begs the question "why did this happen?" Looking at the .config files for the current and older kernels I have on my almalinux machine (5.14.0-503.38.1.el9_5.x86_64, 5.14.0-503.40.1.el9_5.x86_64, and 5.14.0-570.12.1.el9_6.x86_64), I see that CONFIG_X86_VMX_FEATURE_NAMES=y and CONFIG_VMXNET3=m are set in all of them, so why does it fail with VirtualBox only in the latest kernel? And does almalinux support a module blacklist in /etc/modprobe.d to prevent the kvm modules from loading in future reboots? -- -John (JohnDThompson(a)gmail.com) Appleton, WI USA

1 0

Virtualbox fail with new almalinux kernel
by John Thompson 22 May '25

22 May '25

My almalinux-9.6 just updated to kernel 5.14.0-570.12.1.el9_6.x86_64 #1 and Virtualbox can no longer load my virtual machines, failing with this error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot Anybody else seeing this? -- -John Thompson (johndthompson(a)gmail.com) Appleton WI USA

1 0

Re: Install sox in 9.6
by Stephen John Smoogen 21 May '25

21 May '25

On Wed, 21 May 2025 at 08:39, Jerry Geis via AlmaLinux Users < users(a)lists.almalinux.org> wrote: > > > On Wed, May 21, 2025 at 8:15 AM Jerry Geis <jerry.geis(a)gmail.com> wrote: > >> I do the following command to install sox and get an error: >> >> yum install sox >> Last metadata expiration check: 0:13:27 ago on Wed May 21 08:00:40 2025. >> No match for argument: sox >> Error: Unable to find a match: sox >> >> what? how do I install sox ? I tried dnf also >> >> Jerry >> >> > I did this: > yum install epel-release > yum install sox > > > my apologies for the email saying to do the above.. I didn't get this email until after I sent my reply. > that seemed to work > > Jerry > > _______________________________________________ > AlmaLinux Users mailing list -- users(a)lists.almalinux.org > To unsubscribe send an email to users-leave(a)lists.almalinux.org > -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren

1 0

Re: Install sox in 9.6
by Stephen John Smoogen 21 May '25

21 May '25

On Wed, 21 May 2025 at 08:15, Jerry Geis via AlmaLinux Users < users(a)lists.almalinux.org> wrote: > I do the following command to install sox and get an error: > > yum install sox > Last metadata expiration check: 0:13:27 ago on Wed May 21 08:00:40 2025. > No match for argument: sox > Error: Unable to find a match: sox > > what? how do I install sox ? I tried dnf also > > The package sox has not been built for the base EL operating systems but is available in the EPEL repository. Please try the following: dnf config-manager --set-enabled crb dnf install epel-release dnf install sox > Jerry > > _______________________________________________ > AlmaLinux Users mailing list -- users(a)lists.almalinux.org > To unsubscribe send an email to users-leave(a)lists.almalinux.org > -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren

1 0

Install sox in 9.6
by Jerry Geis 21 May '25

21 May '25

I do the following command to install sox and get an error: yum install sox Last metadata expiration check: 0:13:27 ago on Wed May 21 08:00:40 2025. No match for argument: sox Error: Unable to find a match: sox what? how do I install sox ? I tried dnf also Jerry

1 1

Re: tftp not working on almalinux 9
by Gerald Vogt 20 May '25

20 May '25

On 20.05.25 15:31, Jerry Geis via AlmaLinux Users wrote: > Hi - > > I followed these steps: > https://computingforgeeks.com/setup-tftp-server-on-centos-rhel-rocky- > linux/ <https://computingforgeeks.com/setup-tftp-server-on-centos-rhel- > rocky-linux/> Don't do that. Those instructions are often from people who really don't understand what they are doing. Step 2 messes everything totally up. Someone doesn't understand how systemd works and how to overwrite unit files... > now I get this: > systemctl status tftp-server.service > × tftp-server.service - Tftp Server > Loaded: loaded (/etc/systemd/system/tftp-server.service; enabled; > preset: disabled) > Active: failed (Result: resources) > TriggeredBy: ○ tftp-server.socket > Docs: man:in.tftpd > CPU: 0 > > May 20 08:27:27 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- > server.service: Cannot add dependency job, ignoring: Unit tftp- > server.socket has a bad unit file setting. As the error says: your tftp-server.socket is broken. Which probably comes because of step 2 above. # systemctl cat tftp-server.socket will show the content of the active configuration. > May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- > server.service: Got no socket. > May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- > server.service: Failed to run 'start' task: Invalid argument > May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: tftp- > server.service: Failed with result 'resources'. > May 20 08:27:28 VMWare.lsi.com <http://VMWare.lsi.com> systemd[1]: > Failed to start Tftp Server. > > > this is my file after removing start arguments: > more tftp-server.service > [Unit] > Description=Tftp Server > Requires=tftp-server.socket > Documentation=man:in.tftpd > > [Service] > ExecStart=/usr/sbin/in.tftpd /tftpboot > StandardInput=socket > > [Install] > WantedBy=multi-user.target > Also=tftp-server.socket > > STill does not start. Yes. Changing that file doesn't make sense either. The tftp-server.socket unit is broken. > What are the correct steps for setting up TFTP . The correct steps are fairly simple: # dnf -y install tftp-server # systemctl enable --now tftp.socket That's all what is necessary to get it running. After it's running, make necessary changes if you need something different. But that's done via the standard systemd overrides and not by putting different files with different names into /etc/systemd/system... I would recommend in your current setup to remove those copied files # /bin/rm /etc/systemd/system/tftp-server.service # /bin/rm /etc/systemd/system/tftp-server.socket # systemctl daemon-reload # systemctl enable --now tftp.socket And then check if you can access it... -Gerald

1 0

tftp not working on almalinux 9
by Jerry Geis 20 May '25

20 May '25

Hi - I followed these steps: https://computingforgeeks.com/setup-tftp-server-on-centos-rhel-rocky-linux/ now I get this: systemctl status tftp-server.service × tftp-server.service - Tftp Server Loaded: loaded (/etc/systemd/system/tftp-server.service; enabled; preset: disabled) Active: failed (Result: resources) TriggeredBy: ○ tftp-server.socket Docs: man:in.tftpd CPU: 0 May 20 08:27:27 VMWare.lsi.com systemd[1]: tftp-server.service: Cannot add dependency job, ignoring: Unit tftp-server.socket has a bad unit file setting. May 20 08:27:28 VMWare.lsi.com systemd[1]: tftp-server.service: Got no socket. May 20 08:27:28 VMWare.lsi.com systemd[1]: tftp-server.service: Failed to run 'start' task: Invalid argument May 20 08:27:28 VMWare.lsi.com systemd[1]: tftp-server.service: Failed with result 'resources'. May 20 08:27:28 VMWare.lsi.com systemd[1]: Failed to start Tftp Server. this is my file after removing start arguments: more tftp-server.service [Unit] Description=Tftp Server Requires=tftp-server.socket Documentation=man:in.tftpd [Service] ExecStart=/usr/sbin/in.tftpd /tftpboot StandardInput=socket [Install] WantedBy=multi-user.target Also=tftp-server.socket STill does not start. What are the correct steps for setting up TFTP . Thank you. Jerry

1 0

Re: New to Almalinux libnghttp2 needed
by Jerry Geis 19 May '25

19 May '25

On Mon, May 19, 2025 at 10:37 AM Jonathan Wright via AlmaLinux Users < users(a)lists.almalinux.org> wrote: > You probably need to enable the `CRB` repo as that's where the package > exists. > > You can do this with `sudo dnf config-manager --enable crb` > > [jonathan@jon-home ~]$ dnf info libnghttp2-devel > Last metadata expiration check: 0:00:06 ago on Mon 19 May 2025 09:34:07 AM > CDT. > Available Packages > Name : libnghttp2-devel > Version : 1.43.0 > Release : 6.el9 > Architecture : i686 > Size : 52 k > Source : nghttp2-1.43.0-6.el9.src.rpm > Repository : crb > Summary : Files needed for building applications with libnghttp2 > URL : https://nghttp2.org/ > License : MIT > Description : The libnghttp2-devel package includes libraries and header > files needed > : for building applications with libnghttp2. > > Name : libnghttp2-devel > Version : 1.43.0 > Release : 6.el9 > Architecture : x86_64 > Size : 52 k > Source : nghttp2-1.43.0-6.el9.src.rpm > Repository : crb > Summary : Files needed for building applications with libnghttp2 > URL : https://nghttp2.org/ > License : MIT > Description : The libnghttp2-devel package includes libraries and header > files needed > : for building applications with libnghttp2. > _______________________________________________ > AlmaLinux Users mailing list -- users(a)lists.almalinux.org > To unsubscribe send an email to users-leave(a)lists.almalinux.org dnf config-manager --enable crb Updating Subscription Management repositories. Unable to read consumer identity This system is not registered with an entitlement server. You can use subscription-manager to register. The above is what I get.... Jerry

2 4

New to Almalinux libnghttp2 needed
by Jerry Geis 19 May '25

19 May '25

I was moving along pretty good... I did: yum install libnghttp2 then I tried yum install libnghttp2-devel and got "not found" What command do I use to instal the -devel for nghttp2 ? Thanks Jerry

2 1

Setup of default route on multi-homed host
by James Fait 15 May '25

15 May '25

I have a system that is using Almalinux 8.10 that has several active networks for the segregation of traffic according to purpose. Whenever this machine is rebooted, it is random on which interface is selected to be the default route, with two interfaces being selected for default route, only one of which actually connects to the outside network. How can I force that the true default route is always chosen? I have attached the output of the route command before and after deleting the erroneous route. Thanks in advance for your assistance. ## Routing tables after power cycle -- no outside internet access $ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 10.57.30.1 0.0.0.0 UG 100 0 0 eno2 default pancho208 0.0.0.0 UG 101 0 0 eno4 10.57.0.0 0.0.0.0 255.255.0.0 U 100 0 0 eno2 ###.54.208.0 0.0.0.0 255.255.255.0 U 101 0 0 eno4 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 $ sudo route del default # delete the first route ## Routing tables with working outside internet $ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default pancho208 0.0.0.0 UG 101 0 0 eno4 10.57.0.0 0.0.0.0 255.255.0.0 U 100 0 0 eno2 ###.54.208.0 0.0.0.0 255.255.255.0 U 101 0 0 eno4 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0

1 0