The CentOS Virtualization SIG on behalf of the oVirt Project Community is
pleased to announce the general availability of the oVirt 4.5.0 build
for CentOS
Stream, Red Hat Enterprise Linux and derivatives.
The release is already available on the CentOS mirror network.
Read more on the announcement blog post at
https://blogs.ovirt.org/2022/04/ovirt-4-5-0-is-now-generally-available/
Many thanks to the other CentOS Special Interest Groups involved in this
release.
Questions about the release? Please join the discussion on
https://lists.ovirt.org/archives/list/users@ovirt.org/
Thanks,
--
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.*
Hello,
We have launched some EC2 servers 6 month ago using the CentOS 8
MarketPlace AMI 47k9ia2igxpcce2bzo8u3kj03 (
https://aws.amazon.com/marketplace/pp/prodview-ndxelprnnxecs)
Now we have migrated these servers to CentOS Stream 8.
We can change the instance type of these servers until m6i and c6i Intel
based CPU, but we cannot change the instance type to new ADM Epyc c6a and
m6a. There is an error triggered by the AWS console and saying to this
marketplace server is not compatible with c6a and m6a instance types...
Is there a reason for this situation (because this AMI is X86_64
compatible, so AMD Epyc should work with it) ?
Do you know which team is managing this marketplace AMI and which team
could authorize using the new AMD Epyc EC2 instances with this AMI ?
I know that I could relaunch news servers using another AMI, but I don't
want to waste my time in reconfiguring all these servers from a brand new
AMI... I would prefer to just change the instance type of the existing
servers.
I contacted the AWS support to get somes explanations and a solution for
this situation, but they asked me to contact the CentOS community support,
it's why I'm sending this e-mail to this list.
Thank you !
Best regards.
Richard.
--
Ce message et ses pièces jointes éventuelles sont confidentiels et à
l'attention exclusive de ses destinataires. Toute publication, utilisation
ou diffusion, même partielle, doit être autorisée préalablement. DIGITAL
INSURE et ses filiales déclinent toute responsabilité si ce message a été
altéré, déformé ou falsifié. Si vous ne deviez pas être destinataire de ce
message, merci d'en avertir immédiatement l’expéditeur.
This message and
any attachments (the "message") are confidential and intended solely for
the addressees; Any unauthorised use or dissemination is prohibited.
E-mails are susceptible to alteration. Neither DIGITAL INSURE nor any of
its subsidiaries or affiliates shall be liable for the message if altered,
changed or falsified. If you were not supposed to receive this email,
please contact the sender immediatly.
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
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>
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
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
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?
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.