search for: el9

Hello, some days ago I followed these instructions https://sigs.centos.org/virt/tdx/host/ and after enabling the repo I installed the tdx necessary bits as indicated, with the command dnf install kernel-tdx qemu-kvm-tdx libvirt-tdx This gave me: libvirt 9.5.0-1.el9s qemu-kvm 8.0.0-15.el9s kernel 5.14.0-395.el9s But now if I run a usual "dnf update" I'm proposed "standard" libvirt and qemu-kvm sw stack, I think because of their version apparently greater (10 vs 9.5 and 8.2 vs 8.0): Upgrading: libvirt...

Looks like the GPG key we use to sign our RPMs is not longer good with EL9: # rpm --import RPM-GPG-KEY-nwra error: RPM-GPG-KEY-nwra: key 1 import failed gpg key info: sec rsa2048/35DDB0B86218AC2F created: 2017-08-16 expires: never usage: SC trust: ultimate validity: ultimate ssb rsa2048/6A7FBC1E9DB22E8E created: 2017-08-16 expires: never...

Hi guys, Does your 'mock' work when used with 'centos-stream+epel-9-x86_64' config? It fails for me with every rpm packages I tried: -> $ mock -r centos-stream+epel-9-x86_64 --rootdir=~/mock --localrepo=/devs/var/www/dnf.repo --chain --continue rpmbuild/rpm.src/pass-1.7.4-6.el9.src.rpm ... CentOS Stream 9 - BaseOS 1.6 MB/s | 1.6 kB???? 00:00 The GPG keys listed for the "CentOS Stream 9 - BaseOS" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository.. Failing package is: a...

Hi, I've discovered an issue which I don't understand. On a new test install of EL9 I saw this message in the logs: Mar 01 08:09:18 <hostname> pcp-pmie[2870]: Low random number entropy available 15.6%avail at beta.corp.invoca.ch This is on a 64 core "AMD Opteron(tm) Processor 6282 SE" server but I also got the same low entropy on an EL9 KVM guest running on a &qu...

...9;mock' work when used with 'centos-stream+epel-9-x86_64' config? > It fails for me with every rpm packages I tried: > > -> $ mock -r centos-stream+epel-9-x86_64 --rootdir=~/mock > --localrepo=/devs/var/www/dnf.repo --chain --continue > rpmbuild/rpm.src/pass-1.7.4-6.el9.src.rpm > ... > CentOS Stream 9 - BaseOS 1.6 MB/s | 1.6 kB???? 00:00 > The GPG keys listed for the "CentOS Stream 9 - BaseOS" repository are > already installed but they are not correct for this package. > Check that the correct key URLs are configured for this repository....

...suggest an issue with networking / suspend between 388 and 391. Q: If I update, am I going to lose kernel 388? How can I persist that one specific kernel indefinitely and still be able to update the rest of the system? Mike # grubby --info=ALL | grep ^kernel kernel="/boot/vmlinuz-5.14.0-404.el9.x86_64" kernel="/boot/vmlinuz-5.14.0-391.el9.x86_64" kernel="/boot/vmlinuz-5.14.0-388.el9.x86_64" kernel="/boot/vmlinuz-0-rescue-aaab5fbe787947ec94b3c7574b9d41e6" # grubby --default-kernel /boot/vmlinuz-5.14.0-388.el9.x86_64

On 6/1/22 13:43, Fabian Arrotin wrote: > On 01/06/2022 19:51, Orion Poplawski wrote: >> Looks like the GPG key we use to sign our RPMs is not longer good with EL9: >> >> # rpm --import RPM-GPG-KEY-nwra >> error: RPM-GPG-KEY-nwra: key 1 import failed >> >> gpg key info: >> >> sec? rsa2048/35DDB0B86218AC2F >> ????? created: 2017-08-16? expires: never?????? usage: SC >> ????? trust: ultimate????? validity: u...

...gt; scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part2 -> ../../sdb2 I think it maybe caused by sd driver asynchronous scanning. I am lucky that I didn't see this before. nvme may have similar issues, but nvme has boot parameter to avoid it. Suse has boot parameter to avoid it. with EL9 we will wait until EL 9.3 if we are lucky. I had report issue: https://bugzilla.redhat.com/show_bug.cgi?id=2140017

? Wed, 8 May 2024 16:59:25 +0000 Simon Andrews <simon.andrews at babraham.ac.uk> ?????: > The lapack libraries are: > > $ rpm -qa | grep lapack > lapack-3.9.0-10.el9.x86_64 > lapack64_-3.9.0-10.el9.x86_64 > lapack64-3.9.0-10.el9.x86_64 > lapack-devel-3.9.0-10.el9.x86_64 Thanks for this information! I figured out I needed to enable the "PowerTools/CRB" repo, installed lapack-devel from there, and now I get the same configure output and the sa...

Hi All are there somewhere already xen and dom0 kernel packages for el9? --------- Greetz -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20220728/a16364af/attachment-0003.html>

...00143801722C0B0-part2 -> ../../sdb2 > > I think it maybe caused by sd driver asynchronous scanning. > I am lucky that I didn't see this before. nvme may have similar > issues, but nvme has boot parameter to avoid it. > Suse has boot parameter to avoid it. > with EL9 we will wait until EL 9.3 if we are lucky. > I had report issue: https://bugzilla.redhat.com/show_bug.cgi?id=2140017 Thanks for confirming that I'm not alone with this "feature" In the above example, it's much fun if you want to wipe the two partitions on /dev/disk/by-id/s...

Hi, I see some strange and dangerous things happening on a HPE server with HPE Smart Array controller where EL9 ends up with wrong device nodes/symlinks to the attached disks/raid volumes: (I didn't touch anything here but at 08:09 some symlinks were changed) /dev/disk/by-id/: lrwxrwxrwx 1 root root 9 Mar 1 07:57 scsi-0HP_LOGICAL_VOLUME_00000000 -> ../../sdc lrwxrwxrwx 1 root root 10 Mar 1 07:57 s...

...ory at 95000000 (32-bit, non-prefetchable) [size=256K] I/O ports at 1000 [size=128] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/4 Maskable- 64bit+ Kernel driver in use: ast Kernel modules: ast Under kernel 5.14.0-386.el9.x86_64 I'm able to connect via bmc without any problem both in text mode (multi-user.target) and graphical (graphical.target). Both with and without Wayland enabled in /etc/gdm/custom.conf This morning I updated the system and the kernel is now 5.14.0-404.el9.x86_64, and I'm not able to se...

https://bugzilla.redhat.com/show_bug.cgi?id=2175703 In RHEL-9.2, the "detect_kernels" function still exists in virt-v2v, not in the common submodule. Because we need to fix RHBZ#2175703 for RHEL-9.2.z as well, port of the identically named libguestfs-common patch series <http://mid.mail-archive.com/20230320115301.43051-1-lersek at redhat.com> to RHEL-9.2 virt-v2v. This port is

...0 [nfsv4] [ 72.805508] ? __pfx_autoremove_wake_function+0x10/0x10 [ 72.805512] ? __pfx_nfs41_callback_svc+0x10/0x10 [nfsv4] [ 72.805536] kthread+0xdd/0x100 [ 72.805538] ? __pfx_kthread+0x10/0x10 [ 72.805539] ret_from_fork+0x29/0x50 [ 72.805543] </TASK> Kernel: 5.14.0-404.el9.x86_64 How do I boot the previous kernel? Holding Shift down does nothing. Pressing escape brings up some kind of emergency screen that has no options other than to "Press any key to exit". Is CentOS 9 Stream considered stable enough to use as an everyday desktop? Mike

https://bugzilla.redhat.com/show_bug.cgi?id=2175703 Vera Wu's testing covered a backport of this series to the virt-v2v project's rhel-9.2 branch (on top of commit 86517b17be98), where the "detect_kernels" function is still unique/internal to the virt-v2v project. The backport / cherry-pick from libguestfs-common to virt-v2v cannot be automated, but it's not difficult; only

...t r-project.org>; Miguel Esteva <esteva.m at wehi.edu.au> Subject: Re: [R] Compilation problems with R4.4.0 ? Wed, 8 May 2024 16:59:25 +0000 Simon Andrews <simon.andrews at babraham.ac.uk> ?????: > The lapack libraries are: > > $ rpm -qa | grep lapack > lapack-3.9.0-10.el9.x86_64 > lapack64_-3.9.0-10.el9.x86_64 > lapack64-3.9.0-10.el9.x86_64 > lapack-devel-3.9.0-10.el9.x86_64 Thanks for this information! I figured out I needed to enable the "PowerTools/CRB" repo, installed lapack-devel from there, and now I get the same configure output and the sa...

...tween 388 and 391. > > Q: If I update, am I going to lose kernel 388? How can I persist that > one specific kernel indefinitely and still be able to update the rest > of the system? > > Mike > > # grubby --info=ALL | grep ^kernel > kernel="/boot/vmlinuz-5.14.0-404.el9.x86_64" > kernel="/boot/vmlinuz-5.14.0-391.el9.x86_64" > kernel="/boot/vmlinuz-5.14.0-388.el9.x86_64" > kernel="/boot/vmlinuz-0-rescue-aaab5fbe787947ec94b3c7574b9d41e6" > # grubby --default-kernel > /boot/vmlinuz-5.14.0-388.el9.x86_64 > _________...

that's what I thought at first, but there is no gimp-devel either installed, or available. Fred On Tue, Mar 21, 2023 at 2:39?PM Robert Heller <heller at deepsoft.com> wrote: > At Tue, 21 Mar 2023 14:13:50 -0400 CentOS mailing list <centos at centos.org> > wrote: > > > > > well, I'm still confused. > > > > sudo dnf install glib2-devel says it

Hi all, I seem to be getting segfaults when attempting to build R 4.4.0 on RHEL 9.1 (5.14.0-162.23.1.el9_1.x86_64). Interestingly, it seems to build ok on Rocky 9.1 and 9.3. This is the trace: make[3]: Entering directory '/home/esteva.m/R/R-4.4.0/src/library/grDevices' building package 'grDevices' make[4]: Entering directory '/home/esteva.m/R/R-4.4.0/src/library/grDevices'...