Fwd: [PROPOSAL] Creating the NVIDIA Enablement SIG - Accelerating NVIDIA Upstream Integration
---------- Forwarded message --------- From: Amnon Ilan ailan@redhat.com Date: Tue, Jan 13, 2026 at 2:35 PM Subject: [PROPOSAL] Creating the NVIDIA Enablement SIG - Accelerating NVIDIA Upstream Integration To: devel@lists.centos.org Cc: Amy Marrich amarrich@redhat.com, Neo Jia cjia@nvidia.com, < newtonl@nvidia.com>
Hello everyone,
I would like to propose the creation of a new Special Interest Group: the NVIDIA Enablement SIG. Purpose
The NVIDIA Enablement SIG will integrate these "in-flight" upstream patches from NVIDIA into a specialized variant of CentOS Stream, allowing the community to test and utilize next-generation hardware capabilities today. Scope
The initial work of the SIG will focus on the foundational layers of the stack required for modern compute and graphics hardware:
-
Linux Kernel: Integrating and testing patches submitted by NVIDIA to the kernel community that improve hardware support and system integration. -
Virtualization (QEMU & libvirt): Implementing upcoming changes that enhance how virtual machines interact with hardware accelerators and modern GPU architectures. -
Continuous Alignment: Ensuring these patches maintain parallel compatibility with the core CentOS Stream codebase as they evolve during the upstream review process.
Deliverables
-
SIG Repositories: builds of the kernel, qemu-kvm, and libvirt containing the latest upstream-bound patches. -
Enablement Packages: A centos-release-nvidia-enablement package to provide users with an easy path to opt-in to these experimental stacks. -
Future work: -
Expanded package set as appropriate -
Install media / images
Initial Members
-
Amnon Ilan - (Proposed Chair) -
Amy Marrich - (Board Sponsor) -
Neo Gia -
Newton Liu -
[Member Name] (We invite anyone interested in the future of open-source hardware enablement to join us.)
Resources Requested
-
Wiki: sigs.centos.org/nvidia-enablement -
CBS Access: Build tags and targets for CentOS Stream 10.
We look forward to hearing the community's thoughts on this proposal.
Best regards,
Amnon Ilan
On Wed, Jan 14, 2026 at 3:17 PM Amy Marrich via devel devel@lists.centos.org wrote:
---------- Forwarded message --------- From: Amnon Ilan ailan@redhat.com Date: Tue, Jan 13, 2026 at 2:35 PM Subject: [PROPOSAL] Creating the NVIDIA Enablement SIG - Accelerating NVIDIA Upstream Integration To: devel@lists.centos.org Cc: Amy Marrich amarrich@redhat.com, Neo Jia cjia@nvidia.com, newtonl@nvidia.com
Hello everyone,
I would like to propose the creation of a new Special Interest Group: the NVIDIA Enablement SIG.
Purpose
The NVIDIA Enablement SIG will integrate these "in-flight" upstream patches from NVIDIA into a specialized variant of CentOS Stream, allowing the community to test and utilize next-generation hardware capabilities today.
Scope
The initial work of the SIG will focus on the foundational layers of the stack required for modern compute and graphics hardware:
Linux Kernel: Integrating and testing patches submitted by NVIDIA to the kernel community that improve hardware support and system integration.
Virtualization (QEMU & libvirt): Implementing upcoming changes that enhance how virtual machines interact with hardware accelerators and modern GPU architectures.
Continuous Alignment: Ensuring these patches maintain parallel compatibility with the core CentOS Stream codebase as they evolve during the upstream review process.
Deliverables
SIG Repositories: builds of the kernel, qemu-kvm, and libvirt containing the latest upstream-bound patches.
Enablement Packages: A centos-release-nvidia-enablement package to provide users with an easy path to opt-in to these experimental stacks.
Future work:
Expanded package set as appropriate
Install media / images
Initial Members
Amnon Ilan - (Proposed Chair)
Amy Marrich - (Board Sponsor)
Neo Gia
Newton Liu
[Member Name] (We invite anyone interested in the future of open-source hardware enablement to join us.)
Resources Requested
Wiki: sigs.centos.org/nvidia-enablement
CBS Access: Build tags and targets for CentOS Stream 10.
We look forward to hearing the community's thoughts on this proposal.
I would be interested in joining and collaborating. I already work on the NVIDIA driver enablement work in AlmaLinux and I think other members of CentOS Hyperscale[1] would be interested too.
I also maintain the CentOS Hyperscale kernel, tracking mainline and latest Fedora stuff, so it may be interesting to collaborate leveraging that as a base if you folks are interested.
[1]: https://sigs.centos.org/hyperscale/
-- 真実はいつも一つ！/ Always, there's only one truth!
@CentOS Automotive SIG automotive-sig@lists.centos.org may be interested as well.
Il giorno mer 14 gen 2026 alle ore 21:18 Amy Marrich via devel < devel@lists.centos.org> ha scritto:
---------- Forwarded message --------- From: Amnon Ilan ailan@redhat.com Date: Tue, Jan 13, 2026 at 2:35 PM Subject: [PROPOSAL] Creating the NVIDIA Enablement SIG - Accelerating NVIDIA Upstream Integration To: devel@lists.centos.org Cc: Amy Marrich amarrich@redhat.com, Neo Jia cjia@nvidia.com, < newtonl@nvidia.com>
Hello everyone,
I would like to propose the creation of a new Special Interest Group: the NVIDIA Enablement SIG. Purpose
The NVIDIA Enablement SIG will integrate these "in-flight" upstream patches from NVIDIA into a specialized variant of CentOS Stream, allowing the community to test and utilize next-generation hardware capabilities today. Scope
The initial work of the SIG will focus on the foundational layers of the stack required for modern compute and graphics hardware:
Linux Kernel: Integrating and testing patches submitted by NVIDIA to the kernel community that improve hardware support and system integration.
Virtualization (QEMU & libvirt): Implementing upcoming changes that enhance how virtual machines interact with hardware accelerators and modern GPU architectures.
Continuous Alignment: Ensuring these patches maintain parallel compatibility with the core CentOS Stream codebase as they evolve during the upstream review process.
Deliverables
SIG Repositories: builds of the kernel, qemu-kvm, and libvirt containing the latest upstream-bound patches.
Enablement Packages: A centos-release-nvidia-enablement package to provide users with an easy path to opt-in to these experimental stacks.
Future work:
Expanded package set as appropriate
Install media / images
Initial Members
Amnon Ilan - (Proposed Chair)
Amy Marrich - (Board Sponsor)
Neo Gia
Newton Liu
[Member Name] (We invite anyone interested in the future of open-source hardware enablement to join us.)
Resources Requested
Wiki: sigs.centos.org/nvidia-enablement
CBS Access: Build tags and targets for CentOS Stream 10.
We look forward to hearing the community's thoughts on this proposal.
Best regards,
Amnon Ilan _______________________________________________ devel mailing list -- devel@lists.centos.org To unsubscribe send an email to devel-leave@lists.centos.org
* Amy Marrich via devel:
Deliverables
- SIG Repositories: builds of the kernel, qemu-kvm, and libvirt containing the latest upstream-bound patches.
Would it be possible to make it a SIG requirement to reach out to relevant RHEL Product Owners before the scope is extended to additional components?
It may be possible to complete the work the SIG requires in CentOS Stream proper in some cases.
Thanks, Florian
On Thu, Jan 15, 2026 at 3:02 AM Florian Weimer via devel devel@lists.centos.org wrote:
- Amy Marrich via devel:
Deliverables
- SIG Repositories: builds of the kernel, qemu-kvm, and libvirt containing the latest upstream-bound patches.
Would it be possible to make it a SIG requirement to reach out to relevant RHEL Product Owners before the scope is extended to additional components?
Please no. That turns the relationship upside down and invalidates the idea that CentOS is supposed to be a community upstream venue.
As an example, CentOS Hyperscale has in the past and will in the future built virtualization components, and we build kernels today. There's no way we'd block that on talking to RHEL POs that we don't even know to do that work.
It may be possible to complete the work the SIG requires in CentOS Stream proper in some cases.
Then those people should be participating in CentOS Stream community spaces *now* and engaging proactively. The onus isn't on us to talk to them, it's on them to talk to us, because there's no way for us to know who they are.
-- 真実はいつも一つ！/ Always, there's only one truth!
* Neal Gompa:
On Thu, Jan 15, 2026 at 3:02 AM Florian Weimer via devel devel@lists.centos.org wrote:
- Amy Marrich via devel:
Deliverables
- SIG Repositories: builds of the kernel, qemu-kvm, and libvirt containing the latest upstream-bound patches.
Would it be possible to make it a SIG requirement to reach out to relevant RHEL Product Owners before the scope is extended to additional components?
Please no. That turns the relationship upside down and invalidates the idea that CentOS is supposed to be a community upstream venue.
This is just a way to avoid duplicate work and that the development activity occurs in the right place.
There are no public CentOS Stream developer meetings or similar resources for most components, otherwise I would have suggested to engage with those.
As an example, CentOS Hyperscale has in the past and will in the future built virtualization components, and we build kernels today. There's no way we'd block that on talking to RHEL POs that we don't even know to do that work.
It's a different SIG, with different goals.
My understanding is that the Nvidia enablement SIG wants to merge most things back into CentOS Stream eventually. The SIG needs to coordinate with CentOS Stream development to some extent, otherwise that's not going to happen.
Thanks, Florian
On Thu, Jan 15, 2026 at 5:15 AM Florian Weimer fweimer@redhat.com wrote:
- Neal Gompa:
On Thu, Jan 15, 2026 at 3:02 AM Florian Weimer via devel devel@lists.centos.org wrote:
- Amy Marrich via devel:
Deliverables
- SIG Repositories: builds of the kernel, qemu-kvm, and libvirt containing the latest upstream-bound patches.
Would it be possible to make it a SIG requirement to reach out to relevant RHEL Product Owners before the scope is extended to additional components?
Please no. That turns the relationship upside down and invalidates the idea that CentOS is supposed to be a community upstream venue.
This is just a way to avoid duplicate work and that the development activity occurs in the right place.
There are no public CentOS Stream developer meetings or similar resources for most components, otherwise I would have suggested to engage with those.
The reason those don't exist is not because we don't want them, but because RHEL developers need to be present in the CentOS space to make that work. We've had a facility for a while now to organize such meetings, but it's not particularly useful if we don't have them.
Even without meetings, CentOS has a public Matrix room that pretty much all the SIG people are in: https://matrix.to/#/#centos-devel:fedoraproject.org
We probably don't need the overhead of meetings if there was a general expectation that people from the RHEL side were present in that room and here on the mailing list to discuss things (similar to how it works in Fedora).
As an example, CentOS Hyperscale has in the past and will in the future built virtualization components, and we build kernels today. There's no way we'd block that on talking to RHEL POs that we don't even know to do that work.
It's a different SIG, with different goals.
My understanding is that the Nvidia enablement SIG wants to merge most things back into CentOS Stream eventually. The SIG needs to coordinate with CentOS Stream development to some extent, otherwise that's not going to happen.
That's not very different from Automotive, Virtualization, Proposed Updates, or even Hyperscale to some extent. Our ability to do this is dependent on RHEL folks being in the spaces where we are so that this can be done. Those folks should be *here* not the other way around.
-- 真実はいつも一つ！/ Always, there's only one truth!
Would it be possible to make it a SIG requirement to reach out to
relevant RHEL Product Owners before the scope is extended to additional components?
The RHEL team(s) will be collaborating and participating in the SIG. You shouldn't need to reach out to us, as we'll watch mailing lists and participate in Matrix where applicable. We're having various internal kickoff meetings with our kernel teams, and highlighting the importance of the community and CentOS for enablement. You'll see Amnon Ilan and myself actively participating in the SIG.
-Scott M. Herold
Florian,
We would love RHEL Product Owners participating upstream within the community. Several of the SIGs have very active Red Hat contributors and we always welcome more, whether POs, PMs, engineers, or tech writers among many opportunities.
Closer communication and coordination is always welcome and we have several initiatives to improve this. I'm not sure if you were thinking about attending CentOS Connect at the end of the month in Brussels or not but would love to have you join us.
Amy
*Amy Marrich*
She/Her/Hers
Principal Technical Marketing Manager - Cloud Platforms
Red Hat, Inc https://www.redhat.com/
amy@redhat.com
Mobile: 954-818-0514
Slack: amarrich
IRC: spotz
On Thu, Jan 15, 2026 at 2:02 AM Florian Weimer fweimer@redhat.com wrote:
- Amy Marrich via devel:
Deliverables
- SIG Repositories: builds of the kernel, qemu-kvm, and libvirt containing the latest upstream-bound patches.
Would it be possible to make it a SIG requirement to reach out to relevant RHEL Product Owners before the scope is extended to additional components?
It may be possible to complete the work the SIG requires in CentOS Stream proper in some cases.
Thanks, Florian
-
Amy Marrich -
Florian Weimer -
Neal Gompa -
Sandro Bonazzola -
Scott Herold