cloud-hypervisor/vm-migration/Cargo.toml

[package]
name = "vm-migration"
version = "0.1.0"
authors = ["The Cloud Hypervisor Authors"]
edition = "2018"

[dependencies]
anyhow = "1.0"
thiserror = "1.0"
serde = {version = ">=1.0.27", features = ["rc"] }
serde_derive = ">=1.0.27"
serde_json = ">=1.0.9"
vm-memory = { version = "0.5.0", features = ["backend-mmap", "backend-atomic"] }
vm-migration: Define the Snapshottable and Transportable traits A Snapshottable component can snapshot itself and provide a MigrationSnapshot payload as a result. A MigrationSnapshot payload is a map of component IDs to a list of migration sections (MigrationSection). As component can be made of several Migratable sub-components (e.g. the DeviceManager and its device objects), a migration snapshot can be made of multiple snapshot itself. A snapshot is a list of migration sections, each section being a component state snapshot. Having multiple sections allows for easier and backward compatible migration payload extensions. Once created, a migratable component snapshot may be transported and this is what the Transportable trait defines, through 2 methods: send and recv. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: Yi Sun <yi.y.sun@linux.intel.com> 2019-05-01 16:59:51 +00:00			`[package]`
			`name = "vm-migration"`
			`version = "0.1.0"`
			`authors = ["The Cloud Hypervisor Authors"]`
			`edition = "2018"`

			`[dependencies]`
			`anyhow = "1.0"`
			`thiserror = "1.0"`
			`serde = {version = ">=1.0.27", features = ["rc"] }`
			`serde_derive = ">=1.0.27"`
			`serde_json = ">=1.0.9"`
vm-migration: Use vm-memory's ByteValued instead of own AsBytes This addresses a newly added clippy issue: error: methods called `as_*` usually take self by reference or self by mutable reference; consider choosing a less ambiguous name --> vm-migration/src/protocol.rs:57:34 \| 57 \| fn as_mut_bytes<T: Sized>(p: &mut T) -> &mut [u8] { \| ^^^^^^ \| = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#wrong_self_convention error: aborting due to 2 previous errors error: could not compile `vm-migration` Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2021-02-11 15:55:00 +00:00			`vm-memory = { version = "0.5.0", features = ["backend-mmap", "backend-atomic"] }`