Proxmox VE (and also previously libvirt / oVirt.org)

• Cloud driver for private cloud setup #3787

Generic driver for all clouds (both private and public)

• Generic/External internal driver for all OS #2000

Wrapping of libkrun (and libkrun-efi) into CGo:

• Made a small go wrapper to enable using libkrun without krunkit containers/libkrun#350

Note: macOS and Linux have different libraries...

There are also SEV/TDX variants, that I completely ignored. I don't plan on maintaining or updating the wrapper.

AI-generated meeting note

Quick Recap

The team discussed ongoing documentation work and driver development for Lima VM, including networking features and testing approaches using GitHub Actions. They reviewed the status of GSoc tasks, with Akihiro confirming completion of optional work and Jan clarifying the focus of the meeting on wrapping up GSoc activities. The conversation ended with expressions of appreciation and commitment to continue project engagement, along with plans for follow-up feedback on the experience.

Next Steps

• Ansuman to complete the Google Doc shared in the Lima G sock channel.
• Ansuman to revise PR refactor: support external drivers for the recent changes #3910 and submit it for merging.
• Ansuman to keep the citics conscious background from the main package.
• Ansuman to update documentation for driver infrastructure, including make file variables.
• Ansuman to implement the Karen driver in the first week of September.
• Ansuman to remove the copy of B.0 from the boom to the stage.
• Ansuman to investigate the performance of port forwarding.
• Ansuman to provide feedback about his experience with the project after reflection.
• Team to document the concept of internal and external drivers on the website.
• Team to consider creating a sample repo with a skeleton/minimal driver as a starting point for external drivers.

Summary

Document Completion Status Discussion:
Akihiro and Ansuman discussed the status of a document shared in the Lima G sock channel, which Ansuman had not yet completed. Ansuman agreed to revisit and complete the document that day, addressing the comments left by Akihiro.

Lima Networking and Resolver Settings:
The team discussed host resolver settings for QEMU and driver capabilities, with Jan clarifying that Vz is using Gvisor Tap which has its own built-in resolver. They agreed to keep networking features in core Lima for now rather than separating them out immediately, with Jan suggesting this could be a phase one before starting a new project to separate networking. Anders mentioned that CI data is currently required but can be configured differently for ISO, cloud init, or Lima, though there's no complete opt-out option.

Lima VM Driver Development Updates:
The team discussed documentation and driver development for Lima VM. Ansuman agreed to update documentation for surface installation and explain internal/external drivers, while Jan suggested creating a sample repository with a minimal driver example and tutorial to help new contributors. Anders shared progress on a cloud driver implementation, which was simpler than expected. The team also discussed testing approaches, including using GitHub Actions and potentially creating mock drivers. They briefly touched on port forwarding performance and the possibility of implementing a Krun driver, though this would require further investigation.

GSoc Task Completion Status:
The team discussed the completion status of GSoc tasks, with Akihiro confirming that the optional task (PR 310) was nearly finished and only required merging. Jan clarified that the meeting was intended to focus on wrapping up GSoc, and Anders confirmed that while K1 was a potential stretch target, it would be excluded from the GSoc report.

Project Feedback and Commitment Discussion:
The conversation ended with Akihiro expressing appreciation for Ansuman's contributions to the project, and Ansuman confirming his commitment to continue engaging with the community. Anders suggested that Ansuman provide feedback on his experience with the project after completing his current tasks, offering to follow up in a week or two. The conversation ended with participants expressing their thanks and farewells.