Notes: 2026-05-27 CoreCollective Virtualization WG kickoff

[Julianus Larson]

Hi,

Thanks for attending the kickoff meeting today. Please find a pdf of the slide deck attached and the meeting notes below.

If you want to reach out to the group, please create a new conversation in this Google group. This can be done in the UI or by emailing virtualization@corecollective.dev.

If you want to reach out to the chairman and community director you can email  virtualization+managers@corecollective.dev.

Also, one of the actions have already been solved. Sumit and Manos agreed that Sumit will chair the VirtIO subgroup.

Best regards,

Julianus Larson, Community Manager   

Quick recap

The Virtualization Working Group kickoff meeting was held to establish the structure and leadership for the new working group within Core Collective, an ARM ecosystem collaboration forum. Julianus Larsson, the community manager, and Mark, the chair, facilitated the meeting with 18 participants. The group discussed organizing into five subgroups: virtualization, simulation, Virtio, FFA, and maintenance, with chairs being appointed for each to help define goals and coordinate efforts. Through a show of hands, participants expressed interest in these subgroups, with approximately 8 people interested in virtualization, 5-6 in simulation, and 3 in FFA. Bertrand agreed to chair the virtualization subgroup, Alex was nominated for simulation, Sumit and Manos discussed co-chairing Virtio, and Achin nominated a colleague for FFA. The group agreed to meet every other week starting in the next few weeks, with quarterly meetings for the whole group to coordinate across subgroups. Grant explained that Core Collective provides a framework for multi-party engineering projects without requiring all work to be done by a single company, allowing groups to control funding and engineering resources.

Next steps

Achin

• Nominate Magbani Chainam (or confirm another colleague) as chair for the FFA subgroup and provide details to the organizers.

Bertrand

• Take on the role of chair for the Virtualization subgroup and help define the subgroup's scope and initiatives.

Julianus

• Reach out to the subgroup chairs (Bertrand, Alex, Sumit/Manos, Achin/colleague, and potentially Elias) to confirm their roles and coordinate initial subgroup meeting schedules.
• Share the slide deck in the Virtualization Working Group after the meeting.
• Organize the creation of a shared calendar for the Virtualization Working Group, including all subgroup meetings.
• Discuss and decide (with the group) whether to create separate email reflectors for each subgroup or use a single mailing list for now.

Collaboration

• Sumit and Manos: Coordinate and decide who will chair the Virtio subgroup, then inform the group of the decision.
• All subgroup chairs: Schedule initial subgroup meetings (suggested every other week, starting within the next fortnight), and work with subgroup members to define main goals, initiatives, and resource/funding commitments.
• All subgroup chairs: Prepare a list of proposed initiatives for each subgroup, ensuring more than one person is interested in each initiative.
• All members: Reach out to other relevant companies and invite them to join the Virtualization Working Group and sign the membership agreement.
• Mark and Julianus: Coordinate with Elias (if interested) regarding possible involvement in subgroup chairing or cross-group meetings.
• Grant/Julianus: Provide updates and details about the planned transition from Google mailing lists to a new platform, and solicit feedback when ready.
• Mark/Grant: Discuss with relevant parties about the possibility of organizing a general Core Collective gathering in Munich in November.

Summary

Virtualization Working Group Kickoff Meeting

The Virtualization Working Group kickoff meeting began with Julianus welcoming attendees and confirming that Mark would present. Mark initially had concerns about accessing the presentation but resolved the issue himself. The meeting started with a small number of attendees, with Julianus as the community manager facilitating the meeting and Mark expected to speak next.

Core Collective ARM Ecosystem Overview

Mark explained that Core Collective is a collaborative forum for the ARM ecosystem designed to accelerate innovation through shared software tools and standards, with a specific focus on virtualization. He clarified that while joining is free, companies must sign a membership agreement and participants will eventually need to contribute resources or effort toward projects they support.

ARM Virtualization Working Group Formation

Mark was appointed chair of the new virtualization working group focused on ARM architecture, including virtualization, hypervisors, and simulation topics. The working group will be organized into five subgroups, though the specific structure and project definitions are still to be determined through discussion. Mark expressed willingness to incorporate ideas from participants and navigate the group's development process.

Subgroup Formation Discussion Meeting

Mark led a discussion about forming subgroups within a wider group, proposing five potential subgroups including virtualization, simulation, and maintenance. The team used a show of hands to gauge interest in each subgroup, with approximately 8 people expressing interest in the virtualization subgroup and similar numbers for other areas. Mark suggested that interested participants should volunteer to chair their respective subgroups and help define their scope and activities.

Virtualization Subgroup Chair Selection

Mark sought volunteers to chair the virtualization subgroup, explaining that the role would involve scheduling meetings, setting agendas, and managing resources with support from Juliana. Grant clarified that the chair position would not be a significant burden and could be transitioned if needed. Bertrand agreed to take on the role of chairing the virtualization group.

Working Group Formation Planning

The team discussed forming working groups with chairs for virtualization, simulation, Virtio, and FFA. Bertrand agreed to chair the virtualization subject, Alex was selected to chair simulation, and Sumit and Manos agreed to coordinate on the Virtio chair role. The group decided to meet every other week starting in the next few weeks, with quarterly coordination meetings planned once working groups establish their goals and initiatives. Sumit agreed to follow up offline regarding the FFA chair nomination, and the team clarified that work could be conducted by anyone regardless of affiliation.

Core Collective Engineering Framework

Grant explained that Core Collective provides a framework for multi-party engineering projects, offering tools and legal structures while allowing companies to control their initiatives and choose their engineering providers. He outlined two paths for engineering work: either Core Collective provides the framework and infrastructure while companies handle the engineering work, or Core Collective can work with an engineering provider chosen by the funding parties. Mark requested attendees to subscribe to the virtualization group and provided email addresses in the chat for connection purposes.

Virtualization Working Group Subgroup Formation

The meeting focused on the formation of subgroups within the Virtualization Working Group. Julianus requested that participants reach out to other companies to join the working group and mentioned that he would share the slide deck after the meeting. The group discussed platform choices, with Zoom being selected as the default for video conferences due to its global availability, though other options like Jitsi were mentioned as alternatives. The conversation ended with a discussion about scheduling future meetings, considering time zones across different regions, and a suggestion for a potential in-person gathering in Munich in November.