Hi all,
For CentOS infra needs, we have some ppc64le hosts deployed (Power9 and soon Power10) but the existing machines are still relying on RHEL8, as it was the last enterprise distro version in the RH ecosystem to provide kvm host feature. This was dropped after in the RHEL9 version (and still disabled in Stream10 and so for future el10)
I had a look and at least I know that Almalinux people have enabled back what was missing, and so be able to use it as kvm host, and then deploy as usual other guests on top.
I'd like to propose to join myself the SIG and create some tags, just for ppc64le, starting with Stream 10 and eventually (time permitting but not the initial goal) do the same for Stream 9/RHEL9.
Asking so the chair, Sandro, if he minds me (from the Infra SIG perspective) joining the SIG and start some scratch builds as PoC and then promote builds on the mirror network. As said, as we (CentOS Infra) would rely on these builds, we'd maintain these as long as we'd need ppc64le support in our infra, which we don't consider to drop anytime soon.
Opinions, feedback, thoughts ?
PS : trying in parallel to reach out to some folks at the Almalinux side, to see if working on patches can be done in parallel
Indeed, I have no objections to your proposal outlined in the email. It's good to see initiative towards re-enabling the qemu-kvm support for the ppc64le architecture within CentOS Virtualization SIG. I'm adding you to the SIG.
There was a prior effort from IBM ( https://cbs.centos.org/koji/userinfo?userID=313). Your plan to start with CentOS Stream 10 and potentially extend to CentOS Stream 9 seems like a reasonable approach. Furthermore, reaching out to the AlmaLinux team for potential collaboration on patches is a positive step that could prove beneficial.
I would suggest dropping an email to devel@ovirt.org as well as there may be people there interested about this effort.
Il giorno gio 8 mag 2025 alle ore 14:05 Fabian Arrotin arrfab@centos.org ha scritto:
Hi all,
For CentOS infra needs, we have some ppc64le hosts deployed (Power9 and soon Power10) but the existing machines are still relying on RHEL8, as it was the last enterprise distro version in the RH ecosystem to provide kvm host feature. This was dropped after in the RHEL9 version (and still disabled in Stream10 and so for future el10)
I had a look and at least I know that Almalinux people have enabled back what was missing, and so be able to use it as kvm host, and then deploy as usual other guests on top.
I'd like to propose to join myself the SIG and create some tags, just for ppc64le, starting with Stream 10 and eventually (time permitting but not the initial goal) do the same for Stream 9/RHEL9.
Asking so the chair, Sandro, if he minds me (from the Infra SIG perspective) joining the SIG and start some scratch builds as PoC and then promote builds on the mirror network. As said, as we (CentOS Infra) would rely on these builds, we'd maintain these as long as we'd need ppc64le support in our infra, which we don't consider to drop anytime soon.
Opinions, feedback, thoughts ?
PS : trying in parallel to reach out to some folks at the Almalinux side, to see if working on patches can be done in parallel
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
virt mailing list -- virt@lists.centos.org To unsubscribe send an email to virt-leave@lists.centos.org
I have been helping with AlmaLinux adding support back to AlmaLinux 9 and will be verifying it also works with AlmaLinux 10 soon as well. I can certainly help with this as we really need this to support our ppc64le openstack cluster.
On Thu, May 8, 2025 at 5:10 AM Fabian Arrotin arrfab@centos.org wrote:
Hi all,
For CentOS infra needs, we have some ppc64le hosts deployed (Power9 and soon Power10) but the existing machines are still relying on RHEL8, as it was the last enterprise distro version in the RH ecosystem to provide kvm host feature. This was dropped after in the RHEL9 version (and still disabled in Stream10 and so for future el10)
I had a look and at least I know that Almalinux people have enabled back what was missing, and so be able to use it as kvm host, and then deploy as usual other guests on top.
I'd like to propose to join myself the SIG and create some tags, just for ppc64le, starting with Stream 10 and eventually (time permitting but not the initial goal) do the same for Stream 9/RHEL9.
Asking so the chair, Sandro, if he minds me (from the Infra SIG perspective) joining the SIG and start some scratch builds as PoC and then promote builds on the mirror network. As said, as we (CentOS Infra) would rely on these builds, we'd maintain these as long as we'd need ppc64le support in our infra, which we don't consider to drop anytime soon.
Opinions, feedback, thoughts ?
PS : trying in parallel to reach out to some folks at the Almalinux side, to see if working on patches can be done in parallel
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
virt mailing list -- virt@lists.centos.org To unsubscribe send an email to virt-leave@lists.centos.org
On 08/05/2025 18:12, Lance Albertson wrote:
I have been helping with AlmaLinux adding support back to AlmaLinux 9 and will be verifying it also works with AlmaLinux 10 soon as well. I can certainly help with this as we really need this to support our ppc64le openstack cluster.
Great ! Happy to also onboard you (if Sandra agrees but I guess that it shouldn't be a problem)
Where do we want to start ? This was my plan :
- identify which packages need to be modified to just enable back missing "feature" (I have a short list but probably more to have a look at) - create some git repositories under https://gitlab.com/CentOS/virt/rpms (like libvirt , being the obvious one, etc) - push corresponding sources to lookaside cache - test some builds on https://cbs.centos.org, using -candidate tag first - build these against CentOS Stream 10 for now (and eventually RHEL10 so after, when it will be available)
The problem is more about where to test this but I should have access to a Power9 that I'd like to convert from RHEL8 to Stream 10 and see how that goes.
@Lance : how do you want to sync up about this ? this list is ok but we can also use either irc or matrix (I prefer IRC myself but probably because I'm "old" :p)
Il giorno ven 9 mag 2025 alle ore 17:14 Fabian Arrotin via virt < virt@lists.centos.org> ha scritto:
On 08/05/2025 18:12, Lance Albertson wrote:
I have been helping with AlmaLinux adding support back to AlmaLinux 9 and will be verifying it also works with AlmaLinux 10 soon as well. I can certainly help with this as we really need this to support our ppc64le openstack cluster.
Great ! Happy to also onboard you (if Sandra agrees but I guess that it shouldn't be a problem)
Not a problem on my side.
On Fri, May 9, 2025 at 8:14 AM Fabian Arrotin via virt < virt@lists.centos.org> wrote:
On 08/05/2025 18:12, Lance Albertson wrote:
I have been helping with AlmaLinux adding support back to AlmaLinux 9 and will be verifying it also works with AlmaLinux 10 soon as well. I can certainly help with this as we really need this to support our ppc64le openstack cluster.
Great ! Happy to also onboard you (if Sandra agrees but I guess that it shouldn't be a problem)
Where do we want to start ? This was my plan :
- identify which packages need to be modified to just enable back
missing "feature" (I have a short list but probably more to have a look at)
- create some git repositories under https://gitlab.com/CentOS/virt/rpms
(like libvirt , being the obvious one, etc)
I need to come up with an accurate list, but I have cloned most of the rpms from the AlmaLinux repository and hosted them on our Gitlab instance [1]. There are other unrelated RPMs in that group, but you can see some of the changes I made. If you want, I can make proper MR's to the upstream repositories.
Keep in mind, the changes I have in these repos are specifically for getting this to work on AlmaLinux 9, but it should work with 10 as well in theory.
Let me know how you'd like to proceed.
[1] https://git.osuosl.org/rpms?sort=latest_activity_desc
- push corresponding sources to lookaside cache
- test some builds on https://cbs.centos.org, using -candidate tag first
- build these against CentOS Stream 10 for now (and eventually RHEL10 so
after, when it will be available)
The problem is more about where to test this but I should have access to a Power9 that I'd like to convert from RHEL8 to Stream 10 and see how that goes.
@Lance : how do you want to sync up about this ? this list is ok but we can also use either irc or matrix (I prefer IRC myself but probably because I'm "old" :p)
I prefer Matrix but I also have IRC. If you use IRC, just use Ramereth[m].
-- Fabian Arrotin - SysAdmin Community Linux Engineering (CLE team) gpg key: 17F3B7A1 | @arrfab[@fosstodon.org] _______________________________________________ virt mailing list -- virt@lists.centos.org To unsubscribe send an email to virt-leave@lists.centos.org
On 09/05/2025 18:25, Lance Albertson wrote:
On Fri, May 9, 2025 at 8:14 AM Fabian Arrotin via virt <virt@lists.centos.org mailto:virt@lists.centos.org> wrote:
On 08/05/2025 18:12, Lance Albertson wrote: > I have been helping with AlmaLinux adding support back to AlmaLinux 9 > and will be verifying it also works with AlmaLinux 10 soon as well. I > can certainly help with this as we really need this to support our > ppc64le openstack cluster. > Great ! Happy to also onboard you (if Sandra agrees but I guess that it shouldn't be a problem) Where do we want to start ? This was my plan : - identify which packages need to be modified to just enable back missing "feature" (I have a short list but probably more to have a look at) - create some git repositories under https://gitlab.com/CentOS/virt/ rpms <https://gitlab.com/CentOS/virt/rpms> (like libvirt , being the obvious one, etc)
I need to come up with an accurate list, but I have cloned most of the rpms from the AlmaLinux repository and hosted them on our Gitlab instance [1]. There are other unrelated RPMs in that group, but you can see some of the changes I made. If you want, I can make proper MR's to the upstream repositories.
Keep in mind, the changes I have in these repos are specifically for getting this to work on AlmaLinux 9, but it should work with 10 as well in theory.
Let me know how you'd like to proceed.
I had a quick look and it seems that while for el9 kernel was built without kvm support, it seems for stream 10 (and so el10 ?) it's still there. My plan is just to start looking at c10s for now and then eventually see also with you for el9 ? I already started to consolidate some things under https://gitlab.com/CentOS/virt/rpms , and pushed corresponding sources to cbs lookaside (basically a mirror of gitlab.com/redhat/centos-stream/rpms/<pkg>) I just for the build PoC started with libvirt (built from gitlab.com/centos/virt namespace) : https://cbs.centos.org/koji/buildinfo?buildID=60470
Working on some others but let me know if you know some others. I was thinking about a git repo there where we'd be able to sync our tools for git operations etc
Ideally CI testing but that would require access for some machines and that's problematic for now but ideally doable soon
On 10/05/2025 22:57, Fabian Arrotin wrote:
On 09/05/2025 18:25, Lance Albertson wrote:
On Fri, May 9, 2025 at 8:14 AM Fabian Arrotin via virt <virt@lists.centos.org mailto:virt@lists.centos.org> wrote:
On 08/05/2025 18:12, Lance Albertson wrote: > I have been helping with AlmaLinux adding support back to AlmaLinux 9 > and will be verifying it also works with AlmaLinux 10 soon as well. I > can certainly help with this as we really need this to support our > ppc64le openstack cluster. >
Great ! Happy to also onboard you (if Sandra agrees but I guess that it shouldn't be a problem)
Where do we want to start ? This was my plan :
- identify which packages need to be modified to just enable back missing "feature" (I have a short list but probably more to have a look at) - create some git repositories under https://gitlab.com/CentOS/virt/ rpms https://gitlab.com/CentOS/virt/rpms (like libvirt , being the obvious one, etc)
I need to come up with an accurate list, but I have cloned most of the rpms from the AlmaLinux repository and hosted them on our Gitlab instance [1]. There are other unrelated RPMs in that group, but you can see some of the changes I made. If you want, I can make proper MR's to the upstream repositories.
Keep in mind, the changes I have in these repos are specifically for getting this to work on AlmaLinux 9, but it should work with 10 as well in theory.
Let me know how you'd like to proceed.
I had a quick look and it seems that while for el9 kernel was built without kvm support, it seems for stream 10 (and so el10 ?) it's still there. My plan is just to start looking at c10s for now and then eventually see also with you for el9 ? I already started to consolidate some things under https://gitlab.com/ CentOS/virt/rpms , and pushed corresponding sources to cbs lookaside (basically a mirror of gitlab.com/redhat/centos-stream/rpms/<pkg>) I just for the build PoC started with libvirt (built from gitlab.com/ centos/virt namespace) : https://cbs.centos.org/koji/buildinfo?buildID=60470
Working on some others but let me know if you know some others. I was thinking about a git repo there where we'd be able to sync our tools for git operations etc
Ideally CI testing but that would require access for some machines and that's problematic for now but ideally doable soon
Status update : I worked during the weekend on some pkgs that are now appearing on https://gitlab.com/CentOS/virt/rpms (check for the c10s-virt branch, if needed to deviate from base c10s)
I rebuilt all these through https://cbs.centos.org and pkgs are now tagged to -testing, meaning that they are available under : https://buildlogs.centos.org/centos/10-stream/virt/ppc64le/kvm-power/
Feedback is welcome but myself have reinstalled a Power9 box (that was running RHEL8) with CentOS Stream 10 + pkgs from that new kvm-power repo and ... I was able to redeploy some ppc64le el9 guests through ansible automation , so it seems to be working
On 12/05/2025 15:21, Fabian Arrotin wrote:
On 10/05/2025 22:57, Fabian Arrotin wrote:
On 09/05/2025 18:25, Lance Albertson wrote:
On Fri, May 9, 2025 at 8:14 AM Fabian Arrotin via virt <virt@lists.centos.org mailto:virt@lists.centos.org> wrote:
On 08/05/2025 18:12, Lance Albertson wrote: > I have been helping with AlmaLinux adding support back to AlmaLinux 9 > and will be verifying it also works with AlmaLinux 10 soon as well. I > can certainly help with this as we really need this to support our > ppc64le openstack cluster. >
Great ! Happy to also onboard you (if Sandra agrees but I guess that it shouldn't be a problem)
Where do we want to start ? This was my plan :
- identify which packages need to be modified to just enable back missing "feature" (I have a short list but probably more to have a look at) - create some git repositories under https://gitlab.com/CentOS/virt/ rpms https://gitlab.com/CentOS/virt/rpms (like libvirt , being the obvious one, etc)
I need to come up with an accurate list, but I have cloned most of the rpms from the AlmaLinux repository and hosted them on our Gitlab instance [1]. There are other unrelated RPMs in that group, but you can see some of the changes I made. If you want, I can make proper MR's to the upstream repositories.
Keep in mind, the changes I have in these repos are specifically for getting this to work on AlmaLinux 9, but it should work with 10 as well in theory.
Let me know how you'd like to proceed.
I had a quick look and it seems that while for el9 kernel was built without kvm support, it seems for stream 10 (and so el10 ?) it's still there. My plan is just to start looking at c10s for now and then eventually see also with you for el9 ? I already started to consolidate some things under https://gitlab.com/ CentOS/virt/rpms , and pushed corresponding sources to cbs lookaside (basically a mirror of gitlab.com/redhat/centos-stream/rpms/<pkg>) I just for the build PoC started with libvirt (built from gitlab.com/ centos/virt namespace) : https://cbs.centos.org/koji/buildinfo?buildID=60470
Working on some others but let me know if you know some others. I was thinking about a git repo there where we'd be able to sync our tools for git operations etc
Ideally CI testing but that would require access for some machines and that's problematic for now but ideally doable soon
Status update : I worked during the weekend on some pkgs that are now appearing on https://gitlab.com/CentOS/virt/rpms (check for the c10s- virt branch, if needed to deviate from base c10s)
I rebuilt all these through https://cbs.centos.org and pkgs are now tagged to -testing, meaning that they are available under : https://buildlogs.centos.org/centos/10-stream/virt/ppc64le/kvm-power/
Feedback is welcome but myself have reinstalled a Power9 box (that was running RHEL8) with CentOS Stream 10 + pkgs from that new kvm-power repo and ... I was able to redeploy some ppc64le el9 guests through ansible automation , so it seems to be working
Packages (includind now qemu-kvm 10.0, just released to stream 10 this week) are signed and pushed to https://mirror.stream.centos.org/SIGs/10-stream/virt/ppc64le/kvm-power/
I'd like to work on centos-release-kvm-power pkg but was just wondering : as we *don't* inherit from any pkg from centos-release-virt-common, I was considering skipping it (and so just ship the virt GPG key in centos-release-kvm-power). I guess it's fine for you all ? or maybe I should still use -common in case some other SIG would suddenly like to embed both (and so no conflicting files in different pkgs when trying to set these up in parallel)
Opinions ?
Il giorno gio 15 mag 2025 alle ore 07:53 Fabian Arrotin arrfab@centos.org ha scritto:
On 12/05/2025 15:21, Fabian Arrotin wrote:
[cut]
Packages (includind now qemu-kvm 10.0, just released to stream 10 this week) are signed and pushed to https://mirror.stream.centos.org/SIGs/10-stream/virt/ppc64le/kvm-power/
I'd like to work on centos-release-kvm-power pkg but was just wondering : as we *don't* inherit from any pkg from centos-release-virt-common, I was considering skipping it (and so just ship the virt GPG key in centos-release-kvm-power). I guess it's fine for you all ? or maybe I should still use -common in case some other SIG would suddenly like to embed both (and so no conflicting files in different pkgs when trying to set these up in parallel)
Opinions ?
Within oVirt I guess it will be useful enabling ppc64le on el10 so if you don't mind, I would prefer you still use -common dependency (it basically just ships the GPG key). It will also avoid updating the key in multiple places if for some reason we need to issue a new one.
On 15/05/2025 08:59, Sandro Bonazzola via virt wrote:
Il giorno gio 15 mag 2025 alle ore 07:53 Fabian Arrotin <arrfab@centos.org mailto:arrfab@centos.org> ha scritto:
On 12/05/2025 15:21, Fabian Arrotin wrote:
[cut]
Packages (includind now qemu-kvm 10.0, just released to stream 10 this week) are signed and pushed to https://mirror.stream.centos.org/SIGs/10-stream/virt/ppc64le/kvm- power/ <https://mirror.stream.centos.org/SIGs/10-stream/virt/ ppc64le/kvm-power/> I'd like to work on centos-release-kvm-power pkg but was just wondering : as we *don't* inherit from any pkg from centos-release-virt-common, I was considering skipping it (and so just ship the virt GPG key in centos-release-kvm-power). I guess it's fine for you all ? or maybe I should still use -common in case some other SIG would suddenly like to embed both (and so no conflicting files in different pkgs when trying to set these up in parallel) Opinions ?
Within oVirt I guess it will be useful enabling ppc64le on el10 so if you don't mind, I would prefer you still use -common dependency (it basically just ships the GPG key). It will also avoid updating the key in multiple places if for some reason we need to issue a new one.
Makes sense .. let me then work on centos-release-kvm-power, that would Requires: centos-release-virt-common
BTW, just looking at existing rpm pkgs for this, and I see centos-release-kvm but its it still needed anymore ? it seems it's only carrying some specific "{rust-}vhost*" pkgs (for ovirt ?)
Il giorno ven 16 mag 2025 alle ore 08:54 Fabian Arrotin arrfab@centos.org ha scritto:
On 15/05/2025 08:59, Sandro Bonazzola via virt wrote:
Il giorno gio 15 mag 2025 alle ore 07:53 Fabian Arrotin <arrfab@centos.org mailto:arrfab@centos.org> ha scritto:
On 12/05/2025 15:21, Fabian Arrotin wrote:
[cut]
Packages (includind now qemu-kvm 10.0, just released to stream 10
this
week) are signed and pushed to https://mirror.stream.centos.org/SIGs/10-stream/virt/ppc64le/kvm- power/ <https://mirror.stream.centos.org/SIGs/10-stream/virt/ ppc64le/kvm-power/> I'd like to work on centos-release-kvm-power pkg but was just
wondering
: as we *don't* inherit from any pkg from
centos-release-virt-common, I
was considering skipping it (and so just ship the virt GPG key in centos-release-kvm-power). I guess it's fine for you all ? or maybe I should still use -common
in
case some other SIG would suddenly like to embed both (and so no conflicting files in different pkgs when trying to set these up in parallel) Opinions ?
Within oVirt I guess it will be useful enabling ppc64le on el10 so if you don't mind, I would prefer you still use -common dependency (it basically just ships the GPG key). It will also avoid updating the key in multiple places if for some reason we need to issue a new one.
Makes sense .. let me then work on centos-release-kvm-power, that would Requires: centos-release-virt-common
BTW, just looking at existing rpm pkgs for this, and I see centos-release-kvm but its it still needed anymore ? it seems it's only carrying some specific "{rust-}vhost*" pkgs (for ovirt ?)
It ships packages that can be used directly with qemu-kvm, not specific to oVirt. They've been prepared in collaboration with Automotive SIG. I think you can reuse it for shipping qemu-kvm for power.
On 16/05/2025 09:02, Sandro Bonazzola via virt wrote:
Il giorno ven 16 mag 2025 alle ore 08:54 Fabian Arrotin <arrfab@centos.org mailto:arrfab@centos.org> ha scritto:
On 15/05/2025 08:59, Sandro Bonazzola via virt wrote: > > > Il giorno gio 15 mag 2025 alle ore 07:53 Fabian Arrotin > <arrfab@centos.org <mailto:arrfab@centos.org> <mailto:arrfab@centos.org <mailto:arrfab@centos.org>>> ha scritto: > > On 12/05/2025 15:21, Fabian Arrotin wrote: > > [cut] > > Packages (includind now qemu-kvm 10.0, just released to stream 10 this > week) are signed and pushed to > https://mirror.stream.centos.org/SIGs/10-stream/virt/ppc64le/kvm- <https://mirror.stream.centos.org/SIGs/10-stream/virt/ppc64le/kvm-> > power/ <https://mirror.stream.centos.org/SIGs/10-stream/virt/ <https://mirror.stream.centos.org/SIGs/10-stream/virt/> > ppc64le/kvm-power/> > > I'd like to work on centos-release-kvm-power pkg but was just wondering > : as we *don't* inherit from any pkg from centos-release- virt-common, I > was considering skipping it (and so just ship the virt GPG key in > centos-release-kvm-power). > I guess it's fine for you all ? or maybe I should still use - common in > case some other SIG would suddenly like to embed both (and so no > conflicting files in different pkgs when trying to set these up in > parallel) > > Opinions ? > > > Within oVirt I guess it will be useful enabling ppc64le on el10 so if > you don't mind, I would prefer you still use -common dependency (it > basically just ships the GPG key). It will also avoid updating the key > in multiple places if for some reason we need to issue a new one. > Makes sense .. let me then work on centos-release-kvm-power, that would Requires: centos-release-virt-common BTW, just looking at existing rpm pkgs for this, and I see centos-release-kvm but its it still needed anymore ? it seems it's only carrying some specific "{rust-}vhost*" pkgs (for ovirt ?)
It ships packages that can be used directly with qemu-kvm, not specific to oVirt. They've been prepared in collaboration with Automotive SIG. I think you can reuse it for shipping qemu-kvm for power.
FWIW, as I'm also member of the Extras SIG (through Infra SIG membership myself), I just tagged to -release centos-release-kvm-power, and just announced it.