From aghecen at amazon.com Fri Nov 8 15:52:12 2019 From: aghecen at amazon.com (Iordache, Alexandra) Date: Fri, 8 Nov 2019 15:52:12 +0000 Subject: [Rust-VMM] Updated invitation: Rust-VMM Bi-Weekly Community Mtg @ Every 2 weeks from 10am to 11am on Wednesday from Wed Feb 6 to Wed Dec 18 (CST) (rust-vmm@lists.opendev.org) In-Reply-To: <465751cbbeb943fd9d967e1bf9f4a7dd@EX13D21EUC003.ant.amazon.com> References: <465751cbbeb943fd9d967e1bf9f4a7dd@EX13D21EUC003.ant.amazon.com> Message-ID: <1573228332487.17315@amazon.com> Hi, Can we move this to Thursday? Andreea and I won't be able to attend and we have at least one topic to discuss. Thanks, Alexandra ________________________________ From: claire at openstack.org Sent: Tuesday, January 29, 2019 5:49 PM To: claire at openstack.org; rust-vmm at lists.opendev.org Subject: [Rust-VMM] Updated invitation: Rust-VMM Bi-Weekly Community Mtg @ Every 2 weeks from 10am to 11am on Wednesday from Wed Feb 6 to Wed Dec 18 (CST) (rust-vmm at lists.opendev.org) When: Wednesday, November 13, 2019 6:00 PM-7:00 PM. Where: This event has been changed. more details » Rust-VMM Bi-Weekly Community Mtg When Changed: Every 2 weeks from 10am to 11am on Wednesday from Wed Feb 6 to Wed Dec 18 Central Time - Chicago Calendar rust-vmm at lists.opendev.org Who * claire at openstack.org - organizer * rust-vmm at lists.opendev.org Notes / Agenda: https://etherpad.openstack.org/p/rust_vmm_2019_biweekly_calls Join Zoom Meeting https://zoom.us/j/181523033 One tap mobile +16699006833,,181523033# US (San Jose) +16468769923,,181523033# US (New York) Dial by your location +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 181 523 033 Find your local number: https://zoom.us/u/abOe7d3zx9 Going (rust-vmm at lists.opendev.org)? All events in this series: Yes - Maybe - No more options » Invitation from Google Calendar You are receiving this courtesy email at the account rust-vmm at lists.opendev.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn More. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From claire at openstack.org Fri Nov 8 15:54:28 2019 From: claire at openstack.org (Claire Massey) Date: Fri, 8 Nov 2019 09:54:28 -0600 Subject: [Rust-VMM] Updated invitation: Rust-VMM Bi-Weekly Community Mtg @ Every 2 weeks from 10am to 11am on Wednesday from Wed Feb 6 to Wed Dec 18 (CST) (rust-vmm@lists.opendev.org) In-Reply-To: <1573228332487.17315@amazon.com> References: <1573228332487.17315@amazon.com> Message-ID: Sure! I’ll update the invite. > On Nov 8, 2019, at 9:52 AM, Iordache, Alexandra wrote: > >  > Hi, > > > > Can we move this to Thursday? Andreea and I won't be able to attend and we have at least one topic to discuss. > > > > Thanks, > > Alexandra > > > > From: claire at openstack.org > Sent: Tuesday, January 29, 2019 5:49 PM > To: claire at openstack.org; rust-vmm at lists.opendev.org > Subject: [Rust-VMM] Updated invitation: Rust-VMM Bi-Weekly Community Mtg @ Every 2 weeks from 10am to 11am on Wednesday from Wed Feb 6 to Wed Dec 18 (CST) (rust-vmm at lists.opendev.org) > When: Wednesday, November 13, 2019 6:00 PM-7:00 PM. > Where: > > This event has been changed. > more details » > Rust-VMM Bi-Weekly Community Mtg > When > Changed: Every 2 weeks from 10am to 11am on Wednesday from Wed Feb 6 to Wed Dec 18 Central Time - Chicago > Calendar > rust-vmm at lists.opendev.org > Who > • > claire at openstack.org - organizer > • > rust-vmm at lists.opendev.org > > Notes / Agenda: > https://etherpad.openstack.org/p/rust_vmm_2019_biweekly_calls > Join Zoom Meeting > > https://zoom.us/j/181523033 > > > One tap mobile > > +16699006833,,181523033# US (San Jose) > > +16468769923,,181523033# US (New York) > > > Dial by your location > > +1 669 900 6833 US (San Jose) > > +1 646 876 9923 US (New York) > > Meeting ID: 181 523 033 > > Find your local number: > https://zoom.us/u/abOe7d3zx9 > > > > > > Going (rust-vmm at lists.opendev.org)? All events in this series: Yes - Maybe - No more options » > Invitation from Google Calendar > > You are receiving this courtesy email at the account rust-vmm at lists.opendev.org because you are an attendee of this event. > > To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. > > Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn More. > > > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From claire at openstack.org Fri Nov 8 15:55:25 2019 From: claire at openstack.org (claire at openstack.org) Date: Fri, 08 Nov 2019 15:55:25 +0000 Subject: [Rust-VMM] Updated invitation: Rust-VMM Bi-Weekly Community Mtg @ Thu Nov 14, 2019 10am - 11am (CST) (rust-vmm@lists.opendev.org) Message-ID: <0000000000006822ab0596d7cfd6@google.com> This event has been changed. Title: Rust-VMM Bi-Weekly Community Mtg Notes / Agenda: https://etherpad.openstack.org/p/rust_vmm_2019_biweekly_calls Join Zoom Meeting https://zoom.us/j/181523033 One tap mobile +16699006833,,181523033# US (San Jose) +16468769923,,181523033# US (New York) Dial by your location +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 181 523 033 Find your local number: https://zoom.us/u/abOe7d3zx9 When: Thu Nov 14, 2019 10am – 11am Central Time - Chicago (changed) Calendar: rust-vmm at lists.opendev.org Who: * claire at openstack.org - organizer * rust-vmm at lists.opendev.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=Xzg5MTNhYzlqOHAxazJiOWs2c3EzNGI5azhrcGplYjlvOGNxajhiOWg2bDM0OGNhMzhkMGpnaDlrNnNfMjAxOTExMTNUMTYwMDAwWiBydXN0LXZtbUBsaXN0cy5vcGVuZGV2Lm9yZw&tok=MjAjY2xhaXJlQG9wZW5zdGFjay5vcmc3MGQ5MTA4NTllM2MwZGEyY2I3MGRmMTllZWIzYTM5NjhjYmEyN2E0&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account rust-vmm at lists.opendev.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2292 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2351 bytes Desc: not available URL: From claire at openstack.org Thu Nov 14 15:49:10 2019 From: claire at openstack.org (claire at openstack.org) Date: Thu, 14 Nov 2019 15:49:10 +0000 Subject: [Rust-VMM] Updated invitation: Rust-VMM Bi-Weekly Community Mtg @ Every 2 weeks from 10am to 11am on Wednesday from Wed Feb 6 to Wed Dec 18 (CST) (rust-vmm@lists.opendev.org) Message-ID: <000000000000188d710597506c95@google.com> This event has been changed. Title: Rust-VMM Bi-Weekly Community Mtg Notes / Agenda: https://etherpad.openstack.org/p/rust_vmm_2019_biweekly_calls Join Zoom Meeting https://zoom.us/j/181523033 One tap mobile +16699006833,,181523033# US (San Jose) +16468769923,,181523033# US (New York) Dial by your location +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 181 523 033 Find your local number: https://zoom.us/u/abOe7d3zx9 When: Every 2 weeks from 10am to 11am on Wednesday from Wed Feb 6 to Wed Dec 18 Central Time - Chicago (changed) Calendar: rust-vmm at lists.opendev.org Who: * claire at openstack.org - organizer * rust-vmm at lists.opendev.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=Xzg5MTNhYzlqOHAxazJiOWs2c3EzNGI5azhrcGplYjlvOGNxajhiOWg2bDM0OGNhMzhkMGpnaDlrNnMgcnVzdC12bW1AbGlzdHMub3BlbmRldi5vcmc&tok=MjAjY2xhaXJlQG9wZW5zdGFjay5vcmcwMzNmZjVkY2Y1ZjRkMTM3NjVjNzQzODRlZDZjNzM5YTU2YjE3MDI1&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account rust-vmm at lists.opendev.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2860 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2934 bytes Desc: not available URL: From fandree at amazon.com Tue Nov 19 10:46:55 2019 From: fandree at amazon.com (Florescu, Andreea) Date: Tue, 19 Nov 2019 10:46:55 +0000 Subject: [Rust-VMM] Device implementation in rust-vmm Message-ID: <1574160414468.89641@amazon.com> Hey everyone, A couple of weeks ago we merged a trait for DeviceIo. This is very similar to what we have in CrosVM/Firecracker under the name IoBus and serves the same purpose. You can check the commit that introduced the trait for more context [1]. With this trait merged we can now implement simple legacy devices such as the serial console. I added a PR [2] for this, but it is still very much work in progress. This PR started another conversation regarding where to place the device emulation. As far as I know we have two options: - each device in its own crate/repository - all commonly used devices in vm-device We touched on this topic during the Bucharest rust-vmm meetup as well. Each of these options come with disadvantages. The one that I was mostly concerned about is bloating the vm-device with lots of devices that are not needed by all the VMMs using rust-vmm. There are ways to work around this problem, so during the meetup we agreed on adding device emulation in vm-device for now. If we get to the point where vm-device becomes unmanageable ( too many devices making the code hard to audit), we can move the device emulation out of the crate. For people that didn't attend the meetup, what do you think about having the device emulation in vm-device? Andreea [1] https://github.com/rust-vmm/vm-device/commit/21910a148a290fcebec98bf11df4410ef35662d1 [2] https://github.com/rust-vmm/vm-device/pull/15 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.boeuf at intel.com Wed Nov 20 16:43:02 2019 From: sebastien.boeuf at intel.com (Boeuf, Sebastien) Date: Wed, 20 Nov 2019 16:43:02 +0000 Subject: [Rust-VMM] Device implementation in rust-vmm In-Reply-To: <1574160414468.89641@amazon.com> References: <1574160414468.89641@amazon.com> Message-ID: <226602bd864d9728f455a80da451c3b336aa741c.camel@intel.com> Hi Andreea, On Tue, 2019-11-19 at 10:46 +0000, Florescu, Andreea wrote: Hey everyone, A couple of weeks ago we merged a trait for DeviceIo. This is very similar to what we have in CrosVM/Firecracker under the name IoBus and serves the same purpose. You can check the commit that introduced the trait for more context [1]. With this trait merged we can now implement simple legacy devices such as the serial console. I added a PR [2] for this, but it is still very much work in progress. This PR started another conversation regarding where to place the device emulation. As far as I know we have two options: - each device in its own crate/repository - all commonly used devices in vm-device We touched on this topic during the Bucharest rust-vmm meetup as well. Each of these options come with disadvantages. The one that I was mostly concerned about is bloating the vm-device with lots of devices that are not needed by all the VMMs using rust-vmm. There are ways to work around this problem, so during the meetup we agreed on adding device emulation in vm-device for now. If we get to the point where vm-device becomes unmanageable ( too many devices making the code hard to audit), we can move the device emulation out of the crate. For people that didn't attend the meetup, what do you think about having the device emulation in vm-device? I am okay with this approach as we don't really want to end up with a million different crates eventually. And from a Rust perspective, I guess the use of Rust features will make it easy to compile in only the devices needed by each VMM implementation. Thanks, Sebastien Andreea [1] https://github.com/rust-vmm/vm-device/commit/21910a148a290fcebec98bf11df4410ef35662d1 [2] https://github.com/rust-vmm/vm-device/pull/15 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. _______________________________________________ Rust-vmm mailing list Rust-vmm at lists.opendev.org http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm -------------- next part -------------- An HTML attachment was scrubbed... URL: From chao.p.peng at intel.com Thu Nov 21 01:25:02 2019 From: chao.p.peng at intel.com (Peng, Chao P) Date: Thu, 21 Nov 2019 01:25:02 +0000 Subject: [Rust-VMM] Device implementation in rust-vmm In-Reply-To: <1574160414468.89641@amazon.com> References: <1574160414468.89641@amazon.com> Message-ID: From: Florescu, Andreea [mailto:fandree at amazon.com] Sent: Tuesday, November 19, 2019 6:47 PM To: rust-vmm ML Subject: [Rust-VMM] Device implementation in rust-vmm Hey everyone, A couple of weeks ago we merged a trait for DeviceIo. This is very similar to what we have in CrosVM/Firecracker under the name IoBus and serves the same purpose. You can check the commit that introduced the trait for more context [1]. With this trait merged we can now implement simple legacy devices such as the serial console. I added a PR [2] for this, but it is still very much work in progress. This PR started another conversation regarding where to place the device emulation. As far as I know we have two options: - each device in its own crate/repository - all commonly used devices in vm-device We touched on this topic during the Bucharest rust-vmm meetup as well. Each of these options come with disadvantages. The one that I was mostly concerned about is bloating the vm-device with lots of devices that are not needed by all the VMMs using rust-vmm. There are ways to work around this problem, so during the meetup we agreed on adding device emulation in vm-device for now. If we get to the point where vm-device becomes unmanageable ( too many devices making the code hard to audit), we can move the device emulation out of the crate. For people that didn't attend the meetup, what do you think about having the device emulation in vm-device? If you read my original proposal for vm-device(https://github.com/rust-vmm/community/issues/33) I was not going to mix those together in one crate instead I'm going to separate the common part from concrete devices. I believe it's still true for most of the devices we concerned: Virtio/PCI/vfio all have(or will have) their own crates, it's nature to put the concrete devices there or in new crates if new layers are desirable for them. Putting the concrete device in vm-device, for example, putting a concrete PCI device in vm-device, can result circular reference: vm-device(concreate PCI device) -> vm-pci -> vm-device(base device). I'm not strongly opposing you doing this for legacy and very simple device emulations like serial-console(not virtio-console), since we should have very limited number of them and no circular reference it's OK to put them in vm-device temporarily, though I tend to have a separate crate to hold those legacy ones. Besides the two options you mentioned, there is third option that putting all the concrete devices in one new crate, with rust features to select specific devices. Thanks, Chao Andreea [1] https://github.com/rust-vmm/vm-device/commit/21910a148a290fcebec98bf11df4410ef35662d1 [2] https://github.com/rust-vmm/vm-device/pull/15 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From liuj97 at gmail.com Thu Nov 21 04:43:17 2019 From: liuj97 at gmail.com (Jiang Liu) Date: Thu, 21 Nov 2019 12:43:17 +0800 Subject: [Rust-VMM] Device implementation in rust-vmm In-Reply-To: References: <1574160414468.89641@amazon.com> Message-ID: <5BC545C5-D678-4568-A012-5305DD29B281@gmail.com> > On Nov 21, 2019, at 9:25 AM, Peng, Chao P wrote: > > > > From: Florescu, Andreea [mailto:fandree at amazon.com] > Sent: Tuesday, November 19, 2019 6:47 PM > To: rust-vmm ML > Subject: [Rust-VMM] Device implementation in rust-vmm > > Hey everyone, > > A couple of weeks ago we merged a trait for DeviceIo. This is very similar to what we have in CrosVM/Firecracker under the name IoBus and serves the same purpose. You can check the commit that introduced the trait for more context [1]. > > With this trait merged we can now implement simple legacy devices such as the serial console. I added a PR [2] for this, but it is still very much work in progress. This PR started another conversation regarding where to place the device emulation. > > As far as I know we have two options: > - each device in its own crate/repository > - all commonly used devices in vm-device > > We touched on this topic during the Bucharest rust-vmm meetup as well. Each of these options come with disadvantages. The one that I was mostly concerned about is bloating the vm-device with lots of devices that are not needed by all the VMMs using rust-vmm. There are ways to work around this problem, so during the meetup we agreed on adding device emulation in vm-device for now. If we get to the point where vm-device becomes unmanageable ( too many devices making the code hard to audit), we can move the device emulation out of the crate. > > For people that didn't attend the meetup, what do you think about having the device emulation in vm-device? > > If you read my original proposal for vm-device(https://github.com/rust-vmm/community/issues/33) I was not going to mix those together in one crate instead I’m going to separate the common part from concrete devices. I believe it‘s still true for most of the devices we concerned: Virtio/PCI/vfio all have(or will have) their own crates, it’s nature to put the concrete devices there or in new crates if new layers are desirable for them. Putting the concrete device in vm-device, for example, putting a concrete PCI device in vm-device, can result circular reference: vm-device(concreate PCI device) -> vm-pci -> vm-device(base device). I’m not strongly opposing you doing this for legacy and very simple device emulations like serial-console(not virtio-console), since we should have very limited number of them and no circular reference it’s OK to put them in vm-device temporarily, though I tend to have a separate crate to hold those legacy ones. > > Besides the two options you mentioned, there is third option that putting all the concrete devices in one new crate, with rust features to select specific devices. I like this idea to create a create fo each class of devices, such as PCI, virtio, legacy etc. And the vm-device contains basic construction component to support those device classes. > Thanks, > Chao > > > Andreea > > [1] https://github.com/rust-vmm/vm-device/commit/21910a148a290fcebec98bf11df4410ef35662d1 > [2] https://github.com/rust-vmm/vm-device/pull/15 > > 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. > _______________________________________________ > Rust-vmm mailing list > Rust-vmm at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm From claire at openstack.org Wed Nov 27 15:08:19 2019 From: claire at openstack.org (claire at openstack.org) Date: Wed, 27 Nov 2019 15:08:19 +0000 Subject: [Rust-VMM] Canceled event: Rust-VMM Bi-Weekly Community Mtg @ Wed Nov 27, 2019 10am - 11am (CST) (rust-vmm@lists.opendev.org) Message-ID: <000000000000f435640598555d06@google.com> This event has been canceled. Title: Rust-VMM Bi-Weekly Community Mtg Notes / Agenda: https://etherpad.openstack.org/p/rust_vmm_2019_biweekly_calls Join Zoom Meeting https://zoom.us/j/181523033 One tap mobile +16699006833,,181523033# US (San Jose) +16468769923,,181523033# US (New York) Dial by your location +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 181 523 033 Find your local number: https://zoom.us/u/abOe7d3zx9 When: Wed Nov 27, 2019 10am – 11am Central Time - Chicago Calendar: rust-vmm at lists.opendev.org Who: * claire at openstack.org - organizer * rust-vmm at lists.opendev.org Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account rust-vmm at lists.opendev.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1644 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1693 bytes Desc: not available URL: