[Rust-VMM] Rust VMM Crates
liuj97 at gmail.com
Wed Jan 16 15:45:02 UTC 2019
> 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?
> 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?
>> 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 . 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  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  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!
>>  https://fosdem.org/2019/schedule/event/vai_rust_vmm/ <https://fosdem.org/2019/schedule/event/vai_rust_vmm/>
>>  https://github.com/rust-vmm/community <https://github.com/rust-vmm/community>
>>  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...
More information about the Rust-vmm