From fandree at amazon.com  Mon Jan  7 16:41:42 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Mon, 7 Jan 2019 16:41:42 +0000
Subject: [Rust-VMM] KVM bindings as independent crate
Message-ID: <1546879301177.29055@amazon.com>

Hey everyone,


I published the KVM bindings on crates.io [1] under the name "kvm_wrapper". The bindings are available for arm, arm64, x86 and x86_64. The kernel version can be selected by using features. For now I only added bindings for linux-4.14.0 and linux-4.20.0, but others can be added if needed. The version can be selected using features:

kvm_wrapper = { version = "0.1.0", features = ["kvm_v4_14_0"]}

and by default the latest kernel version is used.


We cannot use the crate right away in Firecracker because in the kvm_gen crate (previously named kvm_sys) we also have code that is not auto-generated so the first step for us is to move that code to somewhere else. This step is currently in review [2].

We still have to figure out some loose-ends and I created some issues for them [3], but it would be nice to get your feedback on this.


Thanks,

Andreea


[1] https://crates.io/crates/kvm_wrapper

[2] https://github.com/firecracker-microvm/firecracker/pull/816

[3] https://github.com/andreeaflorescu/kvm_wrapper/issues



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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190107/ae626526/attachment.html>

From liuj97 at gmail.com  Mon Jan  7 16:53:33 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Tue, 8 Jan 2019 00:53:33 +0800
Subject: [Rust-VMM] KVM bindings as independent crate
In-Reply-To: <1546879301177.29055@amazon.com>
References: <1546879301177.29055@amazon.com>
Message-ID: <46A3D68E-7676-477A-AC2B-A3AC78D9CDE6@gmail.com>

Hi Andreea,
	Any plan to share the bindgen script so we could generate the binding again any kernel version if needed?
Thanks!
Gerry

> On Jan 8, 2019, at 12:41 AM, Florescu, Andreea <fandree at amazon.com> wrote:
> 
> Hey everyone,
> 
> I published the KVM bindings on crates.io <http://crates.io/> [1] under the name "kvm_wrapper". The bindings are available for arm, arm64, x86 and x86_64. The kernel version can be selected by using features. For now I only added bindings for linux-4.14.0 and linux-4.20.0, but others can be added if needed. The version can be selected using features:
> kvm_wrapper = { version = "0.1.0", features = ["kvm_v4_14_0"]}
> and by default the latest kernel version is used.
> 
> We cannot use the crate right away in Firecracker because in the kvm_gen crate (previously named kvm_sys) we also have code that is not auto-generated so the first step for us is to move that code to somewhere else. This step is currently in review [2].
> We still have to figure out some loose-ends and I created some issues for them [3], but it would be nice to get your feedback on this.
> 
> Thanks,
> Andreea
> 
> [1] https://crates.io/crates/kvm_wrapper <https://crates.io/crates/kvm_wrapper>
> [2] https://github.com/firecracker-microvm/firecracker/pull/816 <https://github.com/firecracker-microvm/firecracker/pull/816>
> [3] https://github.com/andreeaflorescu/kvm_wrapper/issues <https://github.com/andreeaflorescu/kvm_wrapper/issues>
> 
> 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 <mailto:Rust-vmm at lists.opendev.org>
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm <http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190108/0c5afc00/attachment.html>

From fandree at amazon.com  Mon Jan  7 17:13:56 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Mon, 7 Jan 2019 17:13:56 +0000
Subject: [Rust-VMM] KVM bindings as independent crate
In-Reply-To: <46A3D68E-7676-477A-AC2B-A3AC78D9CDE6@gmail.com>
References: <1546879301177.29055@amazon.com>,
 <46A3D68E-7676-477A-AC2B-A3AC78D9CDE6@gmail.com>
Message-ID: <1546881234863.267@amazon.com>

Hey,


I must shamefully confess that I did the generating part manually, but in the process I documented it here [1]. I also plan to add a script for generating the bindings as I mentioned in the last section of CONTRIBUTING.md, but didn't really got the time to do that.

Can you also submit a PR please if you generate the bindings for another version/architecture just in case some other people would like to use it?


Andreea


[1] https://github.com/andreeaflorescu/kvm_wrapper/blob/master/CONTRIBUTING.md

________________________________
From: Jiang Liu <liuj97 at gmail.com>
Sent: Monday, January 7, 2019 6:53 PM
To: Florescu, Andreea
Cc: rust-vmm at lists.opendev.org
Subject: Re: [Rust-VMM] KVM bindings as independent crate

Hi Andreea,
Any plan to share the bindgen script so we could generate the binding again any kernel version if needed?
Thanks!
Gerry

On Jan 8, 2019, at 12:41 AM, Florescu, Andreea <fandree at amazon.com<mailto:fandree at amazon.com>> wrote:

Hey everyone,

I published the KVM bindings on crates.io<http://crates.io/> [1] under the name "kvm_wrapper". The bindings are available for arm, arm64, x86 and x86_64. The kernel version can be selected by using features. For now I only added bindings for linux-4.14.0 and linux-4.20.0, but others can be added if needed. The version can be selected using features:

kvm_wrapper = { version = "0.1.0", features = ["kvm_v4_14_0"]}

and by default the latest kernel version is used.

We cannot use the crate right away in Firecracker because in the kvm_gen crate (previously named kvm_sys) we also have code that is not auto-generated so the first step for us is to move that code to somewhere else. This step is currently in review [2].
We still have to figure out some loose-ends and I created some issues for them [3], but it would be nice to get your feedback on this.

Thanks,
Andreea

[1] https://crates.io/crates/kvm_wrapper
[2] https://github.com/firecracker-microvm/firecracker/pull/816
[3] https://github.com/andreeaflorescu/kvm_wrapper/issues

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<mailto:Rust-vmm at lists.opendev.org>
http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm




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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190107/868a1a3e/attachment-0001.html>

From fandree at amazon.com  Mon Jan  7 17:19:57 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Mon, 7 Jan 2019 17:19:57 +0000
Subject: [Rust-VMM] KVM bindings as independent crate
In-Reply-To: <1546881234863.267@amazon.com>
References: <1546879301177.29055@amazon.com>,
 <46A3D68E-7676-477A-AC2B-A3AC78D9CDE6@gmail.com>,
 <1546881234863.267@amazon.com>
Message-ID: <1546881595936.90095@amazon.com>

P.S. The bindgen issue by which you couldn't generate the bindings for structures containing zero sized arrays is fixed in the bindgen version 0.46.0.

There are still some issues with adding derive Debug and PartialEq to structures containing long arrays that might be related to this issue [1], but this doesn't seem like a big issue. Other than that it should be very smooth to generate bindings.


[1] https://github.com/rust-lang/rust-bindgen/issues/372

________________________________
From: Florescu, Andreea
Sent: Monday, January 7, 2019 7:13 PM
To: Jiang Liu
Cc: rust-vmm at lists.opendev.org
Subject: Re: [Rust-VMM] KVM bindings as independent crate


Hey,


I must shamefully confess that I did the generating part manually, but in the process I documented it here [1]. I also plan to add a script for generating the bindings as I mentioned in the last section of CONTRIBUTING.md, but didn't really got the time to do that.

Can you also submit a PR please if you generate the bindings for another version/architecture just in case some other people would like to use it?


Andreea


[1] https://github.com/andreeaflorescu/kvm_wrapper/blob/master/CONTRIBUTING.md

________________________________
From: Jiang Liu <liuj97 at gmail.com>
Sent: Monday, January 7, 2019 6:53 PM
To: Florescu, Andreea
Cc: rust-vmm at lists.opendev.org
Subject: Re: [Rust-VMM] KVM bindings as independent crate

Hi Andreea,
Any plan to share the bindgen script so we could generate the binding again any kernel version if needed?
Thanks!
Gerry

On Jan 8, 2019, at 12:41 AM, Florescu, Andreea <fandree at amazon.com<mailto:fandree at amazon.com>> wrote:

Hey everyone,

I published the KVM bindings on crates.io<http://crates.io/> [1] under the name "kvm_wrapper". The bindings are available for arm, arm64, x86 and x86_64. The kernel version can be selected by using features. For now I only added bindings for linux-4.14.0 and linux-4.20.0, but others can be added if needed. The version can be selected using features:

kvm_wrapper = { version = "0.1.0", features = ["kvm_v4_14_0"]}

and by default the latest kernel version is used.

We cannot use the crate right away in Firecracker because in the kvm_gen crate (previously named kvm_sys) we also have code that is not auto-generated so the first step for us is to move that code to somewhere else. This step is currently in review [2].
We still have to figure out some loose-ends and I created some issues for them [3], but it would be nice to get your feedback on this.

Thanks,
Andreea

[1] https://crates.io/crates/kvm_wrapper
[2] https://github.com/firecracker-microvm/firecracker/pull/816
[3] https://github.com/andreeaflorescu/kvm_wrapper/issues

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<mailto:Rust-vmm at lists.opendev.org>
http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm




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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190107/1f81967a/attachment.html>

From liuj97 at gmail.com  Tue Jan  8 00:23:44 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Tue, 8 Jan 2019 08:23:44 +0800
Subject: [Rust-VMM] KVM bindings as independent crate
In-Reply-To: <1546881234863.267@amazon.com>
References: <1546879301177.29055@amazon.com>
 <46A3D68E-7676-477A-AC2B-A3AC78D9CDE6@gmail.com>
 <1546881234863.267@amazon.com>
Message-ID: <D4743290-D507-44C2-A45A-84BB24FF1E5C@gmail.com>

Hi Andreea,
	The CONTRIBUTING.md is very helpful and should be enough for us. Currently we are working with linux 4.19.
Thanks!
Gerry


> On Jan 8, 2019, at 1:13 AM, Florescu, Andreea <fandree at amazon.com> wrote:
> 
> Hey,
> 
> I must shamefully confess that I did the generating part manually, but in the process I documented it here [1]. I also plan to add a script for generating the bindings as I mentioned in the last section of CONTRIBUTING.md, but didn't really got the time to do that.
> Can you also submit a PR please if you generate the bindings for another version/architecture just in case some other people would like to use it?
> 
> Andreea
> 
> [1] https://github.com/andreeaflorescu/kvm_wrapper/blob/master/CONTRIBUTING.md <https://github.com/andreeaflorescu/kvm_wrapper/blob/master/CONTRIBUTING.md>
> From: Jiang Liu <liuj97 at gmail.com>
> Sent: Monday, January 7, 2019 6:53 PM
> To: Florescu, Andreea
> Cc: rust-vmm at lists.opendev.org
> Subject: Re: [Rust-VMM] KVM bindings as independent crate
>  
> Hi Andreea,
> Any plan to share the bindgen script so we could generate the binding again any kernel version if needed?
> Thanks!
> Gerry
> 
>> On Jan 8, 2019, at 12:41 AM, Florescu, Andreea <fandree at amazon.com <mailto:fandree at amazon.com>> wrote:
>> 
>> Hey everyone,
>> 
>> I published the KVM bindings on crates.io <http://crates.io/> [1] under the name "kvm_wrapper". The bindings are available for arm, arm64, x86 and x86_64. The kernel version can be selected by using features. For now I only added bindings for linux-4.14.0 and linux-4.20.0, but others can be added if needed. The version can be selected using features:
>> kvm_wrapper = { version = "0.1.0", features = ["kvm_v4_14_0"]}
>> and by default the latest kernel version is used.
>> 
>> We cannot use the crate right away in Firecracker because in the kvm_gen crate (previously named kvm_sys) we also have code that is not auto-generated so the first step for us is to move that code to somewhere else. This step is currently in review [2].
>> We still have to figure out some loose-ends and I created some issues for them [3], but it would be nice to get your feedback on this.
>> 
>> Thanks,
>> Andreea
>> 
>> [1] https://crates.io/crates/kvm_wrapper <https://crates.io/crates/kvm_wrapper>
>> [2] https://github.com/firecracker-microvm/firecracker/pull/816 <https://github.com/firecracker-microvm/firecracker/pull/816>
>> [3] https://github.com/andreeaflorescu/kvm_wrapper/issues <https://github.com/andreeaflorescu/kvm_wrapper/issues>
>> 
>> 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 <mailto:Rust-vmm at lists.opendev.org>
>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm <http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm>
> 
> 
> 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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190108/bc87918c/attachment-0001.html>

From samuel.ortiz at intel.com  Tue Jan  8 08:28:02 2019
From: samuel.ortiz at intel.com (Samuel Ortiz)
Date: Tue, 8 Jan 2019 09:28:02 +0100
Subject: [Rust-VMM] KVM bindings as independent crate
In-Reply-To: <1546879301177.29055@amazon.com>
References: <1546879301177.29055@amazon.com>
Message-ID: <20190108082802.GK10834@caravaggio>

Hi Andreea,

We created a rust-vmm organization on github [1], maybe we should have
the KVM bindings as our first repo there? I just sent you an invite to
become member of the org.

Cheers,
Samuel.

[1] https://github.com/rust-vmm

On Mon, Jan 07, 2019 at 04:41:42PM +0000, Florescu, Andreea wrote:
> Hey everyone,
> 
> 
> I published the KVM bindings on crates.io [1] under the name "kvm_wrapper". The bindings are available for arm, arm64, x86 and x86_64. The kernel version can be selected by using features. For now I only added bindings for linux-4.14.0 and linux-4.20.0, but others can be added if needed. The version can be selected using features:
> 
> kvm_wrapper = { version = "0.1.0", features = ["kvm_v4_14_0"]}
> 
> and by default the latest kernel version is used.
> 
> 
> We cannot use the crate right away in Firecracker because in the kvm_gen crate (previously named kvm_sys) we also have code that is not auto-generated so the first step for us is to move that code to somewhere else. This step is currently in review [2].
> 
> We still have to figure out some loose-ends and I created some issues for them [3], but it would be nice to get your feedback on this.
> 
> 
> Thanks,
> 
> Andreea
> 
> 
> [1] https://crates.io/crates/kvm_wrapper
> 
> [2] https://github.com/firecracker-microvm/firecracker/pull/816
> 
> [3] https://github.com/andreeaflorescu/kvm_wrapper/issues
> 
> 
> 
> 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

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



From samuel.ortiz at intel.com  Tue Jan  8 08:42:43 2019
From: samuel.ortiz at intel.com (Samuel Ortiz)
Date: Tue, 8 Jan 2019 09:42:43 +0100
Subject: [Rust-VMM] GitHub organization
Message-ID: <20190108084243.GA858@caravaggio>

All,

Jonathan and I created a rust-vmm GitHub organization for hosting the
potential crates and project related to this project:
https://github.com/rust-vmm/

The initial goal for this org is to be a collaboration ground for new
crates. We should collectively decide how it gets organized in terms of
teams, repos and rights. At the moment Jonathan and myself are the 2
admins, but that can be changed at any time.

Please let me know if you'd like to be added as a member of this new
org.

Cheers,
Samuel.

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



From fandree at amazon.com  Tue Jan  8 09:28:16 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Tue, 8 Jan 2019 09:28:16 +0000
Subject: [Rust-VMM] KVM bindings as independent crate
In-Reply-To: <20190108082802.GK10834@caravaggio>
References: <1546879301177.29055@amazon.com>,
 <20190108082802.GK10834@caravaggio>
Message-ID: <1546939694079.46904@amazon.com>

Hey,

Yap, sounds like a good idea to have the kvm_wrapper in the rust-vmm organization.
I think it is best to migrate [1] it so then the old link to the repository would still work. Version 0.1.0 points to the repository from my personal profile. Otherwise I can also just move it, publish a new version on crates.io and yank the 0.1.0.

Andreea

[1] https://help.github.com/articles/transferring-a-repository/
________________________________________
From: Samuel Ortiz <samuel.ortiz at intel.com>
Sent: Tuesday, January 8, 2019 10:28 AM
To: Florescu, Andreea
Cc: rust-vmm at lists.opendev.org
Subject: Re: [Rust-VMM] KVM bindings as independent crate

Hi Andreea,

We created a rust-vmm organization on github [1], maybe we should have
the KVM bindings as our first repo there? I just sent you an invite to
become member of the org.

Cheers,
Samuel.

[1] https://github.com/rust-vmm

On Mon, Jan 07, 2019 at 04:41:42PM +0000, Florescu, Andreea wrote:
> Hey everyone,
>
>
> I published the KVM bindings on crates.io [1] under the name "kvm_wrapper". The bindings are available for arm, arm64, x86 and x86_64. The kernel version can be selected by using features. For now I only added bindings for linux-4.14.0 and linux-4.20.0, but others can be added if needed. The version can be selected using features:
>
> kvm_wrapper = { version = "0.1.0", features = ["kvm_v4_14_0"]}
>
> and by default the latest kernel version is used.
>
>
> We cannot use the crate right away in Firecracker because in the kvm_gen crate (previously named kvm_sys) we also have code that is not auto-generated so the first step for us is to move that code to somewhere else. This step is currently in review [2].
>
> We still have to figure out some loose-ends and I created some issues for them [3], but it would be nice to get your feedback on this.
>
>
> Thanks,
>
> Andreea
>
>
> [1] https://crates.io/crates/kvm_wrapper
>
> [2] https://github.com/firecracker-microvm/firecracker/pull/816
>
> [3] https://github.com/andreeaflorescu/kvm_wrapper/issues
>
>
>
> 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

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.




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.



From fandree at amazon.com  Tue Jan  8 09:43:48 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Tue, 8 Jan 2019 09:43:48 +0000
Subject: [Rust-VMM] KVM bindings as independent crate
In-Reply-To: <1546939694079.46904@amazon.com>
References: <1546879301177.29055@amazon.com>,
 <20190108082802.GK10834@caravaggio>,<1546939694079.46904@amazon.com>
Message-ID: <1546940627911.92492@amazon.com>

I migrated the repository. You can find it here: https://github.com/rust-vmm/kvm_wrapper

Andreea
________________________________________
From: Florescu, Andreea <fandree at amazon.com>
Sent: Tuesday, January 8, 2019 11:28 AM
To: Samuel Ortiz
Cc: rust-vmm at lists.opendev.org
Subject: [UNVERIFIED SENDER] Re: [Rust-VMM] KVM bindings as independent crate

Hey,

Yap, sounds like a good idea to have the kvm_wrapper in the rust-vmm organization.
I think it is best to migrate [1] it so then the old link to the repository would still work. Version 0.1.0 points to the repository from my personal profile. Otherwise I can also just move it, publish a new version on crates.io and yank the 0.1.0.

Andreea

[1] https://help.github.com/articles/transferring-a-repository/
________________________________________
From: Samuel Ortiz <samuel.ortiz at intel.com>
Sent: Tuesday, January 8, 2019 10:28 AM
To: Florescu, Andreea
Cc: rust-vmm at lists.opendev.org
Subject: Re: [Rust-VMM] KVM bindings as independent crate

Hi Andreea,

We created a rust-vmm organization on github [1], maybe we should have
the KVM bindings as our first repo there? I just sent you an invite to
become member of the org.

Cheers,
Samuel.

[1] https://github.com/rust-vmm

On Mon, Jan 07, 2019 at 04:41:42PM +0000, Florescu, Andreea wrote:
> Hey everyone,
>
>
> I published the KVM bindings on crates.io [1] under the name "kvm_wrapper". The bindings are available for arm, arm64, x86 and x86_64. The kernel version can be selected by using features. For now I only added bindings for linux-4.14.0 and linux-4.20.0, but others can be added if needed. The version can be selected using features:
>
> kvm_wrapper = { version = "0.1.0", features = ["kvm_v4_14_0"]}
>
> and by default the latest kernel version is used.
>
>
> We cannot use the crate right away in Firecracker because in the kvm_gen crate (previously named kvm_sys) we also have code that is not auto-generated so the first step for us is to move that code to somewhere else. This step is currently in review [2].
>
> We still have to figure out some loose-ends and I created some issues for them [3], but it would be nice to get your feedback on this.
>
>
> Thanks,
>
> Andreea
>
>
> [1] https://crates.io/crates/kvm_wrapper
>
> [2] https://github.com/firecracker-microvm/firecracker/pull/816
>
> [3] https://github.com/andreeaflorescu/kvm_wrapper/issues
>
>
>
> 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

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.




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



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.



From josh at joshtriplett.org  Tue Jan  8 20:28:57 2019
From: josh at joshtriplett.org (Josh Triplett)
Date: Tue, 8 Jan 2019 12:28:57 -0800
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <20190108084243.GA858@caravaggio>
References: <20190108084243.GA858@caravaggio>
Message-ID: <20190108202857.GB6298@localhost>

On Tue, Jan 08, 2019 at 09:42:43AM +0100, Samuel Ortiz wrote:
> All,
> 
> Jonathan and I created a rust-vmm GitHub organization for hosting the
> potential crates and project related to this project:
> https://github.com/rust-vmm/
> 
> The initial goal for this org is to be a collaboration ground for new
> crates. We should collectively decide how it gets organized in terms of
> teams, repos and rights. At the moment Jonathan and myself are the 2
> admins, but that can be changed at any time.
> 
> Please let me know if you'd like to be added as a member of this new
> org.

Please add me, and I'd be happy to help with this.

I would suggest that we either have one repo per crate, or one repo with
a workspace setup that builds (and tests) all crates. The former makes
it easier to work with individual crates, but harder to coordinate
changes across all of them. The latter makes it easier to make
cross-crate changes, but harder to remember things like updating
versions and dependencies correctly.


From samuel.ortiz at intel.com  Wed Jan  9 09:15:12 2019
From: samuel.ortiz at intel.com (Samuel Ortiz)
Date: Wed, 9 Jan 2019 10:15:12 +0100
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <20190108202857.GB6298@localhost>
References: <20190108084243.GA858@caravaggio> <20190108202857.GB6298@localhost>
Message-ID: <20190109091512.GI858@caravaggio>

On Tue, Jan 08, 2019 at 12:28:57PM -0800, Josh Triplett wrote:
> On Tue, Jan 08, 2019 at 09:42:43AM +0100, Samuel Ortiz wrote:
> > All,
> > 
> > Jonathan and I created a rust-vmm GitHub organization for hosting the
> > potential crates and project related to this project:
> > https://github.com/rust-vmm/
> > 
> > The initial goal for this org is to be a collaboration ground for new
> > crates. We should collectively decide how it gets organized in terms of
> > teams, repos and rights. At the moment Jonathan and myself are the 2
> > admins, but that can be changed at any time.
> > 
> > Please let me know if you'd like to be added as a member of this new
> > org.
> 
> Please add me, and I'd be happy to help with this.
You should have received an invitation to join now.


> I would suggest that we either have one repo per crate, or one repo with
> a workspace setup that builds (and tests) all crates. The former makes
> it easier to work with individual crates, but harder to coordinate
> changes across all of them. The latter makes it easier to make
> cross-crate changes, but harder to remember things like updating
> versions and dependencies correctly.
With Rust, is there a typical and recommended way to set things up for
the latter?

Cheers,
Samuel.


---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



From fandree at amazon.com  Wed Jan  9 09:20:04 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Wed, 9 Jan 2019 09:20:04 +0000
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <20190108202857.GB6298@localhost>
References: <20190108084243.GA858@caravaggio>,
 <20190108202857.GB6298@localhost>
Message-ID: <1547025602843.13694@amazon.com>

Hey,

My personal preference is to have one repository per crate. I am also not aware of other rust crates (published on crates.io) that share the same repository. It would be interesting to find if such projects exist to see how easy it is to publish the crates and make sure that you don't mess up versions. Another reason I would like to have them as separate crates is because I assume that not all rust-vmms (e.g. Firecracker) will use all crates in rust-vmm.
When we get to a "critical mass" of crates that can be used to create a VMM, we can also create a vmm repo that uses all the independent crates.

What do you say?

Andreea
________________________________________
From: Josh Triplett <josh at joshtriplett.org>
Sent: Tuesday, January 8, 2019 10:28 PM
To: Samuel Ortiz
Cc: rust-vmm ML
Subject: Re: [Rust-VMM] GitHub organization

On Tue, Jan 08, 2019 at 09:42:43AM +0100, Samuel Ortiz wrote:
> All,
>
> Jonathan and I created a rust-vmm GitHub organization for hosting the
> potential crates and project related to this project:
> https://github.com/rust-vmm/
>
> The initial goal for this org is to be a collaboration ground for new
> crates. We should collectively decide how it gets organized in terms of
> teams, repos and rights. At the moment Jonathan and myself are the 2
> admins, but that can be changed at any time.
>
> Please let me know if you'd like to be added as a member of this new
> org.

Please add me, and I'd be happy to help with this.

I would suggest that we either have one repo per crate, or one repo with
a workspace setup that builds (and tests) all crates. The former makes
it easier to work with individual crates, but harder to coordinate
changes across all of them. The latter makes it easier to make
cross-crate changes, but harder to remember things like updating
versions and dependencies correctly.

_______________________________________________
Rust-vmm mailing list
Rust-vmm at lists.opendev.org
http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm



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.



From samuel.ortiz at intel.com  Wed Jan  9 09:36:28 2019
From: samuel.ortiz at intel.com (Samuel Ortiz)
Date: Wed, 9 Jan 2019 10:36:28 +0100
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <1547025602843.13694@amazon.com>
References: <20190108084243.GA858@caravaggio> <20190108202857.GB6298@localhost>
 <1547025602843.13694@amazon.com>
Message-ID: <20190109093628.GJ858@caravaggio>

Hi Andreea,

I also tend to prefer one repo per crate. But I want to understand if
there's a typical setup for a shared workspace for multiple crates, to
at least see how that could be workable in practice.

Cheers,
Samuel.

On Wed, Jan 09, 2019 at 09:20:04AM +0000, Florescu, Andreea wrote:
> Hey,
> 
> My personal preference is to have one repository per crate. I am also not aware of other rust crates (published on crates.io) that share the same repository. It would be interesting to find if such projects exist to see how easy it is to publish the crates and make sure that you don't mess up versions. Another reason I would like to have them as separate crates is because I assume that not all rust-vmms (e.g. Firecracker) will use all crates in rust-vmm.
> When we get to a "critical mass" of crates that can be used to create a VMM, we can also create a vmm repo that uses all the independent crates.
> 
> What do you say?
> 
> Andreea
> ________________________________________
> From: Josh Triplett <josh at joshtriplett.org>
> Sent: Tuesday, January 8, 2019 10:28 PM
> To: Samuel Ortiz
> Cc: rust-vmm ML
> Subject: Re: [Rust-VMM] GitHub organization
> 
> On Tue, Jan 08, 2019 at 09:42:43AM +0100, Samuel Ortiz wrote:
> > All,
> >
> > Jonathan and I created a rust-vmm GitHub organization for hosting the
> > potential crates and project related to this project:
> > https://github.com/rust-vmm/
> >
> > The initial goal for this org is to be a collaboration ground for new
> > crates. We should collectively decide how it gets organized in terms of
> > teams, repos and rights. At the moment Jonathan and myself are the 2
> > admins, but that can be changed at any time.
> >
> > Please let me know if you'd like to be added as a member of this new
> > org.
> 
> Please add me, and I'd be happy to help with this.
> 
> I would suggest that we either have one repo per crate, or one repo with
> a workspace setup that builds (and tests) all crates. The former makes
> it easier to work with individual crates, but harder to coordinate
> changes across all of them. The latter makes it easier to make
> cross-crate changes, but harder to remember things like updating
> versions and dependencies correctly.
> 
> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> 
> 
> 
> 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.
> 
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



From allison at lohutok.net  Wed Jan  9 09:49:43 2019
From: allison at lohutok.net (Allison Randal)
Date: Wed, 9 Jan 2019 09:49:43 +0000
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <20190109093628.GJ858@caravaggio>
References: <20190108084243.GA858@caravaggio>
 <20190108202857.GB6298@localhost> <1547025602843.13694@amazon.com>
 <20190109093628.GJ858@caravaggio>
Message-ID: <ed34765b-2d1a-11a3-6987-4e92fe463460@lohutok.net>

Hi Samuel,

Yes, shared workspaces for multiple crates are a standard feature of Rust:

https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html

But, the choice has more to do with how you intend the crates to be
used. If the crates will only ever be used by one VMM implementation
(like crosvm originally), then a shared workspace of crates in a single
monolithic repo makes sense. But, since you are already sharing crates
across two separate VMM implementations, then a clean separation of
different repos for each crate makes more sense now. Cargo is so good
(and flexible) about pulling in dependencies from git repos, versioned
releases, or other sources, that it's straightforward to work with
multiple separate repos.

Allison

On 1/9/19 9:36 AM, Samuel Ortiz wrote:
> Hi Andreea,
> 
> I also tend to prefer one repo per crate. But I want to understand if
> there's a typical setup for a shared workspace for multiple crates, to
> at least see how that could be workable in practice.
> 
> Cheers,
> Samuel.
> 
> On Wed, Jan 09, 2019 at 09:20:04AM +0000, Florescu, Andreea wrote:
>> Hey,
>>
>> My personal preference is to have one repository per crate. I am also not aware of other rust crates (published on crates.io) that share the same repository. It would be interesting to find if such projects exist to see how easy it is to publish the crates and make sure that you don't mess up versions. Another reason I would like to have them as separate crates is because I assume that not all rust-vmms (e.g. Firecracker) will use all crates in rust-vmm.
>> When we get to a "critical mass" of crates that can be used to create a VMM, we can also create a vmm repo that uses all the independent crates.
>>
>> What do you say?
>>
>> Andreea
>> ________________________________________
>> From: Josh Triplett <josh at joshtriplett.org>
>> Sent: Tuesday, January 8, 2019 10:28 PM
>> To: Samuel Ortiz
>> Cc: rust-vmm ML
>> Subject: Re: [Rust-VMM] GitHub organization
>>
>> On Tue, Jan 08, 2019 at 09:42:43AM +0100, Samuel Ortiz wrote:
>>> All,
>>>
>>> Jonathan and I created a rust-vmm GitHub organization for hosting the
>>> potential crates and project related to this project:
>>> https://github.com/rust-vmm/
>>>
>>> The initial goal for this org is to be a collaboration ground for new
>>> crates. We should collectively decide how it gets organized in terms of
>>> teams, repos and rights. At the moment Jonathan and myself are the 2
>>> admins, but that can be changed at any time.
>>>
>>> Please let me know if you'd like to be added as a member of this new
>>> org.
>>
>> Please add me, and I'd be happy to help with this.
>>
>> I would suggest that we either have one repo per crate, or one repo with
>> a workspace setup that builds (and tests) all crates. The former makes
>> it easier to work with individual crates, but harder to coordinate
>> changes across all of them. The latter makes it easier to make
>> cross-crate changes, but harder to remember things like updating
>> versions and dependencies correctly.
>>
>> _______________________________________________
>> Rust-vmm mailing list
>> Rust-vmm at lists.opendev.org
>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>
>>
>>
>> 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.
>>
> ---------------------------------------------------------------------
> Intel Corporation SAS (French simplified joint stock company)
> Registered headquarters: "Les Montalets"- 2, rue de Paris, 
> 92196 Meudon Cedex, France
> Registration Number:  302 456 199 R.C.S. NANTERRE
> Capital: 4,572,000 Euros
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
> 
> 
> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> 


From samuel.ortiz at intel.com  Wed Jan  9 10:07:43 2019
From: samuel.ortiz at intel.com (Samuel Ortiz)
Date: Wed, 9 Jan 2019 11:07:43 +0100
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <ed34765b-2d1a-11a3-6987-4e92fe463460@lohutok.net>
References: <20190108084243.GA858@caravaggio> <20190108202857.GB6298@localhost>
 <1547025602843.13694@amazon.com> <20190109093628.GJ858@caravaggio>
 <ed34765b-2d1a-11a3-6987-4e92fe463460@lohutok.net>
Message-ID: <20190109100743.GK858@caravaggio>

Hi Allison,

Thanks for the pointer and explanation.
So I think we should go with one repo per crate, unless soneone strongly
disagrees.

Cheers,
Samuel.

On Wed, Jan 09, 2019 at 09:49:43AM +0000, Allison Randal wrote:
> Hi Samuel,
> 
> Yes, shared workspaces for multiple crates are a standard feature of Rust:
> 
> https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html
> 
> But, the choice has more to do with how you intend the crates to be
> used. If the crates will only ever be used by one VMM implementation
> (like crosvm originally), then a shared workspace of crates in a single
> monolithic repo makes sense. But, since you are already sharing crates
> across two separate VMM implementations, then a clean separation of
> different repos for each crate makes more sense now. Cargo is so good
> (and flexible) about pulling in dependencies from git repos, versioned
> releases, or other sources, that it's straightforward to work with
> multiple separate repos.
> 
> Allison
> 
> On 1/9/19 9:36 AM, Samuel Ortiz wrote:
> > Hi Andreea,
> > 
> > I also tend to prefer one repo per crate. But I want to understand if
> > there's a typical setup for a shared workspace for multiple crates, to
> > at least see how that could be workable in practice.
> > 
> > Cheers,
> > Samuel.
> > 
> > On Wed, Jan 09, 2019 at 09:20:04AM +0000, Florescu, Andreea wrote:
> >> Hey,
> >>
> >> My personal preference is to have one repository per crate. I am also not aware of other rust crates (published on crates.io) that share the same repository. It would be interesting to find if such projects exist to see how easy it is to publish the crates and make sure that you don't mess up versions. Another reason I would like to have them as separate crates is because I assume that not all rust-vmms (e.g. Firecracker) will use all crates in rust-vmm.
> >> When we get to a "critical mass" of crates that can be used to create a VMM, we can also create a vmm repo that uses all the independent crates.
> >>
> >> What do you say?
> >>
> >> Andreea
> >> ________________________________________
> >> From: Josh Triplett <josh at joshtriplett.org>
> >> Sent: Tuesday, January 8, 2019 10:28 PM
> >> To: Samuel Ortiz
> >> Cc: rust-vmm ML
> >> Subject: Re: [Rust-VMM] GitHub organization
> >>
> >> On Tue, Jan 08, 2019 at 09:42:43AM +0100, Samuel Ortiz wrote:
> >>> All,
> >>>
> >>> Jonathan and I created a rust-vmm GitHub organization for hosting the
> >>> potential crates and project related to this project:
> >>> https://github.com/rust-vmm/
> >>>
> >>> The initial goal for this org is to be a collaboration ground for new
> >>> crates. We should collectively decide how it gets organized in terms of
> >>> teams, repos and rights. At the moment Jonathan and myself are the 2
> >>> admins, but that can be changed at any time.
> >>>
> >>> Please let me know if you'd like to be added as a member of this new
> >>> org.
> >>
> >> Please add me, and I'd be happy to help with this.
> >>
> >> I would suggest that we either have one repo per crate, or one repo with
> >> a workspace setup that builds (and tests) all crates. The former makes
> >> it easier to work with individual crates, but harder to coordinate
> >> changes across all of them. The latter makes it easier to make
> >> cross-crate changes, but harder to remember things like updating
> >> versions and dependencies correctly.
> >>
> >> _______________________________________________
> >> Rust-vmm mailing list
> >> Rust-vmm at lists.opendev.org
> >> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> >>
> >>
> >>
> >> 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.
> >>
> > ---------------------------------------------------------------------
> > Intel Corporation SAS (French simplified joint stock company)
> > Registered headquarters: "Les Montalets"- 2, rue de Paris, 
> > 92196 Meudon Cedex, France
> > Registration Number:  302 456 199 R.C.S. NANTERRE
> > Capital: 4,572,000 Euros
> > 
> > This e-mail and any attachments may contain confidential material for
> > the sole use of the intended recipient(s). Any review or distribution
> > by others is strictly prohibited. If you are not the intended
> > recipient, please contact the sender and delete all copies.
> > 
> > 
> > _______________________________________________
> > Rust-vmm mailing list
> > Rust-vmm at lists.opendev.org
> > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> > 
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



From pbonzini at redhat.com  Wed Jan  9 18:07:00 2019
From: pbonzini at redhat.com (Paolo Bonzini)
Date: Wed, 9 Jan 2019 19:07:00 +0100
Subject: [Rust-VMM] Summer of Code / Outreachy projects
Message-ID: <814bbcd6-524a-f3ec-6961-35babead8f98@redhat.com>

QEMU would be glad to host projects related to VMMs in Rust as part of
Google summer of Code and Outreachy.  This includes all of Firecracker,
CrosVM and common infrastructure that could be reused by multiple
virtual machine monitors; with my QEMU hat, I would obviously favor the
latter :)).

An idea could be to migrate Firecracker and CrosVM to the Fuchsia crates
that were mentioned early here on the mailing list, and/or implement a
sample vhost-user client using whatever standard set of crates are
established.  Another possibility is PCI and virtio-pci in Firecracker.

Thanks,

Paolo


From aliguori at amazon.com  Wed Jan  9 18:20:22 2019
From: aliguori at amazon.com (Liguori, Anthony)
Date: Wed, 9 Jan 2019 18:20:22 +0000
Subject: [Rust-VMM] Summer of Code / Outreachy projects
Message-ID: <9ee64593-8534-4d5f-891e-35abf120ec33@email.android.com>

Thanks an amazing idea!

We can try to come up with some ideas too.  Do you need more mentors?


On Jan 9, 2019 10:08 AM, Paolo Bonzini <pbonzini at redhat.com> wrote:
QEMU would be glad to host projects related to VMMs in Rust as part of
Google summer of Code and Outreachy.  This includes all of Firecracker,
CrosVM and common infrastructure that could be reused by multiple
virtual machine monitors; with my QEMU hat, I would obviously favor the
latter :)).

An idea could be to migrate Firecracker and CrosVM to the Fuchsia crates
that were mentioned early here on the mailing list, and/or implement a
sample vhost-user client using whatever standard set of crates are
established.  Another possibility is PCI and virtio-pci in Firecracker.

Thanks,

Paolo

_______________________________________________
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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190109/f1a68e87/attachment-0001.html>

From pbonzini at redhat.com  Wed Jan  9 21:09:16 2019
From: pbonzini at redhat.com (Paolo Bonzini)
Date: Wed, 9 Jan 2019 22:09:16 +0100
Subject: [Rust-VMM] Summer of Code / Outreachy projects
In-Reply-To: <9ee64593-8534-4d5f-891e-35abf120ec33@email.android.com>
References: <9ee64593-8534-4d5f-891e-35abf120ec33@email.android.com>
Message-ID: <20e9d7ae-2afa-08bb-f676-50334fb32944@redhat.com>

On 09/01/19 19:20, Liguori, Anthony wrote:
> Thanks an amazing idea!
> 
> We can try to come up with some ideas too.

https://wiki.qemu.org/Google_Summer_of_Code_2019#Project_Ideas is the
place then. :)  Also if you want to flesh out mine please place them
there because...

> Do you need more mentors?

... at least I am not experienced enough to be anything more than a
co-mentor, and even though some members of the QEMU community are
already using (or learning) Rust, most of use probably don't know much
about Firecracker and CrosVM.

The idea is just to use QEMU as the umbrella organization and share the
effort of submitting the proposals, herding students and mentors around
evaluation times, etc.  This is not a new thing; libvirt, KVM and
Jailhouse have already enjoyed the opportunity in the past (libvirt has
since graduated to a separate organization), and in general the
organization should have no problem mentoring students working not just
on QEMU, but also in general on KVM.

Paolo

> 
> 
> On Jan 9, 2019 10:08 AM, Paolo Bonzini <pbonzini at redhat.com> wrote:
> 
>     QEMU would be glad to host projects related to VMMs in Rust as part of
>     Google summer of Code and Outreachy.  This includes all of Firecracker,
>     CrosVM and common infrastructure that could be reused by multiple
>     virtual machine monitors; with my QEMU hat, I would obviously favor the
>     latter :)).
> 
>     An idea could be to migrate Firecracker and CrosVM to the Fuchsia crates
>     that were mentioned early here on the mailing list, and/or implement a
>     sample vhost-user client using whatever standard set of crates are
>     established.  Another possibility is PCI and virtio-pci in Firecracker.
> 
>     Thanks,
> 
>     Paolo
> 
>     _______________________________________________
>     Rust-vmm mailing list
>     Rust-vmm at lists.opendev.org
>     http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> 
> 



From dgreid at chromium.org  Thu Jan 10 23:38:27 2019
From: dgreid at chromium.org (Dylan Reid)
Date: Thu, 10 Jan 2019 15:38:27 -0800
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <20190108084243.GA858@caravaggio>
References: <20190108084243.GA858@caravaggio>
Message-ID: <CAEUnVG5SRydBxXkk_KyFM-a7w09qHVY+WXkXrNALPk=U8Qz9Vw@mail.gmail.com>

On Tue, Jan 8, 2019 at 12:43 AM Samuel Ortiz <samuel.ortiz at intel.com> wrote:
>
> All,
>
> Jonathan and I created a rust-vmm GitHub organization for hosting the
> potential crates and project related to this project:
> https://github.com/rust-vmm/
>
> The initial goal for this org is to be a collaboration ground for new
> crates. We should collectively decide how it gets organized in terms of
> teams, repos and rights. At the moment Jonathan and myself are the 2
> admins, but that can be changed at any time.
>
> Please let me know if you'd like to be added as a member of this new
> org.

Could you add the crosvm team?

dgreid - dgreid at chromium.org
smibarber - smbarber at chromium.org
danielverkamp - dverkamp at chromium.org
dtolnay - dtolnay at chromium.org
jynnantonix - chirantan at chromium.org

Thanks,

Dylan


>
> Cheers,
> Samuel.
>
> ---------------------------------------------------------------------
> Intel Corporation SAS (French simplified joint stock company)
> Registered headquarters: "Les Montalets"- 2, rue de Paris,
> 92196 Meudon Cedex, France
> Registration Number:  302 456 199 R.C.S. NANTERRE
> Capital: 4,572,000 Euros
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
>
> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm


From samuel.ortiz at intel.com  Fri Jan 11 08:35:47 2019
From: samuel.ortiz at intel.com (Samuel Ortiz)
Date: Fri, 11 Jan 2019 09:35:47 +0100
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <CAEUnVG5SRydBxXkk_KyFM-a7w09qHVY+WXkXrNALPk=U8Qz9Vw@mail.gmail.com>
References: <20190108084243.GA858@caravaggio>
 <CAEUnVG5SRydBxXkk_KyFM-a7w09qHVY+WXkXrNALPk=U8Qz9Vw@mail.gmail.com>
Message-ID: <20190111083547.GB21034@caravaggio>

On Thu, Jan 10, 2019 at 03:38:27PM -0800, Dylan Reid wrote:
> On Tue, Jan 8, 2019 at 12:43 AM Samuel Ortiz <samuel.ortiz at intel.com> wrote:
> >
> > All,
> >
> > Jonathan and I created a rust-vmm GitHub organization for hosting the
> > potential crates and project related to this project:
> > https://github.com/rust-vmm/
> >
> > The initial goal for this org is to be a collaboration ground for new
> > crates. We should collectively decide how it gets organized in terms of
> > teams, repos and rights. At the moment Jonathan and myself are the 2
> > admins, but that can be changed at any time.
> >
> > Please let me know if you'd like to be added as a member of this new
> > org.
> 
> Could you add the crosvm team?
> 
> dgreid - dgreid at chromium.org
> smibarber - smbarber at chromium.org
> danielverkamp - dverkamp at chromium.org
> dtolnay - dtolnay at chromium.org
> jynnantonix - chirantan at chromium.org
All invitations sent.

Cheers,
Samuel.
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



From acatan at amazon.com  Fri Jan 11 13:30:42 2019
From: acatan at amazon.com (Catangiu, Adrian Costin)
Date: Fri, 11 Jan 2019 13:30:42 +0000
Subject: [Rust-VMM] Join the rust-vmm GitHub organization
Message-ID: <77F4053A-D0EC-425F-92F1-DD68D9C5C99A@amazon.com>

Hi,

Please add me (GitHub user: acatangiu, email: acatan at amazon.com) to the rust-vmm GitHub organization.

Thanks,
Adrian.



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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190111/619a29cc/attachment.html>

From aagch at amazon.com  Fri Jan 11 13:35:03 2019
From: aagch at amazon.com (Agache, Alexandru)
Date: Fri, 11 Jan 2019 13:35:03 +0000
Subject: [Rust-VMM] pls add to the rust-vmm org on Github
Message-ID: <F7155A19-0F58-4746-840A-4DB58ECB3907@amazon.com>

Hi guys,

Please also add me to rust-vmm org. My GH username is alexandruag, and my email address is aagch at amazon.com.

Best,
Alex




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.

From samuel.ortiz at intel.com  Fri Jan 11 13:39:02 2019
From: samuel.ortiz at intel.com (Samuel Ortiz)
Date: Fri, 11 Jan 2019 14:39:02 +0100
Subject: [Rust-VMM] Join the rust-vmm GitHub organization
In-Reply-To: <77F4053A-D0EC-425F-92F1-DD68D9C5C99A@amazon.com>
References: <77F4053A-D0EC-425F-92F1-DD68D9C5C99A@amazon.com>
Message-ID: <20190111133902.GD21034@caravaggio>

Hi Adrian,

Done.

Cheers,
Samuel.

On Fri, Jan 11, 2019 at 01:30:42PM +0000, Catangiu, Adrian Costin wrote:
> Hi,
> 
> Please add me (GitHub user: acatangiu, email: acatan at amazon.com) to the rust-vmm GitHub organization.
> 
> Thanks,
> Adrian.
> 
> 
> 
> 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

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



From dhr at amazon.com  Fri Jan 11 13:47:46 2019
From: dhr at amazon.com (Horobeanu, Dan)
Date: Fri, 11 Jan 2019 13:47:46 +0000
Subject: [Rust-VMM] rust-vmm GitHub Join Request
Message-ID: <55EC2ADB-DA4B-46B1-AF0A-6E79C051F154@amazon.com>

Hey everyone,

I'd like to join the rust-vmm GitHub org, please.
GitHub username: dhrgit
Email: dhr at amazon.com<mailto:dhr at amazon.com>

Thanks!
Dan



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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190111/ad441da9/attachment-0001.html>

From crossd at gmail.com  Fri Jan 11 13:55:35 2019
From: crossd at gmail.com (Dan Cross)
Date: Fri, 11 Jan 2019 08:55:35 -0500
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <20190108084243.GA858@caravaggio>
References: <20190108084243.GA858@caravaggio>
Message-ID: <CAEoi9W7kXU-tQY4Ar2u7s34DGpZC3YojonzJRwNS4kt_-WuUfg@mail.gmail.com>

Could you please add dcross at google.com? Thank you!

        - Dan C.

On Tue, Jan 8, 2019 at 3:43 AM Samuel Ortiz <samuel.ortiz at intel.com> wrote:

> All,
>
> Jonathan and I created a rust-vmm GitHub organization for hosting the
> potential crates and project related to this project:
> https://github.com/rust-vmm/
>
> The initial goal for this org is to be a collaboration ground for new
> crates. We should collectively decide how it gets organized in terms of
> teams, repos and rights. At the moment Jonathan and myself are the 2
> admins, but that can be changed at any time.
>
> Please let me know if you'd like to be added as a member of this new
> org.
>
> Cheers,
> Samuel.
>
> ---------------------------------------------------------------------
> Intel Corporation SAS (French simplified joint stock company)
> Registered headquarters: "Les Montalets"- 2, rue de Paris,
> 92196 Meudon Cedex, France
> Registration Number:  302 456 199 R.C.S. NANTERRE
> Capital: 4,572,000 Euros
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
>
> _______________________________________________
> 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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190111/45f83e37/attachment.html>

From liuj97 at gmail.com  Fri Jan 11 14:29:51 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Fri, 11 Jan 2019 22:29:51 +0800
Subject: [Rust-VMM] Join the rust-vmm GitHub organization
Message-ID: <D4F4EE89-8880-4927-886C-E2B4766649F6@gmail.com>

Hi,
Please add me (GitHub user: jiangliu, email: gerry at linux.alibaba.com <mailto:gerry at linux.alibaba.com>) to the Rust-vmm GitHub organization.

Thanks,
Gerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190111/e67f2f6b/attachment.html>

From fandree at amazon.com  Fri Jan 11 15:52:40 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Fri, 11 Jan 2019 15:52:40 +0000
Subject: [Rust-VMM] rust-vmm at Fosdem 2019
Message-ID: <1547221958963.20770@amazon.com>

Hey,


I did a late submission to talk about rust-vmm at Fosdem conference 2019 [1] and by a series of very fortunate events the talk was accepted.


This is probably a good time to ask if anyone would like to chat about what the next steps look like for rust-vmm crates over a call. I'd like to have more clarity on our direction by the time I am on stage. I think it is a great opportunity to get more people onboard.

I'm keen on on getting input/feedback with regards to the slides I'll be putting together.


Also, is anyone from this list going to Fosdem? It would be awesome if you could attend the talk! Maybe we can also plan a meet-up and discuss about future plans and ideas.


Thanks,

Andreea


[1] https://fosdem.org/2019/schedule/event/vai_rust_vmm/



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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190111/0dbe83cc/attachment.html>

From dgreid at chromium.org  Fri Jan 11 16:17:30 2019
From: dgreid at chromium.org (Dylan Reid)
Date: Fri, 11 Jan 2019 08:17:30 -0800
Subject: [Rust-VMM] rust-vmm at Fosdem 2019
In-Reply-To: <1547221958963.20770@amazon.com>
References: <1547221958963.20770@amazon.com>
Message-ID: <CAEUnVG7Re5WRfDH5s87sjwD5VDaj33kSm6S8C1SmqFJPin3_mQ@mail.gmail.com>

On Fri, Jan 11, 2019 at 7:52 AM Florescu, Andreea <fandree at amazon.com> wrote:
>
> Hey,
>
>
> I did a late submission to talk about rust-vmm at Fosdem conference 2019 [1] and by a series of very fortunate events the talk was accepted.
>
>
> This is probably a good time to ask if anyone would like to chat about what the next steps look like for rust-vmm crates over a call. I'd like to have more clarity on our direction by the time I am on stage. I think it is a great opportunity to get more people onboard.
>
> I'm keen on on getting input/feedback with regards to the slides I'll be putting together.
>
>
> Also, is anyone from this list going to Fosdem? It would be awesome if you could attend the talk! Maybe we can also plan a meet-up and discuss about future plans and ideas.

Google will be giving a talk as well, but more focusesd on the
userspaace that runs under crosvm. I'll probably be there, I'm still
working on flights.

>
>
> Thanks,
>
> Andreea
>
>
> [1] https://fosdem.org/2019/schedule/event/vai_rust_vmm/
>
>
> 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 thierry at openstack.org  Fri Jan 11 16:45:58 2019
From: thierry at openstack.org (Thierry Carrez)
Date: Fri, 11 Jan 2019 17:45:58 +0100
Subject: [Rust-VMM] [SPAM]  rust-vmm at Fosdem 2019
In-Reply-To: <1547221958963.20770@amazon.com>
References: <1547221958963.20770@amazon.com>
Message-ID: <c4802b93-5a40-abdf-b2d5-3860e270bfc7@openstack.org>

Florescu, Andreea wrote:
> Also, is anyone from this list going to Fosdem? It would be awesome if 
> you could attend the talk! Maybe we can also plan a meet-up and discuss 
> about future plans and ideas.

I'll be there and am interested in talking if we can find the time :)

-- 
Thierry Carrez
OpenStack Foundation


From jonolson at google.com  Fri Jan 11 18:33:04 2019
From: jonolson at google.com (Jon Olson)
Date: Fri, 11 Jan 2019 10:33:04 -0800
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <CAEoi9W7kXU-tQY4Ar2u7s34DGpZC3YojonzJRwNS4kt_-WuUfg@mail.gmail.com>
References: <20190108084243.GA858@caravaggio>
 <CAEoi9W7kXU-tQY4Ar2u7s34DGpZC3YojonzJRwNS4kt_-WuUfg@mail.gmail.com>
Message-ID: <CAJoqh4XtxCf4FWsrCZYxFVyr5TRpWqGi5Mh+9Ko=AT3Vmjtqog@mail.gmail.com>

And jonolson at google.com if you wouldn't mind :)

Thanks,
Jon


On Fri, Jan 11, 2019 at 5:56 AM Dan Cross <crossd at gmail.com> wrote:

> Could you please add dcross at google.com? Thank you!
>
>         - Dan C.
>
> On Tue, Jan 8, 2019 at 3:43 AM Samuel Ortiz <samuel.ortiz at intel.com>
> wrote:
>
>> All,
>>
>> Jonathan and I created a rust-vmm GitHub organization for hosting the
>> potential crates and project related to this project:
>> https://github.com/rust-vmm/
>>
>> The initial goal for this org is to be a collaboration ground for new
>> crates. We should collectively decide how it gets organized in terms of
>> teams, repos and rights. At the moment Jonathan and myself are the 2
>> admins, but that can be changed at any time.
>>
>> Please let me know if you'd like to be added as a member of this new
>> org.
>>
>> Cheers,
>> Samuel.
>>
>> ---------------------------------------------------------------------
>> Intel Corporation SAS (French simplified joint stock company)
>> Registered headquarters: "Les Montalets"- 2, rue de Paris,
>> 92196 Meudon Cedex, France
>> Registration Number:  302 456 199 R.C.S. NANTERRE
>> Capital: 4,572,000 Euros
>>
>> This e-mail and any attachments may contain confidential material for
>> the sole use of the intended recipient(s). Any review or distribution
>> by others is strictly prohibited. If you are not the intended
>> recipient, please contact the sender and delete all copies.
>>
>>
>> _______________________________________________
>> Rust-vmm mailing list
>> Rust-vmm at lists.opendev.org
>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>
> _______________________________________________
> 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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190111/7fae592d/attachment-0001.html>

From maccarro at google.com  Fri Jan 11 19:36:43 2019
From: maccarro at google.com (Cory Maccarrone)
Date: Fri, 11 Jan 2019 11:36:43 -0800
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <CAJoqh4XtxCf4FWsrCZYxFVyr5TRpWqGi5Mh+9Ko=AT3Vmjtqog@mail.gmail.com>
References: <20190108084243.GA858@caravaggio>
 <CAEoi9W7kXU-tQY4Ar2u7s34DGpZC3YojonzJRwNS4kt_-WuUfg@mail.gmail.com>
 <CAJoqh4XtxCf4FWsrCZYxFVyr5TRpWqGi5Mh+9Ko=AT3Vmjtqog@mail.gmail.com>
Message-ID: <CAJ-JdHBydWTUsksut6g_ZxXube3XfY5CBgbF3upVog_VmxD87g@mail.gmail.com>

And maccarro at google.com please. :)

Thanks!
- Cory

On Fri, Jan 11, 2019 at 10:33 AM Jon Olson <jonolson at google.com> wrote:

> And jonolson at google.com if you wouldn't mind :)
>
> Thanks,
> Jon
>
>
> On Fri, Jan 11, 2019 at 5:56 AM Dan Cross <crossd at gmail.com> wrote:
>
>> Could you please add dcross at google.com? Thank you!
>>
>>         - Dan C.
>>
>> On Tue, Jan 8, 2019 at 3:43 AM Samuel Ortiz <samuel.ortiz at intel.com>
>> wrote:
>>
>>> All,
>>>
>>> Jonathan and I created a rust-vmm GitHub organization for hosting the
>>> potential crates and project related to this project:
>>> https://github.com/rust-vmm/
>>>
>>> The initial goal for this org is to be a collaboration ground for new
>>> crates. We should collectively decide how it gets organized in terms of
>>> teams, repos and rights. At the moment Jonathan and myself are the 2
>>> admins, but that can be changed at any time.
>>>
>>> Please let me know if you'd like to be added as a member of this new
>>> org.
>>>
>>> Cheers,
>>> Samuel.
>>>
>>> ---------------------------------------------------------------------
>>> Intel Corporation SAS (French simplified joint stock company)
>>> Registered headquarters: "Les Montalets"- 2, rue de Paris,
>>> 92196 Meudon Cedex, France
>>> Registration Number:  302 456 199 R.C.S. NANTERRE
>>> Capital: 4,572,000 Euros
>>>
>>> This e-mail and any attachments may contain confidential material for
>>> the sole use of the intended recipient(s). Any review or distribution
>>> by others is strictly prohibited. If you are not the intended
>>> recipient, please contact the sender and delete all copies.
>>>
>>>
>>> _______________________________________________
>>> Rust-vmm mailing list
>>> Rust-vmm at lists.opendev.org
>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>
>> _______________________________________________
>> Rust-vmm mailing list
>> Rust-vmm at lists.opendev.org
>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>
> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>


-- 
Cory Maccarrone | Staff Software Engineer | maccarro at google.com | Google
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190111/84d4e8bf/attachment.html>

From resouer at gmail.com  Fri Jan 11 19:56:46 2019
From: resouer at gmail.com (Lei Zhang)
Date: Fri, 11 Jan 2019 11:56:46 -0800
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <20190108084243.GA858@caravaggio>
References: <20190108084243.GA858@caravaggio>
Message-ID: <CAFGPykGFEyuwO=+-UV70YSvoRePOMLqMDrvLyqDi5WqVQ5N1fg@mail.gmail.com>

Hi Samuel!

Harry is here :-)

Lei Zhang <resouer at gmail.com>

On Tue, Jan 8, 2019 at 12:43 AM Samuel Ortiz <samuel.ortiz at intel.com> wrote:

> All,
>
> Jonathan and I created a rust-vmm GitHub organization for hosting the
> potential crates and project related to this project:
> https://github.com/rust-vmm/
>
> The initial goal for this org is to be a collaboration ground for new
> crates. We should collectively decide how it gets organized in terms of
> teams, repos and rights. At the moment Jonathan and myself are the 2
> admins, but that can be changed at any time.
>
> Please let me know if you'd like to be added as a member of this new
> org.
>
> Cheers,
> Samuel.
>
> ---------------------------------------------------------------------
> Intel Corporation SAS (French simplified joint stock company)
> Registered headquarters: "Les Montalets"- 2, rue de Paris,
> 92196 Meudon Cedex, France
> Registration Number:  302 456 199 R.C.S. NANTERRE
> Capital: 4,572,000 Euros
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
>
> _______________________________________________
> 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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190111/492434e2/attachment.html>

From fandree at amazon.com  Fri Jan 11 20:45:44 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Fri, 11 Jan 2019 20:45:44 +0000
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <CAFGPykGFEyuwO=+-UV70YSvoRePOMLqMDrvLyqDi5WqVQ5N1fg@mail.gmail.com>
References: <20190108084243.GA858@caravaggio>,
 <CAFGPykGFEyuwO=+-UV70YSvoRePOMLqMDrvLyqDi5WqVQ5N1fg@mail.gmail.com>
Message-ID: <1547239543863.25163@amazon.com>

Hey everyone,


I created a dummy community repository in rust-vmm. I also added a template for accessing request to the rust-vmm organization.

Here it is: https://github.com/rust-vmm/community/issues/new/choose


Andreea

________________________________
From: Lei Zhang <resouer at gmail.com>
Sent: Friday, January 11, 2019 9:56 PM
To: Samuel Ortiz
Cc: rust-vmm ML
Subject: Re: [Rust-VMM] GitHub organization

Hi Samuel!

Harry is here :-)

Lei Zhang <resouer at gmail.com<mailto:resouer at gmail.com>>

On Tue, Jan 8, 2019 at 12:43 AM Samuel Ortiz <samuel.ortiz at intel.com<mailto:samuel.ortiz at intel.com>> wrote:
All,

Jonathan and I created a rust-vmm GitHub organization for hosting the
potential crates and project related to this project:
https://github.com/rust-vmm/

The initial goal for this org is to be a collaboration ground for new
crates. We should collectively decide how it gets organized in terms of
teams, repos and rights. At the moment Jonathan and myself are the 2
admins, but that can be changed at any time.

Please let me know if you'd like to be added as a member of this new
org.

Cheers,
Samuel.

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


_______________________________________________
Rust-vmm mailing list
Rust-vmm at lists.opendev.org<mailto:Rust-vmm at lists.opendev.org>
http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm



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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190111/1c271dbb/attachment.html>

From samuel.ortiz at intel.com  Mon Jan 14 08:56:09 2019
From: samuel.ortiz at intel.com (Samuel Ortiz)
Date: Mon, 14 Jan 2019 09:56:09 +0100
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <CAFGPykGFEyuwO=+-UV70YSvoRePOMLqMDrvLyqDi5WqVQ5N1fg@mail.gmail.com>
References: <20190108084243.GA858@caravaggio>
 <CAFGPykGFEyuwO=+-UV70YSvoRePOMLqMDrvLyqDi5WqVQ5N1fg@mail.gmail.com>
Message-ID: <20190114085609.GG21034@caravaggio>

Hi Harry,

Invitation sent, thanks.

Cheers,
Samuel.

On Fri, Jan 11, 2019 at 11:56:46AM -0800, Lei Zhang wrote:
> Hi Samuel!
> 
> Harry is here :-)
> 
> Lei Zhang <resouer at gmail.com>
> 
> On Tue, Jan 8, 2019 at 12:43 AM Samuel Ortiz <samuel.ortiz at intel.com> wrote:
> 
> > All,
> >
> > Jonathan and I created a rust-vmm GitHub organization for hosting the
> > potential crates and project related to this project:
> > https://github.com/rust-vmm/
> >
> > The initial goal for this org is to be a collaboration ground for new
> > crates. We should collectively decide how it gets organized in terms of
> > teams, repos and rights. At the moment Jonathan and myself are the 2
> > admins, but that can be changed at any time.
> >
> > Please let me know if you'd like to be added as a member of this new
> > org.
> >
> > Cheers,
> > Samuel.
> >
> > ---------------------------------------------------------------------
> > Intel Corporation SAS (French simplified joint stock company)
> > Registered headquarters: "Les Montalets"- 2, rue de Paris,
> > 92196 Meudon Cedex, France
> > Registration Number:  302 456 199 R.C.S. NANTERRE
> > Capital: 4,572,000 Euros
> >
> > This e-mail and any attachments may contain confidential material for
> > the sole use of the intended recipient(s). Any review or distribution
> > by others is strictly prohibited. If you are not the intended
> > recipient, please contact the sender and delete all copies.
> >
> >
> > _______________________________________________
> > Rust-vmm mailing list
> > Rust-vmm at lists.opendev.org
> > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> >
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



From samuel.ortiz at intel.com  Mon Jan 14 08:57:05 2019
From: samuel.ortiz at intel.com (Samuel Ortiz)
Date: Mon, 14 Jan 2019 09:57:05 +0100
Subject: [Rust-VMM] GitHub organization
In-Reply-To: <CAJoqh4XtxCf4FWsrCZYxFVyr5TRpWqGi5Mh+9Ko=AT3Vmjtqog@mail.gmail.com>
References: <20190108084243.GA858@caravaggio>
 <CAEoi9W7kXU-tQY4Ar2u7s34DGpZC3YojonzJRwNS4kt_-WuUfg@mail.gmail.com>
 <CAJoqh4XtxCf4FWsrCZYxFVyr5TRpWqGi5Mh+9Ko=AT3Vmjtqog@mail.gmail.com>
Message-ID: <20190114085705.GH21034@caravaggio>

Hi Jon,

You should have received an invitation now.

Cheers,
Samuel.

On Fri, Jan 11, 2019 at 10:33:04AM -0800, Jon Olson wrote:
> And jonolson at google.com if you wouldn't mind :)
> 
> Thanks,
> Jon
> 
> 
> On Fri, Jan 11, 2019 at 5:56 AM Dan Cross <crossd at gmail.com> wrote:
> 
> > Could you please add dcross at google.com? Thank you!
> >
> >         - Dan C.
> >
> > On Tue, Jan 8, 2019 at 3:43 AM Samuel Ortiz <samuel.ortiz at intel.com>
> > wrote:
> >
> >> All,
> >>
> >> Jonathan and I created a rust-vmm GitHub organization for hosting the
> >> potential crates and project related to this project:
> >> https://github.com/rust-vmm/
> >>
> >> The initial goal for this org is to be a collaboration ground for new
> >> crates. We should collectively decide how it gets organized in terms of
> >> teams, repos and rights. At the moment Jonathan and myself are the 2
> >> admins, but that can be changed at any time.
> >>
> >> Please let me know if you'd like to be added as a member of this new
> >> org.
> >>
> >> Cheers,
> >> Samuel.
> >>
> >> ---------------------------------------------------------------------
> >> Intel Corporation SAS (French simplified joint stock company)
> >> Registered headquarters: "Les Montalets"- 2, rue de Paris,
> >> 92196 Meudon Cedex, France
> >> Registration Number:  302 456 199 R.C.S. NANTERRE
> >> Capital: 4,572,000 Euros
> >>
> >> This e-mail and any attachments may contain confidential material for
> >> the sole use of the intended recipient(s). Any review or distribution
> >> by others is strictly prohibited. If you are not the intended
> >> recipient, please contact the sender and delete all copies.
> >>
> >>
> >> _______________________________________________
> >> Rust-vmm mailing list
> >> Rust-vmm at lists.opendev.org
> >> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> >>
> > _______________________________________________
> > Rust-vmm mailing list
> > Rust-vmm at lists.opendev.org
> > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> >
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



From fandree at amazon.com  Wed Jan 16 15:07:45 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Wed, 16 Jan 2019 15:07:45 +0000
Subject: [Rust-VMM] Rust VMM Crates
Message-ID: <1547651265854.95307@amazon.com>

Hey everyone,


I was thinking it would be nice to add one more crates to rust-vmm before my Fosdem presentation [1]. Another easy pick would be the virtio bindings, what do you say?


As the community is slowly growing, I think it would also be a good idea to have a process for creating repositories so we can get feedback before publishing them on crates.io. The proposal would be to first create a repository on a personal GitHub profile and open a new issue in the community repository [2] asking for review for the crate. Would that be okay? I can do that for the virtio-bindings crate.


Also, while thinking what crate should we add next, I realized that kvm_wrapper [3] was not the most inspired name of them all (enforcing that we should have some kind of review before publishing them). I also noticed that there are a lot of crates on crates.io that over FFI bindings and are named with the "-bindings" suffix. Because you cannot rename crates on crates.io, I was thinking about creating a new crate with the same content, name it kvm-bindings and mark the kvm_wrapper as an obsolete crate. We can keep the kvm_wrapper repository around and at some point re-purpose it to be a wrapper over KVM ioctls (similar to the kvm crate from crosvm/firecracker, but a bit more generic maybe?).


Feedback would be greatly appreciated!

Thanks,

Andreea


[1] https://fosdem.org/2019/schedule/event/vai_rust_vmm/

[2] https://github.com/rust-vmm/community

[3] https://github.com/rust-vmm/kvm_wrapper



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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190116/77cf37fe/attachment.html>

From liuj97 at gmail.com  Wed Jan 16 15:18:01 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Wed, 16 Jan 2019 23:18:01 +0800
Subject: [Rust-VMM] Rust VMM Crates
In-Reply-To: <1547651265854.95307@amazon.com>
References: <1547651265854.95307@amazon.com>
Message-ID: <A87E3EE7-B6A1-41C4-9BF9-43D87C4A1358@gmail.com>

Hi Andreea,
	Really appreciate to have a process to propose new project to rust-vmm:) One question about the relationship between firecracker and rust-vmm. Say I have some proposal to extend the memory_model crate in firecracker, what’s the preferred process for it?
Thanks,
Gerry

> On Jan 16, 2019, at 11:07 PM, Florescu, Andreea <fandree at amazon.com> wrote:
> 
> Hey everyone,
> 
> I was thinking it would be nice to add one more crates to rust-vmm before my Fosdem presentation [1]. Another easy pick would be the virtio bindings, what do you say?
> 
> As the community is slowly growing, I think it would also be a good idea to have a process for creating repositories so we can get feedback before publishing them on crates.io <http://crates.io/>. The proposal would be to first create a repository on a personal GitHub profile and open a new issue in the community repository [2] asking for review for the crate. Would that be okay? I can do that for the virtio-bindings crate.
> 
> Also, while thinking what crate should we add next, I realized that kvm_wrapper [3] was not the most inspired name of them all (enforcing that we should have some kind of review before publishing them). I also noticed that there are a lot of crates on crates.io <http://crates.io/> that over FFI bindings and are named with the "-bindings" suffix. Because you cannot rename crates on crates.io <http://crates.io/>, I was thinking about creating a new crate with the same content, name it kvm-bindings and mark the kvm_wrapper as an obsolete crate. We can keep the kvm_wrapper repository around and at some point re-purpose it to be a wrapper over KVM ioctls (similar to the kvm crate from crosvm/firecracker, but a bit more generic maybe?).  
> 
> Feedback would be greatly appreciated!
> 
> Thanks,
> Andreea
> 
> [1] https://fosdem.org/2019/schedule/event/vai_rust_vmm/ <https://fosdem.org/2019/schedule/event/vai_rust_vmm/>
> [2] https://github.com/rust-vmm/community <https://github.com/rust-vmm/community>
> [3] https://github.com/rust-vmm/kvm_wrapper <https://github.com/rust-vmm/kvm_wrapper>
> 
> 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 <mailto:Rust-vmm at lists.opendev.org>
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm <http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190116/1907dbb3/attachment-0001.html>

From samuel.ortiz at intel.com  Wed Jan 16 15:28:10 2019
From: samuel.ortiz at intel.com (Samuel Ortiz)
Date: Wed, 16 Jan 2019 16:28:10 +0100
Subject: [Rust-VMM] Rust VMM Crates
In-Reply-To: <1547651265854.95307@amazon.com>
References: <1547651265854.95307@amazon.com>
Message-ID: <20190116152810.GC6903@caravaggio>

Hi Andreea,

On Wed, Jan 16, 2019 at 03:07:45PM +0000, Florescu, Andreea wrote:
> Hey everyone,
> 
> 
> I was thinking it would be nice to add one more crates to rust-vmm before my Fosdem presentation [1]. Another easy pick would be the virtio bindings, what do you say?
> 
> 
> As the community is slowly growing, I think it would also be a good idea to have a process for creating repositories so we can get feedback before publishing them on crates.io. The proposal would be to first create a repository on a personal GitHub profile and open a new issue in the community repository [2] asking for review for the crate. Would that be okay? I can do that for the virtio-bindings crate.
>
That looks reasonable to me. I guess we will have to document that
process in the community repo.


> Also, while thinking what crate should we add next, I realized that kvm_wrapper [3] was not the most inspired name of them all (enforcing that we should have some kind of review before publishing them). I also noticed that there are a lot of crates on crates.io that over FFI bindings and are named with the "-bindings" suffix. Because you cannot rename crates on crates.io, I was thinking about creating a new crate with the same content, name it kvm-bindings and mark the kvm_wrapper as an obsolete crate. We can keep the kvm_wrapper repository around and at some point re-purpose it to be a wrapper over KVM ioctls (similar to the kvm crate from crosvm/firecracker, but a bit more generic maybe?).
>
I'm fine with renaming kvm_wrapper to kvm-bindings and use the -bindings
for FFI crates.

Thanks for the proposal.

Cheers,
Samuel.

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



From fandree at amazon.com  Wed Jan 16 15:28:39 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Wed, 16 Jan 2019 15:28:39 +0000
Subject: [Rust-VMM] Rust VMM Crates
In-Reply-To: <A87E3EE7-B6A1-41C4-9BF9-43D87C4A1358@gmail.com>
References: <1547651265854.95307@amazon.com>,
 <A87E3EE7-B6A1-41C4-9BF9-43D87C4A1358@gmail.com>
Message-ID: <1547652519112.52764@amazon.com>

Hey Gerry,


The memory_model crate (firecracker) and the data_model crate (crosvm) have slightly diverged. You can check out this gist as it has some details about them: https://gist.github.com/andreeaflorescu/ce4190b442dea2c48a0d783019579ad3


I think the best to do in this situation is to talk to both projects that currently use the crate (crosvm & firecracker) and find out if/how we can share it. My personal preference would be to have it first as a shared crate between the projects and then submit your changes as PR so both the teams can benefit from your changes.


How does that sound?


Andreea



________________________________
From: Jiang Liu <liuj97 at gmail.com>
Sent: Wednesday, January 16, 2019 5:18 PM
To: Florescu, Andreea
Cc: rust-vmm ML
Subject: Re: [Rust-VMM] Rust VMM Crates

Hi Andreea,
Really appreciate to have a process to propose new project to rust-vmm:) One question about the relationship between firecracker and rust-vmm. Say I have some proposal to extend the memory_model crate in firecracker, what's the preferred process for it?
Thanks,
Gerry

On Jan 16, 2019, at 11:07 PM, Florescu, Andreea <fandree at amazon.com<mailto:fandree at amazon.com>> wrote:

Hey everyone,

I was thinking it would be nice to add one more crates to rust-vmm before my Fosdem presentation [1]. Another easy pick would be the virtio bindings, what do you say?

As the community is slowly growing, I think it would also be a good idea to have a process for creating repositories so we can get feedback before publishing them on crates.io<http://crates.io/>. The proposal would be to first create a repository on a personal GitHub profile and open a new issue in the community repository [2] asking for review for the crate. Would that be okay? I can do that for the virtio-bindings crate.

Also, while thinking what crate should we add next, I realized that kvm_wrapper [3] was not the most inspired name of them all (enforcing that we should have some kind of review before publishing them). I also noticed that there are a lot of crates on crates.io<http://crates.io/> that over FFI bindings and are named with the "-bindings" suffix. Because you cannot rename crates on crates.io<http://crates.io/>, I was thinking about creating a new crate with the same content, name it kvm-bindings and mark the kvm_wrapper as an obsolete crate. We can keep the kvm_wrapper repository around and at some point re-purpose it to be a wrapper over KVM ioctls (similar to the kvm crate from crosvm/firecracker, but a bit more generic maybe?).

Feedback would be greatly appreciated!

Thanks,
Andreea

[1] https://fosdem.org/2019/schedule/event/vai_rust_vmm/
[2] https://github.com/rust-vmm/community
[3] https://github.com/rust-vmm/kvm_wrapper

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<mailto:Rust-vmm at lists.opendev.org>
http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm




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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190116/e4bba33a/attachment.html>

From liuj97 at gmail.com  Wed Jan 16 15:45:02 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Wed, 16 Jan 2019 23:45:02 +0800
Subject: [Rust-VMM] Rust VMM Crates
In-Reply-To: <1547652519112.52764@amazon.com>
References: <1547651265854.95307@amazon.com>
 <A87E3EE7-B6A1-41C4-9BF9-43D87C4A1358@gmail.com>
 <1547652519112.52764@amazon.com>
Message-ID: <C2C8FFE2-7BE4-43BB-AA4D-AF647D59290E@gmail.com>


> On Jan 16, 2019, at 11:28 PM, Florescu, Andreea <fandree at amazon.com> wrote:
> 
> Hey Gerry,
> 
> The memory_model crate (firecracker) and the data_model crate (crosvm) have slightly diverged. You can check out this gist as it has some details about them: https://gist.github.com/andreeaflorescu/ce4190b442dea2c48a0d783019579ad3 <https://gist.github.com/andreeaflorescu/ce4190b442dea2c48a0d783019579ad3>
> 
> I think the best to do in this situation is to talk to both projects that currently use the crate (crosvm & firecracker) and find out if/how we can share it. My personal preference would be to have it first as a shared crate between the projects and then submit your changes as PR so both the teams can benefit from your changes.
> 
> How does that sound?
Great, thanks!

> 
> Andreea
>  
> From: Jiang Liu <liuj97 at gmail.com>
> Sent: Wednesday, January 16, 2019 5:18 PM
> To: Florescu, Andreea
> Cc: rust-vmm ML
> Subject: Re: [Rust-VMM] Rust VMM Crates
>  
> Hi Andreea,
> Really appreciate to have a process to propose new project to rust-vmm:) One question about the relationship between firecracker and rust-vmm. Say I have some proposal to extend the memory_model crate in firecracker, what’s the preferred process for it?
> Thanks,
> Gerry
> 
>> On Jan 16, 2019, at 11:07 PM, Florescu, Andreea <fandree at amazon.com <mailto:fandree at amazon.com>> wrote:
>> 
>> Hey everyone,
>> 
>> I was thinking it would be nice to add one more crates to rust-vmm before my Fosdem presentation [1]. Another easy pick would be the virtio bindings, what do you say?
>> 
>> As the community is slowly growing, I think it would also be a good idea to have a process for creating repositories so we can get feedback before publishing them on crates.io <http://crates.io/>. The proposal would be to first create a repository on a personal GitHub profile and open a new issue in the community repository [2] asking for review for the crate. Would that be okay? I can do that for the virtio-bindings crate.
>> 
>> Also, while thinking what crate should we add next, I realized that kvm_wrapper [3] was not the most inspired name of them all (enforcing that we should have some kind of review before publishing them). I also noticed that there are a lot of crates on crates.io <http://crates.io/> that over FFI bindings and are named with the "-bindings" suffix. Because you cannot rename crates on crates.io <http://crates.io/>, I was thinking about creating a new crate with the same content, name it kvm-bindings and mark the kvm_wrapper as an obsolete crate. We can keep the kvm_wrapper repository around and at some point re-purpose it to be a wrapper over KVM ioctls (similar to the kvm crate from crosvm/firecracker, but a bit more generic maybe?).  
>> 
>> Feedback would be greatly appreciated!
>> 
>> Thanks,
>> Andreea
>> 
>> [1] https://fosdem.org/2019/schedule/event/vai_rust_vmm/ <https://fosdem.org/2019/schedule/event/vai_rust_vmm/>
>> [2] https://github.com/rust-vmm/community <https://github.com/rust-vmm/community>
>> [3] https://github.com/rust-vmm/kvm_wrapper <https://github.com/rust-vmm/kvm_wrapper>
>> 
>> 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 <mailto:Rust-vmm at lists.opendev.org>
>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm <http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm>
> 
> 
> 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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190116/a3139527/attachment-0001.html>

From stefanha at redhat.com  Thu Jan 17 10:52:19 2019
From: stefanha at redhat.com (Stefan Hajnoczi)
Date: Thu, 17 Jan 2019 10:52:19 +0000
Subject: [Rust-VMM] Crate for vhost-user device backend?
Message-ID: <20190117105219.GH27840@stefanha-x1.localdomain>

Hi,
Has anyone implemented a vhost-user device backend in Rust?

QEMU's libvhost-user and DPDK's librte_vhost are C implementations that
provide a device backend API.  They allow you to implement
vhost-user-net, vhost-user-blk, and vhost-user-scsi devices as a
separate process from the main emulator.

Stefan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: not available
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190117/4e2ff8df/attachment.sig>

From liuj97 at gmail.com  Thu Jan 17 10:55:41 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Thu, 17 Jan 2019 18:55:41 +0800
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <20190117105219.GH27840@stefanha-x1.localdomain>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
Message-ID: <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>

We are working on a vhostuser-rs crate, and planned to posted it for RFC later.

> On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <stefanha at redhat.com> wrote:
> 
> Hi,
> Has anyone implemented a vhost-user device backend in Rust?
> 
> QEMU's libvhost-user and DPDK's librte_vhost are C implementations that
> provide a device backend API.  They allow you to implement
> vhost-user-net, vhost-user-blk, and vhost-user-scsi devices as a
> separate process from the main emulator.
> 
> Stefan
> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm



From liuj97 at gmail.com  Thu Jan 17 10:58:22 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Thu, 17 Jan 2019 18:58:22 +0800
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <20190117105219.GH27840@stefanha-x1.localdomain>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
Message-ID: <BF23D9DE-0A0D-4073-96A9-065B236A5815@gmail.com>



> On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <stefanha at redhat.com> wrote:
> 
> Hi,
> Has anyone implemented a vhost-user device backend in Rust?
> 
> QEMU's libvhost-user and DPDK's librte_vhost are C implementations that
> provide a device backend API.  They allow you to implement
> vhost-user-net, vhost-user-blk, and vhost-user-scsi devices as a
> separate process from the main emulator.
> 
> Stefan
> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm



From marcandre.lureau at gmail.com  Thu Jan 17 10:58:30 2019
From: marcandre.lureau at gmail.com (=?UTF-8?B?TWFyYy1BbmRyw6kgTHVyZWF1?=)
Date: Thu, 17 Jan 2019 14:58:30 +0400
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
 <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
Message-ID: <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>

Hi

On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <liuj97 at gmail.com> wrote:
>
> We are working on a vhostuser-rs crate, and planned to posted it for RFC later.

Great news! Looking forward for it! Feel free to share WIP if you want help.

>
> > On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <stefanha at redhat.com> wrote:
> >
> > Hi,
> > Has anyone implemented a vhost-user device backend in Rust?
> >
> > QEMU's libvhost-user and DPDK's librte_vhost are C implementations that
> > provide a device backend API.  They allow you to implement
> > vhost-user-net, vhost-user-blk, and vhost-user-scsi devices as a
> > separate process from the main emulator.
> >
> > Stefan
> > _______________________________________________
> > Rust-vmm mailing list
> > Rust-vmm at lists.opendev.org
> > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>
>
> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm



-- 
Marc-André Lureau


From liuj97 at gmail.com  Thu Jan 17 11:02:22 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Thu, 17 Jan 2019 19:02:22 +0800
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
 <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
 <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
Message-ID: <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>



> On Jan 17, 2019, at 6:58 PM, Marc-André Lureau <marcandre.lureau at gmail.com> wrote:
> 
> Hi
> 
> On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <liuj97 at gmail.com <mailto:liuj97 at gmail.com>> wrote:
>> 
>> We are working on a vhostuser-rs crate, and planned to posted it for RFC later.
> 
> Great news! Looking forward for it! Feel free to share WIP if you want help.
> 
>> 
>>> On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <stefanha at redhat.com> wrote:
>>> 
>>> Hi,
>>> Has anyone implemented a vhost-user device backend in Rust?
>>> 
>>> QEMU's libvhost-user and DPDK's librte_vhost are C implementations that
>>> provide a device backend API.  They allow you to implement
>>> vhost-user-net, vhost-user-blk, and vhost-user-scsi devices as a
>>> separate process from the main emulator.
We are working on this direction, but  enhancements to firecracker/rust-vmm are need to support 
vhostuser. For example we need to support memfd based memory slot management. It’s really
great if we could cooperate on it.


>>> 
>>> Stefan
>>> _______________________________________________
>>> Rust-vmm mailing list
>>> Rust-vmm at lists.opendev.org
>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>> 
>> 
>> _______________________________________________
>> Rust-vmm mailing list
>> Rust-vmm at lists.opendev.org <mailto:Rust-vmm at lists.opendev.org>
>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm <http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm>
> 
> 
> 
> -- 
> Marc-André Lureau

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190117/b575e718/attachment-0001.html>

From dgilbert at redhat.com  Thu Jan 17 11:30:18 2019
From: dgilbert at redhat.com (Dr. David Alan Gilbert)
Date: Thu, 17 Jan 2019 11:30:18 +0000
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
 <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
 <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
 <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>
Message-ID: <20190117113018.GA2108@work-vm>

* Jiang Liu (liuj97 at gmail.com) wrote:
> 
> 
> > On Jan 17, 2019, at 6:58 PM, Marc-André Lureau <marcandre.lureau at gmail.com> wrote:
> > 
> > Hi
> > 
> > On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <liuj97 at gmail.com <mailto:liuj97 at gmail.com>> wrote:
> >> 
> >> We are working on a vhostuser-rs crate, and planned to posted it for RFC later.
> > 
> > Great news! Looking forward for it! Feel free to share WIP if you want help.
> > 
> >> 
> >>> On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <stefanha at redhat.com> wrote:
> >>> 
> >>> Hi,
> >>> Has anyone implemented a vhost-user device backend in Rust?
> >>> 
> >>> QEMU's libvhost-user and DPDK's librte_vhost are C implementations that
> >>> provide a device backend API.  They allow you to implement
> >>> vhost-user-net, vhost-user-blk, and vhost-user-scsi devices as a
> >>> separate process from the main emulator.
> We are working on this direction, but  enhancements to firecracker/rust-vmm are need to support 
> vhostuser. For example we need to support memfd based memory slot management. It’s really
> great if we could cooperate on it.

Are you working on it for the hypervisor side, or the device side, or
both?

Dave

> 
> >>> 
> >>> Stefan
> >>> _______________________________________________
> >>> Rust-vmm mailing list
> >>> Rust-vmm at lists.opendev.org
> >>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> >> 
> >> 
> >> _______________________________________________
> >> Rust-vmm mailing list
> >> Rust-vmm at lists.opendev.org <mailto:Rust-vmm at lists.opendev.org>
> >> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm <http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm>
> > 
> > 
> > 
> > -- 
> > Marc-André Lureau
> 

> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm

--
Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK


From liuj97 at gmail.com  Thu Jan 17 11:32:57 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Thu, 17 Jan 2019 19:32:57 +0800
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <20190117113018.GA2108@work-vm>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
 <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
 <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
 <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>
 <20190117113018.GA2108@work-vm>
Message-ID: <B9E088AD-F16C-46BB-97F9-C52A2C6D070E@gmail.com>



> On Jan 17, 2019, at 7:30 PM, Dr. David Alan Gilbert <dgilbert at redhat.com> wrote:
> 
> * Jiang Liu (liuj97 at gmail.com) wrote:
>> 
>> 
>>> On Jan 17, 2019, at 6:58 PM, Marc-André Lureau <marcandre.lureau at gmail.com> wrote:
>>> 
>>> Hi
>>> 
>>> On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <liuj97 at gmail.com <mailto:liuj97 at gmail.com>> wrote:
>>>> 
>>>> We are working on a vhostuser-rs crate, and planned to posted it for RFC later.
>>> 
>>> Great news! Looking forward for it! Feel free to share WIP if you want help.
>>> 
>>>> 
>>>>> On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <stefanha at redhat.com> wrote:
>>>>> 
>>>>> Hi,
>>>>> Has anyone implemented a vhost-user device backend in Rust?
>>>>> 
>>>>> QEMU's libvhost-user and DPDK's librte_vhost are C implementations that
>>>>> provide a device backend API.  They allow you to implement
>>>>> vhost-user-net, vhost-user-blk, and vhost-user-scsi devices as a
>>>>> separate process from the main emulator.
>> We are working on this direction, but  enhancements to firecracker/rust-vmm are need to support 
>> vhostuser. For example we need to support memfd based memory slot management. It’s really
>> great if we could cooperate on it.
> 
> Are you working on it for the hypervisor side, or the device side, or
> both?
Currently we are focusing on the hypervisor side and vhostuser transport layer. No work on the virtio backend device yet.

> 
> Dave
> 
>> 
>>>>> 
>>>>> Stefan
>>>>> _______________________________________________
>>>>> Rust-vmm mailing list
>>>>> Rust-vmm at lists.opendev.org
>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Rust-vmm mailing list
>>>> Rust-vmm at lists.opendev.org <mailto:Rust-vmm at lists.opendev.org>
>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm <http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm>
>>> 
>>> 
>>> 
>>> -- 
>>> Marc-André Lureau
>> 
> 
>> _______________________________________________
>> Rust-vmm mailing list
>> Rust-vmm at lists.opendev.org
>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> 
> --
> Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK



From jing2.liu at linux.intel.com  Thu Jan 17 15:00:27 2019
From: jing2.liu at linux.intel.com (Liu, Jing2)
Date: Thu, 17 Jan 2019 23:00:27 +0800
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <B9E088AD-F16C-46BB-97F9-C52A2C6D070E@gmail.com>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
 <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
 <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
 <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>
 <20190117113018.GA2108@work-vm>
 <B9E088AD-F16C-46BB-97F9-C52A2C6D070E@gmail.com>
Message-ID: <b5594c8b-438a-831e-d138-753c3cb97ee3@linux.intel.com>

Hi Jiang,

On 1/17/2019 7:32 PM, Jiang Liu wrote:
> 
> 
>> On Jan 17, 2019, at 7:30 PM, Dr. David Alan Gilbert <dgilbert at redhat.com> wrote:
>>
>> * Jiang Liu (liuj97 at gmail.com) wrote:
>>>
>>>
>>>> On Jan 17, 2019, at 6:58 PM, Marc-André Lureau <marcandre.lureau at gmail.com> wrote:
>>>>
>>>> Hi
>>>>
>>>> On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <liuj97 at gmail.com <mailto:liuj97 at gmail.com>> wrote:
>>>>>
>>>>> We are working on a vhostuser-rs crate, and planned to posted it for RFC later.
>>>>
>>>> Great news! Looking forward for it! Feel free to share WIP if you want help.
>>>>
>>>>>
>>>>>> On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <stefanha at redhat.com> wrote:
>>>>>>
>>>>>> Hi,
>>>>>> Has anyone implemented a vhost-user device backend in Rust?
>>>>>>
>>>>>> QEMU's libvhost-user and DPDK's librte_vhost are C implementations that
>>>>>> provide a device backend API.  They allow you to implement
>>>>>> vhost-user-net, vhost-user-blk, and vhost-user-scsi devices as a
>>>>>> separate process from the main emulator.
>>> We are working on this direction, but  enhancements to firecracker/rust-vmm are need to support
>>> vhostuser. For example we need to support memfd based memory slot management. It’s really
>>> great if we could cooperate on it.
>>
>> Are you working on it for the hypervisor side, or the device side, or
>> both?
> Currently we are focusing on the hypervisor side and vhostuser transport layer. No work on the virtio backend device yet.

What application will be the virtio backend on your scenario?

Jing

> 
>>
>> Dave
>>
>>>
>>>>>>
>>>>>> Stefan
>>>>>> _______________________________________________
>>>>>> Rust-vmm mailing list
>>>>>> Rust-vmm at lists.opendev.org
>>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Rust-vmm mailing list
>>>>> Rust-vmm at lists.opendev.org <mailto:Rust-vmm at lists.opendev.org>
>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm <http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm>
>>>>
>>>>
>>>>
>>>> -- 
>>>> Marc-André Lureau
>>>
>>
>>> _______________________________________________
>>> Rust-vmm mailing list
>>> Rust-vmm at lists.opendev.org
>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>
>> --
>> Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK
> 
> 
> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> 


From liuj97 at gmail.com  Thu Jan 17 15:02:46 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Thu, 17 Jan 2019 23:02:46 +0800
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <b5594c8b-438a-831e-d138-753c3cb97ee3@linux.intel.com>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
 <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
 <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
 <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>
 <20190117113018.GA2108@work-vm>
 <B9E088AD-F16C-46BB-97F9-C52A2C6D070E@gmail.com>
 <b5594c8b-438a-831e-d138-753c3cb97ee3@linux.intel.com>
Message-ID: <1C88C7F7-1A8E-4297-9DC9-049392F9A5DD@gmail.com>



> On Jan 17, 2019, at 11:00 PM, Liu, Jing2 <jing2.liu at linux.intel.com> wrote:
> 
> Hi Jiang,
> 
> On 1/17/2019 7:32 PM, Jiang Liu wrote:
>>> On Jan 17, 2019, at 7:30 PM, Dr. David Alan Gilbert <dgilbert at redhat.com> wrote:
>>> 
>>> * Jiang Liu (liuj97 at gmail.com) wrote:
>>>> 
>>>> 
>>>>> On Jan 17, 2019, at 6:58 PM, Marc-André Lureau <marcandre.lureau at gmail.com> wrote:
>>>>> 
>>>>> Hi
>>>>> 
>>>>> On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <liuj97 at gmail.com <mailto:liuj97 at gmail.com>> wrote:
>>>>>> 
>>>>>> We are working on a vhostuser-rs crate, and planned to posted it for RFC later.
>>>>> 
>>>>> Great news! Looking forward for it! Feel free to share WIP if you want help.
>>>>> 
>>>>>> 
>>>>>>> On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <stefanha at redhat.com> wrote:
>>>>>>> 
>>>>>>> Hi,
>>>>>>> Has anyone implemented a vhost-user device backend in Rust?
>>>>>>> 
>>>>>>> QEMU's libvhost-user and DPDK's librte_vhost are C implementations that
>>>>>>> provide a device backend API.  They allow you to implement
>>>>>>> vhost-user-net, vhost-user-blk, and vhost-user-scsi devices as a
>>>>>>> separate process from the main emulator.
>>>> We are working on this direction, but  enhancements to firecracker/rust-vmm are need to support
>>>> vhostuser. For example we need to support memfd based memory slot management. It’s really
>>>> great if we could cooperate on it.
>>> 
>>> Are you working on it for the hypervisor side, or the device side, or
>>> both?
>> Currently we are focusing on the hypervisor side and vhostuser transport layer. No work on the virtio backend device yet.
> 
> What application will be the virtio backend on your scenario?
> 

Hi Jing,
	Net and blk/scsi backends should be enough for most cases.


> Jing
> 
>>> 
>>> Dave
>>> 
>>>> 
>>>>>>> 
>>>>>>> Stefan
>>>>>>> _______________________________________________
>>>>>>> Rust-vmm mailing list
>>>>>>> Rust-vmm at lists.opendev.org
>>>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Rust-vmm mailing list
>>>>>> Rust-vmm at lists.opendev.org <mailto:Rust-vmm at lists.opendev.org>
>>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm <http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm>
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> Marc-André Lureau
>>>> 
>>> 
>>>> _______________________________________________
>>>> Rust-vmm mailing list
>>>> Rust-vmm at lists.opendev.org
>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>> 
>>> --
>>> Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK
>> _______________________________________________
>> Rust-vmm mailing list
>> Rust-vmm at lists.opendev.org
>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm



From dgilbert at redhat.com  Thu Jan 17 16:59:59 2019
From: dgilbert at redhat.com (Dr. David Alan Gilbert)
Date: Thu, 17 Jan 2019 16:59:59 +0000
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <1C88C7F7-1A8E-4297-9DC9-049392F9A5DD@gmail.com>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
 <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
 <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
 <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>
 <20190117113018.GA2108@work-vm>
 <B9E088AD-F16C-46BB-97F9-C52A2C6D070E@gmail.com>
 <b5594c8b-438a-831e-d138-753c3cb97ee3@linux.intel.com>
 <1C88C7F7-1A8E-4297-9DC9-049392F9A5DD@gmail.com>
Message-ID: <20190117165959.GC2108@work-vm>

* Jiang Liu (liuj97 at gmail.com) wrote:
> 
> 
> > On Jan 17, 2019, at 11:00 PM, Liu, Jing2 <jing2.liu at linux.intel.com> wrote:
> > 
> > Hi Jiang,
> > 
> > On 1/17/2019 7:32 PM, Jiang Liu wrote:
> >>> On Jan 17, 2019, at 7:30 PM, Dr. David Alan Gilbert <dgilbert at redhat.com> wrote:
> >>> 
> >>> * Jiang Liu (liuj97 at gmail.com) wrote:
> >>>> 
> >>>> 
> >>>>> On Jan 17, 2019, at 6:58 PM, Marc-André Lureau <marcandre.lureau at gmail.com> wrote:
> >>>>> 
> >>>>> Hi
> >>>>> 
> >>>>> On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <liuj97 at gmail.com <mailto:liuj97 at gmail.com>> wrote:
> >>>>>> 
> >>>>>> We are working on a vhostuser-rs crate, and planned to posted it for RFC later.
> >>>>> 
> >>>>> Great news! Looking forward for it! Feel free to share WIP if you want help.
> >>>>> 
> >>>>>> 
> >>>>>>> On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <stefanha at redhat.com> wrote:
> >>>>>>> 
> >>>>>>> Hi,
> >>>>>>> Has anyone implemented a vhost-user device backend in Rust?
> >>>>>>> 
> >>>>>>> QEMU's libvhost-user and DPDK's librte_vhost are C implementations that
> >>>>>>> provide a device backend API.  They allow you to implement
> >>>>>>> vhost-user-net, vhost-user-blk, and vhost-user-scsi devices as a
> >>>>>>> separate process from the main emulator.
> >>>> We are working on this direction, but  enhancements to firecracker/rust-vmm are need to support
> >>>> vhostuser. For example we need to support memfd based memory slot management. It’s really
> >>>> great if we could cooperate on it.
> >>> 
> >>> Are you working on it for the hypervisor side, or the device side, or
> >>> both?
> >> Currently we are focusing on the hypervisor side and vhostuser transport layer. No work on the virtio backend device yet.
> > 
> > What application will be the virtio backend on your scenario?
> > 
> 
> Hi Jing,
> 	Net and blk/scsi backends should be enough for most cases.

It would be interesting for us to be able to wire virtio-fs to
firecracker, and it would also be interesting to do a Rust filesystem
client.

Dave

> 
> > Jing
> > 
> >>> 
> >>> Dave
> >>> 
> >>>> 
> >>>>>>> 
> >>>>>>> Stefan
> >>>>>>> _______________________________________________
> >>>>>>> Rust-vmm mailing list
> >>>>>>> Rust-vmm at lists.opendev.org
> >>>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> >>>>>> 
> >>>>>> 
> >>>>>> _______________________________________________
> >>>>>> Rust-vmm mailing list
> >>>>>> Rust-vmm at lists.opendev.org <mailto:Rust-vmm at lists.opendev.org>
> >>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm <http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm>
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> -- 
> >>>>> Marc-André Lureau
> >>>> 
> >>> 
> >>>> _______________________________________________
> >>>> Rust-vmm mailing list
> >>>> Rust-vmm at lists.opendev.org
> >>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> >>> 
> >>> --
> >>> Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK
> >> _______________________________________________
> >> Rust-vmm mailing list
> >> Rust-vmm at lists.opendev.org
> >> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> 
--
Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK


From sebastien.boeuf at intel.com  Thu Jan 17 17:07:02 2019
From: sebastien.boeuf at intel.com (Boeuf, Sebastien)
Date: Thu, 17 Jan 2019 17:07:02 +0000
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <20190117165959.GC2108@work-vm>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
 <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
 <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
 <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>
 <20190117113018.GA2108@work-vm>
 <B9E088AD-F16C-46BB-97F9-C52A2C6D070E@gmail.com>
 <b5594c8b-438a-831e-d138-753c3cb97ee3@linux.intel.com>
 <1C88C7F7-1A8E-4297-9DC9-049392F9A5DD@gmail.com>
 <20190117165959.GC2108@work-vm>
Message-ID: <dc9329bde44f0300f1be79c7d1a8acf649738b59.camel@intel.com>

On Thu, 2019-01-17 at 16:59 +0000, Dr. David Alan Gilbert wrote:
> * Jiang Liu (liuj97 at gmail.com) wrote:
> > 
> > 
> > > On Jan 17, 2019, at 11:00 PM, Liu, Jing2 <
> > > jing2.liu at linux.intel.com> wrote:
> > > 
> > > Hi Jiang,
> > > 
> > > On 1/17/2019 7:32 PM, Jiang Liu wrote:
> > > > > On Jan 17, 2019, at 7:30 PM, Dr. David Alan Gilbert <
> > > > > dgilbert at redhat.com> wrote:
> > > > > 
> > > > > * Jiang Liu (liuj97 at gmail.com) wrote:
> > > > > > 
> > > > > > 
> > > > > > > On Jan 17, 2019, at 6:58 PM, Marc-André Lureau <
> > > > > > > marcandre.lureau at gmail.com> wrote:
> > > > > > > 
> > > > > > > Hi
> > > > > > > 
> > > > > > > On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <
> > > > > > > liuj97 at gmail.com <mailto:liuj97 at gmail.com>> wrote:
> > > > > > > > 
> > > > > > > > We are working on a vhostuser-rs crate, and planned to
> > > > > > > > posted it for RFC later.
> > > > > > > 
> > > > > > > Great news! Looking forward for it! Feel free to share
> > > > > > > WIP if you want help.
> > > > > > > 
> > > > > > > > 
> > > > > > > > > On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <
> > > > > > > > > stefanha at redhat.com> wrote:
> > > > > > > > > 
> > > > > > > > > Hi,
> > > > > > > > > Has anyone implemented a vhost-user device backend in
> > > > > > > > > Rust?
> > > > > > > > > 
> > > > > > > > > QEMU's libvhost-user and DPDK's librte_vhost are C
> > > > > > > > > implementations that
> > > > > > > > > provide a device backend API.  They allow you to
> > > > > > > > > implement
> > > > > > > > > vhost-user-net, vhost-user-blk, and vhost-user-scsi
> > > > > > > > > devices as a
> > > > > > > > > separate process from the main emulator.
> > > > > > 
> > > > > > We are working on this direction, but  enhancements to
> > > > > > firecracker/rust-vmm are need to support
> > > > > > vhostuser. For example we need to support memfd based
> > > > > > memory slot management. It’s really
> > > > > > great if we could cooperate on it.
> > > > > 
> > > > > Are you working on it for the hypervisor side, or the device
> > > > > side, or
> > > > > both?
> > > > 
> > > > Currently we are focusing on the hypervisor side and vhostuser
> > > > transport layer. No work on the virtio backend device yet.
> > > 
> > > What application will be the virtio backend on your scenario?
> > > 
> > 
> > Hi Jing,
> > 	Net and blk/scsi backends should be enough for most cases.
> 
> It would be interesting for us to be able to wire virtio-fs to
> firecracker, and it would also be interesting to do a Rust filesystem
> client.

+1 here! Something that would be very useful to build a rust-vmm
hypervisor with filesystem sharing support (and that is not 9p
obviously).

> 
> Dave
> 
> > 
> > > Jing
> > > 
> > > > > 
> > > > > Dave
> > > > > 
> > > > > > 
> > > > > > > > > 
> > > > > > > > > Stefan
> > > > > > > > > _______________________________________________
> > > > > > > > > Rust-vmm mailing list
> > > > > > > > > Rust-vmm at lists.opendev.org
> > > > > > > > > 
http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> > > > > > > > 
> > > > > > > > 
> > > > > > > > _______________________________________________
> > > > > > > > Rust-vmm mailing list
> > > > > > > > Rust-vmm at lists.opendev.org <mailto:
> > > > > > > > Rust-vmm at lists.opendev.org>
> > > > > > > > 
http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> > > > > > > >  <
> > > > > > > > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> > > > > > > > >
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > -- 
> > > > > > > Marc-André Lureau
> > > > > > _______________________________________________
> > > > > > Rust-vmm mailing list
> > > > > > Rust-vmm at lists.opendev.org
> > > > > > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> > > > > 
> > > > > --
> > > > > Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK
> > > > 
> > > > _______________________________________________
> > > > Rust-vmm mailing list
> > > > Rust-vmm at lists.opendev.org
> > > > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> 
> --
> Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK
> 
> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm

From maccarro at google.com  Thu Jan 17 18:07:40 2019
From: maccarro at google.com (Cory Maccarrone)
Date: Thu, 17 Jan 2019 10:07:40 -0800
Subject: [Rust-VMM] Summer of Code / Outreachy projects
In-Reply-To: <814bbcd6-524a-f3ec-6961-35babead8f98@redhat.com>
References: <814bbcd6-524a-f3ec-6961-35babead8f98@redhat.com>
Message-ID: <CAJ-JdHAc=xjsp4SWfq6SBL8U2W2fAS5BHTE0D1B=P-2aOmcNow@mail.gmail.com>

One suggestion I might make would be a rust-implemented instruction
emulator for cracking open MMIOs.  Seems useful for VMMs in general to me.

- Cory

On Wed, Jan 9, 2019 at 10:07 AM Paolo Bonzini <pbonzini at redhat.com> wrote:

> QEMU would be glad to host projects related to VMMs in Rust as part of
> Google summer of Code and Outreachy.  This includes all of Firecracker,
> CrosVM and common infrastructure that could be reused by multiple
> virtual machine monitors; with my QEMU hat, I would obviously favor the
> latter :)).
>
> An idea could be to migrate Firecracker and CrosVM to the Fuchsia crates
> that were mentioned early here on the mailing list, and/or implement a
> sample vhost-user client using whatever standard set of crates are
> established.  Another possibility is PCI and virtio-pci in Firecracker.
>
> Thanks,
>
> Paolo
>
> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>


-- 
Cory Maccarrone | Staff Software Engineer | maccarro at google.com | Google
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190117/6fc76a3f/attachment.html>

From pbonzini at redhat.com  Thu Jan 17 18:21:03 2019
From: pbonzini at redhat.com (Paolo Bonzini)
Date: Thu, 17 Jan 2019 19:21:03 +0100
Subject: [Rust-VMM] Summer of Code / Outreachy projects
In-Reply-To: <CAJ-JdHAc=xjsp4SWfq6SBL8U2W2fAS5BHTE0D1B=P-2aOmcNow@mail.gmail.com>
References: <814bbcd6-524a-f3ec-6961-35babead8f98@redhat.com>
 <CAJ-JdHAc=xjsp4SWfq6SBL8U2W2fAS5BHTE0D1B=P-2aOmcNow@mail.gmail.com>
Message-ID: <c9bf7adf-0ac0-c28a-629a-fa2f3878e181@redhat.com>

On 17/01/19 19:07, Cory Maccarrone wrote:
> One suggestion I might make would be a rust-implemented instruction
> emulator for cracking open MMIOs.  Seems useful for VMMs in general to me.

That's part of the plans indeed, but the support for userspace MMIO
emulation is not in upstream KVM yet.

Paolo

> On Wed, Jan 9, 2019 at 10:07 AM Paolo Bonzini <pbonzini at redhat.com
> <mailto:pbonzini at redhat.com>> wrote:
> 
>     QEMU would be glad to host projects related to VMMs in Rust as part of
>     Google summer of Code and Outreachy.  This includes all of Firecracker,
>     CrosVM and common infrastructure that could be reused by multiple
>     virtual machine monitors; with my QEMU hat, I would obviously favor the
>     latter :)).
> 
>     An idea could be to migrate Firecracker and CrosVM to the Fuchsia crates
>     that were mentioned early here on the mailing list, and/or implement a
>     sample vhost-user client using whatever standard set of crates are
>     established.  Another possibility is PCI and virtio-pci in Firecracker.
> 
>     Thanks,
> 
>     Paolo
> 
>     _______________________________________________
>     Rust-vmm mailing list
>     Rust-vmm at lists.opendev.org <mailto:Rust-vmm at lists.opendev.org>
>     http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> 
> 
> 
> -- 
> Cory Maccarrone | Staff Software Engineer | maccarro at google.com
> <mailto:maccarro at google.com> | Google
> 



From aliguori at amazon.com  Thu Jan 17 18:40:30 2019
From: aliguori at amazon.com (Anthony Liguori)
Date: Thu, 17 Jan 2019 10:40:30 -0800
Subject: [Rust-VMM] Summer of Code / Outreachy projects
In-Reply-To: <c9bf7adf-0ac0-c28a-629a-fa2f3878e181@redhat.com>
References: <814bbcd6-524a-f3ec-6961-35babead8f98@redhat.com>
 <CAJ-JdHAc=xjsp4SWfq6SBL8U2W2fAS5BHTE0D1B=P-2aOmcNow@mail.gmail.com>
 <c9bf7adf-0ac0-c28a-629a-fa2f3878e181@redhat.com>
Message-ID: <cig332imyngmap.fsf@u54e1add816995a33037d.ant.amazon.com>

Paolo Bonzini <pbonzini at redhat.com> writes:

> On 17/01/19 19:07, Cory Maccarrone wrote:
>> One suggestion I might make would be a rust-implemented instruction
>> emulator for cracking open MMIOs.  Seems useful for VMMs in general to me.
>
> That's part of the plans indeed, but the support for userspace MMIO
> emulation is not in upstream KVM yet.

We you thinking a straight port of emulate.c to Rust or something from
scratch?

I think a port is interesting as an intern project.  I think a new
emulator from scratch is a bit unrealistic as an intern project.

Regards,

Anthony Liguori

>
> Paolo
>
>> On Wed, Jan 9, 2019 at 10:07 AM Paolo Bonzini <pbonzini at redhat.com
>> <mailto:pbonzini at redhat.com>> wrote:
>> 
>>     QEMU would be glad to host projects related to VMMs in Rust as part of
>>     Google summer of Code and Outreachy.  This includes all of Firecracker,
>>     CrosVM and common infrastructure that could be reused by multiple
>>     virtual machine monitors; with my QEMU hat, I would obviously favor the
>>     latter :)).
>> 
>>     An idea could be to migrate Firecracker and CrosVM to the Fuchsia crates
>>     that were mentioned early here on the mailing list, and/or implement a
>>     sample vhost-user client using whatever standard set of crates are
>>     established.  Another possibility is PCI and virtio-pci in Firecracker.
>> 
>>     Thanks,
>> 
>>     Paolo
>> 
>>     _______________________________________________
>>     Rust-vmm mailing list
>>     Rust-vmm at lists.opendev.org <mailto:Rust-vmm at lists.opendev.org>
>>     http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>> 
>> 
>> 
>> -- 
>> Cory Maccarrone | Staff Software Engineer | maccarro at google.com
>> <mailto:maccarro at google.com> | Google
>> 
>
>
> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm


From maccarro at google.com  Thu Jan 17 19:48:39 2019
From: maccarro at google.com (Cory Maccarrone)
Date: Thu, 17 Jan 2019 11:48:39 -0800
Subject: [Rust-VMM] Summer of Code / Outreachy projects
In-Reply-To: <cig332imyngmap.fsf@u54e1add816995a33037d.ant.amazon.com>
References: <814bbcd6-524a-f3ec-6961-35babead8f98@redhat.com>
 <CAJ-JdHAc=xjsp4SWfq6SBL8U2W2fAS5BHTE0D1B=P-2aOmcNow@mail.gmail.com>
 <c9bf7adf-0ac0-c28a-629a-fa2f3878e181@redhat.com>
 <cig332imyngmap.fsf@u54e1add816995a33037d.ant.amazon.com>
Message-ID: <CAJ-JdHDBTT6Rr745hMOtezpgxSaO0JR8i0biCzERM2cJPVAC4Q@mail.gmail.com>

A port seems like a much more tractable project than a rewrite for sure.
The KVM instruction emulator is more or less proven and works, so reason
not to port it I think.  Agreed on the intern project, it would be great
for that.

- Cory

On Thu, Jan 17, 2019 at 10:40 AM Anthony Liguori <aliguori at amazon.com>
wrote:

> Paolo Bonzini <pbonzini at redhat.com> writes:
>
> > On 17/01/19 19:07, Cory Maccarrone wrote:
> >> One suggestion I might make would be a rust-implemented instruction
> >> emulator for cracking open MMIOs.  Seems useful for VMMs in general to
> me.
> >
> > That's part of the plans indeed, but the support for userspace MMIO
> > emulation is not in upstream KVM yet.
>
> We you thinking a straight port of emulate.c to Rust or something from
> scratch?
>
> I think a port is interesting as an intern project.  I think a new
> emulator from scratch is a bit unrealistic as an intern project.
>
> Regards,
>
> Anthony Liguori
>
> >
> > Paolo
> >
> >> On Wed, Jan 9, 2019 at 10:07 AM Paolo Bonzini <pbonzini at redhat.com
> >> <mailto:pbonzini at redhat.com>> wrote:
> >>
> >>     QEMU would be glad to host projects related to VMMs in Rust as part
> of
> >>     Google summer of Code and Outreachy.  This includes all of
> Firecracker,
> >>     CrosVM and common infrastructure that could be reused by multiple
> >>     virtual machine monitors; with my QEMU hat, I would obviously favor
> the
> >>     latter :)).
> >>
> >>     An idea could be to migrate Firecracker and CrosVM to the Fuchsia
> crates
> >>     that were mentioned early here on the mailing list, and/or
> implement a
> >>     sample vhost-user client using whatever standard set of crates are
> >>     established.  Another possibility is PCI and virtio-pci in
> Firecracker.
> >>
> >>     Thanks,
> >>
> >>     Paolo
> >>
> >>     _______________________________________________
> >>     Rust-vmm mailing list
> >>     Rust-vmm at lists.opendev.org <mailto:Rust-vmm at lists.opendev.org>
> >>     http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> >>
> >>
> >>
> >> --
> >> Cory Maccarrone | Staff Software Engineer | maccarro at google.com
> >> <mailto:maccarro at google.com> | Google
> >>
> >
> >
> > _______________________________________________
> > Rust-vmm mailing list
> > Rust-vmm at lists.opendev.org
> > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>


-- 
Cory Maccarrone | Staff Software Engineer | maccarro at google.com | Google
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190117/001f7f0a/attachment-0001.html>

From jing2.liu at linux.intel.com  Fri Jan 18 01:47:42 2019
From: jing2.liu at linux.intel.com (Liu, Jing2)
Date: Fri, 18 Jan 2019 09:47:42 +0800
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <dc9329bde44f0300f1be79c7d1a8acf649738b59.camel@intel.com>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
 <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
 <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
 <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>
 <20190117113018.GA2108@work-vm>
 <B9E088AD-F16C-46BB-97F9-C52A2C6D070E@gmail.com>
 <b5594c8b-438a-831e-d138-753c3cb97ee3@linux.intel.com>
 <1C88C7F7-1A8E-4297-9DC9-049392F9A5DD@gmail.com>
 <20190117165959.GC2108@work-vm>
 <dc9329bde44f0300f1be79c7d1a8acf649738b59.camel@intel.com>
Message-ID: <bdff3a96-84e9-ac20-0fc6-eb52d2371a0f@linux.intel.com>



On 1/18/2019 1:07 AM, Boeuf, Sebastien wrote:
> On Thu, 2019-01-17 at 16:59 +0000, Dr. David Alan Gilbert wrote:
>> * Jiang Liu (liuj97 at gmail.com) wrote:
>>>
>>>
>>>> On Jan 17, 2019, at 11:00 PM, Liu, Jing2 <
>>>> jing2.liu at linux.intel.com> wrote:
>>>>
>>>> Hi Jiang,
>>>>
>>>> On 1/17/2019 7:32 PM, Jiang Liu wrote:
>>>>>> On Jan 17, 2019, at 7:30 PM, Dr. David Alan Gilbert <
>>>>>> dgilbert at redhat.com> wrote:
>>>>>>
>>>>>> * Jiang Liu (liuj97 at gmail.com) wrote:
>>>>>>>
>>>>>>>
>>>>>>>> On Jan 17, 2019, at 6:58 PM, Marc-André Lureau <
>>>>>>>> marcandre.lureau at gmail.com> wrote:
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <
>>>>>>>> liuj97 at gmail.com <mailto:liuj97 at gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> We are working on a vhostuser-rs crate, and planned to
>>>>>>>>> posted it for RFC later.
>>>>>>>>
>>>>>>>> Great news! Looking forward for it! Feel free to share
>>>>>>>> WIP if you want help.
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <
>>>>>>>>>> stefanha at redhat.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>> Has anyone implemented a vhost-user device backend in
>>>>>>>>>> Rust?
>>>>>>>>>>
>>>>>>>>>> QEMU's libvhost-user and DPDK's librte_vhost are C
>>>>>>>>>> implementations that
>>>>>>>>>> provide a device backend API.  They allow you to
>>>>>>>>>> implement
>>>>>>>>>> vhost-user-net, vhost-user-blk, and vhost-user-scsi
>>>>>>>>>> devices as a
>>>>>>>>>> separate process from the main emulator.
>>>>>>>
>>>>>>> We are working on this direction, but  enhancements to
>>>>>>> firecracker/rust-vmm are need to support
>>>>>>> vhostuser. For example we need to support memfd based
>>>>>>> memory slot management. It’s really
>>>>>>> great if we could cooperate on it.
>>>>>>
>>>>>> Are you working on it for the hypervisor side, or the device
>>>>>> side, or
>>>>>> both?
>>>>>
>>>>> Currently we are focusing on the hypervisor side and vhostuser
>>>>> transport layer. No work on the virtio backend device yet.
>>>>
>>>> What application will be the virtio backend on your scenario?
>>>>
>>>
>>> Hi Jing,
>>> 	Net and blk/scsi backends should be enough for most cases.
>>
>> It would be interesting for us to be able to wire virtio-fs to
>> firecracker, and it would also be interesting to do a Rust filesystem
>> client.
> 
> +1 here! Something that would be very useful to build a rust-vmm
> hypervisor with filesystem sharing support (and that is not 9p
> obviously).
++ too! I seems all the vhost-user device emulation, backend emulation 
and socket channel needs to be implemented. Not a small job I think :-p

Jing

> 
>>
>> Dave
>>
>>>
>>>> Jing
>>>>
>>>>>>
>>>>>> Dave
>>>>>>
>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Stefan
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Rust-vmm mailing list
>>>>>>>>>> Rust-vmm at lists.opendev.org
>>>>>>>>>>
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Rust-vmm mailing list
>>>>>>>>> Rust-vmm at lists.opendev.org <mailto:
>>>>>>>>> Rust-vmm at lists.opendev.org>
>>>>>>>>>
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>>>>>>>   <
>>>>>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -- 
>>>>>>>> Marc-André Lureau
>>>>>>> _______________________________________________
>>>>>>> Rust-vmm mailing list
>>>>>>> Rust-vmm at lists.opendev.org
>>>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>>>>
>>>>>> --
>>>>>> Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK
>>>>>
>>>>> _______________________________________________
>>>>> Rust-vmm mailing list
>>>>> Rust-vmm at lists.opendev.org
>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>
>> --
>> Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK
>>
>> _______________________________________________
>> Rust-vmm mailing list
>> Rust-vmm at lists.opendev.org
>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> 


From dgilbert at redhat.com  Fri Jan 18 09:09:51 2019
From: dgilbert at redhat.com (Dr. David Alan Gilbert)
Date: Fri, 18 Jan 2019 09:09:51 +0000
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <bdff3a96-84e9-ac20-0fc6-eb52d2371a0f@linux.intel.com>
References: <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
 <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
 <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>
 <20190117113018.GA2108@work-vm>
 <B9E088AD-F16C-46BB-97F9-C52A2C6D070E@gmail.com>
 <b5594c8b-438a-831e-d138-753c3cb97ee3@linux.intel.com>
 <1C88C7F7-1A8E-4297-9DC9-049392F9A5DD@gmail.com>
 <20190117165959.GC2108@work-vm>
 <dc9329bde44f0300f1be79c7d1a8acf649738b59.camel@intel.com>
 <bdff3a96-84e9-ac20-0fc6-eb52d2371a0f@linux.intel.com>
Message-ID: <20190118090951.GA2146@work-vm>

* Liu, Jing2 (jing2.liu at linux.intel.com) wrote:
> 
> 
> On 1/18/2019 1:07 AM, Boeuf, Sebastien wrote:
> > On Thu, 2019-01-17 at 16:59 +0000, Dr. David Alan Gilbert wrote:
> > > * Jiang Liu (liuj97 at gmail.com) wrote:
> > > > 
> > > > 
> > > > > On Jan 17, 2019, at 11:00 PM, Liu, Jing2 <
> > > > > jing2.liu at linux.intel.com> wrote:
> > > > > 
> > > > > Hi Jiang,
> > > > > 
> > > > > On 1/17/2019 7:32 PM, Jiang Liu wrote:
> > > > > > > On Jan 17, 2019, at 7:30 PM, Dr. David Alan Gilbert <
> > > > > > > dgilbert at redhat.com> wrote:
> > > > > > > 
> > > > > > > * Jiang Liu (liuj97 at gmail.com) wrote:
> > > > > > > > 
> > > > > > > > 
> > > > > > > > > On Jan 17, 2019, at 6:58 PM, Marc-André Lureau <
> > > > > > > > > marcandre.lureau at gmail.com> wrote:
> > > > > > > > > 
> > > > > > > > > Hi
> > > > > > > > > 
> > > > > > > > > On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <
> > > > > > > > > liuj97 at gmail.com <mailto:liuj97 at gmail.com>> wrote:
> > > > > > > > > > 
> > > > > > > > > > We are working on a vhostuser-rs crate, and planned to
> > > > > > > > > > posted it for RFC later.
> > > > > > > > > 
> > > > > > > > > Great news! Looking forward for it! Feel free to share
> > > > > > > > > WIP if you want help.
> > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > > On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <
> > > > > > > > > > > stefanha at redhat.com> wrote:
> > > > > > > > > > > 
> > > > > > > > > > > Hi,
> > > > > > > > > > > Has anyone implemented a vhost-user device backend in
> > > > > > > > > > > Rust?
> > > > > > > > > > > 
> > > > > > > > > > > QEMU's libvhost-user and DPDK's librte_vhost are C
> > > > > > > > > > > implementations that
> > > > > > > > > > > provide a device backend API.  They allow you to
> > > > > > > > > > > implement
> > > > > > > > > > > vhost-user-net, vhost-user-blk, and vhost-user-scsi
> > > > > > > > > > > devices as a
> > > > > > > > > > > separate process from the main emulator.
> > > > > > > > 
> > > > > > > > We are working on this direction, but  enhancements to
> > > > > > > > firecracker/rust-vmm are need to support
> > > > > > > > vhostuser. For example we need to support memfd based
> > > > > > > > memory slot management. It’s really
> > > > > > > > great if we could cooperate on it.
> > > > > > > 
> > > > > > > Are you working on it for the hypervisor side, or the device
> > > > > > > side, or
> > > > > > > both?
> > > > > > 
> > > > > > Currently we are focusing on the hypervisor side and vhostuser
> > > > > > transport layer. No work on the virtio backend device yet.
> > > > > 
> > > > > What application will be the virtio backend on your scenario?
> > > > > 
> > > > 
> > > > Hi Jing,
> > > > 	Net and blk/scsi backends should be enough for most cases.
> > > 
> > > It would be interesting for us to be able to wire virtio-fs to
> > > firecracker, and it would also be interesting to do a Rust filesystem
> > > client.
> > 
> > +1 here! Something that would be very useful to build a rust-vmm
> > hypervisor with filesystem sharing support (and that is not 9p
> > obviously).
> ++ too! I seems all the vhost-user device emulation, backend emulation and
> socket channel needs to be implemented. Not a small job I think :-p

It seems like the first step would be to produce a crate with just the
protocol definitions in for vhost-user - has anyone already done that?

Dave

> Jing
> 
> > 
> > > 
> > > Dave
> > > 
> > > > 
> > > > > Jing
> > > > > 
> > > > > > > 
> > > > > > > Dave
> > > > > > > 
> > > > > > > > 
> > > > > > > > > > > 
> > > > > > > > > > > Stefan
> > > > > > > > > > > _______________________________________________
> > > > > > > > > > > Rust-vmm mailing list
> > > > > > > > > > > Rust-vmm at lists.opendev.org
> > > > > > > > > > > 
> > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > _______________________________________________
> > > > > > > > > > Rust-vmm mailing list
> > > > > > > > > > Rust-vmm at lists.opendev.org <mailto:
> > > > > > > > > > Rust-vmm at lists.opendev.org>
> > > > > > > > > > 
> > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> > > > > > > > > >   <
> > > > > > > > > > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> > > > > > > > > > > 
> > > > > > > > > 
> > > > > > > > > 
> > > > > > > > > 
> > > > > > > > > -- 
> > > > > > > > > Marc-André Lureau
> > > > > > > > _______________________________________________
> > > > > > > > Rust-vmm mailing list
> > > > > > > > Rust-vmm at lists.opendev.org
> > > > > > > > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> > > > > > > 
> > > > > > > --
> > > > > > > Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK
> > > > > > 
> > > > > > _______________________________________________
> > > > > > Rust-vmm mailing list
> > > > > > Rust-vmm at lists.opendev.org
> > > > > > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> > > 
> > > --
> > > Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK
> > > 
> > > _______________________________________________
> > > Rust-vmm mailing list
> > > Rust-vmm at lists.opendev.org
> > > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> > _______________________________________________
> > Rust-vmm mailing list
> > Rust-vmm at lists.opendev.org
> > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> > 
--
Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK


From pbonzini at redhat.com  Fri Jan 18 10:06:52 2019
From: pbonzini at redhat.com (Paolo Bonzini)
Date: Fri, 18 Jan 2019 11:06:52 +0100
Subject: [Rust-VMM] Summer of Code / Outreachy projects
In-Reply-To: <CAJ-JdHDBTT6Rr745hMOtezpgxSaO0JR8i0biCzERM2cJPVAC4Q@mail.gmail.com>
References: <814bbcd6-524a-f3ec-6961-35babead8f98@redhat.com>
 <CAJ-JdHAc=xjsp4SWfq6SBL8U2W2fAS5BHTE0D1B=P-2aOmcNow@mail.gmail.com>
 <c9bf7adf-0ac0-c28a-629a-fa2f3878e181@redhat.com>
 <cig332imyngmap.fsf@u54e1add816995a33037d.ant.amazon.com>
 <CAJ-JdHDBTT6Rr745hMOtezpgxSaO0JR8i0biCzERM2cJPVAC4Q@mail.gmail.com>
Message-ID: <7a072585-f2ff-e86b-2b40-e91053923ba0@redhat.com>

On 17/01/19 20:48, Cory Maccarrone wrote:
> A port seems like a much more tractable project than a rewrite for
> sure.  The KVM instruction emulator is more or less proven and works, so
> reason not to port it I think.  Agreed on the intern project, it would
> be great for that.

A better candidate for porting is the emulator embedded in QEMU for
Hypervisor.framework.  It's less complete (it doesn't attempt to cover
big real mode) and less optimized, but the code is very clean.

The question is what you'd use it for---that is, how you would embed it
in Firecracker or crosvm.  A complete port of Firecracker/crosvm to
Hypervisor.framework (which needs such an emulator) is a very large
project, even though some lessons can be learnt from QEMU.  I had a
pretty good GSoC student from 2017 and he used pretty much the whole
summer cleaning up code taken from Android emulator code and getting it
ready for inclusion in upstream QEMU.

It's of course possible to use the Hypervisor.framework emulator as an
experiment in adding Rust components to QEMU, but it's probably not what
the members of this list expect. :)

Paolo

> - Cory
> 
> On Thu, Jan 17, 2019 at 10:40 AM Anthony Liguori <aliguori at amazon.com
> <mailto:aliguori at amazon.com>> wrote:
> 
>     Paolo Bonzini <pbonzini at redhat.com <mailto:pbonzini at redhat.com>> writes:
> 
>     > On 17/01/19 19:07, Cory Maccarrone wrote:
>     >> One suggestion I might make would be a rust-implemented instruction
>     >> emulator for cracking open MMIOs.  Seems useful for VMMs in
>     general to me.
>     >
>     > That's part of the plans indeed, but the support for userspace MMIO
>     > emulation is not in upstream KVM yet.
> 
>     We you thinking a straight port of emulate.c to Rust or something from
>     scratch?
> 
>     I think a port is interesting as an intern project.  I think a new
>     emulator from scratch is a bit unrealistic as an intern project.
> 
>     Regards,
> 
>     Anthony Liguori
> 
>     >
>     > Paolo
>     >
>     >> On Wed, Jan 9, 2019 at 10:07 AM Paolo Bonzini
>     <pbonzini at redhat.com <mailto:pbonzini at redhat.com>
>     >> <mailto:pbonzini at redhat.com <mailto:pbonzini at redhat.com>>> wrote:
>     >>
>     >>     QEMU would be glad to host projects related to VMMs in Rust
>     as part of
>     >>     Google summer of Code and Outreachy.  This includes all of
>     Firecracker,
>     >>     CrosVM and common infrastructure that could be reused by multiple
>     >>     virtual machine monitors; with my QEMU hat, I would obviously
>     favor the
>     >>     latter :)).
>     >>
>     >>     An idea could be to migrate Firecracker and CrosVM to the
>     Fuchsia crates
>     >>     that were mentioned early here on the mailing list, and/or
>     implement a
>     >>     sample vhost-user client using whatever standard set of
>     crates are
>     >>     established.  Another possibility is PCI and virtio-pci in
>     Firecracker.
>     >>
>     >>     Thanks,
>     >>
>     >>     Paolo
>     >>
>     >>     _______________________________________________
>     >>     Rust-vmm mailing list
>     >>     Rust-vmm at lists.opendev.org
>     <mailto:Rust-vmm at lists.opendev.org>
>     <mailto:Rust-vmm at lists.opendev.org <mailto:Rust-vmm at lists.opendev.org>>
>     >>     http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>     >>
>     >>
>     >>
>     >> --
>     >> Cory Maccarrone | Staff Software Engineer | maccarro at google.com
>     <mailto:maccarro at google.com>
>     >> <mailto:maccarro at google.com <mailto:maccarro at google.com>> | Google
>     >>
>     >
>     >
>     > _______________________________________________
>     > Rust-vmm mailing list
>     > Rust-vmm at lists.opendev.org <mailto:Rust-vmm at lists.opendev.org>
>     > http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> 
> 
> 
> -- 
> Cory Maccarrone | Staff Software Engineer | maccarro at google.com
> <mailto:maccarro at google.com> | Google
> 



From stefanha at redhat.com  Fri Jan 18 11:32:51 2019
From: stefanha at redhat.com (Stefan Hajnoczi)
Date: Fri, 18 Jan 2019 11:32:51 +0000
Subject: [Rust-VMM] Summer of Code / Outreachy projects
In-Reply-To: <814bbcd6-524a-f3ec-6961-35babead8f98@redhat.com>
References: <814bbcd6-524a-f3ec-6961-35babead8f98@redhat.com>
Message-ID: <20190118113251.GJ21579@stefanha-x1.localdomain>

On Wed, Jan 09, 2019 at 07:07:00PM +0100, Paolo Bonzini wrote:
> QEMU would be glad to host projects related to VMMs in Rust as part of
> Google summer of Code and Outreachy.  This includes all of Firecracker,
> CrosVM and common infrastructure that could be reused by multiple
> virtual machine monitors; with my QEMU hat, I would obviously favor the
> latter :)).
> 
> An idea could be to migrate Firecracker and CrosVM to the Fuchsia crates
> that were mentioned early here on the mailing list, and/or implement a
> sample vhost-user client using whatever standard set of crates are
> established.  Another possibility is PCI and virtio-pci in Firecracker.

Background information on mentoring Google Summer of Code internships
with QEMU:

 * Presentation on the big picture, how it works, etc
   "QEMU Community Growth Through Open Source Internships"
   Video: https://www.youtube.com/watch?v=xNVCX7YMUL8
   Slides: https://vmsplice.net/~stefan/stefanha-kvm-forum-2016.pdf

 * Good project ideas are suitable for 12 weeks of full-time 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

 * QEMU may have resources for up to 2 Rust-VMM project ideas this year.
   You can post them here (see template on the wiki page) or email them
   to me:

   https://wiki.qemu.org/Google_Summer_of_Code_2019

If you have questions, please let me know.

Stefan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: not available
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190118/212aea34/attachment.sig>

From stefanha at redhat.com  Fri Jan 18 11:40:10 2019
From: stefanha at redhat.com (Stefan Hajnoczi)
Date: Fri, 18 Jan 2019 11:40:10 +0000
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <b5594c8b-438a-831e-d138-753c3cb97ee3@linux.intel.com>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
 <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
 <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
 <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>
 <20190117113018.GA2108@work-vm>
 <B9E088AD-F16C-46BB-97F9-C52A2C6D070E@gmail.com>
 <b5594c8b-438a-831e-d138-753c3cb97ee3@linux.intel.com>
Message-ID: <20190118114010.GK21579@stefanha-x1.localdomain>

On Thu, Jan 17, 2019 at 11:00:27PM +0800, Liu, Jing2 wrote:
> On 1/17/2019 7:32 PM, Jiang Liu wrote:
> > > On Jan 17, 2019, at 7:30 PM, Dr. David Alan Gilbert <dgilbert at redhat.com> wrote:
> > > > > On Jan 17, 2019, at 6:58 PM, Marc-André Lureau <marcandre.lureau at gmail.com> wrote:
> > > > > On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <liuj97 at gmail.com <mailto:liuj97 at gmail.com>> wrote:
> What application will be the virtio backend on your scenario?

This is a technicality but an important one:

  vhost-user device backends are not the same as virtio device backends

vhost-user device backends subsets of virtio device backends.  For
example, they may lack some virtqueues, virtio configuration space, and
the device lifecycle is different.

The way that the vhost-user protocol works today, for better or for
worse, is that some of the virtio device backend still lives inside the
emulator (e.g. the virtio PCI transport which controls negotiation and
lifecycle).

This also means that the vhost-user protocol has messages and features
that have no equivalent in the virtio specification.

It's worth keeping the distinction in mind because confusing these two
things becomes problematic especially when the codebase supports both
virtio and vhost-user devices :).

Stefan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: not available
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190118/bc2f32f6/attachment-0001.sig>

From fandree at amazon.com  Fri Jan 18 13:36:27 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Fri, 18 Jan 2019 13:36:27 +0000
Subject: [Rust-VMM] rust-vmm slack channel
Message-ID: <1547818586564.72606@amazon.com>

Heya,


I created a rust-vmm Slack workspace!

You can join it by following the URL:

https://join.slack.com/t/rust-vmm/shared_invite/enQtNTI3NDM2NjA5MzMzLTJiZjUxOGEwMTJkZDVkYTcxYjhjMWU3YzVhOGQ0M2Y5NmU5MzExMjg5NGE3NjlmNzNhZDlhMmY4ZjVhYTQ4ZmQ


Andreea



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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190118/789bed7d/attachment.html>

From liuj97 at gmail.com  Fri Jan 18 16:32:08 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Sat, 19 Jan 2019 00:32:08 +0800
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <20190118090951.GA2146@work-vm>
References: <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
 <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
 <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>
 <20190117113018.GA2108@work-vm>
 <B9E088AD-F16C-46BB-97F9-C52A2C6D070E@gmail.com>
 <b5594c8b-438a-831e-d138-753c3cb97ee3@linux.intel.com>
 <1C88C7F7-1A8E-4297-9DC9-049392F9A5DD@gmail.com>
 <20190117165959.GC2108@work-vm>
 <dc9329bde44f0300f1be79c7d1a8acf649738b59.camel@intel.com>
 <bdff3a96-84e9-ac20-0fc6-eb52d2371a0f@linux.intel.com>
 <20190118090951.GA2146@work-vm>
Message-ID: <CF28053C-E001-438B-87F7-C4ED9C676F29@gmail.com>



> On Jan 18, 2019, at 5:09 PM, Dr. David Alan Gilbert <dgilbert at redhat.com> wrote:
> 
> * Liu, Jing2 (jing2.liu at linux.intel.com <mailto:jing2.liu at linux.intel.com>) wrote:
>> 
>> 
>> On 1/18/2019 1:07 AM, Boeuf, Sebastien wrote:
>>> On Thu, 2019-01-17 at 16:59 +0000, Dr. David Alan Gilbert wrote:
>>>> * Jiang Liu (liuj97 at gmail.com) wrote:
>>>>> 
>>>>> 
>>>>>> On Jan 17, 2019, at 11:00 PM, Liu, Jing2 <
>>>>>> jing2.liu at linux.intel.com> wrote:
>>>>>> 
>>>>>> Hi Jiang,
>>>>>> 
>>>>>> On 1/17/2019 7:32 PM, Jiang Liu wrote:
>>>>>>>> On Jan 17, 2019, at 7:30 PM, Dr. David Alan Gilbert <
>>>>>>>> dgilbert at redhat.com> wrote:
>>>>>>>> 
>>>>>>>> * Jiang Liu (liuj97 at gmail.com) wrote:
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> On Jan 17, 2019, at 6:58 PM, Marc-André Lureau <
>>>>>>>>>> marcandre.lureau at gmail.com> wrote:
>>>>>>>>>> 
>>>>>>>>>> Hi
>>>>>>>>>> 
>>>>>>>>>> On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <
>>>>>>>>>> liuj97 at gmail.com <mailto:liuj97 at gmail.com>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> We are working on a vhostuser-rs crate, and planned to
>>>>>>>>>>> posted it for RFC later.
>>>>>>>>>> 
>>>>>>>>>> Great news! Looking forward for it! Feel free to share
>>>>>>>>>> WIP if you want help.
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> On Jan 17, 2019, at 6:52 PM, Stefan Hajnoczi <
>>>>>>>>>>>> stefanha at redhat.com> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> Hi,
>>>>>>>>>>>> Has anyone implemented a vhost-user device backend in
>>>>>>>>>>>> Rust?
>>>>>>>>>>>> 
>>>>>>>>>>>> QEMU's libvhost-user and DPDK's librte_vhost are C
>>>>>>>>>>>> implementations that
>>>>>>>>>>>> provide a device backend API.  They allow you to
>>>>>>>>>>>> implement
>>>>>>>>>>>> vhost-user-net, vhost-user-blk, and vhost-user-scsi
>>>>>>>>>>>> devices as a
>>>>>>>>>>>> separate process from the main emulator.
>>>>>>>>> 
>>>>>>>>> We are working on this direction, but  enhancements to
>>>>>>>>> firecracker/rust-vmm are need to support
>>>>>>>>> vhostuser. For example we need to support memfd based
>>>>>>>>> memory slot management. It’s really
>>>>>>>>> great if we could cooperate on it.
>>>>>>>> 
>>>>>>>> Are you working on it for the hypervisor side, or the device
>>>>>>>> side, or
>>>>>>>> both?
>>>>>>> 
>>>>>>> Currently we are focusing on the hypervisor side and vhostuser
>>>>>>> transport layer. No work on the virtio backend device yet.
>>>>>> 
>>>>>> What application will be the virtio backend on your scenario?
>>>>>> 
>>>>> 
>>>>> Hi Jing,
>>>>> 	Net and blk/scsi backends should be enough for most cases.
>>>> 
>>>> It would be interesting for us to be able to wire virtio-fs to
>>>> firecracker, and it would also be interesting to do a Rust filesystem
>>>> client.
>>> 
>>> +1 here! Something that would be very useful to build a rust-vmm
>>> hypervisor with filesystem sharing support (and that is not 9p
>>> obviously).
>> ++ too! I seems all the vhost-user device emulation, backend emulation and
>> socket channel needs to be implemented. Not a small job I think :-p
> 
> It seems like the first step would be to produce a crate with just the
> protocol definitions in for vhost-user - has anyone already done that?
> 
> Dave
> 
>> Jing
>> 
>>> 
>>>> 
>>>> Dave
>>>> 
>>>>> 
>>>>>> Jing
>>>>>> 
>>>>>>>> 
>>>>>>>> Dave
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> Stefan
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> Rust-vmm mailing list
>>>>>>>>>>>> Rust-vmm at lists.opendev.org
>>>>>>>>>>>> 
>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Rust-vmm mailing list
>>>>>>>>>>> Rust-vmm at lists.opendev.org <mailto:
>>>>>>>>>>> Rust-vmm at lists.opendev.org>
>>>>>>>>>>> 
>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>>>>>>>>>  <
>>>>>>>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> -- 
>>>>>>>>>> Marc-André Lureau
>>>>>>>>> _______________________________________________
>>>>>>>>> Rust-vmm mailing list
>>>>>>>>> Rust-vmm at lists.opendev.org
>>>>>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>>>>>> 
>>>>>>>> --
>>>>>>>> Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> Rust-vmm mailing list
>>>>>>> Rust-vmm at lists.opendev.org
>>>>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>>> 
>>>> --
>>>> Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK
>>>> 
>>>> _______________________________________________
>>>> Rust-vmm mailing list
>>>> Rust-vmm at lists.opendev.org
>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>> _______________________________________________
>>> Rust-vmm mailing list
>>> Rust-vmm at lists.opendev.org
>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
>>> 
> --
> Dr. David Alan Gilbert / dgilbert at redhat.com <mailto:dgilbert at redhat.com> / Manchester, UK

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190119/5e619ffc/attachment-0001.html>

From josh at joshtriplett.org  Sat Jan 19 00:23:06 2019
From: josh at joshtriplett.org (Josh Triplett)
Date: Fri, 18 Jan 2019 16:23:06 -0800
Subject: [Rust-VMM] Summer of Code / Outreachy projects
In-Reply-To: <7a072585-f2ff-e86b-2b40-e91053923ba0@redhat.com>
References: <814bbcd6-524a-f3ec-6961-35babead8f98@redhat.com>
 <CAJ-JdHAc=xjsp4SWfq6SBL8U2W2fAS5BHTE0D1B=P-2aOmcNow@mail.gmail.com>
 <c9bf7adf-0ac0-c28a-629a-fa2f3878e181@redhat.com>
 <cig332imyngmap.fsf@u54e1add816995a33037d.ant.amazon.com>
 <CAJ-JdHDBTT6Rr745hMOtezpgxSaO0JR8i0biCzERM2cJPVAC4Q@mail.gmail.com>
 <7a072585-f2ff-e86b-2b40-e91053923ba0@redhat.com>
Message-ID: <20190119002306.GA10453@localhost>

On Fri, Jan 18, 2019 at 11:06:52AM +0100, Paolo Bonzini wrote:
> On 17/01/19 20:48, Cory Maccarrone wrote:
> > A port seems like a much more tractable project than a rewrite for
> > sure.  The KVM instruction emulator is more or less proven and works, so
> > reason not to port it I think.  Agreed on the intern project, it would
> > be great for that.
> 
> A better candidate for porting is the emulator embedded in QEMU for
> Hypervisor.framework.  It's less complete (it doesn't attempt to cover
> big real mode) and less optimized, but the code is very clean.
> 
> The question is what you'd use it for---that is, how you would embed it
> in Firecracker or crosvm.  A complete port of Firecracker/crosvm to
> Hypervisor.framework (which needs such an emulator) is a very large
> project, even though some lessons can be learnt from QEMU.  I had a
> pretty good GSoC student from 2017 and he used pretty much the whole
> summer cleaning up code taken from Android emulator code and getting it
> ready for inclusion in upstream QEMU.

I would suggest not having support in Firecracker/crosvm for hypervisors
other than Linux /dev/kvm. The instruction-set emulator can be a
separate crate, as can the virtio backends, and then someone wanting to
build a minimal hypervisor based on Hypervisor.framework can reuse those
crates.


From jing2.liu at linux.intel.com  Mon Jan 21 04:39:49 2019
From: jing2.liu at linux.intel.com (Liu, Jing2)
Date: Mon, 21 Jan 2019 12:39:49 +0800
Subject: [Rust-VMM] Crate for vhost-user device backend?
In-Reply-To: <20190118114010.GK21579@stefanha-x1.localdomain>
References: <20190117105219.GH27840@stefanha-x1.localdomain>
 <9140D6CF-CCAF-45AC-A2BA-E3EF4CA0699E@gmail.com>
 <CAJ+F1CKWKXJx9UW5HYrEco8S2DqA_qxtDnwLT_UiB0WHXkestg@mail.gmail.com>
 <9E11D32E-A819-4A41-BE97-BAF9D1FA56F7@gmail.com>
 <20190117113018.GA2108@work-vm>
 <B9E088AD-F16C-46BB-97F9-C52A2C6D070E@gmail.com>
 <b5594c8b-438a-831e-d138-753c3cb97ee3@linux.intel.com>
 <20190118114010.GK21579@stefanha-x1.localdomain>
Message-ID: <f009000a-88bf-3378-45a9-1f41133bf923@linux.intel.com>

Hi Stefan,

On 1/18/2019 7:40 PM, Stefan Hajnoczi wrote:
> On Thu, Jan 17, 2019 at 11:00:27PM +0800, Liu, Jing2 wrote:
>> On 1/17/2019 7:32 PM, Jiang Liu wrote:
>>>> On Jan 17, 2019, at 7:30 PM, Dr. David Alan Gilbert <dgilbert at redhat.com> wrote:
>>>>>> On Jan 17, 2019, at 6:58 PM, Marc-André Lureau <marcandre.lureau at gmail.com> wrote:
>>>>>> On Thu, Jan 17, 2019 at 2:56 PM Jiang Liu <liuj97 at gmail.com <mailto:liuj97 at gmail.com>> wrote:
>> What application will be the virtio backend on your scenario?
> 
> This is a technicality but an important one:
> 
>    vhost-user device backends are not the same as virtio device backends
> 
> vhost-user device backends subsets of virtio device backends.  For
> example, they may lack some virtqueues, virtio configuration space, and
> the device lifecycle is different.
> 
> The way that the vhost-user protocol works today, for better or for
> worse, is that some of the virtio device backend still lives inside the
> emulator (e.g. the virtio PCI transport which controls negotiation and
> lifecycle).

Exactly! When reading codes, it is not easy to differ clearly. And 
important key is the backend application.
> 
> This also means that the vhost-user protocol has messages and features
> that have no equivalent in the virtio specification.
> 
> It's worth keeping the distinction in mind because confusing these two
> things becomes problematic especially when the codebase supports both
> virtio and vhost-user devices :).
Yep, agreed with you very much! And thanks for your kind tips and 
reminders on technical keys!

Jing
> 
> Stefan
> 


From liuj97 at gmail.com  Thu Jan 24 04:57:50 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Thu, 24 Jan 2019 12:57:50 +0800
Subject: [Rust-VMM] Firecracker & Crosvm common crates
In-Reply-To: <1545658874428.39674@amazon.com>
References: <1545658874428.39674@amazon.com>
Message-ID: <14D468AC-42DC-4199-A596-252CB9269CD0@gmail.com>

Hi Andreea,
	I’m very interested in ideas you have mentioned in section “memory-related” because I’m trying to enhance firecracker to support vhost-user backends and have dependencies on memory-model. So is there any plan on how to merge memory-model and data-model?
Thanks,
Gerry 

> On Dec 24, 2018, at 9:41 PM, Florescu, Andreea <fandree at amazon.com> wrote:
> 
> Hey everyone,
> 
> I've created a gist [1] so we can start a discussion about what would be worth contributing back to Crosvm.
> The document is far from being completed, but I think it is a good idea to get feedback as early as possible. That gist can also be a starting point for talking about crates that can be shared between the teams (and potentially other rust VMMs).
> 
> Let me know what you think.
> 
> Thanks and happy holidays,
> Andreea
> 
> [1] https://gist.github.com/andreeaflorescu/ce4190b442dea2c48a0d783019579ad3 <https://gist.github.com/andreeaflorescu/ce4190b442dea2c48a0d783019579ad3>
> 
> 
> 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 <mailto:Rust-vmm at lists.opendev.org>
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm <http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190124/0f2cf862/attachment.html>

From fandree at amazon.com  Thu Jan 24 11:29:00 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Thu, 24 Jan 2019 11:29:00 +0000
Subject: [Rust-VMM] Firecracker & Crosvm common crates
In-Reply-To: <14D468AC-42DC-4199-A596-252CB9269CD0@gmail.com>
References: <1545658874428.39674@amazon.com>,
 <14D468AC-42DC-4199-A596-252CB9269CD0@gmail.com>
Message-ID: <1548329339441.8295@amazon.com>

Hey,


I think the best thing to get this kick started is to setup a meeting with both crosvm & firecracker teams. I have some wild ideas about how we can merge it, but it is better to see if that is okay with both teams or other people that are interested.


When would be a good time for you to get into a call? I have some time early next week.


Andreea


________________________________
From: Jiang Liu <liuj97 at gmail.com>
Sent: Thursday, January 24, 2019 6:57 AM
To: Florescu, Andreea
Cc: rust-vmm at lists.opendev.org
Subject: Re: [Rust-VMM] Firecracker & Crosvm common crates

Hi Andreea,
I'm very interested in ideas you have mentioned in section "memory-related" because I'm trying to enhance firecracker to support vhost-user backends and have dependencies on memory-model. So is there any plan on how to merge memory-model and data-model?
Thanks,
Gerry

On Dec 24, 2018, at 9:41 PM, Florescu, Andreea <fandree at amazon.com<mailto:fandree at amazon.com>> wrote:

Hey everyone,

I've created a gist [1] so we can start a discussion about what would be worth contributing back to Crosvm.
The document is far from being completed, but I think it is a good idea to get feedback as early as possible. That gist can also be a starting point for talking about crates that can be shared between the teams (and potentially other rust VMMs).

Let me know what you think.

Thanks and happy holidays,
Andreea

[1] https://gist.github.com/andreeaflorescu/ce4190b442dea2c48a0d783019579ad3


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<mailto:Rust-vmm at lists.opendev.org>
http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm




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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190124/b27d6200/attachment-0001.html>

From dgreid at chromium.org  Fri Jan 25 02:41:46 2019
From: dgreid at chromium.org (Dylan Reid)
Date: Fri, 25 Jan 2019 10:41:46 +0800
Subject: [Rust-VMM] Firecracker & Crosvm common crates
In-Reply-To: <1548329339441.8295@amazon.com>
References: <1545658874428.39674@amazon.com>
 <14D468AC-42DC-4199-A596-252CB9269CD0@gmail.com>
 <1548329339441.8295@amazon.com>
Message-ID: <CAEUnVG7vVvKAD_Wf344HzuYbYBaif3=4k3FSXK315-qnGARcjQ@mail.gmail.com>

On Thu, Jan 24, 2019 at 7:29 PM Florescu, Andreea <fandree at amazon.com> wrote:
>
> Hey,
>
>
> I think the best thing to get this kick started is to setup a meeting with both crosvm & firecracker teams. I have some wild ideas about how we can merge it, but it is better to see if that is okay with both teams or other people that are interested.
>
>
> When would be a good time for you to get into a call? I have some time early next week.

I'll be available either Monday after 1500 PST or Wednesday before 1600 PST.


>
>
> Andreea
>
>
> ________________________________
> From: Jiang Liu <liuj97 at gmail.com>
> Sent: Thursday, January 24, 2019 6:57 AM
> To: Florescu, Andreea
> Cc: rust-vmm at lists.opendev.org
> Subject: Re: [Rust-VMM] Firecracker & Crosvm common crates
>
> Hi Andreea,
> I’m very interested in ideas you have mentioned in section “memory-related” because I’m trying to enhance firecracker to support vhost-user backends and have dependencies on memory-model. So is there any plan on how to merge memory-model and data-model?
> Thanks,
> Gerry
>
> On Dec 24, 2018, at 9:41 PM, Florescu, Andreea <fandree at amazon.com> wrote:
>
> Hey everyone,
>
> I've created a gist [1] so we can start a discussion about what would be worth contributing back to Crosvm.
> The document is far from being completed, but I think it is a good idea to get feedback as early as possible. That gist can also be a starting point for talking about crates that can be shared between the teams (and potentially other rust VMMs).
>
> Let me know what you think.
>
> Thanks and happy holidays,
> Andreea
>
> [1] https://gist.github.com/andreeaflorescu/ce4190b442dea2c48a0d783019579ad3
>
>
> 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
>
>
>
> 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 liuj97 at gmail.com  Fri Jan 25 05:31:12 2019
From: liuj97 at gmail.com (Liu Jiang)
Date: Fri, 25 Jan 2019 13:31:12 +0800
Subject: [Rust-VMM] [RFC, WIP] rust implementation of ghost-user protocol
Message-ID: <0FB344A6-C13A-40B6-B2E0-C4C9551590B3@linux.alibaba.com>

Hi all,
	As we have discussed, community members have showed interests in rust implementation of the ghost-user protocol. It happens that we are working on implementing ghost-user protocol, but still in very early stage. 
I think it would be better to share our work with community as early as possible so we could cooperate on the design and implementation. 
	The overall idea is to implement a rust crate for vhost-user protocol, and then extends the vhost driver in crosvm/firecracker to add a thin wrapper support both vhost (kernel) and vhost-user backends. The crate is in very early stage which only implements the skeleton and basic commands, so a long todo list:
	1) support dirty page log
	2) support live migration
	3) support IOMMU/IOTLB
	4) better documentation
	5) more unit test cases

	I have hosted the crate at my personal GitHub repository at https://github.com/jiangliu/vhostuser_rs <https://github.com/jiangliu/vhostuser_rs> and hope it could be hosted by the rust-vmm project eventually.
	Any comments, suggestions and PRs are welcomed!
Thanks,
Gerry 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190125/11203185/attachment.html>

From liuj97 at gmail.com  Fri Jan 25 05:44:51 2019
From: liuj97 at gmail.com (Jiang Liu)
Date: Fri, 25 Jan 2019 13:44:51 +0800
Subject: [Rust-VMM] Firecracker & Crosvm common crates
In-Reply-To: <CAEUnVG7vVvKAD_Wf344HzuYbYBaif3=4k3FSXK315-qnGARcjQ@mail.gmail.com>
References: <1545658874428.39674@amazon.com>
 <14D468AC-42DC-4199-A596-252CB9269CD0@gmail.com>
 <1548329339441.8295@amazon.com>
 <CAEUnVG7vVvKAD_Wf344HzuYbYBaif3=4k3FSXK315-qnGARcjQ@mail.gmail.com>
Message-ID: <2113AF83-BC90-43B2-BE98-5473737D0ACD@gmail.com>



> On Jan 25, 2019, at 10:41 AM, Dylan Reid <dgreid at chromium.org> wrote:
> 
> On Thu, Jan 24, 2019 at 7:29 PM Florescu, Andreea <fandree at amazon.com> wrote:
>> 
>> Hey,
>> 
>> 
>> I think the best thing to get this kick started is to setup a meeting with both crosvm & firecracker teams. I have some wild ideas about how we can merge it, but it is better to see if that is okay with both teams or other people that are interested.
>> 
>> 
>> When would be a good time for you to get into a call? I have some time early next week.
> 
> I'll be available either Monday after 1500 PST or Wednesday before 1600 PST.
Hi all,
	I’m Ok with these two time slots too.
Thank,
Gerry


> 
> 
>> 
>> 
>> Andreea
>> 
>> 
>> ________________________________
>> From: Jiang Liu <liuj97 at gmail.com>
>> Sent: Thursday, January 24, 2019 6:57 AM
>> To: Florescu, Andreea
>> Cc: rust-vmm at lists.opendev.org
>> Subject: Re: [Rust-VMM] Firecracker & Crosvm common crates
>> 
>> Hi Andreea,
>> I’m very interested in ideas you have mentioned in section “memory-related” because I’m trying to enhance firecracker to support vhost-user backends and have dependencies on memory-model. So is there any plan on how to merge memory-model and data-model?
>> Thanks,
>> Gerry
>> 
>> On Dec 24, 2018, at 9:41 PM, Florescu, Andreea <fandree at amazon.com> wrote:
>> 
>> Hey everyone,
>> 
>> I've created a gist [1] so we can start a discussion about what would be worth contributing back to Crosvm.
>> The document is far from being completed, but I think it is a good idea to get feedback as early as possible. That gist can also be a starting point for talking about crates that can be shared between the teams (and potentially other rust VMMs).
>> 
>> Let me know what you think.
>> 
>> Thanks and happy holidays,
>> Andreea
>> 
>> [1] https://gist.github.com/andreeaflorescu/ce4190b442dea2c48a0d783019579ad3
>> 
>> 
>> 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
>> 
>> 
>> 
>> 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 dgilbert at redhat.com  Fri Jan 25 09:31:21 2019
From: dgilbert at redhat.com (Dr. David Alan Gilbert)
Date: Fri, 25 Jan 2019 09:31:21 +0000
Subject: [Rust-VMM] [RFC, WIP] rust implementation of ghost-user protocol
In-Reply-To: <0FB344A6-C13A-40B6-B2E0-C4C9551590B3@linux.alibaba.com>
References: <0FB344A6-C13A-40B6-B2E0-C4C9551590B3@linux.alibaba.com>
Message-ID: <20190125093117.GA2695@work-vm>

* Liu Jiang (liuj97 at gmail.com) wrote:
> Hi all,
> 	As we have discussed, community members have showed interests in rust implementation of the ghost-user protocol.

There's a *g*host in your message :-)

> It happens that we are working on implementing ghost-user protocol, but still in very early stage. 
> I think it would be better to share our work with community as early as possible so we could cooperate on the design and implementation. 
> 	The overall idea is to implement a rust crate for vhost-user protocol, and then extends the vhost driver in crosvm/firecracker to add a thin wrapper support both vhost (kernel) and vhost-user backends. The crate is in very early stage which only implements the skeleton and basic commands, so a long todo list:
> 	1) support dirty page log
> 	2) support live migration
> 	3) support IOMMU/IOTLB
> 	4) better documentation
> 	5) more unit test cases
> 
> 	I have hosted the crate at my personal GitHub repository at https://github.com/jiangliu/vhostuser_rs <https://github.com/jiangliu/vhostuser_rs> and hope it could be hosted by the rust-vmm project eventually.
> 	Any comments, suggestions and PRs are welcomed!

Great! I'll have a look at it.

Dave

> Thanks,
> Gerry 

> _______________________________________________
> Rust-vmm mailing list
> Rust-vmm at lists.opendev.org
> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm

--
Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK


From liuj97 at gmail.com  Fri Jan 25 09:33:54 2019
From: liuj97 at gmail.com (Liu Jiang)
Date: Fri, 25 Jan 2019 17:33:54 +0800
Subject: [Rust-VMM] [RFC, WIP] rust implementation of ghost-user protocol
In-Reply-To: <20190125093117.GA2695@work-vm>
References: <0FB344A6-C13A-40B6-B2E0-C4C9551590B3@linux.alibaba.com>
 <20190125093117.GA2695@work-vm>
Message-ID: <FCC3EB1D-6083-433A-BC7E-F75172791EA9@gmail.com>



> On Jan 25, 2019, at 5:31 PM, Dr. David Alan Gilbert <dgilbert at redhat.com> wrote:
> 
> * Liu Jiang (liuj97 at gmail.com) wrote:
>> Hi all,
>> 	As we have discussed, community members have showed interests in rust implementation of the ghost-user protocol.
> 
> There's a *g*host in your message :-)
Really sorry for this, the auto-spell-correction always change “vhost” as “ghost”:(

> 
>> It happens that we are working on implementing ghost-user protocol, but still in very early stage. 
>> I think it would be better to share our work with community as early as possible so we could cooperate on the design and implementation. 
>> 	The overall idea is to implement a rust crate for vhost-user protocol, and then extends the vhost driver in crosvm/firecracker to add a thin wrapper support both vhost (kernel) and vhost-user backends. The crate is in very early stage which only implements the skeleton and basic commands, so a long todo list:
>> 	1) support dirty page log
>> 	2) support live migration
>> 	3) support IOMMU/IOTLB
>> 	4) better documentation
>> 	5) more unit test cases
>> 
>> 	I have hosted the crate at my personal GitHub repository at https://github.com/jiangliu/vhostuser_rs <https://github.com/jiangliu/vhostuser_rs> and hope it could be hosted by the rust-vmm project eventually.
>> 	Any comments, suggestions and PRs are welcomed!
> 
> Great! I'll have a look at it.
> 
> Dave
> 
>> Thanks,
>> Gerry 
> 
>> _______________________________________________
>> Rust-vmm mailing list
>> Rust-vmm at lists.opendev.org
>> http://lists.opendev.org/cgi-bin/mailman/listinfo/rust-vmm
> 
> --
> Dr. David Alan Gilbert / dgilbert at redhat.com / Manchester, UK



From fandree at amazon.com  Fri Jan 25 10:28:53 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Fri, 25 Jan 2019 10:28:53 +0000
Subject: [Rust-VMM] Firecracker & Crosvm common crates
In-Reply-To: <2113AF83-BC90-43B2-BE98-5473737D0ACD@gmail.com>
References: <1545658874428.39674@amazon.com>
 <14D468AC-42DC-4199-A596-252CB9269CD0@gmail.com>
 <1548329339441.8295@amazon.com>
 <CAEUnVG7vVvKAD_Wf344HzuYbYBaif3=4k3FSXK315-qnGARcjQ@mail.gmail.com>,
 <2113AF83-BC90-43B2-BE98-5473737D0ACD@gmail.com>
Message-ID: <1548412131565.89967@amazon.com>

I am not going to be able to join that as it is 1 AM or 2 AM for me. Can you send meeting minutes?

Andreea
________________________________________
From: Jiang Liu <liuj97 at gmail.com>
Sent: Friday, January 25, 2019 7:44 AM
To: Dylan Reid
Cc: Florescu, Andreea; rust-vmm at lists.opendev.org
Subject: Re: [Rust-VMM] Firecracker & Crosvm common crates

> On Jan 25, 2019, at 10:41 AM, Dylan Reid <dgreid at chromium.org> wrote:
>
> On Thu, Jan 24, 2019 at 7:29 PM Florescu, Andreea <fandree at amazon.com> wrote:
>>
>> Hey,
>>
>>
>> I think the best thing to get this kick started is to setup a meeting with both crosvm & firecracker teams. I have some wild ideas about how we can merge it, but it is better to see if that is okay with both teams or other people that are interested.
>>
>>
>> When would be a good time for you to get into a call? I have some time early next week.
>
> I'll be available either Monday after 1500 PST or Wednesday before 1600 PST.
Hi all,
        I’m Ok with these two time slots too.
Thank,
Gerry


>
>
>>
>>
>> Andreea
>>
>>
>> ________________________________
>> From: Jiang Liu <liuj97 at gmail.com>
>> Sent: Thursday, January 24, 2019 6:57 AM
>> To: Florescu, Andreea
>> Cc: rust-vmm at lists.opendev.org
>> Subject: Re: [Rust-VMM] Firecracker & Crosvm common crates
>>
>> Hi Andreea,
>> I’m very interested in ideas you have mentioned in section “memory-related” because I’m trying to enhance firecracker to support vhost-user backends and have dependencies on memory-model. So is there any plan on how to merge memory-model and data-model?
>> Thanks,
>> Gerry
>>
>> On Dec 24, 2018, at 9:41 PM, Florescu, Andreea <fandree at amazon.com> wrote:
>>
>> Hey everyone,
>>
>> I've created a gist [1] so we can start a discussion about what would be worth contributing back to Crosvm.
>> The document is far from being completed, but I think it is a good idea to get feedback as early as possible. That gist can also be a starting point for talking about crates that can be shared between the teams (and potentially other rust VMMs).
>>
>> Let me know what you think.
>>
>> Thanks and happy holidays,
>> Andreea
>>
>> [1] https://gist.github.com/andreeaflorescu/ce4190b442dea2c48a0d783019579ad3
>>
>>
>> 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
>>
>>
>>
>> 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




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.



From liuj97 at gmail.com  Fri Jan 25 13:00:30 2019
From: liuj97 at gmail.com (Liu Jiang)
Date: Fri, 25 Jan 2019 21:00:30 +0800
Subject: [Rust-VMM] Firecracker & Crosvm common crates
In-Reply-To: <1548412131565.89967@amazon.com>
References: <1545658874428.39674@amazon.com>
 <14D468AC-42DC-4199-A596-252CB9269CD0@gmail.com>
 <1548329339441.8295@amazon.com>
 <CAEUnVG7vVvKAD_Wf344HzuYbYBaif3=4k3FSXK315-qnGARcjQ@mail.gmail.com>
 <2113AF83-BC90-43B2-BE98-5473737D0ACD@gmail.com>
 <1548412131565.89967@amazon.com>
Message-ID: <DFAC2B59-FD6E-42A6-9F1C-D8D3AA797A97@gmail.com>



> On Jan 25, 2019, at 6:28 PM, Florescu, Andreea <fandree at amazon.com> wrote:
> 
> I am not going to be able to join that as it is 1 AM or 2 AM for me. Can you send meeting minutes?
Seems a little hard to schedule a time slot for for all of us, so could we discuss by email?


> 
> Andreea
> ________________________________________
> From: Jiang Liu <liuj97 at gmail.com>
> Sent: Friday, January 25, 2019 7:44 AM
> To: Dylan Reid
> Cc: Florescu, Andreea; rust-vmm at lists.opendev.org
> Subject: Re: [Rust-VMM] Firecracker & Crosvm common crates
> 
>> On Jan 25, 2019, at 10:41 AM, Dylan Reid <dgreid at chromium.org> wrote:
>> 
>> On Thu, Jan 24, 2019 at 7:29 PM Florescu, Andreea <fandree at amazon.com> wrote:
>>> 
>>> Hey,
>>> 
>>> 
>>> I think the best thing to get this kick started is to setup a meeting with both crosvm & firecracker teams. I have some wild ideas about how we can merge it, but it is better to see if that is okay with both teams or other people that are interested.
>>> 
>>> 
>>> When would be a good time for you to get into a call? I have some time early next week.
>> 
>> I'll be available either Monday after 1500 PST or Wednesday before 1600 PST.
> Hi all,
>       I’m Ok with these two time slots too.
> Thank,
> Gerry
> 
> 
>> 
>> 
>>> 
>>> 
>>> Andreea
>>> 
>>> 
>>> ________________________________
>>> From: Jiang Liu <liuj97 at gmail.com>
>>> Sent: Thursday, January 24, 2019 6:57 AM
>>> To: Florescu, Andreea
>>> Cc: rust-vmm at lists.opendev.org
>>> Subject: Re: [Rust-VMM] Firecracker & Crosvm common crates
>>> 
>>> Hi Andreea,
>>> I’m very interested in ideas you have mentioned in section “memory-related” because I’m trying to enhance firecracker to support vhost-user backends and have dependencies on memory-model. So is there any plan on how to merge memory-model and data-model?
>>> Thanks,
>>> Gerry
>>> 
>>> On Dec 24, 2018, at 9:41 PM, Florescu, Andreea <fandree at amazon.com> wrote:
>>> 
>>> Hey everyone,
>>> 
>>> I've created a gist [1] so we can start a discussion about what would be worth contributing back to Crosvm.
>>> The document is far from being completed, but I think it is a good idea to get feedback as early as possible. That gist can also be a starting point for talking about crates that can be shared between the teams (and potentially other rust VMMs).
>>> 
>>> Let me know what you think.
>>> 
>>> Thanks and happy holidays,
>>> Andreea
>>> 
>>> [1] https://gist.github.com/andreeaflorescu/ce4190b442dea2c48a0d783019579ad3
>>> 
>>> 
>>> 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
>>> 
>>> 
>>> 
>>> 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
> 
> 
> 
> 
> 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.
> 



From samuel.ortiz at intel.com  Fri Jan 25 13:03:45 2019
From: samuel.ortiz at intel.com (Samuel Ortiz)
Date: Fri, 25 Jan 2019 14:03:45 +0100
Subject: [Rust-VMM] Firecracker & Crosvm common crates
In-Reply-To: <DFAC2B59-FD6E-42A6-9F1C-D8D3AA797A97@gmail.com>
References: <1545658874428.39674@amazon.com>
 <14D468AC-42DC-4199-A596-252CB9269CD0@gmail.com>
 <1548329339441.8295@amazon.com>
 <CAEUnVG7vVvKAD_Wf344HzuYbYBaif3=4k3FSXK315-qnGARcjQ@mail.gmail.com>
 <2113AF83-BC90-43B2-BE98-5473737D0ACD@gmail.com>
 <1548412131565.89967@amazon.com>
 <DFAC2B59-FD6E-42A6-9F1C-D8D3AA797A97@gmail.com>
Message-ID: <20190125130345.GC4971@caravaggio>

On Fri, Jan 25, 2019 at 09:00:30PM +0800, Liu Jiang wrote:
> 
> 
> > On Jan 25, 2019, at 6:28 PM, Florescu, Andreea <fandree at amazon.com> wrote:
> > 
> > I am not going to be able to join that as it is 1 AM or 2 AM for me. Can you send meeting minutes?
> Seems a little hard to schedule a time slot for for all of us, so could we discuss by email?
Since this hopefully will end up being a rust-vmm crate, may I suggest
to use a github issue to have that discussion?

Cheers,
Samuel.
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



From fandree at amazon.com  Mon Jan 28 11:53:57 2019
From: fandree at amazon.com (Florescu, Andreea)
Date: Mon, 28 Jan 2019 11:53:57 +0000
Subject: [Rust-VMM] rust-vmm contributors
Message-ID: <1548676437438.90424@amazon.com>

Hey,


I will give a presentation about rust-vmm at Fosdem 2019 (on Saturday) and I will have a slide with people that already contributed to rust-vmm. By contributing I mean: discussions, reviews, pull requests, ideas, others?

As it is a bit too much to include individual people, I was thinking about including group of peoples.


So far I have (in alphabetical order):


Alibaba Cloud
Chromium OS
Firecracker

Kata Containers
Qemu
Red Hat


If I am missing some group, can you please send me an email and I will update the slide?


Thanks,

Andreea



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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190128/91561132/attachment.html>

From claire at openstack.org  Mon Jan 28 16:53:09 2019
From: claire at openstack.org (Claire Massey)
Date: Mon, 28 Jan 2019 08:53:09 -0800
Subject: [Rust-VMM] Schedule Bi-Weekly Calls
Message-ID: <8DC3B91E-4CF3-40BC-92FD-C4E7B302794A@openstack.org>

Hi everyone,

There’s some interest in holding bi-weekly calls to maximize opportunity for collaboration around Rust-VMM topics and discuss project activities that are in flight. 

Please take this poll to find a time that works best for everyone: https://framadate.org/1corf6IQFWCGZrmT

We plan to start hosting the calls next week, in February. 

Thanks,
Claire




From stefanha at gmail.com  Tue Jan 29 05:21:29 2019
From: stefanha at gmail.com (Stefan Hajnoczi)
Date: Tue, 29 Jan 2019 13:21:29 +0800
Subject: [Rust-VMM] Last call for GSoC/Outreachy project ideas
Message-ID: <CAJSP0QUuZZOVOxhuUG4J3sh0qp_BTf-MrVV=Z9eQs4dXBpY1qA@mail.gmail.com>

Dear QEMU, KVM, Jailhouse, and Rust-VMM communities,
Please post your internship project ideas by February 1st so we can
include them in the Google Summer of Code and Outreachy ideas list:

https://wiki.qemu.org/Google_Summer_of_Code_2019

If you'd like to mentor but don't have your own project idea, take a
look at the list and ask to co-mentor one of the existing project
ideas.

Good project ideas are suitable for 12 weeks of full-time 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

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


From claire at openstack.org  Tue Jan 29 15:49:34 2019
From: claire at openstack.org (Claire Massey)
Date: Tue, 29 Jan 2019 09:49:34 -0600
Subject: [Rust-VMM] Schedule Bi-Weekly Calls
In-Reply-To: <8DC3B91E-4CF3-40BC-92FD-C4E7B302794A@openstack.org>
References: <8DC3B91E-4CF3-40BC-92FD-C4E7B302794A@openstack.org>
Message-ID: <DC0DFBF7-C613-42A2-9A6F-6B6233059E62@openstack.org>

Hi everyone,

Thanks for taking the poll. 

Wednesday at 8:00am pacific is the time that works best for everyone. We’ll start the bi-weekly calls next week on February 6. 

I’ll send a meeting invite to the ML, but here’s the info for the call. Please feel free to go ahead and add topics to the agenda. 

Notes / Agenda: https://etherpad.openstack.org/p/rust_vmm_2019_biweekly_calls

Zoom: https://zoom.us/j/181523033

Thanks,
Claire


> On Jan 28, 2019, at 10:53 AM, Claire Massey <claire at openstack.org> wrote:
> 
> Hi everyone,
> 
> There’s some interest in holding bi-weekly calls to maximize opportunity for collaboration around Rust-VMM topics and discuss project activities that are in flight. 
> 
> Please take this poll to find a time that works best for everyone: https://framadate.org/1corf6IQFWCGZrmT
> 
> We plan to start hosting the calls next week, in February. 
> 
> Thanks,
> Claire
> 
> 
> 
> _______________________________________________
> 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: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190129/3809a6a6/attachment.html>

From claire at openstack.org  Tue Jan 29 15:48:28 2019
From: claire at openstack.org (claire at openstack.org)
Date: Tue, 29 Jan 2019 15:48:28 +0000
Subject: [Rust-VMM] 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: <0000000000007c5c6705809ab999@google.com>

You have been invited to the following event.

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
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 modify your RSVP  
response. Learn more at  
https://support.google.com/calendar/answer/37135#forwarding
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190129/d387ae9d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2290 bytes
Desc: not available
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190129/d387ae9d/attachment-0001.ics>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: application/ics
Size: 2348 bytes
Desc: not available
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190129/d387ae9d/attachment-0001.bin>