upgrade vm-memory to 0.8.0

[wllenyj]

The rust-vmm community uses the Comparison requirements form for specific dependencies. The advantage of this is that when a new version of the crate is released, there is no need to update the version for each dependent crate. But, if the new version of the crate is API incompatible. All libs that depend on it must either be modified accordingly, or the version number must be locked. This is exactly what we do in kata currently. So in the next step we need to modify all the dependent libraries.

Making this work requires the following changes.

• upgrade vm-memory to 0.8.0 for https://github.com/cloud-hypervisor/fuse-backend-rs
• upgrade vm-memory to 0.8.0 for https://github.com/dragonflyoss/image-service
• Use QueueStateSync in virtio-queue instead of QueueState for dbs-virtio-devices. And upgrade virtio-queue to 0.3.0.
• upgrade vm-memory to 0.8.0 for all crates.

[uran0sH]

Maybe I could help you to upgrade vm-memory to 0.8.0 for fuse-backend-rs and image-service.

[studychao]

@uran0sH Hello there~ You are welcome to help us to upgrade vm-memory to 0.8.0 for fuse-backend-rs and image-service.
And if you encounter any problem during upgrading, please let us know:)

[studychao]

Hi @uran0sH , are you working at vm-memory update in image-service ? Do you need any help about that?

[uran0sH]

Hi @uran0sH , are you working at vm-memory update in image-service ? Do you need any help about that?

Yeah, but it seems to require waiting for the latest version of fuse-backend-rs to be released to upgrade image-service

[studychao]

@uran0sH Got that, thanks. Let me check whether fuse-backend-rs could do a release.

[studychao]

Hi @uran0sH , fuse-backend-rs has released a new version and maybe you could try to update the vm-memory in image-service .

If you encounter any probleam, please let me know.

[wllenyj]

#213