- Rust-vmm - lists.opendev.org

Add Xen support to vmm-reference? (was Re: Call for topics and skipping next weeks sync)
by Alex Bennée 15 Jul '22

15 Jul '22

(added xen/rust-vmm to CC) Trilok Soni <tsoni(a)quicinc.com> writes: > Hello Alex, > > It would be good to check if there is a enough interest to make > "vmm-reference" extended to work w/ Type-1 Hypervisor like Xen. This > will clean-up vmm-reference w/ KVM references, and it will be a good > independent tool to test the new interfaces additions in the rust-vmm. > > https://github.com/rust-vmm/vmm-reference We have certainly talked about it before and the we've put in some of the groundwork with the xen-sys crate (https://github.com/rust-vmm/xen-sys) which we are using for the xen-vhost-master work. Off the top of my head we would need to work out: - Which additional APIs need implementing for VMM lifecycle management - How the run loop would look - AIUI Hyper-V munges this for rust-vmm by providing a KVM-like ioctl API (POC via CrosVM: https://github.com/petrutlucian94/crosvm/tree/windows) - See also https://github.com/rust-vmm/community/issues/121 - Would we aim for full independence from the exiting Xen userspace libs? - xen-vhost-master was brought up using them, now slowly being replaced with pure rust I've added it as a discussion topic for the sync call: https://calendar.google.com/event?action=TEMPLATE&tmeid=NW83NXNsZ2Q1NmF0bTE… It would be great is we could get any interested folks from the rust-vmm and Xen communities to come along to the call. > > ---Trilok Soni > > -----Original Message----- > From: Alex Bennée <alex.bennee(a)linaro.org> > Sent: Wednesday, July 13, 2022 2:16 AM > To: Stratos Mailing List <stratos-dev(a)op-lists.linaro.org> > Cc: Viresh Kumar <viresh.kumar(a)linaro.org>; Mathieu Poirier > <mathieu.poirier(a)linaro.org>; Mike Holmes <mike.holmes(a)linaro.org>; > Azzedine Touzni <atouzni(a)qti.qualcomm.com>; Stefano Stabellini > <stefano.stabellini(a)xilinx.com>; Christopher Clark > <christopher.w.clark(a)gmail.com>; Arnd Bergmann > <arnd.bergmann(a)linaro.org>; Peter Griffin <peter.griffin(a)linaro.org>; > AKASHI Takahiro <takahiro.akashi(a)linaro.org>; Artem Mygaiev > <Artem_Mygaiev(a)epam.com>; Leonardo Garcia > <leonardo.garcia(a)linaro.org>; Trilok Soni <tsoni(a)quicinc.com>; Randy > Linnell <randy.linnell(a)linaro.org>; don.harbin(a)linaro.org; Sumit > Semwal <sumit.semwal(a)linaro.org> > Subject: Call for topics and skipping next weeks sync > > WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. > > Hi All, > > I'll be on holiday (moving house) next week so I won't be able to > chair the Stratos sync meeting. As it is the middle of summer I'm > going to propose we skip next weeks sync and re-convene on the 3rd of > August. Any objections? > > While on the subject of sync meetings are there any topics to discuss. > We've had some discussions on next rust-vmm device to implement but > beyond a vague "maybe virtio-gpu to help with demos" I don't think > we've nailed it down. virtio-can also keeps getting mentioned and > while useful I'm wary it's not pushing our exploration of the > possibilities of virtio further. > > I did a talk at GST22 last week which was an overview of VirtIO and what we had done so far as well as discussing some future directions. You can see the talk at: > > https://huawei-events.de/en/gsts22-j83dco-vod.htm > (Day 2 stream, Chapter 6/TS 05:13:00) > > In it potential future areas of exploration where: > > Improve Xen API > ═══════════════ > > • More standard mmap > • direct irqfd/eventfd routing > > Memory Isolation > ════════════════ > > • fat virtqueue > • iommu/grants vs regions > (x-over with pKVM/CCA?) > > Bare metal rust > ═══════════════ > > • re-use exiting VirtIO logic > • but without POSIX layer > > I'd like to get a better steer on what we should focus on next after we've demoed our existing rust-vmm daemons and the Xen vhost-master work. -- Alex Bennée

2 1

Licensing Issue in rust-vmm crates
by Andreea Florescu 06 Jul '22

06 Jul '22

[Resending this email from my personal email address as it seems like my other email got into spam for most of you :(] Hey folks, afaria(a)redhat.com reported an issue [1] with the license of some of the rust-vmm crates. In our first rust-vmm meetup we decided the license for the crates to be BSD-3-Clause OR Apache 2.0 (as it's also specified in the meeting notes available here [2]), but when we did the implementation of the crate it looks like we wrote the license for some of the files and crates as "Apache-2.0 AND BSD-3-Clause" instead. This license is unfortunately incompatible with projects such QEMU, and makes the rust-vmm crates impossible to use. With this email I would like to get your agreement to update the license to one that is compatible with QEMU and the other known customers of rust-vmm. One thing that we need to discuss is what the license should be. As there is code in vmm-sys-util coming directly from Crosvm I don't think a Apache 2.0 OR BSD-3-Clause license is appropriate because from my understanding this would require the Crosvm code to be re-licensed as Apache 2.0 OR BSD-3-Clause as well. I would like to propose to re-license it as BSD-3-Clause as this is compatible with the licenses of all projects. More details about the specific files where this is a problem are available in the issue [1]. Thanks, Andreea [1] https://github.com/rust-vmm/vmm-sys-util/issues/161 [2] http://lists.opendev.org/pipermail/rust-vmm/2019-May/000200.html

6 7

Fwd: October 2022 PTG Dates & Registration
by Kendall Nelson 05 Jul '22

05 Jul '22

Hello Everyone! As you may have seen, we announced the next PTG[1] which will take place October 17-20, 2022 in Columbus, Ohio! Registration is now open[2]. We have also secured a limited, discounted hotel block for PTG attendees [3]. If your organization is interested in sponsoring the event, information on packages and pricing are now available on the PTG website [1] or feel free to reach out directly to ptg(a)openinfra.dev. Can't wait to SEE you all there! -Kendall Nelson (diablo_rojo) [1] https://openinfra.dev/ptg/ [2] https://openinfra-ptg.eventbrite.com/ [3] https://www.hyatt.com/en-US/group-booking/CMHRC/G-L0RT

1 0

Fwd: October PTG 2022 Team Signup
by Kendall Nelson 29 Jun '22

29 Jun '22

Hi Everyone, At the Berlin Summit, we announced the next PTG will be held from Monday, October 17th to Thursday, October 20th, 2022 in Columbus, OH! To signup your team, you must complete the survey[1] by August 12th at 7:00 UTC. We NEED accurate contact information for the moderator of your team’s sessions. This is because the survey information will be used to organize the schedule signups which will be done via the PTGBot. If you are not on IRC, please get setup[2] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[3] as well. If you have any questions, please reach out! Information about signing up for timeslots will be sent to moderators mid to late August. Registration will open soon! A discounted room block at the PTG venue will be available. Continue to visit openinfra.dev/ptg for updates. -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2022_ptg_team_signup [2] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [3] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 0

Licensing Issue in rust-vmm crates
by Florescu, Andreea 17 Jun '22

17 Jun '22

Hey folks, afaria(a)redhat.com<mailto:afaria@redhat.com> reported an issue [1] with the license of some of the rust-vmm crates. In our first rust-vmm meetup we decided the license for the crates to be BSD-3-Clause OR Apache 2.0 (as it's also specified in the meeting notes available here [2]), but when we did the implementation of the crate it looks like we wrote the license for some of the files and crates as "Apache-2.0 AND BSD-3-Clause" instead. This license is unfortunately incompatible with projects such QEMU, and makes the rust-vmm crates impossible to use. With this email I would like to get your agreement to update the license to one that is compatible with QEMU and the other known customers of rust-vmm. One thing that we need to discuss is what the license should be. As there is code in vmm-sys-util coming directly from Crosvm I don't think a Apache 2.0 OR BSD-3-Clause license is appropriate because from my understanding this would require the Crosvm code to be re-licensed as Apache 2.0 OR BSD-3-Clause as well. I would like to propose to re-license it as BSD-3-Clause as this is compatible with the licenses of all projects. More details about the specific files where this is a problem are available in the issue [1]. Thanks, Andreea [1] https://github.com/rust-vmm/vmm-sys-util/issues/161 [2] http://lists.opendev.org/pipermail/rust-vmm/2019-May/000200.html Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.

1 0

2022 Grace Hopper Celebration Open Source Day - Call for Projects
by Open Source Day AnitaB GHC 08 Jun '22

08 Jun '22

*Hello,We're excited to announce that the 2022 Grace Hopper Celebration Open Source Day is open for projects <https://bit.ly/osd22-cfp>!Open Source Day (OSD) is an all-day hack-a-thon at Grace Hopper Celebration in which participants of all levels contribute and learn about Open Source while working on projects designed to solve real-world problems. OSD provides an opportunity for attendees of all skill levels and backgrounds to learn and experience open source contributions with the support of project maintainers, experienced mentors, and expert speakers, providing a fast track to becoming open source contributors.This year, OSD will be a virtual pre-event before the Grace Hopper Celebration, scheduled for Friday, September 16, 2022, from 8:00am to 3:00pm U.S. Pacific Time.If you're an open source project maintainer, we invite you to submit your project to be part of Open Source Day 2022!OSD provides a great way for open source project maintainers to promote your project, earn new contributors, and improve overall health of your project. In addition, you will take part in the movement to increase diversity in open source! According to the 2021 Linux foundation DEI Survey report <https://www.linuxfoundation.org/wp-content/uploads/LFResearch_DEISurvey_Rep…>, only 14% of open source participants identify as women and 4% as non-binary or third gender and other estimates are a lot lower. Join us and be part of the change!CFP link: https://bit.ly/osd22-cfp-projects <https://bit.ly/osd22-cfp-projects>One of the big focuses of Open Source Day is highlighting women open source maintainers. If you are aware of any open source projects with women maintainers whom you think are a great fit for this opportunity, please forward this announcement to them.Note: Selected project maintainers will receive a complimentary virtual ticket to the 2022 Grace Hopper Celebration.Best regards,The Open Source Day Team* -- The Open Source Day Team

1 0

Moderation queue flushed
by Jeremy Stanley 01 Jun '22

01 Jun '22

Just a heads up that I flushed some several dozen messages which were waiting for a moderator to approve, so if you received a sudden flood of messages for the ML (some dating back to February), that's why. The majority were held because they were being sent from or cross-posted by people who aren't subscribed to this list, or because they had very large recipient lists (>10 addresses), or were over the default 40KB size limit. On a related note, if anyone is interested in helping check the moderation queue for this list regularly, please let me know. -- Jeremy Stanley

2 1

Remaining Xen enabling work for rust-vmm
by Alex Bennée 23 May '22

23 May '22

Hi, This is one of several emails to follow up on Linaro's internal KWG sprint last week in Cambridge where a number of Project Stratos hackers discussed what next steps we have and started to think about future work. I am splitting the update into several emails so I can freely CC the relevant lists for each without too much cross-posting spam. Intro ===== We've made good progress over the last year and have up-streamed a number of device models as vhost-user daemons. We have also gotten our first proof of concept build of the xen-vhost-master which has allowed us to reuse these backends on the Xen hypervisor. https://github.com/vireshk/xen-vhost-master Remaining Work ============== Scope out the remainder of APIs needed for oxerun ------------------------------------------------- The current xen-vhost-master uses a combination of the native rust oxerun and a bindgen import of libxensys (https://github.com/vireshk/libxen-sys) and a number of xen libraries built directly in the xen-vhost-master repository. Our intention for the Stratos work is to remove any C dependency for the rust backend and use native rust bindings to talk to the hypervisor control ioctl. Identifying what is needed should be easy enough as we can see where in master repository C calls are being made. This work should be broken down into groups in JIRA so the work can be efficiently divided up. Currently our focus for the rust-vmm repo is to support the vhost-user daemons but a wider conversation needs to be had with the community about the rest of the tooling involved in the creation and control of DomU guests. For Stratos we would like to explore the possibilities of bare metal monitor programs for dom0-less (or dom0-light?) setups. Strategy for testing oxerun in the rust-vmm project --------------------------------------------------- Currently the rust-vmm projects rely heavily on unit tests and a (mostly) x86 build farm. While building for non-x86 architectures isn't insurmountable doing blackbox testing on real hypervisors isn't currently supported. Given the low level nature of the interactions simply mocking the ioctl interface to the kernel will not likely sufficiently exercise things. We need a way to execute tests on a real system with a real Xen hypervisor and dom0 setup. We can either: - somehow add Xen hosts to the Buildkite runner pool for rust-vmm or - investigate using QEMU TCG as a portable system in a box to run Xen and guests Currently this is blocking wider up-streaming of the oxerun code to https://github.com/rust-vmm/xen-sys in the same way other rust-vmm repos work. See also ======== Other subjects discussed will be the subject of other emails today with different distribution lists. These are: - Remaining work for vhost-device - Additional virtio devices - Integrating rust-vmm with QEMU Happy reading ;-) -- Alex Bennée

1 0

vhost-device outstanding tasks
by Alex Bennée 23 May '22

23 May '22

Hi, This is one of several emails to follow up on Linaro's internal KWG sprint last week in Cambridge where a number of Project Stratos hackers discussed what next steps we have and started to think about future work. I am splitting the update into several emails so I can freely CC the relevant lists for each without too much cross-posting spam. Intro ===== We've made good progress over the last year and have up-streamed a number of device models as vhost-user daemons. We have also gotten our first proof of concept build of the xen-vhost-master which has allowed us to reuse these backends on the Xen hypervisor. Outstanding work ================ vm-virtio definitions --------------------- Given our vhost-user daemons were not re-implementing existing virtio device models a number of the queue handling definitions are in the vhost-device repository itself. As discussed before now we have these working we should migrate common definitions to the vm-virtio crate so in-VMM virtio emulation can re-use this code. Get outstanding vsock PR merged ------------------------------- We actually have two outstanding PR's against the vhost-device repository which implement virtio-vsock and virtio-scsi. They were done as GSoC projects but didn't get merged at the time due to lack of review. They currently have outstanding requests for code changes but due to the nature of GSoC it looks like the original authors don't have time to make the changes which is understandable given changes the repository has gone through over the last two years. I'm agnostic about virtio-scsi but given the usefulness of virtio-vsock it seems a shame to leave an implementation to wither on a branch. There has been some work on vm-virtio to improve the queue handling and with Andreea's help I have a branch that uses that. Should we just pick up the branch and finish the pull request process? Sort out an official vhost-master repository in rust-vmm -------------------------------------------------------- The rust-vmm project has the vhost-user-backend which implements the core backend behaviour for handling vhost-user messages. There is also an abstraction for vhost (user and kernel handling) from the VMM side in the vhost repository. However it doesn't provide everything needed to implement a full vhost-master. Currently Viresh is using: https://github.com/vireshk/vhost-user-master is the xen-vhost-master project which is constructed from the in-VMM vhost-master bits from Cloud Hypervisor. We should get this properly up-streamed into the rust-vmm project. Should this be merged into the existing rust-vmm/vhost repository or does it require it's own repository? Properly document and support cross-compilation ----------------------------------------------- Currently most of our testing is on Arm systems and currently we are either: - hacking up the local repo for cross-compilation or - doing a "native" build in an QEMU emulated Aarch64 system the second option is potentially quite slow, at least for the first build. Given building backends for non-x86 systems is core to Linaro's goals we should properly support cross compilation for the vhost-device repository and document it. This should be also be enabled in the CI to ensure the configuration doesn't bitrot. See Also ======== Other subjects discussed will be the subject of other emails today with different distribution lists. These are: - Xen specific enabling work - Additional virtio devices - Integrating rust-vmm with QEMU Happy reading ;-) -- Alex Bennée

1 0

CFP Reminder: KVM Forum 2022
by Peter Maydell 18 May '22

18 May '22

================================================================ KVM Forum 2022 September 12-14, 2022 Dublin, Ireland & Virtual All submissions must be received before *** Friday June 3rd, 2022 at 23:59 PDT *** ================================================================ KVM Forum is an annual event that presents a rare opportunity for developers and users to discuss the state of Linux virtualization technology and plan for the challenges ahead. This highly technical conference unites the developers who drive KVM development and the users who depend on KVM as part of their offerings, or to power their data centers and clouds. Sessions include updates on the state of the KVM virtualization stack, planning for the future, and many opportunities for attendees to collaborate. Over the years since its inclusion in the mainline kernel, KVM has become a critical part of the FOSS cloud infrastructure. Come join us in continuing to improve the KVM ecosystem. This year's event is in Dublin, Ireland, but it is a combined physical+virtual conference: both speaking and attending can be virtual if you prefer. For more details, registration, travel and health and safety information, visit: https://events.linuxfoundation.org/kvm-forum/ For more information, some suggested topics, and to submit proposals, please see: https://events.linuxfoundation.org/kvm-forum/program/cfp/ We encourage you to submit and reach out to us should you have any questions. The program committee may be contacted as a group via email: kvm-forum-2022-pc(a)redhat.com. Apologies from the Program Committee for not posting an announcement of the CFP to these lists sooner.

1 0