<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Hey everyone,<br>
</p>
<p><br>
</p>
<p>Thanks for attending the meeting! Below there are some action items & meeting minutes that I took.<br>
</p>
<p>There is no tl;dr sorry about that :)<br>
</p>
<p><br>
</p>
Action Items:<br>
<ul>
<li>fandree@ to create a poll for setting up regular sync meetings</li><li>aagch@ fandree@ lauralg@ to create issues with the AWS-side of the road map</li><li>fandree@ (or delegate to someone else) to create a 2021 Road Map in rust-vmm </li><li>sameo@ to create issues for PCI</li><li>fandree@ sameo@ sync to create issues for vm-vcpu</li><li>Sartura will submit their changes to vmm-reference as a PR</li><li>Sartura & Sergio Lopez to sync on how they can reuse the C bindings (currently in libkrun)</li><li>Amy/Sergio/Sebastien open issue in rust-vmm/community to discuss about vfio-user</li></ul>
Road Map 2021:<br>
<ul>
<li>vm-device:
<ul>
<li>work on publishing it</li></ul>
</li><li>vm-virtio
<ul>
<li>Sartura interested in:
<ul>
<li>net</li><li>block<br>
</li><li>the PRs are opened in vmm-reference, we’ll discuss priorities inside the team (AWS), and come up with a timeline; Sartura is interested in picking up the PRs and merging them.</li></ul>
</li></ul>
</li><li>vm-vcpu<br>
<ul>
<li>Vm & Vcpu traits</li><li>default implementation for booting a Linux</li><li>Sartura is interested in booting Windows as well</li><li>Hypervisor abstractions</li><li>AWS to sync with Cloud Hypervisor and find the best way of contributing this</li></ul>
</li><li>vm-memory:
<ul>
<li>simplify the interface after PRs in flux settle down</li></ul>
</li><li>PCI
<ul>
<li>sameo@ will add issue an issue (if one does not exist this) to </li></ul>
</li><li>vm-superio:
<ul>
<li>there are no concerns to consume it in Cloud Hypervisor</li><li>the crate provides fixes for CVE:
<ul>
<li><a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27173">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27173</a></li><li>this needs to be improved as it is cumbersome to use; AWS will provide a better abstraction</li></ul>
</li><li>we are working on a fix for TX FIFO:
<ul>
<li>the guest is interrupted too often because of a miss in the implementation:
<ul>
<li>instead of sending the THRE interrupt for every 64 bytes that the device receives, we’re sending the interrupt for each byte</li><li>this incurs delays in the guest & makes the serial console slower than it needs to be</li></ul>
</li><li>PR from community member: <a href="https://github.com/rust-vmm/vm-superio/pull/28">
https://github.com/rust-vmm/vm-superio/pull/28</a></li></ul>
</li><li>merged fix for THRE:
<ul>
<li>when writing to out is not possible, the serial console indefinitely blocks (because we are not triggering THRE anymore)</li><li>when using named pipes bytes can be lost in the fraction of time between the time when the pipe gets full up until it gets cleared</li><li>when using ring buffers, the output is not full, so this issue is easier to address</li></ul>
</li><li>vfio-user:
<ul>
<li>can use the rust-vmm/vfio-ioctls crate: <a href="https://github.com/rust-vmm/vfio-ioctls">
https://github.com/rust-vmm/vfio-ioctls</a></li><li>adding support for this has been discussed at Red Hat:
<ul>
<li>concerns: the spec is not final, waiting for it to stabilize before proposing a crate</li><li>Red Hat is willing to add support for it in rust-vmm</li></ul>
</li></ul>
</li></ul>
</li><li>Testing & fuzzing:
<ul>
<li>add fuzzing (linux-loader, virtio devices, vm-memory)</li><li>proposed as GSoC projects:
<ul>
<li>ability to run tests locally using rust-vmm-ci</li><li>mocking utility frameworks for virtio queues</li></ul>
</li></ul>
</li><li>Misc:
<ul>
<li>Transition crates to workspaces where appropriate to simplify development (i.e. kvm, virtio)</li><li>components are still published to <a href="http://crates.io">crates.io</a> individually</li><li>Add threat model to existing components</li></ul>
</li><li>reference-vmm :
<ul>
<li>polish it and make it modular</li><li>add Arm support</li><li>as more functionality gets added to rust-vmm, we can showcase how multiple VMM configurations can be quickly built</li><li>Sartura is interested in providing improvements to the serial console:
<ul>
<li>configuring named pipes for stdin/stdout</li></ul>
</li></ul>
</li><li>Community Improvements:
<ul>
<li>Process for reporting security vulnerabilities</li><li>Improve contributing documentation</li><li>Provide a public road map for existing repositories & for the project</li><li>Setup regular sync meetings
<ul>
<li>interested in participating:
<ul>
<li>Sartura</li><li>Intel</li><li>Google</li><li>AWS<br>
</li></ul>
</li></ul>
</li></ul>
</li></ul>
<p><br>
</p>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Florescu, Andreea<br>
<b>Sent:</b> Thursday, February 11, 2021 5:07 PM<br>
<b>To:</b> rust-vmm@lists.opendev.org; Agache, Alexandru; Loghin, Laura; Iordache, Alexandra; Ochescu, Catalin; Barbu, Iulian; borna.blazevic@sartura.hr; Luka Perkov; goran.medic@sartura.hr; meet@chime.aws<br>
<b>Cc:</b> compute-capsule-feed@amazon.com; Weiss, Radu; Brendan Burns; Paolo Bonzini; juraj.vijtiuk@sartura.hr; Wise, Bob; saket.sinha89@gmail.com; Liguori, Anthony; Dima, Alin; Gheorghe, Alexandru-Cosmin; Cihodaru, Alexandru-Ciprian; Boeuf, Sebastien; Popa,
Diana-Maria; Gowdar, Meena; leo1.blazevic@gmail.com<br>
<b>Subject:</b> rust-vmm 2021 road map discussion<br>
<b>When:</b> Monday, February 15, 2021 10:00 AM-11:00 AM.<br>
<b>Where:</b> </font>
<div> </div>
</div>
<div>
<div>Meeting agenda:</div>
<div><br>
</div>
<div>1. Discuss about the rust-vmm road map for 2021</div>
<div>2. Sartura will present a demo using rust-vmm/vmm-reference.</div>
<div><br>
</div>
<div>It might be a stretch to fit the road map discussions in one hour, so we can look at the high level plans, and then schedule separate meetings to dive deep into certain topics.</div>
<div><br>
</div>
<div>See you soon!</div>
<div>Andreea</div>
<div><br>
</div>
<div>==============Conference Bridge Information==============</div>
<div>You have been invited to an online meeting, powered by Amazon Chime.</div>
<div><span style="font-size:18px"><b>Chime meeting ID: 3058950859</b></span></div>
<div><span style="font-size:18px"><b>Join via Chime clients (manually): Select 'Meetings > Join a Meeting', and enter 3058950859</b></span></div>
<div><span style="font-size:18px"><b>Join via Chime clients (auto-call): If you invite auto-call as attendee, Chime will call you when the meeting starts, select 'Answer'</b></span></div>
<div><span style="font-size:18px"><b>Join via browser screen share: <a href="https://chime.aws/3058950859">
https://chime.aws/3058950859</a></b></span></div>
<div><span style="font-size:18px"><b>Join via phone (US): <a href="tel:+1-929-432-4463,,,3058950859#">
<b>+1-929-432-4463,,,3058950859#</b></a></b></span></div>
<div><span style="font-size:18px"><b>Join via phone (US toll-free): <a href="tel:+1-855-552-4463,,,3058950859#">
<b>+1-855-552-4463,,,3058950859#</b></a></b></span></div>
<div><span style="font-size:18px"><b>International dial-in: <a href="https://chime.aws/dialinnumbers/">
https://chime.aws/dialinnumbers/</a></b></span></div>
<div><span style="font-size:18px"><b>In-room video system: Ext: 62000, Meeting PIN: 3058950859#</b></span></div>
<div>=================================================</div>
<div><br>
</div>
</div>
</div>
<p></p>
<p><br>
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.</p>
</body>
</html>