You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue tracks the progress of moving the rust-vmm crates to the mono-repo: github.com/rust-vmm/rust-vmm/.
Status
Below are the crates that need to be moved to the mono repo.
Status: Not Started, In Progress, Done.
Priority: 1 to 10, where 1 is highest priority and 10 is lowest priority.
The proposed approach to handle this is to start with the crates that cause the biggest pain points when doing updates. Right now it looks like these are the 2 leaf crates vm-memory and vmm-sys-util.
We need to pick up the next one after vm-memory. @rbradford could you chime in here? Where are the pain points in Cloud Hypervisor?
The proposed approach to handle this is to start with the crates that cause the biggest pain points when doing updates. Right now it looks like these are the 2 leaf crates vm-memory and vmm-sys-util.
We need to pick up the next one after vm-memory. @rbradford could you chime in here? Where are the pain points in Cloud Hypervisor?
@andreeaflorescu Welcome back! Thanks for jumping in on this. I think that a monorepo will help a lot since all the releases can be made together. One of the problems we have is that if a crate is bumped to an API breaking release (like linux-loader to the new vm-memory 0.18.0) we can't consume that updated version until all the other crates have moved to vm-memory 0.18.0. This is why I asked that we didn't update that crate until the migration to the monorepo was done (we could have updates all the crates with one PR.)
Since I've already got my feet wet with https://github.com/rust-vmm/kvm a couple of months ago, I can take care of that! Unfortunately I can't promise any progress in the next 14 days.
Since I've already got my feet wet with https://github.com/rust-vmm/kvm a couple of months ago, I can take care of that! Unfortunately I can't promise any progress in the next 14 days.
No worries, I we get there and you happen to be busy, I can take care of it 😉
One thing that is still missing is for the crates to specify their dependencies as local path when their dependencies are already part of the mono-repo. This is a bit hard to explain in words, so I'll add an example with a commit to exemplify what needs to be done. I'll do this as part of vm-memory migration.
Is the list above updated? i.e. the crates which don't have an owner for the move to mono repo are open for owner? I see quite a bit of activity in vfio right now. Is someone pencilled in to move that crate?
We should work next based on priority so that we merge the crates that other crates depend on. This is needed so that we can specify dependencies using the path for all crates that live in the mono repo. See the migration wiki for details: https://github.com/rust-vmm/rust-vmm/wiki/How-to-migrate-a-repo.
Crates with dependency 10 can be migrated at any point. They don't influence other crates, hence priority 10.
Hey there - just returned from a long vacation. I still have this on my radar, but unfortunately I just haven't had the time to get to it. I hope I can get it done within the next 4 weeks or so.
Activity
andreeaflorescu commentedon May 11, 2026
Related to rust-vmm/vmm-sys-util#180
andreeaflorescu commentedon May 11, 2026
The proposed approach to handle this is to start with the crates that cause the biggest pain points when doing updates. Right now it looks like these are the 2 leaf crates vm-memory and vmm-sys-util.
We need to pick up the next one after vm-memory. @rbradford could you chime in here? Where are the pain points in Cloud Hypervisor?
rbradford commentedon May 11, 2026
@andreeaflorescu Welcome back! Thanks for jumping in on this. I think that a monorepo will help a lot since all the releases can be made together. One of the problems we have is that if a crate is bumped to an API breaking release (like linux-loader to the new vm-memory 0.18.0) we can't consume that updated version until all the other crates have moved to vm-memory 0.18.0. This is why I asked that we didn't update that crate until the migration to the monorepo was done (we could have updates all the crates with one PR.)
phip1611 commentedon May 11, 2026
Since I've already got my feet wet with https://github.com/rust-vmm/kvm a couple of months ago, I can take care of that! Unfortunately I can't promise any progress in the next 14 days.
RuoqingHe commentedon May 12, 2026
No worries, I we get there and you happen to be busy, I can take care of it 😉
andreeaflorescu commentedon May 22, 2026
We have a wiki with steps to follow for the move to the mono-repo: https://github.com/rust-vmm/rust-vmm/wiki/How-to-migrate-a-repo.
One thing that is still missing is for the crates to specify their dependencies as local path when their dependencies are already part of the mono-repo. This is a bit hard to explain in words, so I'll add an example with a commit to exemplify what needs to be done. I'll do this as part of vm-memory migration.
bytefire commentedon May 22, 2026
Is the list above updated? i.e. the crates which don't have an owner for the move to mono repo are open for owner? I see quite a bit of activity in vfio right now. Is someone pencilled in to move that crate?
andreeaflorescu commentedon May 26, 2026
@bytefire the list is updated. So far nobody has offered to move vfio. We are prioritizing the CI at this moment.
andreeaflorescu commentedon Jul 14, 2026
@olivereanderson are you still interested in moving linux-loader?
@phip1611 are you still interested in moving kvm?
olivereanderson commentedon Jul 14, 2026
@andreeaflorescu yes, I intend to move linux-loader in the next couple of days.
I was waiting for the vm-memory dependency to be moved first and didn't notice until very recently that it has now indeed been moved.
stefano-garzarella commentedon Jul 16, 2026
Adding myself for moving
vhostworkspaceandreeaflorescu commentedon Jul 16, 2026
We should work next based on priority so that we merge the crates that other crates depend on. This is needed so that we can specify dependencies using the path for all crates that live in the mono repo. See the migration wiki for details: https://github.com/rust-vmm/rust-vmm/wiki/How-to-migrate-a-repo.
Crates with dependency 10 can be migrated at any point. They don't influence other crates, hence priority 10.
phip1611 commentedon Aug 10, 2026
Hey there - just returned from a long vacation. I still have this on my radar, but unfortunately I just haven't had the time to get to it. I hope I can get it done within the next 4 weeks or so.
phip1611 commentedon Sep 3, 2026
@olivereanderson is taken over the kvm migration for me - thanks Oliver!