build(deps): update vm-memory requirement from 0.12.0 to 0.13.0

[dependabot]

Updates the requirements on vm-memory to permit the latest version.

Changelog

Sourced from vm-memory's changelog.

[v0.13.0]

Added

• [#247](rust-vmm/vm-memory#247) Add ReadVolatile and WriteVolatile traits which are equivalents of Read/Write with volatile access semantics.

Changed

• [#247](rust-vmm/vm-memory#247) Deprecate Bytes::{read_from, read_exact_from, write_to, write_all_to}. Instead use ReadVolatile/WriteVolatile, which do not incur the performance penalty of copying to hypervisor memory due to Read/Write being incompatible with volatile semantics (see also #217).

[v0.12.2]

Fixed

• [#251](rust-vmm/vm-memory#251): Inserted checks that verify that the value returned by VolatileMemory::get_slice is of the correct length.

Deprecated

• [#244](rust-vmm/vm-memory#241) Deprecate volatile memory's as_ptr() interfaces. The new interfaces to be used instead are: ptr_guard() and ptr_guard_mut().

[v0.12.1]

Fixed

• [#241](rust-vmm/vm-memory#245) mmap_xen: Don't drop the FileOffset while in use #245

[v0.12.0]

Added

• [#241](rust-vmm/vm-memory#241) Add Xen memory mapping support: Foreign and Grant. Add new API for accessing pointers to volatile slices, as as_ptr() can't be used with Xen's Grant mapping.
• [#237](rust-vmm/vm-memory#237) Implement ByteValued for i/u128.

[v0.11.0]

Added

• [#216](rust-vmm/vm-memory#216) Add GuestRegionMmap::from_region.

Fixed

• [#217](rust-vmm/vm-memory#217) Fix vm-memory internally taking rust-style slices to guest memory in ways that could potentially cause

... (truncated)

Commits

• a6bcb43 chore: Prepare release 0.13.0
• 51a6c74 Add CHANGELOG entry about ReadVolatile/WriteVolatile
• 20135ce Adjust coverage
• 7a911a4 Add read_volatile_from/write_volatile_to to GuestMemory
• 9c3e6aa test: Add tests for VolatileRead/Write
• 0173112 feat: Introduce Read/WriteVolatile traits
• aff1dd4 fix: Validate return value of get_slice in VolatileMemory
• 06ebc2a build(deps): bump rust-vmm-ci from 9dfe5b2 to 7c1057e
• a3f96c3 volatile_memory: Deprecate .as_ptr() interfaces
• d913c99 build(deps): bump rust-vmm-ci from 285971e to 9dfe5b2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[stefano-garzarella]

We need to wait a new version of virtio-queue before updating vm-memory.

[Ablu]

We need to wait a new version of virtio-queue before updating vm-memory.

Is anyone working on that version bump? Or do we just wait for a publish to happen?

[stefano-garzarella]

We need to wait a new version of virtio-queue before updating vm-memory.

Is anyone working on that version bump? Or do we just wait for a publish to happen?

IIRC the last time I checked the main branch, it still used v0.12.0, so I don't think a release will happen soon.
Maybe we can postpone this PR for the next release.

[Ablu]

I am a bit confused why there is no bump PR open on vm-virtio... Did dependabot get stuck there somewhere? But I agree, since vm-virtio does not have 0.13 in main, waiting for this will probably mean waiting for quite some time.

[Ablu]

rust-vmm/vm-memory#256 (review) goes a long way to resolve the issues in vm-virtio.

[stefano-garzarella]

@dependabot rebase

[dependabot]

Superseded by #197.