virt

virt@lists.centos.org

1608 discussions

qemu-kvm-core features moved to separate packages in CentOS 9 Stream
by Miroslav Rezanina 24 Jan '22

24 Jan '22

Hi all, There's currently MR [1] on review with changes making the packing layout more close to fedora. This change unfortunately causes users using qemu-kvm-core package (not qemu-kvm) to lose some functionality as some submodules will be moved to separate packages so anyone using these features has to install such package in addition to qemu-kvm-core package. This change won't affect qemu-kvm usage as this package will keep these packages as dependency. These changes are going to be submitted soon so anyone using CentOS 9 Streams qemu-kvm-core package should check whether the functionality is still provided by core package after the change or additional subpackage is needed. [1] https://gitlab.com/redhat/centos-stream/src/qemu-kvm/-/merge_requests/60 -- MIroslav Rezanina Virtualization Team - Maintainer

1 0

Script for making a KVM VM from a kickstart
by Chris Adams 16 Jan '22

16 Jan '22

I have been building up a script to quickly and easily make CentOS/RHEL and Fedora VMs from kickstart files for a long time, and thought I'd see if anyone else was interested. It's especially useful IMHO if you are working on building kickstarts, because you can fairly rapidly iterate and test. I've got it built as an RPM, so if others think this is useful, I might submit it to Fedora and EPEL. Let me know what you think! https://github.com/cmadamsgit/ks-install -- Chris Adams <linux(a)cmadams.net>

3 2

Azure Kernel for CentOS 7
by Young, Gregory 08 Oct '21

08 Oct '21

I am trying to track down what happened with the “kernel-azure” packages that were created by the Virt SIG? I see the last release was August 2020. I also can’t seem to find the sources in the Virt repo (http://mirror.centos.org/centos/7/virt/x86_64/azure/Packages/k/), nor in the CentOS git repo (https://git.centos.org/group/sig-virt). I’m assuming the status is you no longer wish to build the Azure specific kernel, and I would like to see what was involved in doing so, to decide if I want to build them, or if I need to deprecate the Azure kernel for our appliances in the field. Thanks, Greg [cidimage001.png(a)01D7734F.73EF1D20] Gregory Young | Senior Developer/Systems Engineer | N-able

2 1

XSA-384
by Kevin Stange 22 Sep '21

22 Sep '21

I was looking to see if XSA-384 was in testing for CentOS Virt and so far it doesn't look like it is yet. From the patch, it looks like it touches x86 code. Can anyone push a build with this version? Thanks. Kevin Stange Chief Technology Officer Steadfast | Managed Infrastructure, Datacenter and Cloud Services 231 S LaSalle St, Suite 2100 | Chicago, IL 60604 312.602.2689 x203 | Fax: 312.602.2688 kevin(a)steadfast.net | www.steadfast.net

1 0

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt