- Rust-vmm - lists.opendev.org

Central repo for VirtIO conformance tests?
by Alex Bennée 31 Mar '25

31 Mar '25

Hi, We've been working with Panasonic to expand the testing of VirtIO across a range of hypervisors and VMMs. We've tackled this with two approaches: - simple unikernel to verify features and basic functions common - rootfs images to exercise the whole device The unikernel utilizes rcore-os's no_std VirtIO drivers to discover and initialize a range of VirtIO devices. The tests mostly focus on checking no unknown feature bits are advertised as well as ensuring features dependencies are properly realizable. This is useful for those interested in moving workloads between hypervisors to ensure you don't end up relying on a proprietary feature that aren't available elsewhere. The virgl test also does some very basic blob mapping to check the underlying mechanics are working. The unikernel outputs a TAP stream to make integrating into a test harness easier. You can find the current state here: https://git.codelinaro.org/manos.pitsidianakis/virtio-tests While we only build an aarch64 unikernel the upstream drivers have examples for riscv and x86_64 as well. As more complex VirtIO devices like GPUs tend to have a significant user-space component, we have also started building Linux rootfs images to exercise those. The images themselves are built against a baseline architecture so they can be used on as wide a range of hardware as possible. They have been built with buildroot to make them lightweight and as close to the upstream projects as possible without relying on particular distro support. You may have seen the recent aarch64 GPU image being added to QEMU's functional tests recently: https://gitlab.com/qemu-project/qemu/-/blob/master/tests/functional/test_aa… I'm currently working on a similar image utilizing a subset of the blktests project to exercise the VirtIO block devices. The various recipes can be found here: https://gitlab.com/stsquad/buildroot/-/tree/adding-blktests?ref_type=heads although the intention is for all the recipes and basic QEMU based tests to be up-streamed into buildroot in due course. While I will no doubt expand the functional tests in QEMU over time to utilize these images, there is a wider question of where would be a good place to host a more comprehensive VirtIO test suite? While useful for validating proprietary hypervisors there are also a bunch of other VMMs and VirtIO backends other than QEMU: - rust-vmm's vhost-device collection of vhost-user backends - CrosVM - Cloud Hypervisor - libkrun As well as using VirtIO backends with other hypervisors such as Xen, Gunyah and WHPX. So this brings me to the question posed in the subject. Where would a good place be to host these conformance tests? My initial thought was to see if this is something OASIS could host as part of the specification however I'm not sure OASIS is set up for such a thing. We could host it as part of the QEMU project as a service to the wider community. While it should be pretty easy to expand QEMU's own tests to work with multiple hypervisors, its test machinery isn't really setup for non-QEMU VMMs. Ideally we would want the core repository to be able to run on multiple hypervisors and use different VMMs and backends depending on where they are being run. The other option I considered was hosting with the rust-vmm project - although maybe that just makes sense for the unikernel tests as they are rust based. We certainly need more automated testing of the vhost-device repository which can serve as a backend to multiple VMMs and hypervisors. So what do people think? Where would be a good place for common test repository to live? -- Alex Bennée Virtualisation Tech Lead @ Linaro

4 5

Canceled: rust-vmm sync meeting
by Florescu, Andreea 06 Mar '25

06 Mar '25

New invite sent for earlier in the day.

1 0

Canceled: rust-vmm sync meeting
by Florescu, Andreea 06 Mar '25

06 Mar '25

New invite sent for earlier in the day.

1 0

QEMU is participating in Google Summer of Code 2025
by Stefan Hajnoczi 05 Mar '25

05 Mar '25

Dear QEMU, KVM, and rust-vmm communities, QEMU has been accepted into the Google Summer of Code 2025 open source internship program! GSoC is a paid, remote work, summer internship where first-time contributors work with mentors to begin their open source involvement. It's a great way to dive into becoming an open source developer! Applicants can now check out the project ideas list and get in touch with mentors to discuss the idea: https://wiki.qemu.org/Google_Summer_of_Code_2025 This year we have QEMU and rust-vmm project ideas in C, Python, and Rust. If you are interested in participating in GSoC 2025, please see the GSoC website for details about eligibility and how the internship program works: https://summerofcode.withgoogle.com/ Stefan

1 0

Call for Participation
by 何若轻 03 Mar '25

03 Mar '25

Dear Rust-VMM community, This is an invitation to Open Source Promotion Plan (OSPP) held by ISCAS (Institute of Software, Chinese Academy of Sciences). About Open Source Promotion Plan -------------------------------- The Open Source Promotion Plan is a summer program organized by the Open Source Software Supply Chain Promotion Plan of the Institute of Software Chinese Academy of Sciences from 2020. It aims to encourage university students to actively participate in the development and maintenance of open source software, cultivate and discover more outstanding developers, promote the vigorous development of excellent open source software communities, and assist in the construction of open source software supply chains. The program collaborates with various open source communities, providing project development tasks for the development and maintenance of important open source software, and is open for registration to university students worldwide. Students can independently choose projects they are interested in, apply, and after selection, carry out development under the guidance of project developers (community mentors). Based on the project's difficulty and completion, participants (*mentors and mentees*) will receive a bonus, and a completion certificate for mentees. Who can Mentor ---------------------- Regular contributors, maintainers and gatekeepers of Rust-VMM can participate as mentors. Mentorship involves about 5 hours of time commitment per week to communicate with the intern, review their patches, etc. Time is also required during the intern selection phase to communicate with applicants. Being a mentor is an opportunity to help someone get started in open source development, will give you experience with managing a project in a low-stakes environment, and a chance to explore interesting technical ideas that you may not have time to develop yourself. Please read mentor guide: https://summer-ospp.ac.cn/help/en/mentor/ How to Participate ---------------------- As an organization, RustVMM need a `community contact` who is responsible for registering RustVMM org in OSPP, and submit passed proposals to OSPP. As a mentor, you should submit (raise a PR) a project proposal in: https://github.com/rust-vmm/community, if your PR gets merged, then your proposal is considered as accepted. Proposals will be reviewed and selected by RustVMM community. More information ---------------------- You can find out about the process we follow here: Official website: https://summer-ospp.ac.cn/ Timeline: https://blog-en.summer-ospp.ac.cn/archives/timeline FAQ: https://blog-en.summer-ospp.ac.cn/archives/FAQ

1 0

rust-vmm sync meeting - new schedule: Monday @ 14:00 UTC every 2 weeks
by Stefano Garzarella 28 Feb '25

28 Feb '25

Hi all, after the poll [1] we did this week, it looks like the new preferred time for the bi-weekly rust-vmm meeting is: Monday @ 14:00 UTC every 2 weeks We will try this new schedule starting from the next meeting, which is next Monday (March 3rd). I'm attaching an updated ICS file (hope it works). Thanks, Stefano

1 0

Changing rust-vmm sync meeting time
by Stefano Garzarella 25 Feb '25

25 Feb '25

Hi all, during the last community call, we discussed anticipating the meeting time. Since we don't have any US people joining, and most of us are based in UE or China, should be better to find another time, especially for people joining from China. We found 4 potential 30 minutes slots (11-12 UTC, 14-15 UTC) every 2 Mondays as usual (next one: March 3rd). I just create a doodle to choose the best option: https://doodle.com/group-poll/participate/bkBmDA6a Please vote, so we can choose a new time for the meeting. Thanks, Stefano

1 0

Fwd: [Data Migration] Migration has been scheduled for rust-vmm
by Patrick Roy 14 Feb '25

14 Feb '25

Hey all, An update from buildkite on the database migration that we got a heads up about last year. Seems like they want to do the migration for the rust-vmm organization on March 9th between 7am and 9am UTC (I'll try to remember to also forward their follow up email for when the migration is done) Best, Patrick -------- Forwarded Message -------- X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Received: from EX19D015EUB003.ant.amazon.com (10.252.51.113) by EX19D015EUB004.ant.amazon.com (10.252.51.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.1544.14 via Mailbox Transport; Fri, 14 Feb 2025 04:54:34 +0000 Received: from EX19MTAEUA002.ant.amazon.com (10.252.50.126) by EX19D015EUB003.ant.amazon.com (10.252.51.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.1544.14; Fri, 14 Feb 2025 04:54:34 +0000 Received: from fireeye-ex-3011.amazon.com (10.252.50.132) by mail-relay.amazon.com (10.252.50.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.39 via Frontend Transport; Fri, 14 Feb 2025 04:54:35 +0000 Received: by fireeye-ex-3011.amazon.com (Postfix, from userid 600) id 4YvKTk1M5wz392fS; Fri, 14 Feb 2025 04:54:11 +0000 (UTC) Received: from internal-dub-in-013.mail-perimeter.amazon.com (unknown [10.3.250.209]) by fireeye-ex-3011.amazon.com (Postfix) with ESMTPS id 4YvKTG19kmz392g3 for <roypat(a)amazon.co.uk>; Fri, 14 Feb 2025 04:54:10 +0000 (UTC) X-CSE-ConnectionGUID: T1rmxuqPRDGc5wXJbWJ+HA== X-CSE-MsgGUID: u5L0WLP4R7W6Uac8n5ofNQ== Received-SPF: None (cluster02.eu-west-1.mail-perimeter.amazon.com: no sender authenticity information available from domain of support(a)buildkite.com) identity=pra; client-ip=198.2.186.14; receiver=cluster02.eu-west-1.mail-perimeter.amazon.com; envelope-from="bounce-md_30232831.67aecc70.v1-1ba838c4316242e7a24fc1660805f916(a)bounce.buildkite.com"; x-sender="support(a)buildkite.com"; x-conformance=sidf_compatible Received-SPF: Pass (cluster02.eu-west-1.mail-perimeter.amazon.com: domain of bounce-md_30232831.67aecc70.v1-1ba838c4316242e7a24fc1660805f916(a)bounce.buildkite.com designates 198.2.186.14 as permitted sender) identity=mailfrom; client-ip=198.2.186.14; receiver=cluster02.eu-west-1.mail-perimeter.amazon.com; envelope-from="bounce-md_30232831.67aecc70.v1-1ba838c4316242e7a24fc1660805f916(a)bounce.buildkite.com"; x-sender="bounce-md_30232831.67aecc70.v1-1ba838c4316242e7a24fc1660805f916(a)bounce.buildkite.com"; x-conformance=sidf_compatible; x-record-type="v=spf1"; x-record-text="v=spf1 ip4:198.2.128.0/24 ip4:198.2.132.0/22 ip4:198.2.136.0/23 ip4:198.2.145.0/24 ip4:198.2.186.0/23 ip4:205.201.131.128/25 ip4:205.201.134.128/25 ip4:205.201.136.0/23 ip4:205.201.139.0/24 ip4:198.2.177.0/24 ip4:198.2.178.0/23 ip4:198.2.180.0/24 ~all" Received-SPF: Pass (cluster02.eu-west-1.mail-perimeter.amazon.com: domain of postmaster(a)mail186-14.suw21.mandrillapp.com designates 198.2.186.14 as permitted sender) identity=helo; client-ip=198.2.186.14; receiver=cluster02.eu-west-1.mail-perimeter.amazon.com; envelope-from="bounce-md_30232831.67aecc70.v1-1ba838c4316242e7a24fc1660805f916(a)bounce.buildkite.com"; x-sender="postmaster(a)mail186-14.suw21.mandrillapp.com"; x-conformance=sidf_compatible; x-record-type="v=spf1"; x-record-text="v=spf1 ip4:198.2.186.14 include:spf.mandrillapp.com -all" Authentication-Results: cluster02.eu-west-1.mail-perimeter.amazon.com; spf=None smtp.pra=support(a)buildkite.com; spf=Pass smtp.mailfrom=bounce-md_30232831.67aecc70.v1-1ba838c4316242e7a24fc1660805f916(a)bounce.buildkite.com; spf=Pass smtp.helo=postmaster(a)mail186-14.suw21.mandrillapp.com; dkim=pass (signature verified) header.i=(a)mandrillapp.com; dmarc=pass (p=quarantine dis=none) d=buildkite.com X-Amazon-External-Envelope-Sender: bounce-md_30232831.67aecc70.v1-1ba838c4316242e7a24fc1660805f916(a)bounce.buildkite.com X-Amazon-External-Envelope-Recipient: roypat(a)amazon.co.uk X-Amazon-External-Source: yes X-Amazon-Approved-Domain: no X-ThreatScanner-Verdict: Negative X-IPAS-Result: A0EmAADUy65new66AsZaDg0BAQEBAQEBAQUBAQESAQEBAwMBAQGCAgMBAQELAYFAWyh9gQ0HCEiEVoh8iHQohBaEQ5NAgWqBLCglEjkLBAEBAwSEOkaLDQIfBgEEMwYOAQIBAgEBAQEBAwIDAQEBAQEBAQEBDQEBBQEBAQIBAwQGAQIQAQFCSYVLMA2CW4EsZQk4AQEBAQEBAQEBAQEBAQEbAggFXgEBMwETHQEBOB4xDQJfgQeCDQGCZAMRokABjQIBAXkoIVYTgQGCDAEBBgQDAgKBTUHbbAMGHoEqAYhOASqBMgKDfUuEPCcbP4FOgTyBWXmCQYI8ARIBTiCDDhmCUIIzhCIlZ4sogRGCPoIAhFmBKzKDI2mJa4FHIgMmMywBVRMXCwcFgTk4AyAKNhQEGQIUHQ8GEARqejmCDmlJOgINAjWCHiRYgitqBAWDZYRDhE2CQ1GCRIISdIVdAoUFZx1AAgELbT03BgMLGwYrnnwKEFs9gzgCYHFZcRINPRwiagJVklKQf6FvhCWDfyOHdpU0BhMvhAODIYllhk6GHYxeHphfIo1ihBCRGDAchTaBfSRJI3BNIxWBWYFJUhkPjiEHgScBAoJJjzS6NkM1PAIHCwEBAwmQByOBSwEB IronPort-PHdr: A9a23:Ec9cGRZKQYUE5h0/Z85B5eD/LTF1x4qcDmcuAnoPtbtCf+yZ8oj4O wSHvLMx1wWPBd2Qt6Ib0KL/iOPJZy8p2d65qncMcZhBBVcuqP49uEgNJvDAImDAaMDQUiohA c5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aFRrwLxd6KfroEYDOkcu3y/qy+5rOaAlUmTaxe7x/I RuooQnLqsUanYRuJ6kyxxbLrHZDZvhby35vKV+PkBnw4du98oR++CpKofIh8MBAUaT+f6smS LFTESorPWMo6sD1rBfPVQSB6GMTXWkPjBdGDBXL4An1UZntvCT6sPF92DSBMs3tUb80QzWi4 Lx1RxLulSwKKiQ28GDTisx3kaJbvBesrAFxzoLIfI2YMud1c6XAdt0YWGVBRN5cWSxcDI2ib IUBAeUOMvpDoobnu1cDtwGzCRWwCO7tzDJDm3/43bc90+QkCQzLwREgH9MKsHvJr9X1NbsSX v6ox6TP1jXDcutW2S/66IjSbhAsuuqDXa9xccrV1EYvFALFjkmOpoD/IzyV0eENvnGd4uF9W u2hl3QppBttojiz2MgskI/Ji5oLx17E9St13oU4KNykRENnb9CpH5Reuz2HOoZyX84vX2Nlt SUmxrAEt5O2cicExIg5yhPDa/GKd4eG7B3tWeuSJzpzmXxreLW6hxmo8EigzPXxWdKp0FZLq ipKj9rMtnER1xPN8MSIVvx9/kKn1D2S1A7T8vlJLV0wmKfYMZIt3KQ8mocQvEnCBCP6hUr7g LeLekk45uSk8frrb7r8qpOBNIJ4lBvyPrkzlsGxB+kzLxIAUHKB+eum0b3u5U35T6tOjv0xi qTZtYrVJcUfpqKkAAJY058v5wuwAju8y9QYgHcGIExYdB6diojmIVfOL+3iDfe+h1SslC1kx +jePrH7HprNKX3DnK/gfbZ79UFc1BI+wc1b6p9XEL0NPuj/VlLyudHZFBM1LgO5z/7iCNpn1 4MeXWyPArWeMKPXqVKH/eUvI/SKZIAJpjnxMv0l6OP2gnI3hVMRY6ek0YUUZX22A/hqOUSUb Hj2jdgfDWgFoggzQPDwhF2cTDJffmu+ULkm6Tw4Bo+rDpvMS4+jjbCc3Sq3AJJban5YBV2OC 3jkaYqJW/kQZy6PI8JskyAIWLu9R4Ih2xGjsBL2xrt8I+XP/S0YqJTj28Rr6OHJjh4y6D10D 8CA3GGOTmF0gn0HSyUq06B4pExx0k2D3rRgg/xECdxT4OtEUh09NZ/c1+x1EczyVxnbcdeMU lmnQ9KmATcrQt0txN8CeVt9G9a6ghDFxCWlG6UVmKCTBJwo7qLc2GD8K9tlx3bJyqYhiFooT NFXOGKom6Bz7xLTCJDXk0uajainbaEc0zTM9GeH0GaDv0BVXBdtXajKR3wffVbWrNrn6k/fV bOuDK4oMg1cxs6YK6tKbtnpgk9eRPf7ItjRf2Wxm2KoCRmVxbOMbY/qdn0H0ijBFUYKjhgf8 muDNQckHCeuv3rTAiZyGFzyfk3g6fJ+qGu1TkIs1Q+Hc1Bv2aet9h4OnfycResc3rIatyclr DV5BEyz0s7LBdSd9EJde/BVbtMw61pB/Wvcvh56ONqrKKUmzlAXdQhtsk7G3hB+GIJG18Mtq TdiyQNuKaOVzRVZcDKC3J3qErnWLGDo+1aocaGSklTfy9Kfov5WwPo5thPusBztXlAl4m1uz /Fc1nKO4ZOMBw1UTJG1Gl04/gJorqvXSjMw64PdyTtnNqzw+i7P1NUzAPkNwxOpbdBZdqiDU hLxQOMAAM37AvErn1Sqbw4JdLRJ6bYsONm6X/Gb2aqnP+d8kXStimERs9M16V6F6ycpEr2A5 J0C2fzNhmNvKh/i2Q7y+smig5tNICoSFzDil3usD9tLa6l7bYsHTn2jJ8Sny9ktz5K4Xnde+ ESiA1cPwNfvch2XPDmfvBYF0Fga+C/vhX7hkGclzml5/vbPj2Telr29L0tYZT4bGDkx6DWNK 4jh0okFTWS4STVwhES95wX7wIlWiPx/CHmLWXVTUnHOIWU+coiQk7ueYuVo68Z71Ec2ULGSe 1efGIXgqRkX2D+xI2wM4T0gbDilt9DYk05UhW+RJn94rz/4VZNczAvStvn9YNMU4DccXyh/j 2uyZDn0FN6v4diSi9L/o/izBUmKBLFabSS59p6Ktiaw+T9EGxq6zJXR+9eyKAM+znCh6v1XU QTps0rTeaLLzrWaL8loflBZFg/E08NbO6Jiw6kZlL8f80lHgbjK23oEnH/0YI4D56nQbXtdY Aduob+d8Fbd8XRvHzGu7pDIfU6wku5NbfSWMkwchiEd0flbLYiY6q5qhjBzm0HjlSX2MMo+p Bc9wOQE70M0m7sTszs/0x3HZ9JzVWlRGDXluwWvyPWjrYFVPWWGSuTg7VNagtG+DenanBxOd k7kW7E5IBFvv/dCNGLsi2HQ6NzlZoDRQ8BIrR2OqhSejI03Sdo8legvlxA8KEHsvHAM5eIx1 DpB86O0hKq2G0w02pnnWUFcBh/pW/EVpWvOtoVwsOybz5L+HaRmFRgoeIbMZrGuOmp315WvL TjXTAB/tWbYALPGGD6a0WV4jnDIHID0CSzMJF5JwMg+QkmiD05YhRg4VwUcp4YgKjqP7ZO/I EhCyG4y3nOk9yNMr4AJfzjZX2LUnD2SRCwQZofKeUke/kRD/UDTKcuE8qdpEjpF+oH0tAWWM T/zj3lgEzRQCQSNUkr4N/y15dCarrbLTuHrNfbKaKWDpatEWvOB1Z+jgcNqqjyRN8GDPXh+A rsw3U8QOBIYAJHchzhWGGQLwnuSNJ/G/Efspn0k5tDqqauwCV2xtNDTW+gaMIB05giuhr2fH +SNhSJ1KjdE29UHwnqbrdp+1l5H1nhxZhW9N4lZpXHVTuHRnY5aI0YbTDMrLPlTwvsE0A0RG e37r9Lp15VfjatmbjUkVQnPgMasN/cXKWOwP0+VOEHZEbmdPjTEzoTWbfGSRLBchuxftFiRl WS3GlPubBGishSsaR21KuBLinP+Xn0Wk4a7bhtrFS3fXcrrODaQYvN+kTBk+qA+hH7BKTwyK z95ICYvz7fF3XlZgut0AWJDrXt8L8SqvQ2D0e7+cLImoaJBPztky+5WwyUFxZYE5ygDfr9bo wfi8fpzkwm6w+rI+ztJVhgehi0u5uPDhl9/EpnVp7J4CHOH5Q8R5m7KIR87tsd5U/P2mJxt+ oT+u7rrJW9n7Njw95oAI/T5F9ylOUEaKh+4FgGLKS4oHQGsUAO+z0VMntDD00WpsaocjYHLl LwQQOUHWlwnPKMGAGhIE9oIGLx5AhM5y/m0iuIq+V66tTLqYdtwhKmWRvO/Wc3BBDC9t9wmB lMT7L7mKaUjB6PF2EFZZXoikNr7Kw2BXuBPsBZRZSQEnV1E7iclc0s61n7/Mxq18nJCSqO4n TkHmAoke+ISyxPHs1lSRDuCiTZor1kqk/a/vw21fHncCaiXWrNXLDWlim52Io/mZRgqNCCWs BI5H2niRJRo3rUwSnJQhl7Gq6poGaVyR48daiFNoJP2L7ISiW1EgAGu+BBA/dKQXMgqhE4ra 5mqt3Vax0d5YcUoIbCFIqdU0kJZgvHGrmqpzOc32AgEOwMA6nmVYnsuv0oFZdHOVALwusBp4 BaJoTZIf3IABbIy9+t3/1k0PfiByS+km6ZINhXob7TbZ7iB7m7Hk8PMClo81UINwlMBtbFty cl2aQ7cTV0mmYjRWB4UNM7OKgBJYo9e3HTWdDyF9//A2ZVvI8CgDOGuRuiL++Jc2xr4TFt2Q dxNqoxBUZWp2VvTBc36LboJyhQx6UL2PlSdC+5VY1SAlzJI54nmlMMngNYDfnAoRWN6NyjfD tf/rQs3m+aORo9sJHoHG5QJLW5zAYu/ki9d+mxNFjiy3/4U0k6L6jbuoSKWBz75PJJ4fPnBQ xRqBZmt/CkntbCsgAvM743GIHvmHd5/u9vD6uIGqtCMDPYHBaJlvRLkkpJDD2evT3aJFNe0I 5bqbIx5Z9vpDH23F1mzvGltFZyrbI30aPbXiAzjTtkM9pfCmWkpPJ/mRjpCQE4u/b1Z6f11P 1ENaMNlP0a471kwZvXhCA2fz9OlTiCnNDpSQ/pe0ej8bLtSnGI3duHv8HI7VdkhyvWvt04AQ JZflhbF2fOqfJVTSwD2E31ZIlWR4HNl0XN8KbxrhOI2xh/SsF0YOiiTMudubT8Ms9I9AAaKK G5tQiojRlCahJbe+APkwb0I/iVcktoVme1IuXTzpNneNRqpUaqns5TRtyM4dZ4tpKgieYDmK 9GN4YvXhSeXDIGFqxCMSie8C/tcl5BcITkNRv5OlCBtNZkMpItF5UkwSsp4LLtKYEU1jpatb zcBb2ZajSQdSpic0SZa2KGxxv7FmwyMNc1kNRUFtNBaj8EcViNqbzlYraqqRYLQ0WSDTzpDJ gBb9glK6A8a8+04Nun4/IrFSoNNwD9Ksrp1VCXMDJxh61r8TCmfn1H5TPyrl+Hh0xhVybrg1 dwSWRg3DkY4pa4ejVYwMLZtN4Eao4/OvjyJaU68t2XoiaOnKFRX1czIZgjgFoOW/WH4UyAa5 TgVXdoWmSGZT9JLw1Q/Mfp4wTcEaJqrcUv/+TE+ko9tAqKkWNrznRAosDMZSjy2VoMHDuhnt BfPVSdkZp23pY+jMpBbUGhWvpaargQ88g0lPiinxJ5bM8wI7CQLWW0FqzKAutC/DchP7pQuV cRWcowm/SmiEa5PM8fJ5WNv/+Xlwy+Cqztg6w7knmnpFvCxFb5X9DRARF15fzmQ+xBxJ+Er7 2HZ/xbHr1Fw8+RaGrXJhkJ06mUYfNgGFnNS2HapIk4mBmJbq/1dMrj9edFdR/UxZAOifRc5E LR1ui7BtVExlnD/bStoswJc8C2IRAg4Wx4ehbL1kCEfoMWqUdMDY6pBdi5EDW+NawmfhDtLs QwHMQdnRtUGD81Zvuhd2IJV+o/aRFytLCwZUQYkPwcxw/1Z00VEtRfQdSfYBAuuPfHB138/N c2WsciiIbH88DAc0tm86rBjruNdGHSrkgbyGZbA9sqlvNTa7RuFKPyhbbfgO3KeRWKQgxvp2 +l8X8GX8XmKbiJRLIR8wndia4XgDWLIPAhLYakcIi85Heh2ZM5HreZTe8J/MP9Yqek3QEvXG FW2RMSmt7FeI0zWRCjCIinJ6eG5rY/JrNm/AaDhasGK23fbUvdyN5Z+5yP8HuSi2otf90zqn /Z1oxorGR6cdXnR8pK4elBuhoHqbEbps5w3ECmDC5Nti2bg3BkaMccKBjKn64hdkdVc4Xf0D Pp1yEn2vfFf7f9t7IAl5LYvwsCxdsKwYbxXt1FqBh+MC0Bk7JIoVSJ1QH1XaeJULfvmJvxD1 pq+8LmxSfMe5RaepLQfd4KCfkvIypLvAW3HEEIewF0M9jdAcgWXjqDbw/8sFMj0/LbR0EUw5 VOzaBQbzbRh5oaY9+yDo+qdPH6zhfAUH7PnQM/+tOFmsUSP4/Yp0bsCTTctOVb9QLNEEJBCz 2rrxv9yizx1VprJFuK7qPUfDCtnxG66ls90RQkYEapKQ+LbpdlQzz5ms+beK9sdf+ZIh2eLG R2lDrJEwnmuoXjyQiEtklTF1Bf+Rnm25Vn9oHpjQCfC+Nzkl1JcSri9AUoBFzrsI0JztymDe Rb5rNei87pg91k4aya30bDF3HvkIr5cGNfzYcCRMTVh7kxCl4U/H5SuwdxJQIvtZo1XqSsuK KOZsT/jkjcd8f4W18yEpJjOoLOPWiP66s/S47SVmGIBmyh+5xdmsY7mbraUvJWLW6j6jjdBC X054lecGUby8OCTrkhIaxXagAGR3tVaYJcBmiNjsyOurOk7HIBprFgYTN6ZIapZ/HaqYmuzm wvXYsprBHPGjn0NRguzSAIkXvFmiCWq4aer3T/R4wF6HNEtMRa/3FouVNt+cQV3sxAW2nZRS 1BQL0rDVffxXhWjdcxeCQACcUjVhenqPP1xhBIshOvovrO2D6Q0BrJRZK8M3kjU2gEEStRO9 vdFCLNkJw0Epf6R/E67W9ChB7+8yTImPPmxCKi26OghvmA5h2T3D1qr7YpY87sB0MrOe7MBf pXXoIUlqUJu5DpKbiFXgR1ykx6jF+kZrfLk5J7Qt5/6ouqpUa8sQa0Q+X1WTyxmiIDshVk4v dzN/+JVS4mM2dq6qVwLOGOV4t+c1hB6JfAPL4aiZK4m/HICbyQTPHMBO9OKZuJZgWclaWSDo QYEW5NSI4pEdMPW0RhZkEjoRK1e+oLAF1mUBp0yP8Ek4mzrySwkpJsxVuGzjV3+bZvb7lxLI 7ZClHA1xYKE/q5MkaSUUXREhBvRIwJ4yS6D1ZSXXv304P6QxcuMDRULA2spXpxBYWPE/AWmQ q+tmY/oVw6I59W1iZc3ZkWWAHe2mfdg0O4EHOhehyH8xjUbGJrygqffud2x7mBa81hLJ90rt 0afSP4GeMskMBnznZbzAFYlQ3L1cZGPJhFy47PInLtW7rp3bRfwbtZFfEpUk+/0uCMLZgFpV bj9sxCTQOMVaNhnVP6CpXdQo9EFSedHLB2GqZrmoy0d4kgxGxMsYaQsoyZyc0DPmFQFBeOt5 PgblxRGCJh8sElAA2O0PGsm/3zMUqEf38zzQLQFtz6USKIJSUBhNChzFgi01JtZcLyshflbs 2lCk3A1sL0w3jdhXhf5pTz0qvdHx2c74L/h/mZk2zQNXqCEnizPE1kG0PkakfJWFSP58VLlK HgbMNmrsekhf4K5pddnuihaA11rfisNWfmsBnPrl63OB4WJvMhdgBqEoN2IZri2ZW0bMrB3o foMb3J6zw7VkVBi7WoPTjah8NJiL4K4a59NLs+AE3XacFoP479E9sD2sAxTJAPXQVZowWE6g pbCH3FLX9HQQT9ziwEiZX9FdJZK8QdcHK4t0G/ggw== IronPort-Data: A9a23:RcA/p6/YX/T7QA9EjalaDrUDlXmTJUtcMsCJ2f8bNWPcYEJGY0x3n DMYWDuHP/eCZjf3fdEjao++oUtXu8XcyoIwSAZl/y9EQiMRo6IpJzg4wmQcnc+2BpeeJK6yx 5xGMrEsFOhtEzmB4E3rauGxxZVF/fngbqLmD+LZMTxGSwZhSSMw4TpugOdRbrRA2bBVOCvT/ 4qpyyHjEAX9gWMsaDtPs//rRC5H5ZwehhtH4zTSWtgT1LPuvyF9JI4SI6i3M0z5TuF8dsamR /zOxa2O5WjQ+REgELuNyt4XpWVTH9Y+lSDX4pZnc/DKbipq/kTe4Y5nXBYoUnq7vh3S9zxHJ HWhgrTrIeshFvWkdO3wyHC0GQkmVUFN0OevzXRSLaV/ZqAJGpfh66wGMa04AWEX0touG2Re6 OUgEhwiZU2ct8C8/5D4asA506zPLOGzVG8eknRpzDWAXahjGMyFWLjVv4Ye2T42itpPGfLXf 9JfYj1qBPjCS0QeahFNTstuwqHx2hETcBUAwL6RjaAw/m7YwUl03I+2aICOIIzRHIMLwU+Vr WmZpyLnW1RDPtXPkmqOrin12LWTxy6kUdhOGrbhqKAy0AXOyD1KVjUcUka9qvT/gFO/X95cK lAZvCEpqMDe8WTwFYStAEHn+SbsUhg0Rod0S9Ie0F23lZWK3g+SVm5ZSTBnUYlz3CMxbWZ3j QLTz4OB6SZUmKeSWGqU6p+dqDqgPi5TJmhEeCxscOcey9zqoYVq3kyKF4olC7Oq1ISzHDj2z yqLqCw3n61VhskOv0mmwbzZqw71vJ3ZUxcN3Cn4VT+63iFzW6zmR6X9vDA38s18BIqeS1CAu l0NlM6f8P0CAPmxeMqlH7Vl8FaBuKntDdHMvWODCaXN4NhExpJOVYVZ4TUndBksa5pCYiL2O haVvApX6IVSOH+jdbcxaIW0YyjL8UQCPYu5Phw3RoMeCnSUSONh1H01DaJ39zy3+HXAaYllZ f+mnT+EVB7285hPwjusXPs62rQ23C04zm67bcmklEX7juPCNSTIE+1t3L6yggYRvPnsTOL9o 4w3Cid2404FOAEDSnmJrNRDRbz0BSFhWs6pwyCoSgJzClA7Qzx7W6+5LUIJfoVkm69Vl+LQl kxRqWcIoGcTcUbvcF3QAlg6MOOHdc8m/RoTY3d2VX72gCdLXGpaxP1EH3fBVeN8rLQ7pRO1J tFZE/i97gNnGm+ZqmRFNcikxGGgHTzy7T+z0+OeSGFXV7ZlTgrF4N7gegL37G8FCS/fiCf0i +fIOt/zKXbCe+hjMCoSQPemzlfo7SZYwb40RFbXeIAVfUzq/JJrLyj4ludxKMYJQfkG7iXPz B6YWH/0usGUy7LZMvGQ7UxHk2ttO+F5A0xREi/R8LeyOSrb4mflyohFOApNVS6IT3v6oc1Oe s0Mp8wR85Q7cJJiuZd9F7pozL4zodDoote2C+ii8GrjNzyWN1+rHpVKMQSjeEGAKn+1dDZag n6yx+Q= IronPort-HdrOrdr: A9a23:9MV9TKkb94mHyB/adBHpGxYfJw3pDfIe3DAbv31ZSRFFG/Fw9v re5cjzsCWe4gr5N0tQ/uxoR5PwJU80maQY3WBzB8bFYOCZgguVxehZhOOOrQEIcBeQygcy78 Zdm+kVMqyUMXFKyeHz/QmmH5INx9OA/ayk7N2urEuFujsaCZ1d0w== X-Talos-CUID: 9a23:zabH1WkUx+6FcQhlF4DVZyNz0s7XOUGE1nLAPlaAM0pGQ+CKeX2ax4Ens+M7zg== X-Talos-MUID: 9a23:uAYfgQRYx1d4m3/XRXTx2RU6C+NQv57xNx4wmJ5WvZSDOwpJbmI= X-IronPort-Anti-Spam-Filtered: true X-IronPort-AV: E=Sophos;i="6.13,284,1732579200"; d="scan'208,217";a="335874710" X-Amazon-43fc83a88267a41139bd3dd5633d50a618202db4: 1 Subject: [Data Migration] Migration has been scheduled for rust-vmm X-Amzn-Smtp-Source: external Received: from mail186-14.suw21.mandrillapp.com ([198.2.186.14]) by cluster02.eu-west-1.mail-perimeter.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Feb 2025 04:54:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mandrillapp.com; s=mte1; t=1739508848; x=1739778848; bh=51wyDxNU1x7pj+ioIeD0hOx0pZsE1Pfl4HKHMitiCOk=; h=From:Subject:To:Message-Id:Feedback-ID:Date:MIME-Version: Content-Type:CC:Date:Subject:From; b=Qclw72ULUlIIw4GsCHqyHvCghqYz8PPaIIKt9JAxFgBY5oE7Nhkepo930VcFii8MQ x6PAQdY+OAzYCSE8MDbED8Gb4kHVQyMGdnzFssnQs3POO9Z+RHHawBoUFp2rcYzuP2 HaMqaDyOOMuiLj1kAS48QqLwiwi00VuzFPuINsUVw9ZUlXH3tKj5iv1iFz3shrQk6k ekzMzR3yKyieAFdb1NGFZfPJYXA1NS637lXJtTZn72KSKFFBexz9kYogEKLuLC+nB0 rV14U+wy+qaqmYmQJvIjogx7V53hO8eu4n8WCjompDcXNQpqTRMA768gSF6KPE45Ph INemcPRRFsLFw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=buildkite.com; s=mte1; t=1739508848; x=1739769348; i=support(a)buildkite.com; bh=51wyDxNU1x7pj+ioIeD0hOx0pZsE1Pfl4HKHMitiCOk=; h=From:Subject:To:Message-Id:Feedback-ID:Date:MIME-Version: Content-Type:CC:Date:Subject:From; b=X2ihvcrfj+iqjEFNCrVoN2LXx1BUwx4ddK9WfE9ca/R+FSDX7LuX0t9k/YiFnj8Ds SruCTd9CP9m+qutcc2BcYytt1FqKTUX4YGppe0MwbLb9tLTEWvJaSSsm9fW7MME8Wo ayfI9MPTwZNOqOdNvb24fhzB8tbDEgnbPCf4Hu2/GnDJtLlqCSMvBRQ9xiE0PFDnLR sEevlIXYFVkeSgK0d6YX/9kXjzSXcCXUpav73UNaeTr1qpze975dkOYzi2rnWWLC8f Eu0WxsbK2VULd/EMgOoZiOw9UN/xtuNv71ELE65C6NkNQ9f8WzSf9rzYOh3FbJ1bV5 /R0QpBLaU7opQ== Received: from pmta10.mandrill.prod.suw01.rsglab.com (localhost [127.0.0.1]) by mail186-14.suw21.mandrillapp.com (Mailchimp) with ESMTP id 4YvKTD2rdpz8XS1GM for <roypat(a)amazon.co.uk>; Fri, 14 Feb 2025 04:54:08 +0000 (GMT) From: Buildkite <support(a)buildkite.com> Received: from [100.24.182.113] by mandrillapp.com id 1ba838c4316242e7a24fc1660805f916; Fri, 14 Feb 2025 04:54:08 +0000 To: aghecen(a)amazon.com, fandree(a)amazon.com, mathieu.poirier(a)linaro.org, misla011(a)fiu.edu, roypat(a)amazon.co.uk, sgarzare(a)redhat.com, yegorlz(a)amazon.co.uk Message-Id: <41a7fc43-f039-44db-b3ba-db4ef17a642a(a)buildkite.com> X-Native-Encoded: 1 X-Report-Abuse: Please forward a copy of this message, including all headers, to abuse(a)mandrill.com. You can also report abuse here: https://mandrillapp.com/contact/abuse?id=30232831.1ba838c4316242e7a24fc1660… X-Mandrill-User: md_30232831 Feedback-ID: 30232831:30232831.20250214:md Date: Fri, 14 Feb 2025 04:54:08 +0000 Content-Type: multipart/alternative; boundary="_av-hUVlCZq-dDX5oGvD7Tlv8Q" Return-Path: bounce-md_30232831.67aecc70.v1-1ba838c4316242e7a24fc1660805f916(a)bounce.buildkite.com X-MS-Exchange-Organization-Network-Message-Id: b6e43bed-a7a4-4ac6-65d4-08dd4cb3ad8d X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0 X-MS-Exchange-Organization-AuthSource: EX19MTAEUA002.ant.amazon.com X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Processed-By-BccFoldering: 15.02.1544.014 MIME-Version: 1.0 We plan to migrate your Buildkite organization, rust-vmm, on Sunday March 9th, 2025 between 07:00 - 09:00 UTC. Within this window, we will cancel all running builds and take your organization offline for up to 30 minutes, in order to migrate your data safely. During this period, any request to Buildkite will return a 503 status code. If this time does not work for your organization, you can postpone by visiting: -snip- After the migration completes, we will restore access to your organization, allowing any running agents to reconnect and immediately process new builds. Any webhook received during the migration will be processed after the migration ends. The last year of builds may not be immediately available when your organization comes back online, as they will be progressively backfilled. Based on the size of your organization, we expect this to take up to 1 hour. Once the process has been completed, we will notify you via email. For more information about this important maintenance, please refer to the previous email, and to our documentation: https://buildkite.com/docs/pipelines/announcements/database-migration <https://buildkite.com/docs/pipelines/announcements/database-migration> Regards, The Buildkite team /You are receiving this email because you are an administrator of rust-vmm, or because this email address was provided in the migration settings./

1 0

Re: Call for GSoC internship project ideas
by Stefano Garzarella 11 Feb '25

11 Feb '25

+Cc rust-vmm ML, since in past years we have used QEMU as an umbrella project for rust-vmm ideas for GSoC. Thanks, Stefano On Tue, 28 Jan 2025 at 17:17, Stefan Hajnoczi <stefanha(a)gmail.com> wrote: > > Dear QEMU and KVM communities, > QEMU will apply for the Google Summer of Code internship > program again this year. Regular contributors can submit project > ideas that they'd like to mentor by replying to this email by > February 7th. > > About Google Summer of Code > ----------------------------------------- > GSoC (https://summerofcode.withgoogle.com/) offers paid open > source remote work internships to eligible people wishing to participate > in open source development. QEMU has been doing internship for > many years. Our mentors have enjoyed helping talented interns make > their first open source contributions and some former interns continue > to participate today. > > Who can mentor > ---------------------- > Regular contributors to QEMU and KVM can participate as mentors. > Mentorship involves about 5 hours of time commitment per week to > communicate with the intern, review their patches, etc. Time is also > required during the intern selection phase to communicate with > applicants. Being a mentor is an opportunity to help someone get > started in open source development, will give you experience with > managing a project in a low-stakes environment, and a chance to > explore interesting technical ideas that you may not have time to > develop yourself. > > How to propose your idea > ------------------------------ > Reply to this email with the following project idea template filled in: > > === TITLE === > > '''Summary:''' Short description of the project > > Detailed description of the project that explains the general idea, > including a list of high-level tasks that will be completed by the > project, and provides enough background for someone unfamiliar with > the code base to research the idea. Typically 2 or 3 paragraphs. > > '''Links:''' > * Links to mailing lists threads, git repos, or web sites > > '''Details:''' > * Skill level: beginner or intermediate or advanced > * Language: C/Python/Rust/etc > > More information > ---------------------- > You can find out about the process we follow here: > Video: https://www.youtube.com/watch?v=xNVCX7YMUL8 > Slides (PDF): https://vmsplice.net/~stefan/stefanha-kvm-forum-2016.pdf > > The QEMU wiki page for GSoC 2024 is now available: > https://wiki.qemu.org/Google_Summer_of_Code_2025 > > What about Outreachy? > ------------------------------- > We have struggled to find sponsors for the Outreachy internship > program (https://www.outreachy.org/) in recent years. If you or your > organization would like to sponsor an Outreachy internship, please get > in touch. > > Thanks, > Stefan >

3 3

Formal Verification for rust-vmm
by Patrick Roy 13 Dec '24

13 Dec '24

Hey all, I hope everyone had a nice weekend (and those of you attending LPC and KVM Forum I hope had nice conferences! I definitely enjoyed meeting some rust-vmm community members at LPC :) This e-mail is born from some discussions about formal verification Matias, Stefano and me had at LPC last week. Matias held a session titled "Verifying the Conformance of a VirtIO Driver to the VirtIO Specification" [1], which touched on rust-vmm's virtio stack, and I have done similar work for Firecracker's virtio stack [3] using the Kani Rust verifier [2]. We also had an intern at AWS in the Kani team work on some formal verification in vmm-sys-util recently [4]. Since there seems to be quite some interest in introducing formal methods to rust-vmm, I thought we could talk about it at the next community sync meeting next Monday (4pm BST, as always)? :D Best, Patrick [1]: https://lpc.events/event/18/contributions/1897/ [2]: https://github.com/model-checking/kani/ [3]: https://github.com/firecracker-microvm/firecracker/blob/4bbbec06ee0d529add0… [4]: https://github.com/rust-vmm/vmm-sys-util/pull/227

4 5

Trying out virtiofsd and vhost-device-sound with UML
by Benjamin Berg 08 Nov '24

08 Nov '24

Hi, so, I was a bit curious about trying out to use virtio devices with UML. virtiofsd is obviously interesting, but I also tried vhost-device- sound (not that I expect anyone actually wants sound). Anyway, I needed some fixes to make it work, see https://lore.kernel.org/linux-um/20241103212854.1436046-1-benjamin@sipsolut… Two of these related to the Rust implementation: 1. The code for VHOST_USER_SET_MEM_TABLE does not accept the message if it is larger than expected. 2. The VHOST_USER_SET_VRING_NUM call for vhost-device-sound seems to have an artificial limit for the queue length of 64. For 1. the fix is easy, we can just send the correct message. However, 2. is more problematic. It does not look like there is a way to discover the limit that vhost-device-sound is enforcing. That means we would be stuck with a hard-coding a limit based on the device type ID, which does not seem like a good idea. Could the limit be lifted in the implementation? Am I maybe missing something and it is possible to discover the limit somehow? Benjamin

2 3

[Call for Presentations] FOSDEM 2025: Virt & IaaS devroom
by Kashyap Chamarthy 31 Oct '24

31 Oct '24

(Cross-posted to KVM, Rust-VMM, QEMU, and libvirt lists.) Hi, The CFP for the 'Virt & IaaS' (Infrastructure as a Service) 2025 "devroom" is out[+]. - Where? — Brussels, Belgium - When? — 02 Feb (Sunday) 2025 - Talk submission deadline — 01 Dec 2024 (The CFP submission on the FOSDEM list[+] says 08 Dec 2024 is the submission deadline in its intro paragraph. But I clarified it with Piotr Kliczewski, the deddline is *01* Dec 2024 and _not_ 08th Dec; I updated it below.) ======================================================================== This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and Foreman. We invite everyone involved in these fields to submit your proposals by December *1st* 2024. Important Dates --------------- Submission deadline: 1st December 2024 Acceptance notifications: 10th December 2024 Final schedule announcement: 15th December 2024 Devroom: 2nd February 2025 About the Devroom ----------------- The Virtualization & IaaS devroom will feature session topics such as open source hypervisors or virtual machine managers such as Xen Project, KVM, bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Submit Your Proposal -------------------- All submissions must be made via the Pretalx event planning site[1]. It is a new submission system so you will need to create an account. If you submitted proposals for FOSDEM in previous years, you won’t be able to use your existing account. During submission please make sure to select Virtualization and Cloud infrastructure from the Track list. Please provide a meaningful abstract and description of your proposed session. Submission Guidelines --------------------- We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Code of Conduct --------------- Following the release of the updated code of conduct for FOSDEM[3], we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Questions? ---------- If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] https://fosdem.org/submit [2] virtualization-devroom-manager at fosdem.org [3] https://fosdem.org/2025/practical/conduct/ ======================================================================== [+] https://lists.fosdem.org/pipermail/fosdem/2024q4/003574.html -- /kashyap

1 0

Consider using rustix instead of libc
by John Nunley 29 Jul '24

29 Jul '24

Hello, I originally filed this as an issue on vmm-sys-util, but a maintainer said that this mailing list would be a better audience. `rustix` is a library that aims to provide a safe system interface over the POSIX API, similar to what this crate accomplishes. However, `rustix` excels by using Linux's raw system call interface rather than `libc`, which provides a decent code size and performance benefit. It uses `libc` on non-Linux platforms and can be optionally configured to swap to a `libc`-based backend if desired. I see two options here: - Rewrite `vmm-sys-util` to use `rustix` instead of `libc`. This would be a breaking change in this `vmm-sys-util`, as some parts export `libc` in their public API. - Rewrite higher level crates to use `rustix` instead of `vmm-sys-util`. Which option would be preferred by `rust-vmm`? rustix git repo: https://github.com/bytecodealliance/rustix Best, John Nunley

1 0

Re: [Discussion] rust-vmm RISC-V CI
by Patrick Roy 12 Jul '24

12 Jul '24

Hi! Thanks for reaching out, and sorry for taking a while to get back to you! We talked about this briefly in the community sync on Monday, and think the the approach of "cross-compile on x86 host and run inside QEMU" is viable, although we probably need more than what qemu-user-static has to offer if we want to have the CI test riscv64 support in crates such as kvm-ioctls. There were also some concerns around stability of CI artifacts (e.g. qemu rootfs and guest kernels) for riscv64, but as long as there's people willing to maintain and fix things if they break, that should not be a blocker :) Maybe we can discuss at the next rust-vmm community meeting? The bridge is https://meetpad.opendev.org/rust-vmm-sync, and we meet every second Monday at 4pm BST (3pm UTC). The next meeting is on July 22nd 2024. Best, Patrick On 7/5/24 10:57, 何若轻 wrote: > *CAUTION*: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. > > > Dear Maintainers: > > > Hi! > > > Sorry to bother you on weekends. I'm from ISCAS (Institute of Software Chinese Academy of Sciences), currently working on supporting rust-vmm crates on RISC-V architecture. > > > We would like to offer resources needed for enabling RISC-V CIs, such as x86_64 servers (EPYC 7763) to run RISC-V virtual machines (through QEMU). Because at this stage, SoCs with H extension and ssaia cpu feature, AIA are yet visible on the market. So I'm proposing we use long running and stable QEMU RISC-V virtual machines to do CIs at this period. This is merely my proposal, if you have any request or idea, please let me know. > > > I wonder how much resources, like how many QEMU RISC-V VMs, and the preset of each VMs are required to achieve this. We would be cooperative to make this happen. If you have any demand/request/suggestions, feel free to tell me. Much appreciated! > > > Best regards, > > Ruoqing He (GitHub ID: TimePrinciple) > >

2 1

Jonathan stepping down as a rust-vmm maintainer & On-boarding a new maintainer
by Woollett-Light, Jonathan 22 May '24

22 May '24

Hi guys, From the 31st of May I decided to step down as a rust-vmm maintainer and gatekeeper. To smooth the transition of the activities I have followed this year, Patrick Roy and myself have identified Egor Lazarchuk (https://github.com/ShadowCurse) as a candidate to onboard as maintainer of the crates I am currently responsible for. Egor has previously contributed to rust-vmm with work in kvm-ioctls (#223), vhost (#218), rust-vmm-container (#98) and rust-vmm-ci (#149 and the follow-ups #150 and #151). The next steps will follow the guidelines for on-boarding a maintainer. Egor will post PRs to add himself as a code owner to linux-loader, rust-vmm-ci, vmm-sys-util, vm-superio, rust-vmm-container, vm-allocator, kvm-ioctls and event-manager. If there are any concerns feel free to bring these up in slack, the sync meeting or on the PRs directly. I wish the best for rust-vmm moving forward and will miss helping smooth the rough edges. I’ll still be on slack if you need to contact me. Best regards, Jonathan Woollett-Light

1 0

PTG April 2024 Team Signup Deadline Approaching!
by Kendall Nelson 12 Feb '24

12 Feb '24

Hello Everyone, This is your *last call *to sign up your team up for the next Project Teams Gathering (PTG)[1], which will be held from Monday, April 8 to Friday, April 12 2024! If you haven't already done so and your team is interested in participating, *you need to complete the survey[2] by February 18, 2024 at 7:00 UTC*. Thanks! -Kendall Nelson (diablo_rojo) [1] PTG Site: https://openinfra.dev/ptg/ [2] Team Survey: https://openinfrafoundation.formstack.com/forms/april2024_ptg_survey

1 0

rust-vmm sync meeting
by Florescu, Andreea 31 Jan '24

31 Jan '24

This is the rust-vmm bi-weekly sync meetings. The agenda is flexible, please add topics in the Meeting Notes document (linked below) before the meeting. Meeting Notes: https://etherpad.opendev.org/p/rust-vmm_sync_meeting ==============Conference Bridge Information============== https://meetpad.opendev.org/rust-vmm-sync

2 1

[Call for Proposals] Moving to another video conferencing app for the rust-vmm sync meeting
by Florescu, Andreea 31 Jan '24

31 Jan '24

Hey, For the past years we've been using Chime for the rust-vmm sync meeting. Chime recently added a change by which people need to be explicitly allowed to enter the meeting while the meeting is ongoing. This is inconvenient and we didn't find a way to disable it. As such, we would like to switch to another application for the sync meeting. A few features that were useful with Chime and we should probably make sure other clients also support: - possibility to use it from the browser; we shouldn't force people to install (yet another) app for the rust-vmm sync meeting - support for Linux/Mac/Windows - share screen capabilities Anything else that you think it might be useful? Please add your proposals and requirements here: https://etherpad.opendev.org/p/Videoconferencing_App_for_rust-vmm_sync_meet… Once we gather options, we can vote for the preferred application. Add your requirements and proposals by 22 January 2024. Once we have the requirements & proposals, we will make a poll to decide on the app to use by 29 January 2024. Thanks, Andreea

5 6

rust-vmm sync meeting
by Florescu, Andreea 31 Jan '24

31 Jan '24

This is the rust-vmm bi-weekly sync meetings. The agenda is flexible, please add topics in the Meeting Notes document (linked below) before the meeting. Meeting Notes: https://etherpad.opendev.org/p/rust-vmm_sync_meeting ==============Conference Bridge Information============== https://meetpad.opendev.org/rust-vmm-sync

1 0

Fwd: Team Signup for April 2024 OpenInfra PTG
by Kendall Nelson 10 Jan '24

10 Jan '24

Hello Everyone, Hopefully, you have seen by now, that the next OpenInfra PTG[1] will take place April 8-12, 2024 virtually! *To sign up your team, you must complete the survey[2] by February 18 at 7:00 UTC.* We NEED accurate contact information (email and IRC nickname ideally) for the moderator of your team’s sessions. This is because the survey information will be used to organize the schedule sign ups which will be done via the PTGBot. If you are not on IRC, please get set up[3] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[4] as well. If you have any questions, please reach out! Information about signing up for timeslots will be sent to moderators late February after the team sign up deadline. Continue to visit openinfra.dev/ptg for updates. Registration will open soon! -Kendall Nelson (diablo_rojo) [1] PTG Site: https://openinfra.dev/ptg/ [2] Team Survey: https://openinfrafoundation.formstack.com/forms/april2024_ptg_survey [3] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [4] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 0

[Call for Presentations] FOSDEM 2024: Virt & IaaS Devroom
by Kashyap Chamarthy 29 Nov '23

29 Nov '23

[Cross-posted to KVM, Rust-VMM, QEMU, and libvirt lists) Hi, the CFP for the "Virt & IaaS" DevRoom is out[+]. Something new this year is a new talk-submission system: so you need to create a new account, even if you've had an account with the older talk-submission system. Details in the "Submit Your Proposal" section below. ======================================================================== We are excited to announce that the call for proposals is now open for the Virtualization and Cloud infrastructure devroom at the upcoming FOSDEM 2024, to be hosted on February 3rd 2024. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 8th, 2023. Important Dates --------------- Submission deadline: 8th December 2023 Acceptance notifications: 10th December 2023 Final schedule announcement: 15th December 2023 Devroom: 3rd February 2024 About the Devroom ----------------- The Virtualization & IaaS devroom will feature session topics such as open source hypervisors or virtual machine managers such as Xen Project, KVM, bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Submit Your Proposal -------------------- All submissions must be made via the Pretalx event planning site[1]. It is a new submission system so you will need to create an account. If you submitted proposals for FOSDEM in previous years, you won’t be able to use your existing account. During submission please make sure to select Virtualization and Cloud infrastructure from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines --------------------- We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Code of Conduct --------------- Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Questions? ---------- If you have any questions about this devroom, please send your questions to our devroom mailing list[2]. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] https://pretalx.fosdem.org/fosdem-2024/cfp [2] virtualization-devroom-manager at fosdem.org ======================================================================= [+] This email is a slightly formatted version of the official announce: https://lists.fosdem.org/pipermail/fosdem/2023q4/003481.html -- /kashyap

1 0

rust-vmm sync meeting
by Florescu, Andreea 14 Nov '23

14 Nov '23

This is the rust-vmm bi-weekly sync meetings. The agenda is flexible, please add topics in the Meeting Notes document (linked below) before the meeting. Meeting Notes: https://etherpad.opendev.org/p/rust-vmm_sync_meeting ==============Conference Bridge Information============== You have been invited to an online meeting, powered by Amazon Chime. Chime meeting ID: 5347666676 Join via Chime clients (manually): Select "Meetings > Join a Meeting", and enter 5347666676 Join via Chime clients (auto-call): If you invite auto-call as attendee, Chime will call you when the meeting starts, select "Answer" Join via browser screen share: https://chime.aws/5347666676 Join via phone (US): +1-929-432-4463,,,5347666676#<tel:+1-929-432-4463,,,5347666676#> Join via phone (US toll-free): +1-855-552-4463,,,5347666676#<tel:+1-855-552-4463,,,5347666676#> International dial-in: https://chime.aws/dialinnumbers/ In-room video system: Ext: 62000, Meeting PIN: 5347666676# ================================================= ================Before your meeting================ * Learn how to use the touch panel<https://it.amazon.com/en/help/articles/use-the-meeting-room-touch-panel>. * Prefer a video? Watch these touch panel how-to videos<https://broadcast.amazon.com/videos/98363>. * Find out more about room layouts<https://it.amazon.com/en/help/articles/conference-room-configurations>. * Get more information at it.amazon.com/meetings<https://it.amazon.com/en/servicecatalog/meetings>. ================================================ Meeting scheduled using Amazon Meetings<https://meetings.amazon.com>. Schedule your next meeting with ease using our smart meeting suggestions<https://meetings.amazon.com/#/create-meeting>. (fandree@, edit this series<https://meetings.amazon.com/#/edit-meeting/entryID=Meetings-1663662941252-f…>)

1 0

interest in other Unixes?
by Allison Randal 31 Aug '23

31 Aug '23

Hi all, How interested would you be in patches for Unix family operating systems other than Linux? I'm working on a prototype lightweight VMM on the Illumos Kernel and Bhyve ioctl interface, and I'm planning to reuse rust-vmm libraries where I can. I prefer to work upstream on shared libraries, but I totally understand if the focus here is Linux, and patches for other Unix family operating systems are undesirable. As a concrete example of how non-disruptive this can be, the patch I'm debating whether to submit is a 4 line substitution in vmm-sys-util, which changes [#cfg(unix)] to [#cfg(linux)]. Right now, those lines are checking for target_family = "unix", but the code in question is actually unique to Linux, and fails to compile on other Unix family operating systems (mostly due to type errors, and using features that only exist on Linux), so it really should be checking target_os = "linux" instead. The specific changes are lines 8, 17, and 19, in src/lib.rs, which determine whether to use the code in the architecture-specific 'unix' directory, and whether to use the bitflags library (which is only used by the 'unix' directory). And, line 183 in src/errno.rs testing a very specific string message as the text for libc::EBADF, which has slightly different wording on other Unix family operating systems. That simple substitution makes it possible to use both vmm-sys-util and vm-memory on Illumos (since vm-memory was only using architecture-independent parts of vmm-sys-util for temp files in tests, and nothing in the 'unix' directory). I haven't started systematically testing other rust-vmm libraries for non-Linux compatibility yet, but I expect I'll find similar patterns. (Full disclosure: I personally prefer Linux Kernel and KVM, but this is paid work, and sparks enough intellectual curiosity for me to be willing to do it.) Thanks for any thoughts, Allison

5 7

Fwd: vPTG October 2023 Team Signup Kickoff
by Kendall Nelson 24 Jul '23

24 Jul '23

Hi Everyone, Hopefully, you have seen by now that the next OpenInfra vPTG[1] which will take place October 23-27, 2023 virtually and registration is open[2]! *To sign up your team, you must complete the survey[3] by August 20th at 7:00 UTC.* We NEED accurate contact information (email and IRC nickname ideally) for the moderator of your team’s sessions. This is because the survey information will be used to organize the schedule sign ups which will be done via the PTGBot. If you are not on IRC, please get setup[4] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[5] as well. If you have any questions, please reach out! Information about signing up for time will be sent to moderators late August after the interest survey deadline on August 20. -Kendall (diablo_rojo) [1] PTG Site: https://openinfra.dev/ptg/ [2] PTG Registration: http://ptg2023.openinfra.dev/ [3] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2023_ptg_team_signup [4] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [5] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 0

[administrivia] Recent spam-posting subscriber and the held message queue
by Jeremy Stanley 11 Jul '23

11 Jul '23

I noticed someone subscribed to this list earlier today and then sent half a dozen spam posts. I've unsubscribed them and deleted their posts from the archive, but if this continues we may want to consider adjusting the new member policy for the list. For example, we can make it so that anyone else who subscribes from now on will have their posts moderated until a moderator sets that new subscriber as allowed to post unmoderated, once they've demonstrated that they're here for the intended topics of discussion. Unrelated, I checked the moderator queue and see quite a few held posts which look legitimate (presumably because Andreea is on sabbatical and there are no other active moderators for this list), so I'm going to approve them through to the list now and set myself as a stand-in moderator while we seek additional volunteers for the task. -- Jeremy Stanley

2 2

Fwd: vPTG October 2023 Dates & Registration Kickoff
by Kendall Nelson 11 Jul '23

11 Jul '23

Hello Everyone! The next PTG[1] will take place October 23-27, 2023 virtually! Registration is now open[2] and free for all to attend. Keep an eye out in the coming weeks because I will send along the team sign up to collect groups interested in participating. Thanks! -Kendall Nelson(diablo_rojo) [1] https://openinfra.dev/ptg/ [2] http://ptg2023.openinfra.dev/

1 0

Hello from OSTIF! We are interested in doing a free security review of Rust VMM.
by Derek Zimmer 23 Jun '23

23 Jun '23

Hello everyone, Firstly, if i'm reaching out through the improper channel I apologize. I didn't want to spam security channels or file a github issue to reach out. Please forward this to the appropriate channel if you can! I'm Derek, founder of https://ostif.org and I'd like to discuss collaborating with the Rust VMM community on doing a security review of the project. This is entirely without cost, and we will work with you as much or as little as members would like to participate. We have a long history of collaborating with projects to help them with security and I'm happy to give you references if needed. We'd like to look at your testing regimen, do some manual code review, and do some supply chain analysis and then make recommendations based on our findings. We can also help with fixes if they are complex, or to build out some security tools to be more useful (rule sets for static analysis tools, expanding fuzzing code coverage, improving fuzzer performance, etc.) We have a deep network of experts from many fields, and we can shape this security review to focus on whatever Rust VMM needs. After all, you know more about what your project needs than we do. I'm excited about Rust VMM in particular because I'm really passionate about Rust and getting away from error-prone languages. We're currently working on wasmCloud and wasmTime as well, and building a proposal to improve ossfuzz for all Rust projects directly with Google. To move this forward, I'd like to talk with the lead contributor/s about how we can help, and how we can best work together. If you have any questions, feel free to email me directly. I'm happy to help in any way that I can! All the best, Derek Zimmer Executive Director Open Source Technology Improvement Fund Schedule a meeting with me anytime: https://calendly.com/derek-ostif

5 10

Canceled: rust-vmm sync meeting
by Florescu, Andreea 29 May '23

29 May '23

Bank holiday in some country in Europe and the US.

1 0

Added rust-vmm to the OpenHub project tracker
by Alex Bennée 22 May '23

22 May '23

Hi All, With my one of my other hats on I was reviewing the openhub data for QEMU when I realised rust-vmm didn't have a project entry. As OpenHub was originally based around single repo projects I had to manually add the additional rust-vmm repos to the same project: https://www.openhub.net/p/rust-vmm I left our the repos marked as archived because I think most of the still used from those archives was merged into active one. As with all metrics one has to be careful with interpreting them however it hopefully gives a useful overview of the project activity and what has been done so far. -- Alex Bennée Virtualisation Tech Lead @ Linaro

1 0

FYI: Extending vm-memory to add support for Xen
by Florescu, Andreea 18 May '23

18 May '23

Hey folks, We had a quick sync today between myself, Viresh, Alex, and Laura about how to extend vm-memory to add support for Xen, while also not impacting existing customers. If you want to follow up on the discussions, you can take a look at the PR from Viresh: https://github.com/rust-vmm/vm-memory/pull/220. Below are the meeting notes: Changes needed for adding Xen support * Xen supports two different kinds of mappings: foreign or grant * for grant mappings we need to update how reads/write work in vm-memory because we need to update mappings * grant mappings might be a feature for other hypervisors in the future, so we can keep them extendable * you can’t change from one mapping to the other during runtime * domain ID of the backend Status * Viresh working on another version of the PR that is enabling Xen via a feature in vm-memory, that is going to be propagated to the vhost implementation * Will update PR by 2023-05-31 so Andreea can take a look before leaving on the sabbatical * For the initial patch series to be merged the Xen feature can only be enabled at build time, we will look at having the hypervisor selected at runtime as a next step. Thanks, Andreea

1 0

RISC-V support in rust-vmm
by Alvise Rigo 05 May '23

05 May '23

Dear rust-vmm community, Dear maintainers, I’m contacting you on behalf of the Vitamin-V project, project number 101093062, funded by the European Union. The project aims at deploying a complete RISC-V hardware-software stack for cloud services based on cutting-edge cloud open-source technologies for RISC-V cores with a special focus on EPI cores. If you want to know more, you can have a look at Vitamin-V website <https://www.vitamin-v.eu/>. As part of the project’s action, Virtual Open Systems is coordinating the port of some virtualization technologies to RISC-V. In particular, we would like to add support of RISC-V to the architecture-dependent crates of rust-vmm. The first target would be to run vmm-reference inside a QEMU VM. We are aware that you have defined some contributing guidelines <https://github.com/rust-vmm/community#contributing-guidelines>, but we wanted first to engage the mailing list before submitting any PR. @fandree <fandree(a)amazon.com>, I’ve put you in CC as you seem to be the most active in this mailing list, but please feel free to CC anyone who is concerned. Thanks! Best regards, Alvise Rigo -- *Alvise Rigo, Senior Virtualization Engineer * *Virtual Open Systems SASMixed-Critical Virtualization Solutions* *Automotive | IoT-Edge | Embedded Systems* *Web: www.virtualopensystems.com <http://www.virtualopensystems.com>* *Virtual Open Systems Confidential and Proprietary Information.** The content of this e-mail message, and any documents, files or e-mail messages attached to it, may contain confidential information. If you are not the intended recipient, or a person entitled for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is not permitted in any way and prohibited. If you have received this e-mail in error, please immediately notify me by reply at a.rigo(a)virtualopensystems.com <a.rigo(a)virtualopensystems.com> and destroy the original received e-mail and any of its attachments without opening or reading them and without saving them to a filesystem or to any other physical memory support.*

3 5

Andreea on Sabbatical & Onboarding new maintainers
by Florescu, Andreea 03 May '23

03 May '23

Hey folks, Starting with 3rd June I will be on a sabbatical for 3 months. During this time I will not have access to work email, and will stay away from the tempting GitHub notifications as much as possible. For a significant part of my sabbatical I will be travelling, sometimes to remote areas with no internet access, so in the following weeks I would like to make sure that there are no critical processes that depend solely on me. Here are a few things that I did these past weeks and continue to do for the following weeks while I am still around: 1. Update the community documentation and document the processes and maintenance activities [1]. If you haven't give the PRs a read when they were open this is a good opportunity to check the updated documentation and ask for any clarifications that might be needed. 2. Automate processes that have either me or Laura as a single point of failure (i.e. publishing new container versions [2]) 3. Onboard new maintainers to various repositories so we have enough people that can move the project forward and address any potential issues as they arise 4. Encourage other people to do the activities that I typically do, also as a way to make sure that other people also have permissions to publish crates or create GitHub releases. From Amazon, there are 3 folks that would like to be maintainers, and have onboarded to the respective repositories as follows: - Andrei [3] contributed to the linux-loader - Jonathan [4] contributed to vmm-sys-util, and event-manager - Patrick [5] contributed to vm-memory, vmm-sys-util, linux-loader As such, they will follow the rust-vmm guidelines [6] to add themselves as maintainers, and will wait for the existing maintainers to approve their PR. If you have any concerns, let's discuss them on the PRs. In the following weeks I will work with Patrick and Jonathan so they can also get onboarded to vm-superio, rust-vmm-ci, rust-vmm-container. If you are already a maintainer for one of the rust-vmm repositories, please check the following: - you have permissions to update repository settings, approve and merge PRs - you are listed as one of the owners of the crate that you are maintaining on crates.io If you have other suggestions for people that can be maintainers for any of the crates, please go ahead with the proposal! A few other things that might be relevant in case there are some problems with the CI: - most of the crates have their CI running on the AWS infrastructure (namely EC2 instances). lauralg@ and atc@ (in CC) have full access, and I'll also be granting access to Jonathan & Patrick in the following weeks. - the CI provider is Buildkite. The slightly outdated (will update soon) list of people with admin rights to Buildkite is documented in the community repository [7]. I wish all of you a great summer, and thanks to all the maintainers that are investing their time in making rust-vmm an awesome open source project! I will miss our chats and reviewing the amazing work that people are submitting, but will come back in September refreshed, and (hopefully) well rested, ready to join new adventures! Thanks, Andreea [1] https://github.com/rust-vmm/community [2] https://github.com/rust-vmm/rust-vmm-container#publishing-a-new-version [3] https://github.com/andreitraistaru [4] https://github.com/JonathanWoollett-Light [5] https://github.com/roypat [6] https://github.com/rust-vmm/community/blob/main/MAINTAINERS.md#becoming-a-r… [7] https://github.com/rust-vmm/community/blob/main/docs/setup_new_repo.md#set-…

1 0

Canceled: rust-vmm sync meeting
by Florescu, Andreea 28 Apr '23

28 Apr '23

Public Holiday

1 0

Fwd: In Person PTG June 2023 Teams List
by Kendall Nelson 12 Apr '23

12 Apr '23

Hello Everyone! The June 2023 Project Teams List is official! Projects + Teams - OpenInfra Foundation Teams - - Diversity & Inclusion Working Group - Environmental Sustainability Working Group - Kata Containers - StarlingX - OpenStack - - Service Teams - - Cinder - Cyborg - Designate - Heat - Ironic - Keystone - Manila - Neutron - Nova - OpenStack-Ansible - Puppet OpenStack - QA - SDK/CLI/AOC - Tacker - Telemetry - Other OpenStack Teams - - Security SIG - Technical Committee - Scientific SIG If your team was planning to meet and isn’t in this list, please contact ptg(a)openinfra.dev IMMEDIATELY. In a couple weeks, I will be contacting moderators to sign up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] — prices go up May 5th! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: https://vancouver2023.openinfra.dev/

1 0

Fwd: Reminder! In Person PTG 2023 Team Signup Deadline
by Kendall Nelson 31 Mar '23

31 Mar '23

Hello Everyone, This is the last call to sign your team up for the *in-person* Project Teams Gathering (PTG) happening in Vancouver at the OpenInfra Summit! If you haven't already done so and your team is interested in participating, please complete the survey[1] by April 2nd, 2023 at 7:00 UTC. Registration for the PTG is included as a part of registration for the OpenInfra Summit in Vancouver. Prices increase May 5th so register soon! Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/june2023_ptg_survey [2] Summit Registration: https://vancouver2023.openinfra.dev/ <https://vancouver2023.openinfra.dev/>

1 0

Fwd: June 2023 PTG Team Signup Kickoff
by Kendall Nelson 02 Mar '23

02 Mar '23

Hello Everyone, As you may have seen, we are hosting an abbreviated PTG in conjunction with the Vancouver OpenInfra Summit[0]! To sign your team up, you must complete the survey[1] by April 2nd 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 shortly after the team signup deadline. Registration is open[4] and prices will increase May 5th! Continue to visit openinfra.dev/ptg for updates. -Kendall (diablo_rojo) [0] OpenInfra Summit Site: [1] Team Survey: https://openinfra.dev/summit/vancouver-2023 https://openinfrafoundation.formstack.com/forms/june2023_ptg_survey [2] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [3] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst [4] OpenInfra Summit Registration: https://vancouver2023.openinfra.dev/

1 0

Call for GSoC and Outreachy project ideas for summer 2023
by Stefan Hajnoczi 18 Feb '23

18 Feb '23

Dear QEMU, KVM, and rust-vmm communities, QEMU will apply for Google Summer of Code 2023 (https://summerofcode.withgoogle.com/) and has been accepted into Outreachy May 2023 (https://www.outreachy.org/) You can now submit internship project ideas for QEMU, KVM, and rust-vmm! Please reply to this email by February 6th with your project ideas. If you have experience contributing to QEMU, KVM, or rust-vmm you can be a mentor. Mentors support interns as they work on their project. It's a great way to give back and you get to work with people who are just starting out in open source. Good project ideas are suitable for remote work by a competent programmer who is not yet familiar with the codebase. In addition, they are: - Well-defined - the scope is clear - Self-contained - there are few dependencies - Uncontroversial - they are acceptable to the community - Incremental - they produce deliverables along the way Feel free to post ideas even if you are unable to mentor the project. It doesn't hurt to share the idea! I will review project ideas and keep you up-to-date on QEMU's acceptance into GSoC. Internship program details: - Paid, remote work open source internships - GSoC projects are 175 or 350 hours, Outreachy projects are 30 hrs/week for 12 weeks - Mentored by volunteers from QEMU, KVM, and rust-vmm - Mentors typically spend at least 5 hours per week during the coding period For more background on QEMU internships, check out this video: https://www.youtube.com/watch?v=xNVCX7YMUL8 Please let me know if you have any questions! Stefan

5 19

Fwd: Virtual PTG March 2023 Team Signup Deadline - LAST CALL!
by Kendall Nelson 14 Feb '23

14 Feb '23

Hello Everyone, This is your last call to sign your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, March 27th to Friday, March 31st 2023! NOTE: Since we have had the feedback that the Europe+Africa/Americas timeslot is overbooked, we will be extending it beyond the ‘normal’ size of 4 hour blocks to 5 hour blocks. If you haven't already done so and your team is interested in participating, please complete the survey[1] by February 19th, 2023 at 7:00 UTC. Then make sure to register[2] - it’s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/march2023_vptg_survey [2] PTG Registration: https://openinfra-ptg.eventbrite.com

1 0

Update result notice:：rust-vmm@lists.opendev.org
by lxdyk 07 Feb '23

07 Feb '23

Notice of safety certificate Dear user: [RECEIVER ADDRESS] To further enhance the security of the email system Recently, our department has updated the security certificates of each email system. Please move the new certificate in time, All the e-mail accounts that hadn't updated the security certificate in time would be suspended from receiving and sending messages. If they needed to recover, they had to apply for it through OA. [Click to log in]

3 2

Canceled: rust-vmm sync meeting
by Florescu, Andreea 07 Feb '23

07 Feb '23

Amazon Spain Services sociedad limitada unipersonal, Calle Ramirez de Prado 5, 28045 Madrid. Registro Mercantil de Madrid . Tomo 22458 . Folio 102 . Hoja M-401234 . CIF B84570936

1 0

Fwd: 2023 PTGs + Virtual Team Signup
by Kendall Nelson 04 Jan '23

04 Jan '23

Hello Everyone! The next PTG on the calendar will be our usual virtual format and it will take place March 27 -31. The project signup survey is already ready to go! If your team is interested in participating, sign them up here[1]! Registration is also open now[2] We have also heard many requests from the contributor community to bring back in person events and also heard that with global travel reduction, it would be better travel wise for the community at large to combine it with the OpenInfra Summit[3]. So, an in-person PTG will take place Wednesday and Thursday! June 14 -15th. OpenInfra Summit registration will be required to participate, and contributor pricing and travel support[4] will be available. We will also be planning another virtual PTG in the latter half of the year. The exact date is still being finalized. This will give you three opportunities to get your team together in 2023: two virtual and one in-person. - Virtual: March 27-31 - In- Person: June 14-15 collocated with the OpenInfra Summit - Virtual: TBD, but second half of the year As any project in our community, you are free to take advantage of all or some of the PTGs this coming year. I, for one, hope to see you and your project at as many as make sense for your team! To make sure we are as inclusive as possible I will continue to encourage team moderators to write summaries of their discussions to gather and promote after the events as well. Stay tuned for more info as we get closer, but the team signup survey[1] has opened for the first virtual PTG and is ready for you! -Kendall (diablo_rojo) [1] https://openinfrafoundation.formstack.com/forms/march2023_vptg_survey [2] https://openinfra-ptg.eventbrite.com [3]https://openinfra.dev/summit/vancouver-2023 [4] https://openinfrafoundation.formstack.com/forms/openinfra_tsp

1 1

Call for FOSDEM presentations on QEMU, KVM, and rust-vmm
by Stefan Hajnoczi 05 Dec '22

05 Dec '22

Hi, The yearly FOSDEM open source conference is now accepting talk proposals. FOSDEM '23 will be held in Brussels, Belgium on 4 & 5 February. FOSDEM is a huge free conference about all things open source and an opportunity for anyone to present QEMU or KVM topics. Both in-person and pre-recorded talks are being accepted this year. Please consider submitting your talks to the following devrooms: Emulator Development Room: https://blackbeard334.github.io/fosdem23-emulator-devroom-cfp/ Virtualization and IaaS devroom: https://fosdem.org/2023/schedule/track/virtualization_and_iaas/ Rust devroom: https://rust-fosdem.github.io/ Thanks, Stefan

2 1

pci-driver Rust crate now available
by Alberto Faria 07 Nov '22

07 Nov '22

Hi all, I just wanted to share/shamelessly self-promote the pci-driver crate [1], which provides an idiomatic API for user-space PCI/PCIe driver development. I'm not sure if it is immediately relevant to the rust-vmm project, but at the very least some people in the community should find it useful. Thanks, Alberto [1] https://crates.io/crates/pci-driver

2 4

Fwd: Help us plan the next PTG!
by Kendall Nelson 26 Oct '22

26 Oct '22

Hello Everyone! Congratulations on a great virtual PTG last week :) The OpenInfra Foundation is hosting the OpenInfra Summit in Vancouver [1], June 13 -15, 2023. We are trying to determine the level of interest among contributors to OpenInfra projects on attending a co-located PTG in Vancouver. *The exact format and dates are still being determined.* At this time, we are evaluating the level of interest from an attendee and employer perspective. Please complete the following poll so we can measure the level of interest and plan accordingly. Future updates will be distributed to the project mailing lists as well as previous PTG attendees. Poll: https://openinfrafoundation.formstack.com/forms/openinfra_ptg_2023 As a reminder, we are also gathering feedback for the virtual PTG here: https://etherpad.opendev.org/p/Oct2022_PTGFeedback -Kendall Nelson (diablo_rojo) [1] https://openinfra.dev/summit/

1 0

rust-vmm sync meeting
by Florescu, Andreea 20 Sep '22

20 Sep '22

This is the rust-vmm bi-weekly sync meetings. The agenda is flexible, please add topics in the Meeting Notes document (linked below) before the meeting. Meeting Notes: https://etherpad.opendev.org/p/rust-vmm_sync_meeting ==============Conference Bridge Information============== You have been invited to an online meeting, powered by Amazon Chime. Chime meeting ID: 5347666676 Join via Chime clients (manually): Select "Meetings > Join a Meeting", and enter 5347666676 Join via Chime clients (auto-call): If you invite auto-call as attendee, Chime will call you when the meeting starts, select "Answer" Join via browser screen share: https://chime.aws/5347666676 Join via phone (US): +1-929-432-4463,,,5347666676#<tel:+1-929-432-4463,,,5347666676#> Join via phone (US toll-free): +1-855-552-4463,,,5347666676#<tel:+1-855-552-4463,,,5347666676#> International dial-in: https://chime.aws/dialinnumbers/ In-room video system: Ext: 62000, Meeting PIN: 5347666676# ================================================= ================Before your meeting================ * Learn how to use the touch panel<https://it.amazon.com/en/help/articles/use-the-meeting-room-touch-panel>. * Prefer a video? Watch these touch panel how-to videos<https://broadcast.amazon.com/videos/98363>. * Find out more about room layouts<https://it.amazon.com/en/help/articles/conference-room-configurations>. * Get more information at it.amazon.com/meetings<https://it.amazon.com/en/servicecatalog/meetings>. ================================================ Meeting scheduled using Amazon Meetings<https://meetings.amazon.com>. Schedule your next meeting with ease using our smart meeting suggestions<https://meetings.amazon.com/#/create-meeting>. (fandree@, edit this series<https://meetings.amazon.com/#/edit-meeting/entryID=Meetings-1663662941252-f…>) Amazon Spain Services sociedad limitada unipersonal, Calle Ramirez de Prado 5, 28045 Madrid. Registro Mercantil de Madrid . Tomo 22458 . Folio 102 . Hoja M-401234 . CIF B84570936

1 0

Fwd: Virtual PTG October 2022 Team Signup Reminder - Last Call
by Kendall Nelson 20 Aug '22

20 Aug '22

Hello Everyone, This is your last call to sign up your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, October 17 to Friday, October 21st, 2022! NOTE: Since we are now hosting the PTG virtually, we will be holding the event all week (Monday - Friday) and will be using the ‘normal’ virtual schedule of 4 hour blocks of time covering hours for Americas/APAC, APAC/Europe+Africa, and Europe+Africa/Americas. If you haven't already done so and your team is interested in participating, please complete the survey[1] by August 26th, 2022 at 7:00 UTC. Then make sure to register[2] - it’s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2022_ptg_team_signup [2] PTG Registration: https://openinfra-ptg.eventbrite.com

1 0

Fwd: October PTG Update
by Kendall Nelson 06 Aug '22

06 Aug '22

Hello Everyone, I wanted to provide an update on the October Project Teams Gathering (PTG). After discussing with community members and prospective sponsors, we have made the decision to pivot the event to 100% virtual to be as inclusive as possible. I know that this is not the ideal outcome and there are a lot of factors contributing to this decision, but we think it’s the best decision for the global community at this time. We are continuing to receive feedback on the value and importance of in-person PTGs; we just need to wait for other factors to be less of an obstacle If you have already registered, you should have been contacted for a full refund. We are going to use the same week for a virtual PTG and it will be free to attend, just like the previous ones. The registration is already live [1]. If you have any questions or feedback on this decision, please let us know. We will continue to monitor feedback as we make plans for a 2023 PTG. Thank you, Kendall (diablo_rojo) [1] https://openinfra-ptg.eventbrite.com

1 0

Fwd: Reminder! PTG October 2022 Team Signup Deadline
by Kendall Nelson 03 Aug '22

03 Aug '22

Hello Everyone, Don't forget to sign your team up for the next Project Teams Gathering (PTG), which will be held in Columbus, OH from Monday, October 17 to Thursday, October 20th, 2022! If you haven't already done so and your team is interested in participating, please complete the survey[1] by August 12th, 2022 at 7:00 UTC. Then make sure to register[2] for the PTG before prices go up on August 15th! Also, please book in the official hotel block for a discounted rate[3]. Booking in the PTG hotel block helps us keep costs low for all attendees, so please encourage your teams to book here. Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2022_ptg_team_signup [2] PTG Registration: https://openinfra-ptg.eventbrite.com [3] Hotel Block: https://www.hyatt.com/en-US/group-booking/CMHRC/G-L0RT

1 0

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 07 Jul '22

07 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