virt

virt@lists.centos.org

2 participants
1613 discussions

recommended network setup for kvm/qemu VM running pfsense?
by hw 15 Sep '21

15 Sep '21

Hi, I'm planning to set a up a kvm/qemu VM with pfsense. I have a quad-port Intel PRO/1000 PT networking card to put into my server which I want to use as card dedicted to this VM. I was planning to use PCI passthrough to hand over the network card (or all ports on the card) to the VM. However, according to https://libvirt.org/formatdomain.html#network-interfaces using a bridge (bridges in this case) is the "recommended config for general guest connectivity on hosts with static wired networking configs". Pfsense running in the VM will have a static ipv4 address and a dynamic ipv6 subnet via a pppoe connection to the ISP. Addresses on the other networks the VM will be connected to are static, except for the ipv6 addresses Pfsense will get via prefix-delegation and distribute to local clients. The libvirt documentation shows a multitude of options to give network access to VMs. What would be the best option for this purpose?

1 0

Registration for oVirt 2021 online conference is now open!
by Sandro Bonazzola 29 Jul '21

29 Jul '21

Hi, The registration for oVirt 2021 online conference is now open! You can register now at https://www.eventbrite.it/e/ovirt-2021-online-conference-registration-16509… Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA sbonazzo(a)redhat.com Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

1 0

Re: [CentOS-virt] qemu-kvm-ev: usb: out-of-bounds r/w(CVE-2020-14364)
by rjmcy＠vip.qq.com 29 Mar '21

29 Mar '21

I have reported on bugzilla, link: https://bugzilla.redhat.com/show_bug.cgi?id=1943399; But this seems to only support ovirt. Then，opened an issue on CentOS community;link: https://bugs.centos.org/view.php?id=18131; Thanks. jasonrao From: centos-virt-request Date: 2021-03-16 20:00 To: centos-virt Subject: CentOS-virt Digest, Vol 159, Issue 2 Send CentOS-virt mailing list submissions to centos-virt(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-virt or, via email, send a message with subject or body 'help' to centos-virt-request(a)centos.org You can reach the person managing the list at centos-virt-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-virt digest..." Today's Topics: 1. Re: qemu-kvm-ev: usb: out-of-bounds r/w(CVE-2020-14364) (Sandro Bonazzola) 2. Unable to Login to AWS AMI With SSH Key - aarch64 (David Lemcoe) 3. Re: Unable to Login to AWS AMI With SSH Key - aarch64 (David Lemcoe) ---------------------------------------------------------------------- Message: 1 Date: Mon, 15 Mar 2021 17:30:44 +0100 From: Sandro Bonazzola <sbonazzo(a)redhat.com> To: Discussion about the virtualization on CentOS <centos-virt(a)centos.org> Subject: Re: [CentOS-virt] qemu-kvm-ev: usb: out-of-bounds r/w(CVE-2020-14364) Message-ID: <CAPQRNTmoDbYqHew9p824LG8CLWHr3Ca=kGv+Jaky4N0OVD2WrA(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Il giorno mer 3 mar 2021 alle ore 09:56 rjmcy(a)vip.qq.com <rjmcy(a)vip.qq.com> ha scritto: > Hello > I saw that qemu-kvm-rhev has fixed the issue, but CentOS > community hasn't updated the repaired version of qemu-kvm-ev; > will it be fixed in the future? > Can you please open a BZ on https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-distribution&compon… ? Thanks > thanks > _______________________________________________ > CentOS-virt mailing list > CentOS-virt(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-virt > -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.* -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20210315/52e2ec49…> ------------------------------ Message: 2 Date: Mon, 15 Mar 2021 12:36:42 -0400 From: David Lemcoe <david(a)delcoe.com> To: centos-virt(a)centos.org Subject: [CentOS-virt] Unable to Login to AWS AMI With SSH Key - aarch64 Message-ID: <12D7B36C-DB26-41D6-BE8F-779153ECA319(a)delcoe.com> Content-Type: text/plain; charset="us-ascii" When launching CentOS Stream for aarch64 in us-east-1 using the CentOS-sponsored AMI (ami-0a311be1169cd6581, found at https://wiki.centos.org/Cloud/AWS <https://wiki.centos.org/Cloud/AWS>) I am able to launch the EC2 instance using a Gravitron2 processor, as expected. However, when attempting to login to that instance, I get a password prompt for the ec2-user, centos, and root users. This behavior is not expected, because on the x86_64 AMIs the centos user is configured to use the SSH key selected in the AWS EC2 Launch Wizard, and a SSH login password is not required. In the aarch64 AMI, the centos and root usernames all prompt for password, and never seem to consider the provided SSH key. This is the SSH command that I am using: ssh -i ssh_key_selected_at_launch.pem centos@<the_public_ip> This command results in a password prompt. What is the process for connecting to the CentOS Stream AMI spun for aarch64? Thank you! David Lemcoe Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20210315/1237a0c6…> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1481 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20210315/1237a0c6…> ------------------------------ Message: 3 Date: Mon, 15 Mar 2021 12:46:49 -0400 From: David Lemcoe <david(a)delcoe.com> To: centos-virt(a)centos.org Subject: Re: [CentOS-virt] Unable to Login to AWS AMI With SSH Key - aarch64 Message-ID: <FFA02901-53F9-4996-9331-E04640881528(a)delcoe.com> Content-Type: text/plain; charset="utf-8" I have resolved my ?issue.? It would appear that CentOS 8 Stream for aarch64 does not support `t4g.nano` instance sizes. Once I moved to t4g.small, my SSH login worked as expected. Sorry to bother! -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1481 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20210315/77b64c18…> ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-virt mailing list CentOS-virt(a)centos.org https://lists.centos.org/mailman/listinfo/centos-virt ------------------------------ End of CentOS-virt Digest, Vol 159, Issue 2 *******************************************

1 0

Unable to Login to AWS AMI With SSH Key - aarch64
by David Lemcoe 15 Mar '21

15 Mar '21

When launching CentOS Stream for aarch64 in us-east-1 using the CentOS-sponsored AMI (ami-0a311be1169cd6581, found at https://wiki.centos.org/Cloud/AWS <https://wiki.centos.org/Cloud/AWS>) I am able to launch the EC2 instance using a Gravitron2 processor, as expected. However, when attempting to login to that instance, I get a password prompt for the ec2-user, centos, and root users. This behavior is not expected, because on the x86_64 AMIs the centos user is configured to use the SSH key selected in the AWS EC2 Launch Wizard, and a SSH login password is not required. In the aarch64 AMI, the centos and root usernames all prompt for password, and never seem to consider the provided SSH key. This is the SSH command that I am using: ssh -i ssh_key_selected_at_launch.pem centos@<the_public_ip> This command results in a password prompt. What is the process for connecting to the CentOS Stream AMI spun for aarch64? Thank you! David Lemcoe Jr.

1 1

qemu-kvm-ev: usb: out-of-bounds r/w(CVE-2020-14364)
by rjmcy＠vip.qq.com 15 Mar '21

15 Mar '21

Hello I saw that qemu-kvm-rhev has fixed the issue, but CentOS community hasn't updated the repaired version of qemu-kvm-ev; will it be fixed in the future? thanks

2 1

OS-level virtualization using LXC and systemd-nspawn containers
by Gena Makhomed 28 Jan '21

28 Jan '21

Hello All, OpenVZ 6 in the past was a very popular technology for creating OS-level virtualization containers. But OpenVZ 6 is EOL now (because RHEL 6 / CentOS 6 is EOL) and all OpenVZ 6 users should migrate to some alternatives. I found only two possible free/open source alternatives for OpenVZ 6: - LXC - systemd-nspawn Does anyone use LXC and/or systemd-nspawn containers on RHEL 8 / CentOS 8 for production? What are advantages and disadvantages of each of these technologies? Can you share your experience with LXC and/or systemd-nspawn for RHEL 8 / CentOS 8 operating system on the hardware node? ============================================================ As I understand, LXC is not supported by Red Hat and it should be used on RHEL at its own risk? But, as I understand from the articles - https://access.redhat.com/solutions/1533893 - https://access.redhat.com/articles/2726611 systemd-nspawn is also not supported by Red Hat and should be used at its own risk? So, between LXC and systemd-nspawn is there no difference despite what systemd-nspawn is the part of the RHEL 8 operating system and can be installed on the RHEL 8 from the BaseOS repo? Are there any chances that the situation with support for systemd-nspawn will change in the future and this OS-level virtualization technology will become fully supported in the RHEL 8.x or the RHEL 9.x version? -- Best regards, Gena

3 9

HCI Cluster - CentOS8 to Streams Upgrade Broken
by Jeremey Wise 18 Jan '21

18 Jan '21

I have a test environment. Three node HCI cluster. CentOS8 build. Gluster as file system with standard cockpit deploy of HCI. Converted to CentOS Streams which seemed to go fine. Did a yum update and no issues. Did a reboot.. and now engine will no longer start. So I can no longer start my Virtual machines. I posted as bug https://bugzilla.redhat.com/show_bug.cgi?id=1911910 I posted to CentOS forum https://forums.centos.org/viewtopic.php?f=54&t=76716 but no responses. Can anyone provide means or next step to root cause and or fix? It would take me days to rebuild the entire solution and I really hate to "reload" as a fix.. but after two weeks... nothing changing... just have to find some means to get cluster back working. Thanks. ##### all three servers are looping below events in /var/log/messages ### Jan 7 09:48:03 thor journal[2375050]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Failed initializing the broker: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/thorst.penguinpages.local:_engine/3afc47ba-afb9-413f-8de5-8d9a2f45ecde/ha_agent/hosted-engine.metadata' Jan 7 09:48:03 thor journal[2375050]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 64, in run#012 self._storage_broker_instance = self._get_storage_broker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 143, in _get_storage_broker#012 return storage_broker.StorageBroker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", line 97, in __init__#012 self._backend.connect()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 408, in connect#012 self._check_symlinks(self._storage_path, volume.path, service_link)#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 105, in _check_symlinks#012 os.unlink(service_link)#012OSError: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/thorst.penguinpages.local:_engine/3afc47ba-afb9-413f-8de5-8d9a2f45ecde/ha_agent/hosted-engine.metadata' Jan 7 09:48:03 thor journal[2375050]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Trying to restart the broker Jan 7 09:48:03 thor platform-python[2375050]: detected unhandled Python exception in '/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker' Jan 7 09:48:03 thor abrt-server[2375084]: Not saving repeating crash in '/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker' Jan 7 09:48:03 thor systemd[1]: ovirt-ha-broker.service: Main process exited, code=exited, status=1/FAILURE Jan 7 09:48:03 thor systemd[1]: ovirt-ha-broker.service: Failed with result 'exit-code'. Jan 7 09:48:04 thor systemd[1]: ovirt-ha-broker.service: Service RestartSec=100ms expired, scheduling restart. Jan 7 09:48:04 thor systemd[1]: ovirt-ha-broker.service: Scheduled restart job, restart counter is at 44569. Jan 7 09:48:04 thor systemd[1]: Stopped oVirt Hosted Engine High Availability Communications Broker. Jan 7 09:48:04 thor systemd[1]: Started oVirt Hosted Engine High Availability Communications Broker. Jan 7 09:48:06 thor systemd[1]: ovirt-ha-agent.service: Service RestartSec=10s expired, scheduling restart. Jan 7 09:48:06 thor systemd[1]: ovirt-ha-agent.service: Scheduled restart job, restart counter is at 22270. Jan 7 09:48:06 thor systemd[1]: Stopped oVirt Hosted Engine High Availability Monitoring Agent. Jan 7 09:48:06 thor systemd[1]: Started oVirt Hosted Engine High Availability Monitoring Agent. Jan 7 09:48:06 thor systemd[1]: Started Session c44598 of user root. Jan 7 09:48:06 thor systemd[1]: session-c44598.scope: Succeeded. Jan 7 09:48:06 thor journal[2375091]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR Failed to start necessary monitors Jan 7 09:48:06 thor journal[2375091]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 85, in start_monitor#012 response = self._proxy.start_monitor(type, options)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__#012 return self.__send(self.__name, args)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request#012 verbose=self.__verbose#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request#012 return self.single_request(host, handler, request_body, verbose)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1166, in single_request#012 http_conn = self.send_request(host, handler, request_body, verbose)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1279, in send_request#012 self.send_content(connection, request_body)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1309, in send_content#012 connection.endheaders(request_body)#012 File "/usr/lib64/python3.6/http/client.py", line 1264, in endheaders#012 self._send_output(message_body, encode_chunked=encode_chunked)#012 File "/usr/lib64/python3.6/http/client.py", line 1040, in _send_output#012 self.send(msg)#012 File "/usr/lib64/python3.6/http/client.py", line 978, in send#012 self.connect()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 74, in connect#012 self.sock.connect(base64.b16decode(self.host))#012FileNotFoundError: [Errno 2] No such file or directory#012#012During handling of the above exception, another exception occurred:#012#012Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 131, in _run_agent#012 return action(he)#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 55, in action_proper#012 return he.start_monitoring()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 437, in start_monitoring#012 self._initialize_broker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 561, in _initialize_broker#012 m.get('options', {}))#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 91, in start_monitor#012 ).format(t=type, o=options, e=e)#012ovirt_hosted_engine_ha.lib.exceptions.RequestError: brokerlink - failed to start monitor via ovirt-ha-broker: [Errno 2] No such file or directory, [monitor: 'network', options: {'addr': '172.16.100.1', 'network_test': 'dns', 'tcp_t_address': '', 'tcp_t_port': ''}] Jan 7 09:48:06 thor journal[2375091]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Trying to restart agent Jan 7 09:48:06 thor systemd[1]: ovirt-ha-agent.service: Main process exited, code=exited, status=157/n/a Jan 7 09:48:06 thor systemd[1]: ovirt-ha-agent.service: Failed with result 'exit-code'. #### Is their a means to start a VM... when oVirt / engine is offline? -- penguinpages

2 1

LZ4 Kernel Decompression not supported
by Dr Francis Greaves 12 Oct '20

12 Oct '20

I am running XEN on CentOS Linux release 7.8.2003 I have a Debian 7, and two Gentoo DomU Guests running fine. I am trying to get an Ubuntu 20.04 DomU Guest running but I get this error when trying to run the netboot kernel image xc_dom_probe_bzimage_kernel unable to LZ4 decompress kernel I understand that CentOS Xen does not support LZ4 decompression. Is there a workaround for this? Regards Francis

2 1

CentOS 8 Install as DOMU in PV Environment
by Niklas Anderson 28 Sep '20

28 Sep '20

All, I have successfully installed CentOS 7 on a PV environment, and have been trying to see if I can can get a CentOS 8 install running. Hardware does not support virtualization extensions, hence the PV environment and I cant do HVM for the install then migrate. My understanding is that PV support is in the kernel, and that the distro of Linux shouldn't technically matter. But currently when trying to "PXEBoot" using a CentOS 8 kernel and ram image I get a near instant crash for an invalid kernel. I tried to get around the issue by using DOM0 kernel and Ram Disk for the install (DOM0 is Debian 10), having the boot progress until it reaches the following, looping ISCSI error: >[ OK ] Reached target Slices. > Starting Create Static Device Nodes in /dev... >[ OK ] Started iSCSI UserSpace I/O driver. >[ OK ] Started Setup Virtual Console. > Starting dracut cmdline hook... >[ OK ] Started Apply Kernel Variables. >[ OK ] Stopped iSCSI UserSpace I/O driver. > Starting iSCSI UserSpace I/O driver... I have also tried the CentOS 7 kernel Ram Disk with the same results. I even tried installing CentOS 7 clean, then upgrading in place (by unofficial and unsupported means) and was left with an error that pygrub couldnt find the partition with the kernel. Is this is a bug, or is PV just not supported? Or am I doing something wrong? Config for the install is below: ># Kernel paths for install >#kernel = "/var/opt/xen/ISO_Store/Centos8PXEBoot/vmlinuz" >kernel = "/vmlinuz" >#ramdisk = "/var/opt/xen/ISO_Store/Centos8PXEBoot/initrd.img" >ramdisk = "/initrd.img" >extra="modules=loop,squashfs console=hvc0" > ># Path to HDD and iso file >disk = [ > #'file:/vmdisk0,xvda,w' > 'format=raw, vdev=xvda, access=w, target=/dev/mapper/vg_1-virtualmachine', > ] > >extra="ksdevice= inst.repo=https://mirror.jaleco.com/centos/8.2.2004/isos/x86_64/ nameserver=1.1.1.1" > ># Network configuration >vif = ['bridge=xenbr0'] > >#DomU Settings >memory = 3072 >name = "centos-8.2" Thank you to all.

6 8

Re: [CentOS-virt] CentOS-virt Digest, Vol 156, Issue 3
by Daniel Sichel 14 Sep '20

14 Sep '20

Make sure that the interface that you are bridging to is not a wireless interface otherwise it won't work. Very deep in the documentation about setting up KVM there is a warning about that it's something about how they initiate connections on a wireless interface is different than on a wired one and it breaks things in KVM bridging. Daniel Sichel ________________________________ From: CentOS-virt <centos-virt-bounces(a)centos.org> on behalf of centos-virt-request(a)centos.org <centos-virt-request(a)centos.org> Sent: Monday, September 14, 2020 5:00:03 AM To: centos-virt(a)centos.org <centos-virt(a)centos.org> Subject: CentOS-virt Digest, Vol 156, Issue 3 Send CentOS-virt mailing list submissions to centos-virt(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.cen… or, via email, send a message with subject or body 'help' to centos-virt-request(a)centos.org You can reach the person managing the list at centos-virt-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-virt digest..." Today's Topics: 1. Re: Centos + VM + public ip (Subscriber) 2. Re: Centos + VM + public ip (Soumya Bhowmik) ---------------------------------------------------------------------- Message: 1 Date: Sun, 13 Sep 2020 15:47:00 +0300 (EEST) From: Subscriber <ml-lists(a)agoris.net.ua> To: Discussion about the virtualization on CentOS <centos-virt(a)centos.org> Subject: Re: [CentOS-virt] Centos + VM + public ip Message-ID: <1516494674.1906.1600001220556.JavaMail.zimbra(a)agoris.net.ua> Content-Type: text/plain; charset=utf-8 > Hi, > > I've got a dedicated server with OVH and I'd like to host a public VM. I'd like > Centos OS 7 or 8, I installed KVM already, I got the VM and bought the IP and > created a virtual mac id. I know I have to bridge it somehow but I can't seem > to find a proper tutorial. Do you know where to start? You can do next: 1) Create bridge interface (for example br0) on dedicated server. Associate this interface with your Ethernet interface and assign IP address to br0. 2a) When you would create VM add parameter --network=bridge:br0 to the virt-install in command line. Or smth similar if you create VM in another way. 2b) Or edit xml file for your VM and add or change config: <interface type='bridge'> <mac address='insert_you_virtual_mac_here'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </interface> 3) Inside the VM assign real/public IP to you Ethernet (probably eth0) interface. That's all. If you have additional questions or you need more detail explanation you can write me directly. ------------------------------ Message: 2 Date: Sun, 13 Sep 2020 13:15:02 +0000 (UTC) From: Soumya Bhowmik <som3939(a)yahoo.co.in> To: Discussion about the virtualization on CentOS <centos-virt(a)centos.org> Subject: Re: [CentOS-virt] Centos + VM + public ip Message-ID: <868650482.1233750.1600002902917(a)mail.yahoo.com> Content-Type: text/plain; charset="utf-8" You can create bridge in CentOS 7 withbr command line tool. In case if CentOS 8, bridge can be created with nmcli, cockpit or nm-connection-editor.? Sent from Yahoo Mail on Android On Mon, 7 Sep 2020 at 9:54 PM, Yoram Halberstam<yoram.halberstam(a)gmail.com> wrote: Hi, I've got a dedicated server with OVH and I'd like to host a public VM. I'd like Centos OS 7 or 8, I installed KVM already, I got the VM and bought the IP and created a virtual mac id. I know I have to bridge it somehow but I can't seem to find a proper tutorial. Do you know where to start? Thanks _______________________________________________ CentOS-virt mailing list CentOS-virt(a)centos.org https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.cen…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt