roypat
commented
2 years ago I went through all of the rust-vmm crates and created the following table that keeps track of all their dependencies and whether they currently rely on (a) non-caret requirements and (b) outdated versions
| Crate | Version | Uses caret deps? | rust-vmm deps at fixed versions (outdated are bold) | rust-vmm deps at non-caret versions |
|---|---|---|---|---|
| kvm-ioctl | 0.11.0 | yes | vmm-sys-util@0.10.0 kvm-bindings@0.5.0 (MERGED) | |
| vmm-sys-util | 0.11.0 | yes | ||
| kvm-bindings | 0.5.0 | yes | vmm-sys-util@0.10.0 (MERGED) | |
| event-manager | 0.2.1 | no | vmm-sys-util>=0.8.0 | |
| vfio-ioctls | 0.1.0 | no | kvm-bindings\~0, kvm-ioctls\~0, vm-memory>=0.6, vfio-bindings~0, vmm-sys-util>=0.8.0 (NO PR OPEN) | |
| vfio-bindings | 0.3.1 | no | vmm-sys-util>=0.8.0 (NO PR OPEN) | |
| vhost-device-gpio | 0.1.0 | no | virtio-queue@0.6. vhost-user-backend@0.7.0 | vmm-sys-util=0.10.0. vm-memory>=0.8, virtio-binding>=0.1 (NO PR OPEN) |
| vhost-device-i2c | 0.1.0 | no | vhost-user-backend@0.7.0, vhost@0.5, virtio-queue@0.6 | vm-memory>=0.8, vmm-sys-util=0.10.0 (NO PR OPEN) |
| vhost-device-rng | 0.1.0 | no | vhost@0.5, vhost-user-backend@0.7.0, virtio-queue@0.6 | vm-memory>=0.8, vmm-sys-util=0.10.0, virtio-bindings>=0.1 (NO PR OPEN) |
| vhost-device-vsock | 0.1.0 | no | vhost@0.5, vhost-user-backend@0.7.0, virtio-queue@0.6, viortio-vsock@0.1.0 | vm-memory>=0.8, vmm-sys-util=0.10.0, virtio-bindings>=0.1 (NO PR OPEN) |
| mshv-ioctls | 0.1.1 | no | vmm-sys-util>=0.8.0 (NO PR) | |
| mshv-bindings | 0.1.1 | no | vmm-sys-util>=0.2.1 (NO PR) | |
| virtio-blk | 0.1.0 | no | vmm-sys-util@0.10.0, vm-memory@0.9.0, virtio-device, virtio-bindings(MERGED) | |
| virtio-console | 0.1.0 | no | virtio-queue@0.6.0, virtio-bindings@0.1.0, vm-memory@0.9.0(MERGED) | |
| virtio-vsock | 0.1.0 | no | virtio-queue@0.6.0, virtio-bindings@0.1.0, vm-memory@0.9.0(MERGED) | |
| virtio-queue | 0.6.1 | no | vm-memory@0.9.0, vmm-sys-util@0.10.0, virtio-bindings@0.1.0(MERGED) | |
| virtio-queue-ser | 0.3.0 | no | virtio-memory@0.9.0, virtio-queue@0.6.0(MERGED) | |
| virtio-device | 0.1.0 | no | vm-memory@0.9.0, virtio-queue@0.6.0, virtio-bindings (MERGED) | |
| virtio-bindings | 0.1.0 | no | ||
| vm-fdt | 0.2.0 | yes | ||
| vm-device | 0.1.0 | yes | ||
| vm-allocator | 0.1.0 | no | ||
| vm-memory | 0.9.0 | yes | vmm-sys-util@0.10.0 (MERGED) | |
| vhost | 0.5.0 | yes | vmm-sys-util@0.10.0 (No PR), vm-memory@0.9.0 | |
| vhost-user-backend | 0.7.0 | yes | vmm-sys-util@0.10.0 (No PR), vm-memory@0.9.0, vhost@0.5, virtio-queue@0.6, virtio-bindings@0.1 | |
| vm-superio | 0.6.0 | no | vmm-sys-util>=0.7.0 (MERGED) | |
| vm-superio-ser | 0.2.0 | no | vm-superio@=0.6.0 | vmm-sys-util>=0.7.0 (MERGED) |
| linux-loader | 0.7.0 | yes | vm-memory@0.9.0 (MERGED) |
andreeaflorescu
alxiord
studychao
wllenyj
rbradford
This update is needed because otherwise there will be crates using vmm-sys-util 0.10.0 and others using 0.11.0. The reason behind this is the (wrong) way in which we specify dependencies in a few of the rust-vmm crates. Specifically, some crates will just pick up the latest available version of a crate even if it introduces breaking changes (i.e. picking up 0.11.0 because the dep is specified as
>= 0.9.0). We're progressively fixing this by always having dependencies specified with caret, but this work was not yet completed for a few crates. As such, we need to:For example, we first need to update kvm-bindings, publish it, and then update kvm-ioctls by specifying a new version for both vmm-sys-util and kvm-bindings.
This issue is tracking this one time effort. We're not tracking here a saner way to do the updates, as this is going to happen afterwards. Tracking issues: #135 & TBD (for releases).