External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-07-02 16:02:37 +00:00
Code Issues Packages Projects Releases Wiki Activity
7e146a2057
cloud-hypervisor/Cargo.lock

1463 lines
30 KiB
Plaintext
Raw Normal View History

build: Switch over to using rust-vmm linux-loader crate With everything now merged upstream we no longer need to rely on Cathy's fork. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-06-13 10:07:32 +00:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
devices: Move to versioned snapshots Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-11 14:26:09 +00:00
version = 3
acpi_tables: Add initial ACPI tables support Add a revision 2 RSDP table only supporting an XSDT along with support for creating generic SDT based tables. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-07 16:53:37 +00:00
[[package]]
name = "acpi_tables"
version = "0.1.0"
dependencies = [
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
acpi_tables: Add initial ACPI tables support Add a revision 2 RSDP table only supporting an XSDT along with support for creating generic SDT based tables. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-07 16:53:37 +00:00
]
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
[[package]]
name = "aho-corasick"
build: Bump regex from 1.4.6 to 1.5.3 Bumps [regex](https://github.com/rust-lang/regex) from 1.4.6 to 1.5.3. - [Release notes](https://github.com/rust-lang/regex/releases) - [Changelog](https://github.com/rust-lang/regex/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/regex/compare/1.4.6...1.5.3) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-03 10:06:31 +00:00
version = "0.7.18"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump regex from 1.4.6 to 1.5.3 Bumps [regex](https://github.com/rust-lang/regex) from 1.4.6 to 1.5.3. - [Release notes](https://github.com/rust-lang/regex/releases) - [Changelog](https://github.com/rust-lang/regex/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/regex/compare/1.4.6...1.5.3) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-03 10:06:31 +00:00
checksum = "1e37cfd5e7657ada45f742d6e99ca5788580b5c529dc78faf11ece6dc702656f"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
dependencies = [
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
"memchr",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-18 14:30:54 +00:00
[[package]]
name = "anyhow"
build: bump anyhow from 1.0.53 to 1.0.55 Bumps [anyhow](https://github.com/dtolnay/anyhow) from 1.0.53 to 1.0.55. - [Release notes](https://github.com/dtolnay/anyhow/releases) - [Commits](https://github.com/dtolnay/anyhow/compare/1.0.53...1.0.55) --- updated-dependencies: - dependency-name: anyhow dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-21 23:10:51 +00:00
version = "1.0.55"
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-18 14:30:54 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump anyhow from 1.0.53 to 1.0.55 Bumps [anyhow](https://github.com/dtolnay/anyhow) from 1.0.53 to 1.0.55. - [Release notes](https://github.com/dtolnay/anyhow/releases) - [Commits](https://github.com/dtolnay/anyhow/compare/1.0.53...1.0.55) --- updated-dependencies: - dependency-name: anyhow dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-21 23:10:51 +00:00
checksum = "159bb86af3a200e19a068f4224eae4c8bb2d0fa054c7e5d1cacd5cef95e684cd"
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-18 14:30:54 +00:00
ch-remote, api_client: Split HTTP/API client code into new crate Split out the HTTP request handling code from ch-remote into a new crate which can be used in other places where talking to the API server by HTTP is necessary. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-10-23 10:20:37 +00:00
[[package]]
name = "api_client"
version = "0.1.0"
api_client: Add ability to send file descriptors Allow the user to send a list of file descriptors along with the HTTP request. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-07-20 13:31:32 +00:00
dependencies = [
"vmm-sys-util",
]
ch-remote, api_client: Split HTTP/API client code into new crate Split out the HTTP request handling code from ch-remote into a new crate which can be used in other places where talking to the API server by HTTP is necessary. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-10-23 10:20:37 +00:00
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
[[package]]
name = "arc-swap"
build: bump arc-swap from 1.4.0 to 1.5.0 Bumps [arc-swap](https://github.com/vorner/arc-swap) from 1.4.0 to 1.5.0. - [Release notes](https://github.com/vorner/arc-swap/releases) - [Changelog](https://github.com/vorner/arc-swap/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/arc-swap/compare/v1.4.0...v1.5.0) --- updated-dependencies: - dependency-name: arc-swap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2021-11-15 23:09:49 +00:00
version = "1.5.0"
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump arc-swap from 1.4.0 to 1.5.0 Bumps [arc-swap](https://github.com/vorner/arc-swap) from 1.4.0 to 1.5.0. - [Release notes](https://github.com/vorner/arc-swap/releases) - [Changelog](https://github.com/vorner/arc-swap/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/arc-swap/compare/v1.4.0...v1.5.0) --- updated-dependencies: - dependency-name: arc-swap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2021-11-15 23:09:49 +00:00
checksum = "c5d78ce20460b82d3fa150275ed9d55e21064fc7951177baacf86a145c4a4b1f"
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 13:16:58 +00:00
[[package]]
name = "arch"
version = "0.1.0"
dependencies = [
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
"acpi_tables",
arch, pci, vmm: Initial switch to the hypervisor crate Start moving the vmm, arch and pci crates to being hypervisor agnostic by using the hypervisor trait and abstractions. This is not a complete switch and there are still some remaining KVM dependencies. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-02 02:29:54 +00:00
"anyhow",
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
"byteorder",
build: Add missing Cargo.lock change Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-06-18 14:24:33 +00:00
"fdt",
arch, pci, vmm: Initial switch to the hypervisor crate Start moving the vmm, arch and pci crates to being hypervisor agnostic by using the hypervisor trait and abstractions. This is not a complete switch and there are still some remaining KVM dependencies. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-02 02:29:54 +00:00
"hypervisor",
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
"libc",
"linux-loader",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
build: Update Cargo.lock Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-09-23 16:20:55 +00:00
"serde",
migration: Use MemoryManager restore code path Instead of creating a MemoryManager from scratch, let's reuse the same code path used by snapshot/restore, so that memory regions are created identically to what they were on the source VM. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-05 15:53:08 +00:00
"serde_derive",
arch: Include "thiserror" crate as well as "anyhow" Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-02-03 10:23:35 +00:00
"thiserror",
arch: aarch64: Versionize Gicv3State Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-26 15:06:28 +00:00
"versionize",
"versionize_derive",
build: Bump vhost from `c4cd1d3` to `cc4da71` Bumps [vhost](https://github.com/rust-vmm/vhost) from `c4cd1d3` to `cc4da71`. - [Release notes](https://github.com/rust-vmm/vhost/releases) - [Commits](https://github.com/rust-vmm/vhost/compare/c4cd1d375e386069d0b781174de9f62ef41812e2...cc4da710ac68ca8ffe68cddcd80d562699445522) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-10 10:19:24 +00:00
"vm-fdt",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
build: Update Cargo.lock Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-09-23 16:20:55 +00:00
"vm-migration",
arch, vmm: Move "generate_common_cpuid" from "CpuManager" to "arch" This refactoring ensures all CPUID related operations are centralized in `arch::x86_64` module, and exposes only two related public functions to the vmm crate, e.g. `generate_common_cpuid` and `configure_vcpu`. Signed-off-by: Bo Chen <chen.bo@intel.com>
2021-07-14 21:44:38 +00:00
"vmm-sys-util",
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 13:16:58 +00:00
]
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
[[package]]
name = "atty"
build(deps): bump atty from 0.2.13 to 0.2.14 Bumps [atty](https://github.com/softprops/atty) from 0.2.13 to 0.2.14. - [Release notes](https://github.com/softprops/atty/releases) - [Changelog](https://github.com/softprops/atty/blob/master/CHANGELOG.md) - [Commits](https://github.com/softprops/atty/compare/0.2.13...0.2.14) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-05 22:32:54 +00:00
version = "0.2.14"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
dependencies = [
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
"hermit-abi",
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"winapi",
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
]
build(deps): bump openssl-sys from 0.9.53 to 0.9.54 Bumps [openssl-sys](https://github.com/sfackler/rust-openssl) from 0.9.53 to 0.9.54. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-sys-v0.9.53...openssl-sys-v0.9.54) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-30 07:46:26 +00:00
[[package]]
name = "autocfg"
build: bump autocfg from 1.0.1 to 1.1.0 Bumps [autocfg](https://github.com/cuviper/autocfg) from 1.0.1 to 1.1.0. - [Release notes](https://github.com/cuviper/autocfg/releases) - [Commits](https://github.com/cuviper/autocfg/compare/1.0.1...1.1.0) --- updated-dependencies: - dependency-name: autocfg dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-07 23:16:06 +00:00
version = "1.1.0"
build(deps): bump openssl-sys from 0.9.53 to 0.9.54 Bumps [openssl-sys](https://github.com/sfackler/rust-openssl) from 0.9.53 to 0.9.54. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-sys-v0.9.53...openssl-sys-v0.9.54) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-30 07:46:26 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump autocfg from 1.0.1 to 1.1.0 Bumps [autocfg](https://github.com/cuviper/autocfg) from 1.0.1 to 1.1.0. - [Release notes](https://github.com/cuviper/autocfg/releases) - [Commits](https://github.com/cuviper/autocfg/compare/1.0.1...1.1.0) --- updated-dependencies: - dependency-name: autocfg dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-07 23:16:06 +00:00
checksum = "d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa"
build(deps): bump openssl-sys from 0.9.53 to 0.9.54 Bumps [openssl-sys](https://github.com/sfackler/rust-openssl) from 0.9.53 to 0.9.54. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-sys-v0.9.53...openssl-sys-v0.9.54) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-30 07:46:26 +00:00
vm-migration: Add versioned versions of snapshot & state API This will allow progressive porting of parts of the VMM to using versioned state. A new trait VersionMapped is introduced with a default implementation that returns an empty VersionMap to ease implementation. If a struct is updated the the trait will need to be fully implemented with VersionMapped::version_map() returning a new VersionMap handling the change. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-05 15:16:19 +00:00
[[package]]
name = "bincode"
version = "1.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b1f45e9417d87227c7a56d22e471c6206462cba514c7590c09aff4cf6d1ddcad"
dependencies = [
"serde",
]
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-03-07 13:56:43 +00:00
[[package]]
name = "bitflags"
build: bump bitflags from 1.3.1 to 1.3.2 Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.1 to 1.3.2. - [Release notes](https://github.com/bitflags/bitflags/releases) - [Changelog](https://github.com/bitflags/bitflags/blob/main/CHANGELOG.md) - [Commits](https://github.com/bitflags/bitflags/compare/1.3.1...1.3.2) --- updated-dependencies: - dependency-name: bitflags dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-16 23:11:36 +00:00
version = "1.3.2"
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-03-07 13:56:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump bitflags from 1.3.1 to 1.3.2 Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.1 to 1.3.2. - [Release notes](https://github.com/bitflags/bitflags/releases) - [Changelog](https://github.com/bitflags/bitflags/blob/main/CHANGELOG.md) - [Commits](https://github.com/bitflags/bitflags/compare/1.3.1...1.3.2) --- updated-dependencies: - dependency-name: bitflags dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-16 23:11:36 +00:00
checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-03-07 13:56:43 +00:00
vhost_user_block, virtio-devices, block_util: Extract common block code Extract the code that is used by vhost_user_block from the virtio-devices crate to remove the dependencies on unrequired functionality such as the virtio transports. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-14 09:43:33 +00:00
[[package]]
name = "block_util"
version = "0.1.0"
dependencies = [
block_util: Add utilities to support io_uring Creates a dedicated function relying on io_uring crate to execute io_uring specific requests. Also creates a function for checking io_uring support on the host. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-07-27 13:58:53 +00:00
"io-uring",
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
block_util: Port synchronous RAW file to AsyncIo trait Based on the synchronous RAW file implementation present in the qcow crate, we created a new raw_sync module in block_util that ports this synchronous implementation to the AsyncIo trait. The point is to reuse virtio-blk asynchronous implementation for both synchronous and asynchronous backends. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-01-20 18:03:59 +00:00
"qcow",
block_util: Add new traits for handling disk files asynchronously Both DiskFile and AsyncIo traits are introduced to allow all kind of files (RAW, QCOW, VHD) to be able to handle asynchronous access to the underlying file. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-01-20 09:53:27 +00:00
"thiserror",
virtio-devices: Version state structures Version the state for device state for the virtio devices. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-06 13:34:31 +00:00
"versionize",
"versionize_derive",
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
"vhdx",
vhost_user_block, virtio-devices, block_util: Extract common block code Extract the code that is used by vhost_user_block from the virtio-devices crate to remove the dependencies on unrequired functionality such as the virtio transports. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-14 09:43:33 +00:00
"virtio-bindings",
Move Cloud Hypervisor to virtio-queue crate Relying on the vm-virtio/virtio-queue crate from rust-vmm which has been copied inside the Cloud Hypervisor tree, the entire codebase is moved to the new definition of a Queue and other related structures. The reason for this move is to follow the upstream until we get some agreement for the patches that we need on top of that to make it properly work with Cloud Hypervisor. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-21 10:41:16 +00:00
"virtio-queue",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
vhost_user_block, virtio-devices, block_util: Extract common block code Extract the code that is used by vhost_user_block from the virtio-devices crate to remove the dependencies on unrequired functionality such as the virtio transports. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-14 09:43:33 +00:00
"vm-virtio",
block_util: Add utilities to support io_uring Creates a dedicated function relying on io_uring crate to execute io_uring specific requests. Also creates a function for checking io_uring support on the host. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-07-27 13:58:53 +00:00
"vmm-sys-util",
vhost_user_block, virtio-devices, block_util: Extract common block code Extract the code that is used by vhost_user_block from the virtio-devices crate to remove the dependencies on unrequired functionality such as the virtio transports. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-14 09:43:33 +00:00
]
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 13:16:58 +00:00
[[package]]
name = "byteorder"
build(deps): bump byteorder from 1.4.2 to 1.4.3 Bumps [byteorder](https://github.com/BurntSushi/byteorder) from 1.4.2 to 1.4.3. - [Release notes](https://github.com/BurntSushi/byteorder/releases) - [Changelog](https://github.com/BurntSushi/byteorder/blob/master/CHANGELOG.md) - [Commits](https://github.com/BurntSushi/byteorder/compare/1.4.2...1.4.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-03-10 12:36:39 +00:00
version = "1.4.3"
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 13:16:58 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump byteorder from 1.4.2 to 1.4.3 Bumps [byteorder](https://github.com/BurntSushi/byteorder) from 1.4.2 to 1.4.3. - [Release notes](https://github.com/BurntSushi/byteorder/releases) - [Changelog](https://github.com/BurntSushi/byteorder/blob/master/CHANGELOG.md) - [Commits](https://github.com/BurntSushi/byteorder/compare/1.4.2...1.4.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-03-10 12:36:39 +00:00
checksum = "14c189c53d098945499cdfa7ecc63567cf3886b3332b312a5b4585d8d3a6a610"
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 13:16:58 +00:00
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
[[package]]
name = "cc"
build: bump cc from 1.0.72 to 1.0.73 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.72 to 1.0.73. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.72...1.0.73) --- updated-dependencies: - dependency-name: cc dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-16 23:13:28 +00:00
version = "1.0.73"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump cc from 1.0.72 to 1.0.73 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.72 to 1.0.73. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.72...1.0.73) --- updated-dependencies: - dependency-name: cc dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-16 23:13:28 +00:00
checksum = "2fff2a6927b3bb87f9595d67196a70493f627687a71d87a0d692242c33f58c11"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
build(deps): bump backtrace from 0.3.52 to 0.3.53 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.52 to 0.3.53. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.52...0.3.53) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-10-11 17:22:55 +00:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
[[package]]
name = "clap"
build: bump clap from 3.1.3 to 3.1.5 Bumps [clap](https://github.com/clap-rs/clap) from 3.1.3 to 3.1.5. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v3.1.3...v3.1.5) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-02 23:27:37 +00:00
version = "3.1.5"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump clap from 3.1.3 to 3.1.5 Bumps [clap](https://github.com/clap-rs/clap) from 3.1.3 to 3.1.5. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v3.1.3...v3.1.5) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-02 23:27:37 +00:00
checksum = "ced1892c55c910c1219e98d6fc8d71f6bddba7905866ce740066d8bfea859312"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
dependencies = [
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
"atty",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"bitflags",
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
"indexmap",
"lazy_static",
"os_str_bytes",
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
"strsim",
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
"termcolor",
"terminal_size",
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
"textwrap",
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
]
cloud-hypervisor: Initial commit Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:04:44 +00:00
[[package]]
name = "cloud-hypervisor"
build: Release v22.0 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-03-03 12:34:59 +00:00
version = "22.0.0"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
dependencies = [
main: Simplify error and return handling in start_vmm Use a Result<> type with an error to simplify the code in start_vmm(). This will also make it easier to add cleanup funtionality. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-10-26 16:16:56 +00:00
"anyhow",
ch-remote, api_client: Split HTTP/API client code into new crate Split out the HTTP request handling code from ch-remote into a new crate which can be used in other places where talking to the API server by HTTP is necessary. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-10-23 10:20:37 +00:00
"api_client",
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
"clap",
build: Use consistent version of dirs crate Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-03-03 15:47:14 +00:00
"dirs",
tests: Wait explicitly for the guest vm to boot Instead of blindly waiting for 20-40s for the guest VM to boot, this patch waits the notification from the guest VM explicitly by using a simple TcpListener on the host and a custom systemd service in the guest. This patch also ported few tests to use this new machanism, while more tests are to be ported. Signed-off-by: Bo Chen <chen.bo@intel.com>
2020-10-26 23:46:04 +00:00
"epoll",
main: Add "--monitor-fd" to write structured event data to If supplied then structured JSON event data will be written to that file descriptor. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-02-17 11:19:39 +00:00
"event_monitor",
hypervisor: Introduce hypervisor crate The purpose of this trait is to add support for other hypervisors than KVM, like e.g. Microsoft Hyper-V. Further commits will define additional hypervisor related traits like Vcpu and Vm. Each of the supported hypervisor will need to implement all traits defined from the hypervisor crate. Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-06-08 00:50:38 +00:00
"hypervisor",
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
"lazy_static",
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
tests: Add tests checking for host MAC address setting Extend the set of tests we have for virtio-net and vhost-user-net to check for host MAC address setting. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-05-15 09:19:51 +00:00
"net_util",
ch-remote: Support using unit suffices for "resize" Remove the requirement for the user to calculate the size they want in bytes. Fixes: #1596 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-09-08 14:51:00 +00:00
"option_parser",
virtio-devices, vmm: Move to the seccompiler crate Fixes: #2929 Signed-off-by: Bo Chen <chen.bo@intel.com>
2021-08-17 03:40:11 +00:00
"seccompiler",
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
"serde_json",
main: Give a friendly message when we get a seccomp violation If we receive SIGSYS and identify it as a seccomp violation then give friendly instructions on how to debug further. We are unable to decode the siginfo_t struct ourselves due to https://github.com/rust-lang/libc/issues/716 Fixes: #2139 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-01-11 18:32:35 +00:00
"signal-hook",
tests: Move test_infra from a module to crate It must be specified as excluded from the workspace as it must not be built on non-test targets due to issues with the ssh2 dependency and the musl toolchain. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-03-23 16:15:48 +00:00
"test_infra",
main: Simplify error and return handling in start_vmm Use a Result<> type with an error to simplify the code in start_vmm(). This will also make it easier to add cleanup funtionality. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-10-26 16:16:56 +00:00
"thiserror",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
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
"vmm",
"vmm-sys-util",
tests: Wait explicitly for vm shutdown w/ the 'wait-timeout' crate Instead of waiting blindly with fixed amount of sleeping time, we can use the `wait-timeout` crate to explicitly wait VM shutdown (with a timeout). It can reduces the execution time of some tests substantially. Also, this patch increases the `shutdown` timeout for 'test_reboot', which should fix the recent sporadic failures on this test. Signed-off-by: Bo Chen <chen.bo@intel.com>
2020-10-28 23:40:50 +00:00
"wait-timeout",
cloud-hypervisor: Call into the test_vm() routine test_vm is a dummy VM workload, we use it to test our initial VMM settings. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-22 16:05:02 +00:00
]
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
[[package]]
name = "crc32c"
build: bump crc32c from 0.6.0 to 0.6.1 Bumps [crc32c](https://github.com/zowens/crc32c) from 0.6.0 to 0.6.1. - [Release notes](https://github.com/zowens/crc32c/releases) - [Commits](https://github.com/zowens/crc32c/commits/v0.6.1) --- updated-dependencies: - dependency-name: crc32c dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-05 23:46:55 +00:00
version = "0.6.1"
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump crc32c from 0.6.0 to 0.6.1 Bumps [crc32c](https://github.com/zowens/crc32c) from 0.6.0 to 0.6.1. - [Release notes](https://github.com/zowens/crc32c/releases) - [Commits](https://github.com/zowens/crc32c/commits/v0.6.1) --- updated-dependencies: - dependency-name: crc32c dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-05 23:46:55 +00:00
checksum = "ee6b9c9389584bcba988bd0836086789b7f87ad91892d6a83d5291dbb24524b5"
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
dependencies = [
"rustc_version",
]
vm-migration: Add versioned versions of snapshot & state API This will allow progressive porting of parts of the VMM to using versioned state. A new trait VersionMapped is introduced with a default implementation that returns an empty VersionMap to ease implementation. If a struct is updated the the trait will need to be fully implemented with VersionMapped::version_map() returning a new VersionMap handling the change. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-05 15:16:19 +00:00
[[package]]
name = "crc64"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "55626594feae15d266d52440b26ff77de0e22230cf0c113abe619084c1ddc910"
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-03-07 13:56:43 +00:00
[[package]]
name = "devices"
version = "0.1.0"
dependencies = [
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
"acpi_tables",
devices: ioapic: Implement the Snapshottable trait Signed-off-by: Yi Sun <yi.y.sun@linux.intel.com>
2019-12-12 01:36:13 +00:00
"anyhow",
virtio-devices: vhost_user: Enable most virtio reserved features A lot of the VIRTIO reserved features should be supported or not by the vhost-user backend. That means on the VMM side, these features should be available, so that they don't get lost during the negotiation. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-05-21 16:26:00 +00:00
"arch",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"bitflags",
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
"byteorder",
"epoll",
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
devices: Move to versioned snapshots Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-11 14:26:09 +00:00
"versionize",
"versionize_derive",
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
"vm-device",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
devices: ioapic: Implement the Snapshottable trait Signed-off-by: Yi Sun <yi.y.sun@linux.intel.com>
2019-12-12 01:36:13 +00:00
"vm-migration",
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
"vmm-sys-util",
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-03-07 13:56:43 +00:00
]
build: bump dirs from 3.0.2 to 4.0.0 Bumps [dirs](https://github.com/soc/dirs-rs) from 3.0.2 to 4.0.0. - [Release notes](https://github.com/soc/dirs-rs/releases) - [Commits](https://github.com/soc/dirs-rs/commits) --- updated-dependencies: - dependency-name: dirs dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2021-09-15 23:09:12 +00:00
[[package]]
name = "dirs"
version = "4.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ca3aa72a6f96ea37bbc5aa912f6788242832f75369bdfdadcb0e38423f100059"
dependencies = [
"dirs-sys",
]
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
[[package]]
name = "dirs-sys"
build(deps): bump dirs from 3.0.1 to 3.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/soc/dirs-rs/releases) - [Commits](https://github.com/soc/dirs-rs/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-04-23 22:44:20 +00:00
version = "0.3.6"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump dirs from 3.0.1 to 3.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/soc/dirs-rs/releases) - [Commits](https://github.com/soc/dirs-rs/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-04-23 22:44:20 +00:00
checksum = "03d86534ed367a67548dc68113a0f5db55432fdfbb6e6f9d77704397d95d5780"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
dependencies = [
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
"libc",
"redox_users",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"winapi",
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
]
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
[[package]]
name = "env_logger"
build: bump env_logger from 0.8.4 to 0.9.0 Bumps [env_logger](https://github.com/env-logger-rs/env_logger) from 0.8.4 to 0.9.0. - [Release notes](https://github.com/env-logger-rs/env_logger/releases) - [Changelog](https://github.com/env-logger-rs/env_logger/blob/main/CHANGELOG.md) - [Commits](https://github.com/env-logger-rs/env_logger/compare/v0.8.4...v0.9.0) --- updated-dependencies: - dependency-name: env_logger dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2021-07-14 23:09:44 +00:00
version = "0.9.0"
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump env_logger from 0.8.4 to 0.9.0 Bumps [env_logger](https://github.com/env-logger-rs/env_logger) from 0.8.4 to 0.9.0. - [Release notes](https://github.com/env-logger-rs/env_logger/releases) - [Changelog](https://github.com/env-logger-rs/env_logger/blob/main/CHANGELOG.md) - [Commits](https://github.com/env-logger-rs/env_logger/compare/v0.8.4...v0.9.0) --- updated-dependencies: - dependency-name: env_logger dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2021-07-14 23:09:44 +00:00
checksum = "0b2cf0344971ee6c64c31be0d530793fba457d322dfec2810c453d0ef228f9c3"
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
dependencies = [
"atty",
"humantime",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
"regex",
"termcolor",
]
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-03-07 13:56:43 +00:00
[[package]]
name = "epoll"
build(deps): bump epoll from 4.3.0 to 4.3.1 Bumps [epoll](https://github.com/nathansizemore/epoll) from 4.3.0 to 4.3.1. - [Release notes](https://github.com/nathansizemore/epoll/releases) - [Commits](https://github.com/nathansizemore/epoll/commits/4.3.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-06-25 13:31:37 +00:00
version = "4.3.1"
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-03-07 13:56:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump epoll from 4.3.0 to 4.3.1 Bumps [epoll](https://github.com/nathansizemore/epoll) from 4.3.0 to 4.3.1. - [Release notes](https://github.com/nathansizemore/epoll/releases) - [Commits](https://github.com/nathansizemore/epoll/commits/4.3.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-06-25 13:31:37 +00:00
checksum = "20df693c700404f7e19d4d6fae6b15215d2913c27955d2b9d6f2c0f537511cd0"
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-03-07 13:56:43 +00:00
dependencies = [
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"bitflags",
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
"libc",
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-03-07 13:56:43 +00:00
]
event_monitor: Add new crate for event reporting This crate exposes the abililty for the VMM to set a file that events should be written to. The event!() macro provides an interface to report those events allowing the specification of an event source, an event type and optional extra data. This will be written to the provided file descriptor as JSON data. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-02-17 11:16:00 +00:00
[[package]]
name = "event_monitor"
version = "0.1.0"
dependencies = [
"libc",
"serde",
"serde_derive",
"serde_json",
]
build: Add missing Cargo.lock change Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-06-18 14:24:33 +00:00
[[package]]
name = "fdt"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b643857cf70949306b81d7e92cb9d47add673868edac9863c4a49c42feaf3f1e"
vmm: Add `Debuggable` trait implementation This commit adds initial gdb.rs implementation for `Debuggable` trait to describe a debuggable component. Some part of the trait bound implementations is based on the crosvm GDB stub code [1]. [1] https://github.com/google/crosvm/blob/main/src/gdb.rs Signed-off-by: Akira Moroo <retrage01@gmail.com>
2022-02-20 03:17:50 +00:00
[[package]]
name = "gdbstub"
build: bump gdbstub from 0.6.0 to 0.6.1 Bumps [gdbstub](https://github.com/daniel5151/gdbstub) from 0.6.0 to 0.6.1. - [Release notes](https://github.com/daniel5151/gdbstub/releases) - [Changelog](https://github.com/daniel5151/gdbstub/blob/master/CHANGELOG.md) - [Commits](https://github.com/daniel5151/gdbstub/compare/0.6.0...0.6.1) --- updated-dependencies: - dependency-name: gdbstub dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-24 00:47:20 +00:00
version = "0.6.1"
vmm: Add `Debuggable` trait implementation This commit adds initial gdb.rs implementation for `Debuggable` trait to describe a debuggable component. Some part of the trait bound implementations is based on the crosvm GDB stub code [1]. [1] https://github.com/google/crosvm/blob/main/src/gdb.rs Signed-off-by: Akira Moroo <retrage01@gmail.com>
2022-02-20 03:17:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump gdbstub from 0.6.0 to 0.6.1 Bumps [gdbstub](https://github.com/daniel5151/gdbstub) from 0.6.0 to 0.6.1. - [Release notes](https://github.com/daniel5151/gdbstub/releases) - [Changelog](https://github.com/daniel5151/gdbstub/blob/master/CHANGELOG.md) - [Commits](https://github.com/daniel5151/gdbstub/compare/0.6.0...0.6.1) --- updated-dependencies: - dependency-name: gdbstub dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-24 00:47:20 +00:00
checksum = "9fa2ca5d6b045de372cef3991f873389b421b4cabcfbe52f7787fae8b8b37906"
vmm: Add `Debuggable` trait implementation This commit adds initial gdb.rs implementation for `Debuggable` trait to describe a debuggable component. Some part of the trait bound implementations is based on the crosvm GDB stub code [1]. [1] https://github.com/google/crosvm/blob/main/src/gdb.rs Signed-off-by: Akira Moroo <retrage01@gmail.com>
2022-02-20 03:17:50 +00:00
dependencies = [
"bitflags",
"cfg-if",
"log",
"managed",
"num-traits",
"paste",
]
[[package]]
name = "gdbstub_arch"
build: bump gdbstub_arch from 0.2.0 to 0.2.2 Bumps [gdbstub_arch](https://github.com/daniel5151/gdbstub) from 0.2.0 to 0.2.2. - [Release notes](https://github.com/daniel5151/gdbstub/releases) - [Changelog](https://github.com/daniel5151/gdbstub/blob/master/CHANGELOG.md) - [Commits](https://github.com/daniel5151/gdbstub/commits/0.2.2) --- updated-dependencies: - dependency-name: gdbstub_arch dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-24 02:00:16 +00:00
version = "0.2.2"
vmm: Add `Debuggable` trait implementation This commit adds initial gdb.rs implementation for `Debuggable` trait to describe a debuggable component. Some part of the trait bound implementations is based on the crosvm GDB stub code [1]. [1] https://github.com/google/crosvm/blob/main/src/gdb.rs Signed-off-by: Akira Moroo <retrage01@gmail.com>
2022-02-20 03:17:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump gdbstub_arch from 0.2.0 to 0.2.2 Bumps [gdbstub_arch](https://github.com/daniel5151/gdbstub) from 0.2.0 to 0.2.2. - [Release notes](https://github.com/daniel5151/gdbstub/releases) - [Changelog](https://github.com/daniel5151/gdbstub/blob/master/CHANGELOG.md) - [Commits](https://github.com/daniel5151/gdbstub/commits/0.2.2) --- updated-dependencies: - dependency-name: gdbstub_arch dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-24 02:00:16 +00:00
checksum = "51dc4b5718ac76d21e8605c0966dd32d80273b89b11e6cfef467b04e45934d37"
vmm: Add `Debuggable` trait implementation This commit adds initial gdb.rs implementation for `Debuggable` trait to describe a debuggable component. Some part of the trait bound implementations is based on the crosvm GDB stub code [1]. [1] https://github.com/google/crosvm/blob/main/src/gdb.rs Signed-off-by: Akira Moroo <retrage01@gmail.com>
2022-02-20 03:17:50 +00:00
dependencies = [
"gdbstub",
"num-traits",
]
vm-virtio: Add virtio console device for single port operation The virtio console device is a console for the communication between the host and guest userspace. It has two parts: the device and the driver. The console device is implemented here as a virtio-pci device to the guest. On the other side, the guest OS expected to have a character device driver which provides an interface to the userspace applications. The console device can have multiple ports where each port has one transmit queue and one receive queue. The current implementation only supports one port. For data IO communication, one or more empty buffers are placed in the receive queue for incoming data, and outgoing characters are placed in the transmit queue. Details spec can be found from the following link. https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.pdf#e7 Apart from the console, for the communication between guest and host, the Cloud Hypervisor has a legacy serial device implemented. However, the implementation of a console device lets us be independent of legacy pin-based interrupts without losing the logs and access to the VM. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-22 18:50:56 +00:00
[[package]]
name = "getrandom"
build: bump getrandom from 0.2.4 to 0.2.5 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.2.4 to 0.2.5. - [Release notes](https://github.com/rust-random/getrandom/releases) - [Changelog](https://github.com/rust-random/getrandom/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/getrandom/compare/v0.2.4...v0.2.5) --- updated-dependencies: - dependency-name: getrandom dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-22 23:12:24 +00:00
version = "0.2.5"
vm-virtio: Add virtio console device for single port operation The virtio console device is a console for the communication between the host and guest userspace. It has two parts: the device and the driver. The console device is implemented here as a virtio-pci device to the guest. On the other side, the guest OS expected to have a character device driver which provides an interface to the userspace applications. The console device can have multiple ports where each port has one transmit queue and one receive queue. The current implementation only supports one port. For data IO communication, one or more empty buffers are placed in the receive queue for incoming data, and outgoing characters are placed in the transmit queue. Details spec can be found from the following link. https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.pdf#e7 Apart from the console, for the communication between guest and host, the Cloud Hypervisor has a legacy serial device implemented. However, the implementation of a console device lets us be independent of legacy pin-based interrupts without losing the logs and access to the VM. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-22 18:50:56 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump getrandom from 0.2.4 to 0.2.5 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.2.4 to 0.2.5. - [Release notes](https://github.com/rust-random/getrandom/releases) - [Changelog](https://github.com/rust-random/getrandom/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/getrandom/compare/v0.2.4...v0.2.5) --- updated-dependencies: - dependency-name: getrandom dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-22 23:12:24 +00:00
checksum = "d39cd93900197114fa1fcb7ae84ca742095eed9442088988ae74fa744e930e77"
vm-virtio: Add virtio console device for single port operation The virtio console device is a console for the communication between the host and guest userspace. It has two parts: the device and the driver. The console device is implemented here as a virtio-pci device to the guest. On the other side, the guest OS expected to have a character device driver which provides an interface to the userspace applications. The console device can have multiple ports where each port has one transmit queue and one receive queue. The current implementation only supports one port. For data IO communication, one or more empty buffers are placed in the receive queue for incoming data, and outgoing characters are placed in the transmit queue. Details spec can be found from the following link. https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.pdf#e7 Apart from the console, for the communication between guest and host, the Cloud Hypervisor has a legacy serial device implemented. However, the implementation of a console device lets us be independent of legacy pin-based interrupts without losing the logs and access to the VM. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-22 18:50:56 +00:00
dependencies = [
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
"cfg-if",
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
"libc",
"wasi",
vm-virtio: Add virtio console device for single port operation The virtio console device is a console for the communication between the host and guest userspace. It has two parts: the device and the driver. The console device is implemented here as a virtio-pci device to the guest. On the other side, the guest OS expected to have a character device driver which provides an interface to the userspace applications. The console device can have multiple ports where each port has one transmit queue and one receive queue. The current implementation only supports one port. For data IO communication, one or more empty buffers are placed in the receive queue for incoming data, and outgoing characters are placed in the transmit queue. Details spec can be found from the following link. https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.pdf#e7 Apart from the console, for the communication between guest and host, the Cloud Hypervisor has a legacy serial device implemented. However, the implementation of a console device lets us be independent of legacy pin-based interrupts without losing the logs and access to the VM. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-22 18:50:56 +00:00
]
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
[[package]]
name = "glob"
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
version = "0.3.0"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
checksum = "9b919933a397b79c37e33b77bb2aa3dc8eb6e165ad809e58ff75bc7db2e34574"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
[[package]]
name = "hashbrown"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ab5ef0d4909ef3724cc8cce6ccc8572c5c817592e9285f5464f8e86f8bd3726e"
build(deps): bump atty from 0.2.13 to 0.2.14 Bumps [atty](https://github.com/softprops/atty) from 0.2.13 to 0.2.14. - [Release notes](https://github.com/softprops/atty/releases) - [Changelog](https://github.com/softprops/atty/blob/master/CHANGELOG.md) - [Commits](https://github.com/softprops/atty/compare/0.2.13...0.2.14) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-05 22:32:54 +00:00
[[package]]
name = "hermit-abi"
build: bump hermit-abi from 0.1.19 to 0.1.20 Bumps [hermit-abi](https://github.com/hermitcore/rusty-hermit) from 0.1.19 to 0.1.20. - [Release notes](https://github.com/hermitcore/rusty-hermit/releases) - [Commits](https://github.com/hermitcore/rusty-hermit/compare/hermit-abi-0.1.19...hermit-abi-0.1.20) --- updated-dependencies: - dependency-name: hermit-abi dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-10 08:47:06 +00:00
version = "0.1.20"
build(deps): bump atty from 0.2.13 to 0.2.14 Bumps [atty](https://github.com/softprops/atty) from 0.2.13 to 0.2.14. - [Release notes](https://github.com/softprops/atty/releases) - [Changelog](https://github.com/softprops/atty/blob/master/CHANGELOG.md) - [Commits](https://github.com/softprops/atty/compare/0.2.13...0.2.14) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-05 22:32:54 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump hermit-abi from 0.1.19 to 0.1.20 Bumps [hermit-abi](https://github.com/hermitcore/rusty-hermit) from 0.1.19 to 0.1.20. - [Release notes](https://github.com/hermitcore/rusty-hermit/releases) - [Commits](https://github.com/hermitcore/rusty-hermit/compare/hermit-abi-0.1.19...hermit-abi-0.1.20) --- updated-dependencies: - dependency-name: hermit-abi dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-10 08:47:06 +00:00
checksum = "c7a30908dbce072eca83216eab939d2290080e00ca71611b96a09e5cdce5f3fa"
build(deps): bump atty from 0.2.13 to 0.2.14 Bumps [atty](https://github.com/softprops/atty) from 0.2.13 to 0.2.14. - [Release notes](https://github.com/softprops/atty/releases) - [Changelog](https://github.com/softprops/atty/blob/master/CHANGELOG.md) - [Commits](https://github.com/softprops/atty/compare/0.2.13...0.2.14) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-05 22:32:54 +00:00
dependencies = [
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
"libc",
build(deps): bump atty from 0.2.13 to 0.2.14 Bumps [atty](https://github.com/softprops/atty) from 0.2.13 to 0.2.14. - [Release notes](https://github.com/softprops/atty/releases) - [Changelog](https://github.com/softprops/atty/blob/master/CHANGELOG.md) - [Commits](https://github.com/softprops/atty/compare/0.2.13...0.2.14) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-05 22:32:54 +00:00
]
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
[[package]]
name = "humantime"
build(deps): bump humantime from 2.0.1 to 2.1.0 Bumps [humantime](https://github.com/tailhook/humantime) from 2.0.1 to 2.1.0. - [Release notes](https://github.com/tailhook/humantime/releases) - [Commits](https://github.com/tailhook/humantime/compare/v2.0.1...v2.1.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-01-13 20:44:38 +00:00
version = "2.1.0"
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump humantime from 2.0.1 to 2.1.0 Bumps [humantime](https://github.com/tailhook/humantime) from 2.0.1 to 2.1.0. - [Release notes](https://github.com/tailhook/humantime/releases) - [Commits](https://github.com/tailhook/humantime/compare/v2.0.1...v2.1.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-01-13 20:44:38 +00:00
checksum = "9a3a5bfb195931eeb336b2a7b4d761daec841b97f947d34394601737a7bba5e4"
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
hypervisor: Introduce hypervisor crate The purpose of this trait is to add support for other hypervisors than KVM, like e.g. Microsoft Hyper-V. Further commits will define additional hypervisor related traits like Vcpu and Vm. Each of the supported hypervisor will need to implement all traits defined from the hypervisor crate. Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-06-08 00:50:38 +00:00
[[package]]
name = "hypervisor"
version = "0.1.0"
hypervisor: Add Vcpu trait This Vcpu trait should be implemented by each underlying hypervisor. Previously created hypervisor object should create the VM based on already selected hypervisor and Vm object should create this vcpu object based on same hyperviosr. Each of this object should be referenced by trait object i.e <dyn Vcpu>. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-03 19:23:56 +00:00
dependencies = [
"anyhow",
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
"env_logger",
hypervisor: mshv: Emulate IrqFd and IOEventFd for mshv module We don't have IrqFd and IOEventFd support in the kernel for now. So an emulation layer is needed. In the future, we will be adding this support in the kernel. Co-Developed-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-04 18:30:29 +00:00
"epoll",
hypervisor: x86: Add a CpuStateManager interface For efficiently emulating x86 instructions, we need to build and pass a CPU state copy/reference to instruction emulation handlers. Those handlers will typically modify the CPU state and let the caller commit those changes back through the PlatformEmulator trait set_cpu_state method. Hypervisors typically have internal CPU state structures, that maps back to the correspinding kernel APIs. By implementing the CpuState trait, instruction emulators will be able to directly work on CPU state instances that are directly consumable by the underlying hypervisor and its kernel APIs. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-13 11:30:25 +00:00
"iced-x86",
hypervisor: Add Vcpu trait This Vcpu trait should be implemented by each underlying hypervisor. Previously created hypervisor object should create the VM based on already selected hypervisor and Vm object should create this vcpu object based on same hyperviosr. Each of this object should be referenced by trait object i.e <dyn Vcpu>. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-03 19:23:56 +00:00
"kvm-bindings",
"kvm-ioctls",
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
hypervisor: Modify toml file to add mshv-{bindings, ioctls) crates Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-03 22:43:48 +00:00
"mshv-bindings",
"mshv-ioctls",
hypervisor: Add Vcpu trait This Vcpu trait should be implemented by each underlying hypervisor. Previously created hypervisor object should create the VM based on already selected hypervisor and Vm object should create this vcpu object based on same hyperviosr. Each of this object should be referenced by trait object i.e <dyn Vcpu>. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-03 19:23:56 +00:00
"serde",
"serde_derive",
"serde_json",
"thiserror",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
hypervisor: Add Vcpu trait This Vcpu trait should be implemented by each underlying hypervisor. Previously created hypervisor object should create the VM based on already selected hypervisor and Vm object should create this vcpu object based on same hyperviosr. Each of this object should be referenced by trait object i.e <dyn Vcpu>. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-03 19:23:56 +00:00
"vmm-sys-util",
]
hypervisor: Introduce hypervisor crate The purpose of this trait is to add support for other hypervisors than KVM, like e.g. Microsoft Hyper-V. Further commits will define additional hypervisor related traits like Vcpu and Vm. Each of the supported hypervisor will need to implement all traits defined from the hypervisor crate. Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-06-08 00:50:38 +00:00
hypervisor: x86: Add a CpuStateManager interface For efficiently emulating x86 instructions, we need to build and pass a CPU state copy/reference to instruction emulation handlers. Those handlers will typically modify the CPU state and let the caller commit those changes back through the PlatformEmulator trait set_cpu_state method. Hypervisors typically have internal CPU state structures, that maps back to the correspinding kernel APIs. By implementing the CpuState trait, instruction emulators will be able to directly work on CPU state instances that are directly consumable by the underlying hypervisor and its kernel APIs. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-13 11:30:25 +00:00
[[package]]
name = "iced-x86"
build: bump iced-x86 from 1.16.0 to 1.17.0 Bumps [iced-x86](https://github.com/icedland/iced) from 1.16.0 to 1.17.0. - [Release notes](https://github.com/icedland/iced/releases) - [Commits](https://github.com/icedland/iced/compare/v1.16.0...v1.17.0) --- updated-dependencies: - dependency-name: iced-x86 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-24 23:14:18 +00:00
version = "1.17.0"
hypervisor: x86: Add a CpuStateManager interface For efficiently emulating x86 instructions, we need to build and pass a CPU state copy/reference to instruction emulation handlers. Those handlers will typically modify the CPU state and let the caller commit those changes back through the PlatformEmulator trait set_cpu_state method. Hypervisors typically have internal CPU state structures, that maps back to the correspinding kernel APIs. By implementing the CpuState trait, instruction emulators will be able to directly work on CPU state instances that are directly consumable by the underlying hypervisor and its kernel APIs. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-13 11:30:25 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump iced-x86 from 1.16.0 to 1.17.0 Bumps [iced-x86](https://github.com/icedland/iced) from 1.16.0 to 1.17.0. - [Release notes](https://github.com/icedland/iced/releases) - [Commits](https://github.com/icedland/iced/compare/v1.16.0...v1.17.0) --- updated-dependencies: - dependency-name: iced-x86 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-24 23:14:18 +00:00
checksum = "158f5204401d08f91d19176112146d75e99b3cf745092e268fa7be33e09adcec"
hypervisor: x86: Add a CpuStateManager interface For efficiently emulating x86 instructions, we need to build and pass a CPU state copy/reference to instruction emulation handlers. Those handlers will typically modify the CPU state and let the caller commit those changes back through the PlatformEmulator trait set_cpu_state method. Hypervisors typically have internal CPU state structures, that maps back to the correspinding kernel APIs. By implementing the CpuState trait, instruction emulators will be able to directly work on CPU state instances that are directly consumable by the underlying hypervisor and its kernel APIs. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-13 11:30:25 +00:00
dependencies = [
"lazy_static",
"static_assertions",
]
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
[[package]]
name = "indexmap"
build: bump indexmap from 1.7.0 to 1.8.0 Bumps [indexmap](https://github.com/bluss/indexmap) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/bluss/indexmap/releases) - [Changelog](https://github.com/bluss/indexmap/blob/master/RELEASES.rst) - [Commits](https://github.com/bluss/indexmap/compare/1.7.0...1.8.0) --- updated-dependencies: - dependency-name: indexmap dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-07 23:11:53 +00:00
version = "1.8.0"
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump indexmap from 1.7.0 to 1.8.0 Bumps [indexmap](https://github.com/bluss/indexmap) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/bluss/indexmap/releases) - [Changelog](https://github.com/bluss/indexmap/blob/master/RELEASES.rst) - [Commits](https://github.com/bluss/indexmap/compare/1.7.0...1.8.0) --- updated-dependencies: - dependency-name: indexmap dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-07 23:11:53 +00:00
checksum = "282a6247722caba404c065016bbfa522806e51714c34f5dfc3e4a3a46fcb4223"
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
dependencies = [
"autocfg",
"hashbrown",
]
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
[[package]]
name = "instant"
build: bump instant from 0.1.11 to 0.1.12 Bumps [instant](https://github.com/sebcrozet/instant) from 0.1.11 to 0.1.12. - [Release notes](https://github.com/sebcrozet/instant/releases) - [Changelog](https://github.com/sebcrozet/instant/blob/master/CHANGELOG.md) - [Commits](https://github.com/sebcrozet/instant/compare/v0.1.11...v0.1.12) --- updated-dependencies: - dependency-name: instant dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-18 23:11:32 +00:00
version = "0.1.12"
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump instant from 0.1.11 to 0.1.12 Bumps [instant](https://github.com/sebcrozet/instant) from 0.1.11 to 0.1.12. - [Release notes](https://github.com/sebcrozet/instant/releases) - [Changelog](https://github.com/sebcrozet/instant/blob/master/CHANGELOG.md) - [Commits](https://github.com/sebcrozet/instant/compare/v0.1.11...v0.1.12) --- updated-dependencies: - dependency-name: instant dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-18 23:11:32 +00:00
checksum = "7a5bbe824c507c5da5956355e86a746d82e0e1464f65d862cc5e71da70e94b2c"
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
dependencies = [
"cfg-if",
]
block_util: Add utilities to support io_uring Creates a dedicated function relying on io_uring crate to execute io_uring specific requests. Also creates a function for checking io_uring support on the host. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-07-27 13:58:53 +00:00
[[package]]
name = "io-uring"
build: bump io-uring from 0.5.1 to 0.5.2 Bumps [io-uring](https://github.com/tokio-rs/io-uring) from 0.5.1 to 0.5.2. - [Release notes](https://github.com/tokio-rs/io-uring/releases) - [Commits](https://github.com/tokio-rs/io-uring/commits) --- updated-dependencies: - dependency-name: io-uring dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-23 23:07:20 +00:00
version = "0.5.2"
io-uring: Move to the crates.io 0.4.0 version Now that io-uring crate has been stabilized, let's move to the latest release 0.4.0 from crates.io. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-08-10 06:51:34 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump io-uring from 0.5.1 to 0.5.2 Bumps [io-uring](https://github.com/tokio-rs/io-uring) from 0.5.1 to 0.5.2. - [Release notes](https://github.com/tokio-rs/io-uring/releases) - [Commits](https://github.com/tokio-rs/io-uring/commits) --- updated-dependencies: - dependency-name: io-uring dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-23 23:07:20 +00:00
checksum = "8d75829ed9377bab6c90039fe47b9d84caceb4b5063266142e21bcce6550cda8"
block_util: Add utilities to support io_uring Creates a dedicated function relying on io_uring crate to execute io_uring specific requests. Also creates a function for checking io_uring support on the host. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-07-27 13:58:53 +00:00
dependencies = [
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"bitflags",
block_util: Add utilities to support io_uring Creates a dedicated function relying on io_uring crate to execute io_uring specific requests. Also creates a function for checking io_uring support on the host. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-07-27 13:58:53 +00:00
"libc",
]
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
[[package]]
name = "ipnetwork"
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
version = "0.18.0"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
checksum = "4088d739b183546b239688ddbc79891831df421773df95e236daf7867866d355"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
dependencies = [
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
"serde",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
[[package]]
name = "itoa"
build: bump serde_json from 1.0.72 to 1.0.73 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.72 to 1.0.73. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.72...v1.0.73) --- updated-dependencies: - dependency-name: serde_json dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-13 23:42:55 +00:00
version = "1.0.1"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump serde_json from 1.0.72 to 1.0.73 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.72 to 1.0.73. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.72...v1.0.73) --- updated-dependencies: - dependency-name: serde_json dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-13 23:42:55 +00:00
checksum = "1aab8fc367588b89dcee83ab0fd66b72b50b72fa1904d7095045ace2b0c81c35"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
cloud-hypervisor: Call into the test_vm() routine test_vm is a dummy VM workload, we use it to test our initial VMM settings. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-22 16:05:02 +00:00
[[package]]
name = "kvm-bindings"
deps: Bump kvm-bindings to v0.5.0 Update the kvm-bindings dependency so that Cloud Hypervisor now depends on the version 0.5.0, which is based on Linux kernel v5.13.0. We still have to rely on a forked version to be able to serialize all the KVM structures we need. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-09-15 13:55:15 +00:00
version = "0.5.0"
deps: Move to kvm-bindings fork including TDX definitions A new fork of the kvm-bindings crate has been submitted to the ch-v0.5.0-tdx branch. It contains updated bindings for x86 to support TDX. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-02-16 13:47:12 +00:00
source = "git+https://github.com/cloud-hypervisor/kvm-bindings?branch=ch-v0.5.0-tdx#52e56d0e8ef0f6ea32fc0492e6a175b73617a49f"
cargo: Bump the kvm and vmm-sys-util crates Since the kvm crates now depend on vmm-sys-util, the bump must be atomic. The kvm-bindings and ioctls 0.2.0 and 0.4.0 crates come with a few API changes, one of them being the use of a kvm_ioctls specific error type. Porting our code to that type makes for a fairly large diff stat. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-29 15:36:33 +00:00
dependencies = [
vmm: cpu: Get and set KVM vCPU state These two new helpers will be useful to capture a vCPU state and being able to restore it at a later time. Signed-off-by: Cathy Zhang <cathy.zhang@intel.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-02-16 20:42:42 +00:00
"serde",
"serde_derive",
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
"vmm-sys-util",
cargo: Bump the kvm and vmm-sys-util crates Since the kvm crates now depend on vmm-sys-util, the bump must be atomic. The kvm-bindings and ioctls 0.2.0 and 0.4.0 crates come with a few API changes, one of them being the use of a kvm_ioctls specific error type. Porting our code to that type makes for a fairly large diff stat. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-29 15:36:33 +00:00
]
cloud-hypervisor: Call into the test_vm() routine test_vm is a dummy VM workload, we use it to test our initial VMM settings. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-22 16:05:02 +00:00
[[package]]
name = "kvm-ioctls"
build: bump kvm-ioctls from 0.10.0 to 0.11.0 Bumps [kvm-ioctls](https://github.com/rust-vmm/kvm-ioctls) from 0.10.0 to 0.11.0. - [Release notes](https://github.com/rust-vmm/kvm-ioctls/releases) - [Changelog](https://github.com/rust-vmm/kvm-ioctls/blob/main/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/kvm-ioctls/commits) --- updated-dependencies: - dependency-name: kvm-ioctls dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2021-11-18 23:08:40 +00:00
version = "0.11.0"
deps: Update kvm-ioctls to retrieve kvm_run structure Rely on latest version of rust-vmm/kvm-ioctls to be able to invoke the new method get_kvm_run() that returns a mutable reference of the kvm_run structure. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-02-16 14:39:06 +00:00
source = "git+https://github.com/rust-vmm/kvm-ioctls?branch=main#1e03e29cdfbb0cb108a98de7a78045a5a517f18e"
cloud-hypervisor: Call into the test_vm() routine test_vm is a dummy VM workload, we use it to test our initial VMM settings. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-22 16:05:02 +00:00
dependencies = [
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
"kvm-bindings",
"libc",
"vmm-sys-util",
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
]
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
[[package]]
name = "lazy_static"
build(deps): bump lazy_static from 1.3.0 to 1.4.0 Bumps [lazy_static](https://github.com/rust-lang-nursery/lazy-static.rs) from 1.3.0 to 1.4.0. - [Release notes](https://github.com/rust-lang-nursery/lazy-static.rs/releases) - [Commits](https://github.com/rust-lang-nursery/lazy-static.rs/compare/1.3.0...1.4.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-26 01:05:43 +00:00
version = "1.4.0"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
[[package]]
name = "libc"
build: bump libc from 0.2.118 to 0.2.119 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.118 to 0.2.119. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.118...0.2.119) --- updated-dependencies: - dependency-name: libc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-22 08:46:43 +00:00
version = "0.2.119"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump libc from 0.2.118 to 0.2.119 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.118 to 0.2.119. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.118...0.2.119) --- updated-dependencies: - dependency-name: libc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-22 08:46:43 +00:00
checksum = "1bf2e165bb3457c8e098ea76f3e3bc9db55f87aa90d52d0e6be741470916aaa4"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
[[package]]
name = "libssh2-sys"
build: bump libssh2-sys from 0.2.21 to 0.2.23 Bumps [libssh2-sys](https://github.com/alexcrichton/ssh2-rs) from 0.2.21 to 0.2.23. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/libssh2-sys-0.2.21...libssh2-sys-0.2.23) --- updated-dependencies: - dependency-name: libssh2-sys dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-11 23:09:32 +00:00
version = "0.2.23"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump libssh2-sys from 0.2.21 to 0.2.23 Bumps [libssh2-sys](https://github.com/alexcrichton/ssh2-rs) from 0.2.21 to 0.2.23. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/libssh2-sys-0.2.21...libssh2-sys-0.2.23) --- updated-dependencies: - dependency-name: libssh2-sys dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-11 23:09:32 +00:00
checksum = "b094a36eb4b8b8c8a7b4b8ae43b2944502be3e59cd87687595cf6b0a71b3f4ca"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
dependencies = [
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
"cc",
"libc",
"libz-sys",
"openssl-sys",
"pkg-config",
"vcpkg",
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
]
[[package]]
name = "libz-sys"
build: Bump libz-sys from 1.1.2 to 1.1.3 Bumps [libz-sys](https://github.com/rust-lang/libz-sys) from 1.1.2 to 1.1.3. - [Release notes](https://github.com/rust-lang/libz-sys/releases) - [Commits](https://github.com/rust-lang/libz-sys/compare/1.1.2...1.1.3) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-30 08:13:32 +00:00
version = "1.1.3"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump libz-sys from 1.1.2 to 1.1.3 Bumps [libz-sys](https://github.com/rust-lang/libz-sys) from 1.1.2 to 1.1.3. - [Release notes](https://github.com/rust-lang/libz-sys/releases) - [Commits](https://github.com/rust-lang/libz-sys/compare/1.1.2...1.1.3) Signed-off-by: dependabot[bot] <support@github.com>
2021-04-30 08:13:32 +00:00
checksum = "de5435b8549c16d423ed0c03dbaafe57cf6c3344744f1242520d59c9d8ecec66"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
dependencies = [
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
"cc",
"libc",
"pkg-config",
"vcpkg",
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
]
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 13:16:58 +00:00
[[package]]
name = "linux-loader"
build: bump linux-loader from 0.3.0 to 0.4.0 Requires manual change to command line loading. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-09-24 07:43:14 +00:00
version = "0.4.0"
misc: Bulk upgrade dependencies In particular update for the vmm-sys-util upgrade and all the other dependent packages. This requires an updated forked version of kvm-bindings (due to updated vfio-ioctls) but allowed the removal of our forked version of kvm-ioctls. The changes to the API from kvm-ioctls and vmm-sys-util required some other minor changes to the code. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-02-25 16:53:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump linux-loader from 0.3.0 to 0.4.0 Requires manual change to command line loading. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-09-24 07:43:14 +00:00
checksum = "8a5e77493808403a6bd56a301a64ea6b9342e36ea845044bf0dfdf56fe52fa08"
vendor: Add vendored dependencies We use cargo vendor to generate a .cargo/config file and the vendor directory. Vendoring allows us to lock our dependencies and to modify them easily from the top level Cargo.toml. We vendor all dependencies, including the crates.io ones, which allows for network isolated builds. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-06-03 14:40:09 +00:00
dependencies = [
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
vendor: Add vendored dependencies We use cargo vendor to generate a .cargo/config file and the vendor directory. Vendoring allows us to lock our dependencies and to modify them easily from the top level Cargo.toml. We vendor all dependencies, including the crates.io ones, which allows for network isolated builds. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-06-03 14:40:09 +00:00
]
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
[[package]]
name = "lock_api"
build: bump lock_api from 0.4.5 to 0.4.6 Bumps [lock_api](https://github.com/Amanieu/parking_lot) from 0.4.5 to 0.4.6. - [Release notes](https://github.com/Amanieu/parking_lot/releases) - [Changelog](https://github.com/Amanieu/parking_lot/blob/master/CHANGELOG.md) - [Commits](https://github.com/Amanieu/parking_lot/compare/lock_api-0.4.5...lock_api-0.4.6) --- updated-dependencies: - dependency-name: lock_api dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-28 23:14:14 +00:00
version = "0.4.6"
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump lock_api from 0.4.5 to 0.4.6 Bumps [lock_api](https://github.com/Amanieu/parking_lot) from 0.4.5 to 0.4.6. - [Release notes](https://github.com/Amanieu/parking_lot/releases) - [Changelog](https://github.com/Amanieu/parking_lot/blob/master/CHANGELOG.md) - [Commits](https://github.com/Amanieu/parking_lot/compare/lock_api-0.4.5...lock_api-0.4.6) --- updated-dependencies: - dependency-name: lock_api dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-28 23:14:14 +00:00
checksum = "88943dd7ef4a2e5a4bfa2753aaab3013e34ce2533d1996fb18ef591e315e2b3b"
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
dependencies = [
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
"scopeguard",
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
]
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
[[package]]
name = "log"
build(deps): bump log from 0.4.13 to 0.4.14 Bumps [log](https://github.com/rust-lang/log) from 0.4.13 to 0.4.14. - [Release notes](https://github.com/rust-lang/log/releases) - [Changelog](https://github.com/rust-lang/log/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/log/compare/0.4.13...0.4.14) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-01-27 03:17:53 +00:00
version = "0.4.14"
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump log from 0.4.13 to 0.4.14 Bumps [log](https://github.com/rust-lang/log) from 0.4.13 to 0.4.14. - [Release notes](https://github.com/rust-lang/log/releases) - [Changelog](https://github.com/rust-lang/log/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/log/compare/0.4.13...0.4.14) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-01-27 03:17:53 +00:00
checksum = "51b9bbe6c47d51fc3e1a9b945965946b4c44142ab8792c50835a980d362c2710"
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
dependencies = [
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
"cfg-if",
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
]
vmm: Add `Debuggable` trait implementation This commit adds initial gdb.rs implementation for `Debuggable` trait to describe a debuggable component. Some part of the trait bound implementations is based on the crosvm GDB stub code [1]. [1] https://github.com/google/crosvm/blob/main/src/gdb.rs Signed-off-by: Akira Moroo <retrage01@gmail.com>
2022-02-20 03:17:50 +00:00
[[package]]
name = "managed"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0ca88d725a0a943b096803bd34e73a4437208b6077654cc4ecb2947a5f91618d"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
[[package]]
name = "memchr"
build: bump memchr from 2.4.0 to 2.4.1 Bumps [memchr](https://github.com/BurntSushi/memchr) from 2.4.0 to 2.4.1. - [Release notes](https://github.com/BurntSushi/memchr/releases) - [Commits](https://github.com/BurntSushi/memchr/compare/2.4.0...2.4.1) --- updated-dependencies: - dependency-name: memchr dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-18 23:08:40 +00:00
version = "2.4.1"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump memchr from 2.4.0 to 2.4.1 Bumps [memchr](https://github.com/BurntSushi/memchr) from 2.4.0 to 2.4.1. - [Release notes](https://github.com/BurntSushi/memchr/releases) - [Commits](https://github.com/BurntSushi/memchr/compare/2.4.0...2.4.1) --- updated-dependencies: - dependency-name: memchr dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-18 23:08:40 +00:00
checksum = "308cc39be01b73d0d18f82a0e7b2a3df85245f84af96fdddc5d202d27e47b86a"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
vmm: api: Add HTTP server The Cloud Hyper HTTP server runs a synchronous, multi-threaded loop that receives HTTP requests and tries to call the corresponding endpoint handlers for the requests URIs. An endpoint handler will parse the HTTP request and potentially translate it into and IPC request. The handler holds an notifier and an mspc Sender for respectively notifying and sending the IPC payload to the VMM API server. The handler then waits for an API server response and translate it back into an HTTP response. The HTTP server is responsible for sending the reponse back to the caller. The HTTP server uses a static routes hash table that maps URIs to endpoint handlers. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-09-18 09:14:49 +00:00
[[package]]
name = "micro_http"
version = "0.1.0"
vmm: api: Support multiple fds with add-net Based on the latest code from the micro-http crate, this patch adds the support for multiple file descriptors to be sent along with the add-net request. This means we can now hotplug multiqueue network interface to the VM. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-01-21 07:54:22 +00:00
source = "git+https://github.com/firecracker-microvm/micro-http?branch=main#a730d86940081ad044cdfbc1285c1db6d3048392"
cargo: Update micro_http Update micro_http create to allow set content type. Suggested-by: Samuel Ortiz <sameo@linux.intel.com> Tested-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com> Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
2019-11-08 17:49:51 +00:00
dependencies = [
build(deps): bump micro_http from `59ab644` to `49240ce` Bumps [micro_http](https://github.com/firecracker-microvm/micro-http) from `59ab644` to `49240ce`. - [Release notes](https://github.com/firecracker-microvm/micro-http/releases) - [Commits](https://github.com/firecracker-microvm/micro-http/compare/59ab64440a95f7b16253fef67b5201c2ec4adaf7...49240ce1d5a81a594aa12895c1ef4091c0fd8e9b) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-04-16 05:31:15 +00:00
"libc",
"vmm-sys-util",
cargo: Update micro_http Update micro_http create to allow set content type. Suggested-by: Samuel Ortiz <sameo@linux.intel.com> Tested-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com> Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
2019-11-08 17:49:51 +00:00
]
vmm: api: Add HTTP server The Cloud Hyper HTTP server runs a synchronous, multi-threaded loop that receives HTTP requests and tries to call the corresponding endpoint handlers for the requests URIs. An endpoint handler will parse the HTTP request and potentially translate it into and IPC request. The handler holds an notifier and an mspc Sender for respectively notifying and sending the IPC payload to the VMM API server. The handler then waits for an API server response and translate it back into an HTTP response. The HTTP server is responsible for sending the reponse back to the caller. The HTTP server uses a static routes hash table that maps URIs to endpoint handlers. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-09-18 09:14:49 +00:00
hypervisor: Modify toml file to add mshv-{bindings, ioctls) crates Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-03 22:43:48 +00:00
[[package]]
name = "mshv-bindings"
version = "0.1.0"
build: bump mshv-ioctls from `b8b69b6` to `d241ffc` Bumps [mshv-ioctls](https://github.com/rust-vmm/mshv) from `b8b69b6` to `d241ffc`. - [Release notes](https://github.com/rust-vmm/mshv/releases) - [Commits](https://github.com/rust-vmm/mshv/compare/b8b69b655337292037219ab765d2c94c565a076e...d241ffcacdfa4240b4a1d34b44af89dc7b113986) --- updated-dependencies: - dependency-name: mshv-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-24 23:12:26 +00:00
source = "git+https://github.com/rust-vmm/mshv?branch=main#d241ffcacdfa4240b4a1d34b44af89dc7b113986"
hypervisor: Modify toml file to add mshv-{bindings, ioctls) crates Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-03 22:43:48 +00:00
dependencies = [
"libc",
"serde",
"serde_derive",
"vmm-sys-util",
"zerocopy",
]
[[package]]
name = "mshv-ioctls"
version = "0.1.0"
build: bump mshv-ioctls from `b8b69b6` to `d241ffc` Bumps [mshv-ioctls](https://github.com/rust-vmm/mshv) from `b8b69b6` to `d241ffc`. - [Release notes](https://github.com/rust-vmm/mshv/releases) - [Commits](https://github.com/rust-vmm/mshv/compare/b8b69b655337292037219ab765d2c94c565a076e...d241ffcacdfa4240b4a1d34b44af89dc7b113986) --- updated-dependencies: - dependency-name: mshv-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-24 23:12:26 +00:00
source = "git+https://github.com/rust-vmm/mshv?branch=main#d241ffcacdfa4240b4a1d34b44af89dc7b113986"
hypervisor: Modify toml file to add mshv-{bindings, ioctls) crates Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-03 22:43:48 +00:00
dependencies = [
"libc",
"mshv-bindings",
"vmm-sys-util",
]
network: Add virtio-net dependencies The newly added virtio-net implementation needs to interact with TAP interfaces and MAC addresses, which is the reason why it is easier to rely on existing packages net_util and net_gen. One more thing, both net_util and net_gen could be trimmed down, based on using only the things we need from cloud-hypervisor. Both net_util, net_gen and sys_util are based on Firecracker commit d4a89cdc0bd2867f821e3678328dabad6dd8b767. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-08 05:28:02 +00:00
[[package]]
name = "net_gen"
version = "0.1.0"
dependencies = [
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
"vmm-sys-util",
network: Add virtio-net dependencies The newly added virtio-net implementation needs to interact with TAP interfaces and MAC addresses, which is the reason why it is easier to rely on existing packages net_util and net_gen. One more thing, both net_util and net_gen could be trimmed down, based on using only the things we need from cloud-hypervisor. Both net_util, net_gen and sys_util are based on Firecracker commit d4a89cdc0bd2867f821e3678328dabad6dd8b767. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-08 05:28:02 +00:00
]
[[package]]
name = "net_util"
version = "0.1.0"
dependencies = [
net_util, virtio-devices: Move TAP register/unregister helpers Move these helper functions into net_util so that they can be used from code inside there. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-07 15:06:54 +00:00
"epoll",
net_util: Change libc::getrandom to getrandom::getrandom libc::getrandom need to be called inside unsafe and it is not cross-platform friendly. Change it to getrandom::getrandom that is safe and cross-platform friendly. Signed-off-by: Hui Zhu <teawater@antfin.com>
2021-09-15 13:50:03 +00:00
"getrandom",
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
"lazy_static",
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
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
"net_gen",
"pnet",
virtio-devices, vmm: Add rate limiter for the TX queue of virtio-net Partially fixes: #1286 Signed-off-by: Bo Chen <chen.bo@intel.com>
2021-03-17 22:41:52 +00:00
"rate_limiter",
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
"serde",
"serde_json",
net_util: Move virtio-net helpers to net_util crate Moving helpers to the net_util crate since we don't want virtio-net common code to be split between two places. The net_util crate should be the only place to host virtio-net common code. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-05-21 10:25:18 +00:00
"versionize",
"versionize_derive",
net_util, virtio-devices, vhost_user_net: Relocate code for opening TAP By moving the code for opening the TAP device into a shared location we are starting to remove the requirement for the vhost-user-net backend to depend on the virtio-devices crate which in of itself depends on many other crates that are not necessary for the backend to function. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-07 14:02:18 +00:00
"virtio-bindings",
Move Cloud Hypervisor to virtio-queue crate Relying on the vm-virtio/virtio-queue crate from rust-vmm which has been copied inside the Cloud Hypervisor tree, the entire codebase is moved to the new definition of a Queue and other related structures. The reason for this move is to follow the upstream until we get some agreement for the patches that we need on top of that to make it properly work with Cloud Hypervisor. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-21 10:41:16 +00:00
"virtio-queue",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
net_util, virtio-devices, vhost_user_net: Relocate {Rx,Tx}Virtio By moving the code for opening the two RX and TX queues into a shared location we are starting to remove the requirement for the vhost-user-net backend to depend on the virtio-devices crate which in of itself depends on many other crates that are not necessary for the backend to function. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-07 14:02:18 +00:00
"vm-virtio",
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
"vmm-sys-util",
network: Add virtio-net dependencies The newly added virtio-net implementation needs to interact with TAP interfaces and MAC addresses, which is the reason why it is easier to rely on existing packages net_util and net_gen. One more thing, both net_util and net_gen could be trimmed down, based on using only the things we need from cloud-hypervisor. Both net_util, net_gen and sys_util are based on Firecracker commit d4a89cdc0bd2867f821e3678328dabad6dd8b767. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-08 05:28:02 +00:00
]
vmm: Add `Debuggable` trait implementation This commit adds initial gdb.rs implementation for `Debuggable` trait to describe a debuggable component. Some part of the trait bound implementations is based on the crosvm GDB stub code [1]. [1] https://github.com/google/crosvm/blob/main/src/gdb.rs Signed-off-by: Akira Moroo <retrage01@gmail.com>
2022-02-20 03:17:50 +00:00
[[package]]
name = "num-traits"
version = "0.2.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9a64b1ec5cda2586e284722486d802acf1f7dbdc623e2bfc57e65ca1cd099290"
dependencies = [
"autocfg",
]
test_infra: Enable cross-build for "musl" and "aarch64" targets With enabling the `vendered-openssl` feature, we can now cross-build the `test_infra` crate for "musl" and "aarch64" targets. In this way, we can remove the `test_infra` crate from the "exclude" list, so that this crate can be checked and processed by "cargo clippy" and "cargo fmt". More details can be found: https://docs.rs/openssl/latest/openssl/#vendored As 'musl-gcc' is required, this commit also installs the `musl-tools` package for our "build" github action on the musl target [1]. [1] https://github.com/actions-rs/toolchain/issues/102 Signed-off-by: Bo Chen <chen.bo@intel.com>
2022-02-11 02:29:53 +00:00
[[package]]
name = "openssl-src"
version = "111.17.0+1.1.1m"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "05d6a336abd10814198f66e2a91ccd7336611f30334119ca8ce300536666fcf4"
dependencies = [
"cc",
]
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
[[package]]
name = "openssl-sys"
build: bump openssl-sys from 0.9.71 to 0.9.72 Bumps [openssl-sys](https://github.com/sfackler/rust-openssl) from 0.9.71 to 0.9.72. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-sys-v0.9.71...openssl-sys-v0.9.72) --- updated-dependencies: - dependency-name: openssl-sys dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-13 23:46:45 +00:00
version = "0.9.72"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump openssl-sys from 0.9.71 to 0.9.72 Bumps [openssl-sys](https://github.com/sfackler/rust-openssl) from 0.9.71 to 0.9.72. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-sys-v0.9.71...openssl-sys-v0.9.72) --- updated-dependencies: - dependency-name: openssl-sys dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-13 23:46:45 +00:00
checksum = "7e46109c383602735fa0a2e48dd2b7c892b048e1bf69e5c3b1d804b7d9c203cb"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
dependencies = [
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
"autocfg",
"cc",
"libc",
test_infra: Enable cross-build for "musl" and "aarch64" targets With enabling the `vendered-openssl` feature, we can now cross-build the `test_infra` crate for "musl" and "aarch64" targets. In this way, we can remove the `test_infra` crate from the "exclude" list, so that this crate can be checked and processed by "cargo clippy" and "cargo fmt". More details can be found: https://docs.rs/openssl/latest/openssl/#vendored As 'musl-gcc' is required, this commit also installs the `musl-tools` package for our "build" github action on the musl target [1]. [1] https://github.com/actions-rs/toolchain/issues/102 Signed-off-by: Bo Chen <chen.bo@intel.com>
2022-02-11 02:29:53 +00:00
"openssl-src",
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
"pkg-config",
"vcpkg",
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
]
vhost_user_net, vhost_user_block, option_parser: Remove vmm dependency Remove the vmm dependency from vhost_user_block and vhost_user_net where it was existing to use config::OptionParser. By moving the OptionParser to its own crate at the top-level we can remove the very heavy dependency that these vhost-user backends had. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-06 15:41:45 +00:00
[[package]]
name = "option_parser"
version = "0.1.0"
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
[[package]]
name = "os_str_bytes"
version = "6.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8e22443d1643a904602595ba1cd8f7d896afe56d26712531c5ff73a15b2fbf64"
dependencies = [
"memchr",
]
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
[[package]]
name = "parking_lot"
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
version = "0.11.2"
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
checksum = "7d17b78036a60663b797adeaee46f5c9dfebb86948d1255007a1d6be0271ff99"
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
dependencies = [
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
"instant",
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
"lock_api",
"parking_lot_core",
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
]
[[package]]
name = "parking_lot_core"
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
version = "0.8.5"
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
checksum = "d76e8e1493bcac0d2766c42737f34458f1c8c50c0d23bcb24ea953affb273216"
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
dependencies = [
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
"cfg-if",
"instant",
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
"libc",
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
"redox_syscall",
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
"smallvec",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"winapi",
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
]
vmm: Add `Debuggable` trait implementation This commit adds initial gdb.rs implementation for `Debuggable` trait to describe a debuggable component. Some part of the trait bound implementations is based on the crosvm GDB stub code [1]. [1] https://github.com/google/crosvm/blob/main/src/gdb.rs Signed-off-by: Akira Moroo <retrage01@gmail.com>
2022-02-20 03:17:50 +00:00
[[package]]
name = "paste"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0744126afe1a6dd7f394cb50a716dbe086cb06e255e53d8d0185d82828358fb5"
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
[[package]]
name = "pci"
version = "0.1.0"
dependencies = [
pci: Implement Snapshottable trait for MsixConfig In order to restore devices relying on MSI-X, the MsixConfig structure must be restored with the correct values. Additionally, the KVM routes must be restored so that interrupts can be delivered through KVM the way they were configured before the snapshot was taken. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-05-06 15:50:56 +00:00
"anyhow",
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
"byteorder",
arch, pci, vmm: Initial switch to the hypervisor crate Start moving the vmm, arch and pci crates to being hypervisor agnostic by using the hypervisor trait and abstractions. This is not a complete switch and there are still some remaining KVM dependencies. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-02 02:29:54 +00:00
"hypervisor",
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
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
pci, vmm: Update DeviceNode to store PciBdf instead of u32 By having the DeviceNode storing a PciBdf, we simplify the internal code as well as allow for custom Serialize/Deserialize implementation for the PciBdf structure. These custom implementations let us display the PCI s/b/d/f in a human readable format. Fixes #3711 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-02-16 08:55:26 +00:00
"serde",
"serde_derive",
pci: vfio: Cleanup error handling After the refactoring to split the common VFIO code out for vfio-user there were some inconsistencies in the error handling. Correct this so that the error is independent of the transport (hardware vs user) VFIO and migrate to anyhow/thiserror in the process. Some unused errors from earlier refactoring have also been removed. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-08-02 14:20:09 +00:00
"thiserror",
pci: Versionize PCI state Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-26 15:28:15 +00:00
"versionize",
"versionize_derive",
pci: use vfio-bindings from crates.io This fixes `cargo vendor` throwing an error ``` $ cargo vendor error: failed to sync Caused by: found duplicate version of package `vfio-bindings v0.2.0` vendored from two sources: source 1: https://github.com/rust-vmm/vfio-bindings#f08cbcbf source 2: registry `https://github.com/rust-lang/crates.io-index` ``` Both sources are indeed same, the conflict is only cause by the different URLs. Signed-off-by: Anatol Belski <ab@php.net>
2020-08-05 11:53:09 +00:00
"vfio-bindings",
vfio: Rename to vfio-ioctls Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-08 15:27:05 +00:00
"vfio-ioctls",
pci: Add support for vfio-user PCI devices Taking advantage of the refactored VFIO code implement a new VfioUserPciDevice that wraps the client for vfio-user and exposes the BusDevice and PciDevice into the VMM. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-06-09 13:43:04 +00:00
"vfio_user",
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
"vm-allocator",
"vm-device",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
pci: Implement Snapshottable trait for MsixConfig In order to restore devices relying on MSI-X, the MsixConfig structure must be restored with the correct values. Additionally, the KVM routes must be restored so that interrupts can be delivered through KVM the way they were configured before the snapshot was taken. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-05-06 15:50:56 +00:00
"vm-migration",
vfio: Move the PCI implementation to the PCI crate There is a much stronger PCI dependency from vfio_pci.rs than a VFIO one from pci/src/vfio.rs. It seems more natural to have the PCI specific VFIO implementation in the PCI crate rather than the other way around. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-08 14:50:39 +00:00
"vmm-sys-util",
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
]
performance-metrics: Add a binary target for performance metrics This commit creates a new binary target for generating performance metrics, and also adds a set of performance tests for network throughput/latency, block I/O performance, and boot time. Signed-off-by: Bo Chen <chen.bo@intel.com>
2022-01-11 05:27:58 +00:00
[[package]]
name = "performance-metrics"
version = "0.1.0"
dependencies = [
performance-metrics: Generate a summary report in Json The report contains the test results with commit hash and date. Signed-off-by: Bo Chen <chen.bo@intel.com>
2022-02-11 02:02:03 +00:00
"clap",
build: Use consistent version of dirs crate Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-03-03 15:47:14 +00:00
"dirs",
performance-metrics: Support test filter and json output Signed-off-by: Bo Chen <chen.bo@intel.com>
2022-02-01 05:24:13 +00:00
"serde",
"serde_derive",
performance-metrics: Add a binary target for performance metrics This commit creates a new binary target for generating performance metrics, and also adds a set of performance tests for network throughput/latency, block I/O performance, and boot time. Signed-off-by: Bo Chen <chen.bo@intel.com>
2022-01-11 05:27:58 +00:00
"serde_json",
"test_infra",
performance-metrics: Add option "--report-file" Signed-off-by: Bo Chen <chen.bo@intel.com>
2022-02-15 16:11:58 +00:00
"thiserror",
performance-metrics: Add a binary target for performance metrics This commit creates a new binary target for generating performance metrics, and also adds a set of performance tests for network throughput/latency, block I/O performance, and boot time. Signed-off-by: Bo Chen <chen.bo@intel.com>
2022-01-11 05:27:58 +00:00
"wait-timeout",
]
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
[[package]]
name = "pkg-config"
build: bump pkg-config from 0.3.23 to 0.3.24 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.23 to 0.3.24. - [Release notes](https://github.com/rust-lang/pkg-config-rs/releases) - [Changelog](https://github.com/rust-lang/pkg-config-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/pkg-config-rs/commits) --- updated-dependencies: - dependency-name: pkg-config dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-13 23:15:03 +00:00
version = "0.3.24"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump pkg-config from 0.3.23 to 0.3.24 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.23 to 0.3.24. - [Release notes](https://github.com/rust-lang/pkg-config-rs/releases) - [Changelog](https://github.com/rust-lang/pkg-config-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/pkg-config-rs/commits) --- updated-dependencies: - dependency-name: pkg-config dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-13 23:15:03 +00:00
checksum = "58893f751c9b0412871a09abd62ecd2a00298c6c83befa223ef98c52aef40cbe"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
[[package]]
name = "pnet"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
version = "0.29.0"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
checksum = "8750e073f82219c01e771133c64718d7685aef922da8a0d430a46aed05b6341a"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
dependencies = [
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
"ipnetwork",
"pnet_base",
"pnet_datalink",
"pnet_packet",
"pnet_sys",
"pnet_transport",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
[[package]]
name = "pnet_base"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
version = "0.29.0"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
checksum = "8205fe084bd43a3af79b3155c19feddd62e733640498842e631a2ffe107d1538"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
[[package]]
name = "pnet_datalink"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
version = "0.29.0"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
checksum = "6f85aef5e52e22ff06b1b11f2eb6d52959a9e0ecad3cb3f5cc2d78cadc077f0e"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
dependencies = [
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
"ipnetwork",
"libc",
"pnet_base",
"pnet_sys",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"winapi",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
[[package]]
name = "pnet_macros"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
version = "0.29.0"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
checksum = "98cc3af95fed6dc318dfede3e81320f96ad5e237c6f7c4688108b19c8e67432d"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
dependencies = [
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"proc-macro2",
"quote",
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
"regex",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"syn",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
[[package]]
name = "pnet_macros_support"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
version = "0.29.0"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
checksum = "feaba58ba96abb218ec584d6caf0d3ff48922df05dbbeb1560553c197091b29e"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
dependencies = [
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
"pnet_base",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
[[package]]
name = "pnet_packet"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
version = "0.29.0"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
checksum = "f246edaaf1aaf82072d4cd38ee18bcc5dfc0464093f9ca39e4ac5962d68cf9d4"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
dependencies = [
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
"glob",
"pnet_base",
"pnet_macros",
"pnet_macros_support",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
[[package]]
name = "pnet_sys"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
version = "0.29.0"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
checksum = "028c87a5e3a48fc07df099a2025f2ef16add5993712e1494ba69a6707ee7ed06"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
dependencies = [
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
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"winapi",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
[[package]]
name = "pnet_transport"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
version = "0.29.0"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump pnet from 0.28.0 to 0.29.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.28.0 to 0.29.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.28.0...v0.29.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-13 23:13:01 +00:00
checksum = "950f2a7961e19d22e19e84ff0a6e0955013185fe149673499662633d02b41b7a"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
dependencies = [
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
"libc",
"pnet_base",
"pnet_packet",
"pnet_sys",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
[[package]]
name = "proc-macro2"
build: bump proc-macro2 from 1.0.34 to 1.0.36 Bumps [proc-macro2](https://github.com/dtolnay/proc-macro2) from 1.0.34 to 1.0.36. - [Release notes](https://github.com/dtolnay/proc-macro2/releases) - [Commits](https://github.com/dtolnay/proc-macro2/compare/1.0.34...1.0.36) --- updated-dependencies: - dependency-name: proc-macro2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-28 06:09:19 +00:00
version = "1.0.36"
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump proc-macro2 from 1.0.34 to 1.0.36 Bumps [proc-macro2](https://github.com/dtolnay/proc-macro2) from 1.0.34 to 1.0.36. - [Release notes](https://github.com/dtolnay/proc-macro2/releases) - [Commits](https://github.com/dtolnay/proc-macro2/compare/1.0.34...1.0.36) --- updated-dependencies: - dependency-name: proc-macro2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-28 06:09:19 +00:00
checksum = "c7342d5883fbccae1cc37a2353b09c87c9b0f3afd73f5fb9bba687a1f733b029"
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
dependencies = [
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"unicode-xid",
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
]
qcow: Add qcow support Extracted from crosvm (commit:f82d632), with clippy fixes. Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
2019-04-29 19:32:56 +00:00
[[package]]
name = "qcow"
version = "0.1.0"
dependencies = [
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
"byteorder",
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
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
"remain",
"vmm-sys-util",
qcow: Add qcow support Extracted from crosvm (commit:f82d632), with clippy fixes. Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
2019-04-29 19:32:56 +00:00
]
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
[[package]]
name = "quote"
build: bump quote from 1.0.14 to 1.0.15 Bumps [quote](https://github.com/dtolnay/quote) from 1.0.14 to 1.0.15. - [Release notes](https://github.com/dtolnay/quote/releases) - [Commits](https://github.com/dtolnay/quote/compare/1.0.14...1.0.15) --- updated-dependencies: - dependency-name: quote dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-25 02:25:05 +00:00
version = "1.0.15"
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump quote from 1.0.14 to 1.0.15 Bumps [quote](https://github.com/dtolnay/quote) from 1.0.14 to 1.0.15. - [Release notes](https://github.com/dtolnay/quote/releases) - [Commits](https://github.com/dtolnay/quote/compare/1.0.14...1.0.15) --- updated-dependencies: - dependency-name: quote dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-25 02:25:05 +00:00
checksum = "864d3e96a899863136fc6e99f3d7cae289dafe43bf2c5ac19b70df7210c0a145"
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
dependencies = [
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
"proc-macro2",
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
]
virtio-devices: Move the 'rate_limiter' module to its own crate To support I/O throttling on virt-net devices, we need to use the 'rate_limiter' module from the 'net_utils' crate. Given the 'virtio-devices' crate has dependency on the 'net_utils', we will need to move the 'rate_limiter' module out of the 'virtio-devices' crate to avoid circular dependency issue. Considering the 'rate_limiter' is not virtio specific and could be reused for non virtio devices, we move it to its own crate. Signed-off-by: Bo Chen <chen.bo@intel.com>
2021-03-22 18:23:51 +00:00
[[package]]
name = "rate_limiter"
version = "0.1.0"
dependencies = [
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
virtio-devices: Move the 'rate_limiter' module to its own crate To support I/O throttling on virt-net devices, we need to use the 'rate_limiter' module from the 'net_utils' crate. Given the 'virtio-devices' crate has dependency on the 'net_utils', we will need to move the 'rate_limiter' module out of the 'virtio-devices' crate to avoid circular dependency issue. Considering the 'rate_limiter' is not virtio specific and could be reused for non virtio devices, we move it to its own crate. Signed-off-by: Bo Chen <chen.bo@intel.com>
2021-03-22 18:23:51 +00:00
"vmm-sys-util",
]
build(deps): bump dirs from 3.0.1 to 3.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/soc/dirs-rs/releases) - [Commits](https://github.com/soc/dirs-rs/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-04-23 22:44:20 +00:00
[[package]]
name = "redox_syscall"
build: bump redox_syscall from 0.2.10 to 0.2.11 Bumps redox_syscall from 0.2.10 to 0.2.11. --- updated-dependencies: - dependency-name: redox_syscall dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-28 23:14:36 +00:00
version = "0.2.11"
build(deps): bump dirs from 3.0.1 to 3.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/soc/dirs-rs/releases) - [Commits](https://github.com/soc/dirs-rs/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-04-23 22:44:20 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump redox_syscall from 0.2.10 to 0.2.11 Bumps redox_syscall from 0.2.10 to 0.2.11. --- updated-dependencies: - dependency-name: redox_syscall dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-28 23:14:36 +00:00
checksum = "8380fe0152551244f0747b1bf41737e0f8a74f97a14ccefd1148187271634f3c"
build(deps): bump dirs from 3.0.1 to 3.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/soc/dirs-rs/releases) - [Commits](https://github.com/soc/dirs-rs/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-04-23 22:44:20 +00:00
dependencies = [
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"bitflags",
build(deps): bump dirs from 3.0.1 to 3.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/soc/dirs-rs/releases) - [Commits](https://github.com/soc/dirs-rs/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-04-23 22:44:20 +00:00
]
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
[[package]]
name = "redox_users"
build(deps): bump dirs from 3.0.1 to 3.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/soc/dirs-rs/releases) - [Commits](https://github.com/soc/dirs-rs/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-04-23 22:44:20 +00:00
version = "0.4.0"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump dirs from 3.0.1 to 3.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/soc/dirs-rs/releases) - [Commits](https://github.com/soc/dirs-rs/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-04-23 22:44:20 +00:00
checksum = "528532f3d801c87aec9def2add9ca802fe569e44a544afe633765267840abe64"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
dependencies = [
arch: use libc::getrandom() instead of rand crate This removes the last use of rand in our tree and the removal of several dependencies. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-02-22 15:43:48 +00:00
"getrandom",
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
"redox_syscall",
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
]
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
[[package]]
name = "regex"
build: Bump regex from 1.5.3 to 1.5.4 Bumps [regex](https://github.com/rust-lang/regex) from 1.5.3 to 1.5.4. - [Release notes](https://github.com/rust-lang/regex/releases) - [Changelog](https://github.com/rust-lang/regex/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/regex/compare/1.5.3...1.5.4) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-07 08:13:44 +00:00
version = "1.5.4"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump regex from 1.5.3 to 1.5.4 Bumps [regex](https://github.com/rust-lang/regex) from 1.5.3 to 1.5.4. - [Release notes](https://github.com/rust-lang/regex/releases) - [Changelog](https://github.com/rust-lang/regex/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/regex/compare/1.5.3...1.5.4) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-07 08:13:44 +00:00
checksum = "d07a8629359eb56f1e2fb1652bb04212c072a87ba68546a04065d525673ac461"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
dependencies = [
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
"aho-corasick",
"memchr",
"regex-syntax",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
[[package]]
name = "regex-syntax"
build: Bump regex from 1.4.6 to 1.5.3 Bumps [regex](https://github.com/rust-lang/regex) from 1.4.6 to 1.5.3. - [Release notes](https://github.com/rust-lang/regex/releases) - [Changelog](https://github.com/rust-lang/regex/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/regex/compare/1.4.6...1.5.3) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-03 10:06:31 +00:00
version = "0.6.25"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump regex from 1.4.6 to 1.5.3 Bumps [regex](https://github.com/rust-lang/regex) from 1.4.6 to 1.5.3. - [Release notes](https://github.com/rust-lang/regex/releases) - [Changelog](https://github.com/rust-lang/regex/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/regex/compare/1.4.6...1.5.3) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-03 10:06:31 +00:00
checksum = "f497285884f3fcff424ffc933e56d7cbca511def0c9831a7f9b5f6153e3cc89b"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
qcow: Add qcow support Extracted from crosvm (commit:f82d632), with clippy fixes. Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
2019-04-29 19:32:56 +00:00
[[package]]
name = "remain"
build(deps): bump remain from 0.2.1 to 0.2.2 Bumps [remain](https://github.com/dtolnay/remain) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.2.1...0.2.2) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-06-16 18:45:06 +00:00
version = "0.2.2"
qcow: Add qcow support Extracted from crosvm (commit:f82d632), with clippy fixes. Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
2019-04-29 19:32:56 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump remain from 0.2.1 to 0.2.2 Bumps [remain](https://github.com/dtolnay/remain) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.2.1...0.2.2) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-06-16 18:45:06 +00:00
checksum = "70ba1e78fa68412cb93ef642fd4d20b9a941be49ee9333875ebaf13112673ea7"
qcow: Add qcow support Extracted from crosvm (commit:f82d632), with clippy fixes. Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
2019-04-29 19:32:56 +00:00
dependencies = [
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
"proc-macro2",
"quote",
"syn",
qcow: Add qcow support Extracted from crosvm (commit:f82d632), with clippy fixes. Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
2019-04-29 19:32:56 +00:00
]
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
[[package]]
name = "rustc_version"
build: bump crc32c from 0.6.0 to 0.6.1 Bumps [crc32c](https://github.com/zowens/crc32c) from 0.6.0 to 0.6.1. - [Release notes](https://github.com/zowens/crc32c/releases) - [Commits](https://github.com/zowens/crc32c/commits/v0.6.1) --- updated-dependencies: - dependency-name: crc32c dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-05 23:46:55 +00:00
version = "0.4.0"
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump crc32c from 0.6.0 to 0.6.1 Bumps [crc32c](https://github.com/zowens/crc32c) from 0.6.0 to 0.6.1. - [Release notes](https://github.com/zowens/crc32c/releases) - [Commits](https://github.com/zowens/crc32c/commits/v0.6.1) --- updated-dependencies: - dependency-name: crc32c dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-05 23:46:55 +00:00
checksum = "bfa0f585226d2e68097d4f95d113b15b83a82e819ab25717ec0590d9584ef366"
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
dependencies = [
"semver",
]
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
[[package]]
name = "ryu"
build: bump ryu from 1.0.6 to 1.0.9 Bumps [ryu](https://github.com/dtolnay/ryu) from 1.0.6 to 1.0.9. - [Release notes](https://github.com/dtolnay/ryu/releases) - [Commits](https://github.com/dtolnay/ryu/compare/1.0.6...1.0.9) --- updated-dependencies: - dependency-name: ryu dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-14 01:14:32 +00:00
version = "1.0.9"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump ryu from 1.0.6 to 1.0.9 Bumps [ryu](https://github.com/dtolnay/ryu) from 1.0.6 to 1.0.9. - [Release notes](https://github.com/dtolnay/ryu/releases) - [Commits](https://github.com/dtolnay/ryu/compare/1.0.6...1.0.9) --- updated-dependencies: - dependency-name: ryu dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-14 01:14:32 +00:00
checksum = "73b4b750c782965c211b42f022f59af1fbceabdd026623714f104152f1ec149f"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
[[package]]
name = "scopeguard"
build(deps): bump scopeguard from 1.0.0 to 1.1.0 Bumps [scopeguard](https://github.com/bluss/scopeguard) from 1.0.0 to 1.1.0. - [Release notes](https://github.com/bluss/scopeguard/releases) - [Commits](https://github.com/bluss/scopeguard/compare/1.0.0...v1.1.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-02-16 23:05:44 +00:00
version = "1.1.0"
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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
checksum = "d29ab0c6d3fc0ee92fe66e2d99f700eab17a8d57d1c1d3b748380fb20baa78cd"
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
vmm: Pull seccomp crate from Firecracker The seccomp crate from Firecracker is nicely implemented, documented and tested, which is a good reason for relying on it to create and apply seccomp filters. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-03-19 10:49:13 +00:00
[[package]]
virtio-devices, vmm: Move to the seccompiler crate Fixes: #2929 Signed-off-by: Bo Chen <chen.bo@intel.com>
2021-08-17 03:40:11 +00:00
name = "seccompiler"
Build: Seccompiler: Move to use the released version from crate.io Signed-off-by: Bo Chen <chen.bo@intel.com>
2021-10-01 17:29:21 +00:00
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e01d1292a1131b22ccea49f30bd106f1238b5ddeec1a98d39268dcc31d540e68"
vmm: Pull seccomp crate from Firecracker The seccomp crate from Firecracker is nicely implemented, documented and tested, which is a good reason for relying on it to create and apply seccomp filters. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-03-19 10:49:13 +00:00
dependencies = [
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
"libc",
vmm: Pull seccomp crate from Firecracker The seccomp crate from Firecracker is nicely implemented, documented and tested, which is a good reason for relying on it to create and apply seccomp filters. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-03-19 10:49:13 +00:00
]
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
[[package]]
name = "semver"
build: bump semver from 1.0.5 to 1.0.6 Bumps [semver](https://github.com/dtolnay/semver) from 1.0.5 to 1.0.6. - [Release notes](https://github.com/dtolnay/semver/releases) - [Commits](https://github.com/dtolnay/semver/compare/1.0.5...1.0.6) --- updated-dependencies: - dependency-name: semver dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-22 08:47:25 +00:00
version = "1.0.6"
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump semver from 1.0.5 to 1.0.6 Bumps [semver](https://github.com/dtolnay/semver) from 1.0.5 to 1.0.6. - [Release notes](https://github.com/dtolnay/semver/releases) - [Commits](https://github.com/dtolnay/semver/compare/1.0.5...1.0.6) --- updated-dependencies: - dependency-name: semver dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-22 08:47:25 +00:00
checksum = "a4a3381e03edd24287172047536f20cabde766e2cd3e65e6b00fb3af51c4f38d"
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
network: Add virtio-net dependencies The newly added virtio-net implementation needs to interact with TAP interfaces and MAC addresses, which is the reason why it is easier to rely on existing packages net_util and net_gen. One more thing, both net_util and net_gen could be trimmed down, based on using only the things we need from cloud-hypervisor. Both net_util, net_gen and sys_util are based on Firecracker commit d4a89cdc0bd2867f821e3678328dabad6dd8b767. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-08 05:28:02 +00:00
[[package]]
name = "serde"
build: bump serde from 1.0.135 to 1.0.136 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.135 to 1.0.136. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.135...v1.0.136) --- updated-dependencies: - dependency-name: serde dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-26 14:12:30 +00:00
version = "1.0.136"
network: Add virtio-net dependencies The newly added virtio-net implementation needs to interact with TAP interfaces and MAC addresses, which is the reason why it is easier to rely on existing packages net_util and net_gen. One more thing, both net_util and net_gen could be trimmed down, based on using only the things we need from cloud-hypervisor. Both net_util, net_gen and sys_util are based on Firecracker commit d4a89cdc0bd2867f821e3678328dabad6dd8b767. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-08 05:28:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump serde from 1.0.135 to 1.0.136 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.135 to 1.0.136. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.135...v1.0.136) --- updated-dependencies: - dependency-name: serde dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-26 14:12:30 +00:00
checksum = "ce31e24b01e1e524df96f1c2fdd054405f8d7376249a5110886fb4b658484789"
network: Add virtio-net dependencies The newly added virtio-net implementation needs to interact with TAP interfaces and MAC addresses, which is the reason why it is easier to rely on existing packages net_util and net_gen. One more thing, both net_util and net_gen could be trimmed down, based on using only the things we need from cloud-hypervisor. Both net_util, net_gen and sys_util are based on Firecracker commit d4a89cdc0bd2867f821e3678328dabad6dd8b767. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-08 05:28:02 +00:00
vmm: {De}serialize VmConfig We use the serde crate to serialize and deserialize the VmVConfig structure. This structure will be passed from the HTTP API caller as a JSON payload and we need to deserialize it into a VmConfig. For a convenient use of the HTTP API, we also provide Default traits implementations for some of the VmConfig fields (vCPUs, memory, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-09-27 09:40:50 +00:00
[[package]]
name = "serde_derive"
build: bump serde_derive from 1.0.135 to 1.0.136 Bumps [serde_derive](https://github.com/serde-rs/serde) from 1.0.135 to 1.0.136. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.135...v1.0.136) --- updated-dependencies: - dependency-name: serde_derive dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-26 15:14:53 +00:00
version = "1.0.136"
vmm: {De}serialize VmConfig We use the serde crate to serialize and deserialize the VmVConfig structure. This structure will be passed from the HTTP API caller as a JSON payload and we need to deserialize it into a VmConfig. For a convenient use of the HTTP API, we also provide Default traits implementations for some of the VmConfig fields (vCPUs, memory, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-09-27 09:40:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump serde_derive from 1.0.135 to 1.0.136 Bumps [serde_derive](https://github.com/serde-rs/serde) from 1.0.135 to 1.0.136. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.135...v1.0.136) --- updated-dependencies: - dependency-name: serde_derive dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-26 15:14:53 +00:00
checksum = "08597e7152fcd306f41838ed3e37be9eaeed2b61c42e2117266a554fab4662f9"
vmm: {De}serialize VmConfig We use the serde crate to serialize and deserialize the VmVConfig structure. This structure will be passed from the HTTP API caller as a JSON payload and we need to deserialize it into a VmConfig. For a convenient use of the HTTP API, we also provide Default traits implementations for some of the VmConfig fields (vCPUs, memory, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-09-27 09:40:50 +00:00
dependencies = [
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
"proc-macro2",
"quote",
"syn",
vmm: {De}serialize VmConfig We use the serde crate to serialize and deserialize the VmVConfig structure. This structure will be passed from the HTTP API caller as a JSON payload and we need to deserialize it into a VmConfig. For a convenient use of the HTTP API, we also provide Default traits implementations for some of the VmConfig fields (vCPUs, memory, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-09-27 09:40:50 +00:00
]
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
[[package]]
name = "serde_json"
build: bump serde_json from 1.0.78 to 1.0.79 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.78 to 1.0.79. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.78...v1.0.79) --- updated-dependencies: - dependency-name: serde_json dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-14 23:14:11 +00:00
version = "1.0.79"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump serde_json from 1.0.78 to 1.0.79 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.78 to 1.0.79. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.78...v1.0.79) --- updated-dependencies: - dependency-name: serde_json dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-14 23:14:11 +00:00
checksum = "8e8d9fa5c3b304765ce1fd9c4c8a3de2c8db365a5b91be52f186efc675681d95"
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
dependencies = [
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
"itoa",
"ryu",
"serde",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
[[package]]
name = "signal-hook"
build: bump signal-hook from 0.3.12 to 0.3.13 Bumps [signal-hook](https://github.com/vorner/signal-hook) from 0.3.12 to 0.3.13. - [Release notes](https://github.com/vorner/signal-hook/releases) - [Changelog](https://github.com/vorner/signal-hook/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/signal-hook/compare/v0.3.12...v0.3.13) --- updated-dependencies: - dependency-name: signal-hook dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-20 23:14:55 +00:00
version = "0.3.13"
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump signal-hook from 0.3.12 to 0.3.13 Bumps [signal-hook](https://github.com/vorner/signal-hook) from 0.3.12 to 0.3.13. - [Release notes](https://github.com/vorner/signal-hook/releases) - [Changelog](https://github.com/vorner/signal-hook/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/signal-hook/compare/v0.3.12...v0.3.13) --- updated-dependencies: - dependency-name: signal-hook dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-20 23:14:55 +00:00
checksum = "647c97df271007dcea485bb74ffdb57f2e683f1306c854f468a0c244badabf2d"
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
dependencies = [
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
"libc",
"signal-hook-registry",
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
]
[[package]]
name = "signal-hook-registry"
build: bump signal-hook from 0.3.8 to 0.3.9 Bumps [signal-hook](https://github.com/vorner/signal-hook) from 0.3.8 to 0.3.9. - [Release notes](https://github.com/vorner/signal-hook/releases) - [Changelog](https://github.com/vorner/signal-hook/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/signal-hook/compare/v0.3.8...v0.3.9) --- updated-dependencies: - dependency-name: signal-hook dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-06-02 07:23:14 +00:00
version = "1.4.0"
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump signal-hook from 0.3.8 to 0.3.9 Bumps [signal-hook](https://github.com/vorner/signal-hook) from 0.3.8 to 0.3.9. - [Release notes](https://github.com/vorner/signal-hook/releases) - [Changelog](https://github.com/vorner/signal-hook/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/signal-hook/compare/v0.3.8...v0.3.9) --- updated-dependencies: - dependency-name: signal-hook dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-06-02 07:23:14 +00:00
checksum = "e51e73328dc4ac0c7ccbda3a494dfa03df1de2f46018127f60c693f2648455b0"
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
dependencies = [
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
"libc",
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
]
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
[[package]]
name = "smallvec"
build: bump smallvec from 1.7.0 to 1.8.0 Bumps [smallvec](https://github.com/servo/rust-smallvec) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/servo/rust-smallvec/releases) - [Commits](https://github.com/servo/rust-smallvec/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: smallvec dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-14 23:21:54 +00:00
version = "1.8.0"
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump smallvec from 1.7.0 to 1.8.0 Bumps [smallvec](https://github.com/servo/rust-smallvec) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/servo/rust-smallvec/releases) - [Commits](https://github.com/servo/rust-smallvec/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: smallvec dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-14 23:21:54 +00:00
checksum = "f2dd574626839106c320a323308629dcb1acfc96e32a8cba364ddc61ac23ee83"
build(deps): bump ssh2 from 0.6.0 to 0.7.1 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.6.0 to 0.7.1. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.6.0...0.7.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-25 22:43:45 +00:00
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
[[package]]
name = "ssh2"
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
version = "0.9.3"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump ssh2 from 0.9.1 to 0.9.3 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.1 to 0.9.3. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.1...0.9.3) --- updated-dependencies: - dependency-name: ssh2 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:09:59 +00:00
checksum = "269343e64430067a14937ae0e3c4ec604c178fb896dde0964b1acd22b3e2eeb1"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
dependencies = [
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"bitflags",
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
"libc",
"libssh2-sys",
"parking_lot",
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
]
hypervisor: x86: Add a CpuStateManager interface For efficiently emulating x86 instructions, we need to build and pass a CPU state copy/reference to instruction emulation handlers. Those handlers will typically modify the CPU state and let the caller commit those changes back through the PlatformEmulator trait set_cpu_state method. Hypervisors typically have internal CPU state structures, that maps back to the correspinding kernel APIs. By implementing the CpuState trait, instruction emulators will be able to directly work on CPU state instances that are directly consumable by the underlying hypervisor and its kernel APIs. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-13 11:30:25 +00:00
[[package]]
name = "static_assertions"
deps: bump iced-x86 from 1.10.3 to 1.11.0 Bumps iced-x86 from 1.10.3 to 1.11.0. Manual update of the code was needed since memory_displacement() was deprecated and replaced with either memory_displacement32() or memory_displacement64(). Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-03-22 14:39:51 +00:00
version = "1.1.0"
hypervisor: x86: Add a CpuStateManager interface For efficiently emulating x86 instructions, we need to build and pass a CPU state copy/reference to instruction emulation handlers. Those handlers will typically modify the CPU state and let the caller commit those changes back through the PlatformEmulator trait set_cpu_state method. Hypervisors typically have internal CPU state structures, that maps back to the correspinding kernel APIs. By implementing the CpuState trait, instruction emulators will be able to directly work on CPU state instances that are directly consumable by the underlying hypervisor and its kernel APIs. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-13 11:30:25 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: bump iced-x86 from 1.10.3 to 1.11.0 Bumps iced-x86 from 1.10.3 to 1.11.0. Manual update of the code was needed since memory_displacement() was deprecated and replaced with either memory_displacement32() or memory_displacement64(). Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-03-22 14:39:51 +00:00
checksum = "a2eb9349b6444b326872e140eb1cf5e7c522154d69e7a0ffb0fb81c06b37543f"
hypervisor: x86: Add a CpuStateManager interface For efficiently emulating x86 instructions, we need to build and pass a CPU state copy/reference to instruction emulation handlers. Those handlers will typically modify the CPU state and let the caller commit those changes back through the PlatformEmulator trait set_cpu_state method. Hypervisors typically have internal CPU state structures, that maps back to the correspinding kernel APIs. By implementing the CpuState trait, instruction emulators will be able to directly work on CPU state instances that are directly consumable by the underlying hypervisor and its kernel APIs. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-13 11:30:25 +00:00
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
[[package]]
name = "strsim"
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
version = "0.10.0"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
checksum = "73473c0e59e6d5812c5dfe2a064a6444949f089e20eec9a2e5506596494e4623"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
[[package]]
name = "syn"
build: bump syn from 1.0.85 to 1.0.86 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.85 to 1.0.86. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.85...1.0.86) --- updated-dependencies: - dependency-name: syn dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-20 23:38:12 +00:00
version = "1.0.86"
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump syn from 1.0.85 to 1.0.86 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.85 to 1.0.86. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.85...1.0.86) --- updated-dependencies: - dependency-name: syn dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-01-20 23:38:12 +00:00
checksum = "8a65b3f4ffa0092e9887669db0eae07941f023991ab58ea44da8fe8e2d511c6b"
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
dependencies = [
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
"proc-macro2",
"quote",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"unicode-xid",
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
]
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
[[package]]
name = "synstructure"
build: bump synstructure from 0.12.5 to 0.12.6 Bumps [synstructure](https://github.com/mystor/synstructure) from 0.12.5 to 0.12.6. - [Release notes](https://github.com/mystor/synstructure/releases) - [Commits](https://github.com/mystor/synstructure/commits) --- updated-dependencies: - dependency-name: synstructure dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-11 23:09:17 +00:00
version = "0.12.6"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump synstructure from 0.12.5 to 0.12.6 Bumps [synstructure](https://github.com/mystor/synstructure) from 0.12.5 to 0.12.6. - [Release notes](https://github.com/mystor/synstructure/releases) - [Commits](https://github.com/mystor/synstructure/commits) --- updated-dependencies: - dependency-name: synstructure dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-11 23:09:17 +00:00
checksum = "f36bdaa60a83aca3921b5259d5400cbf5e90fc51931376a9bd4a0eb79aa7210f"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
dependencies = [
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
"proc-macro2",
"quote",
"syn",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"unicode-xid",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
build: Use "wrap_help" feature for clap This prevents the output being wrapped at 120 characters and giving strange results. Fixes: #899 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-03-12 16:00:40 +00:00
[[package]]
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
name = "termcolor"
build: bump termcolor from 1.1.2 to 1.1.3 Bumps [termcolor](https://github.com/BurntSushi/termcolor) from 1.1.2 to 1.1.3. - [Release notes](https://github.com/BurntSushi/termcolor/releases) - [Commits](https://github.com/BurntSushi/termcolor/compare/1.1.2...1.1.3) --- updated-dependencies: - dependency-name: termcolor dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-03 00:01:51 +00:00
version = "1.1.3"
build: Use "wrap_help" feature for clap This prevents the output being wrapped at 120 characters and giving strange results. Fixes: #899 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-03-12 16:00:40 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump termcolor from 1.1.2 to 1.1.3 Bumps [termcolor](https://github.com/BurntSushi/termcolor) from 1.1.2 to 1.1.3. - [Release notes](https://github.com/BurntSushi/termcolor/releases) - [Commits](https://github.com/BurntSushi/termcolor/compare/1.1.2...1.1.3) --- updated-dependencies: - dependency-name: termcolor dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-03 00:01:51 +00:00
checksum = "bab24d30b911b2376f3a13cc2cd443142f0c81dda04c118693e35b3835757755"
build: Use "wrap_help" feature for clap This prevents the output being wrapped at 120 characters and giving strange results. Fixes: #899 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-03-12 16:00:40 +00:00
dependencies = [
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
"winapi-util",
build: Use "wrap_help" feature for clap This prevents the output being wrapped at 120 characters and giving strange results. Fixes: #899 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-03-12 16:00:40 +00:00
]
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
[[package]]
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
name = "terminal_size"
version = "0.1.17"
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
checksum = "633c1a546cee861a1a6d0dc69ebeca693bf4296661ba7852b9d21d159e0506df"
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
dependencies = [
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
"libc",
"winapi",
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
]
tests: Move test_infra from a module to crate It must be specified as excluded from the workspace as it must not be built on non-test targets due to issues with the ssh2 dependency and the musl toolchain. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-03-23 16:15:48 +00:00
[[package]]
name = "test_infra"
version = "0.1.0"
dependencies = [
build: Use consistent version of dirs crate Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-03-03 15:47:14 +00:00
"dirs",
tests: Move test_infra from a module to crate It must be specified as excluded from the workspace as it must not be built on non-test targets due to issues with the ssh2 dependency and the musl toolchain. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-03-23 16:15:48 +00:00
"epoll",
test_infra: Move `struct Guest` and `struct GuestCommand` from tests In this way, these structs can be reused for performance tests. Signed-off-by: Bo Chen <chen.bo@intel.com>
2022-02-04 19:14:41 +00:00
"lazy_static",
tests: Move test_infra from a module to crate It must be specified as excluded from the workspace as it must not be built on non-test targets due to issues with the ssh2 dependency and the musl toolchain. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-03-23 16:15:48 +00:00
"libc",
"ssh2",
"vmm-sys-util",
"wait-timeout",
]
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
[[package]]
name = "textwrap"
build: bump clap from 3.1.3 to 3.1.5 Bumps [clap](https://github.com/clap-rs/clap) from 3.1.3 to 3.1.5. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v3.1.3...v3.1.5) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-02 23:27:37 +00:00
version = "0.15.0"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump clap from 3.1.3 to 3.1.5 Bumps [clap](https://github.com/clap-rs/clap) from 3.1.3 to 3.1.5. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v3.1.3...v3.1.5) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-02 23:27:37 +00:00
checksum = "b1141d4d61095b28419e22cb0bbf02755f5e54e0526f97f1e3d1d160e60885fb"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
dependencies = [
build: bump clap from 2.34.0 to 3.0.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.34.0 to 3.0.0. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v2.34.0...clap_complete-v3.0.0) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-31 23:09:17 +00:00
"terminal_size",
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
]
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-18 14:30:54 +00:00
[[package]]
name = "thiserror"
build: bump thiserror from 1.0.29 to 1.0.30 Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.29 to 1.0.30. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.29...1.0.30) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:10:27 +00:00
version = "1.0.30"
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-18 14:30:54 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump thiserror from 1.0.29 to 1.0.30 Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.29 to 1.0.30. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.29...1.0.30) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:10:27 +00:00
checksum = "854babe52e4df1653706b98fcfc05843010039b406875930a70e4d9644e5c417"
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-18 14:30:54 +00:00
dependencies = [
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
"thiserror-impl",
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-18 14:30:54 +00:00
]
[[package]]
name = "thiserror-impl"
build: bump thiserror from 1.0.29 to 1.0.30 Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.29 to 1.0.30. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.29...1.0.30) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:10:27 +00:00
version = "1.0.30"
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-18 14:30:54 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump thiserror from 1.0.29 to 1.0.30 Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.29 to 1.0.30. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.29...1.0.30) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-10-12 05:10:27 +00:00
checksum = "aa32fd3f627f367fe16f893e2597ae3c05020f8bba2666a4e6ea73d377e5714b"
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-18 14:30:54 +00:00
dependencies = [
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
"proc-macro2",
"quote",
"syn",
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-18 14:30:54 +00:00
]
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
[[package]]
name = "unicode-xid"
build: Bulk upgrade dependencies including fuzz Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-12 12:06:01 +00:00
version = "0.2.2"
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk upgrade dependencies including fuzz Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-12 12:06:01 +00:00
checksum = "8ccb82d61f80a663efe1f787a51b16b5a51e3314d6ac365b08639f52387b33f3"
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
deps: Update Cargo.lock to include uuid crate Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-06-09 13:00:07 +00:00
[[package]]
name = "uuid"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bc5cf98d8186244414c848017f0e2676b3fcb46807f6668a97dfe67359a3c4b7"
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
dependencies = [
"getrandom",
]
deps: Update Cargo.lock to include uuid crate Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-06-09 13:00:07 +00:00
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
[[package]]
name = "vcpkg"
build: bump vcpkg from 0.2.14 to 0.2.15 Bumps [vcpkg](https://github.com/mcgoo/vcpkg-rs) from 0.2.14 to 0.2.15. - [Release notes](https://github.com/mcgoo/vcpkg-rs/releases) - [Changelog](https://github.com/mcgoo/vcpkg-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/mcgoo/vcpkg-rs/compare/vcpkg-rs-0.2.14...vcpkg-rs-0.2.15) --- updated-dependencies: - dependency-name: vcpkg dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-06-21 23:10:33 +00:00
version = "0.2.15"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump vcpkg from 0.2.14 to 0.2.15 Bumps [vcpkg](https://github.com/mcgoo/vcpkg-rs) from 0.2.14 to 0.2.15. - [Release notes](https://github.com/mcgoo/vcpkg-rs/releases) - [Changelog](https://github.com/mcgoo/vcpkg-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/mcgoo/vcpkg-rs/compare/vcpkg-rs-0.2.14...vcpkg-rs-0.2.15) --- updated-dependencies: - dependency-name: vcpkg dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-06-21 23:10:33 +00:00
checksum = "accd4ea62f7bb7a82fe23066fb0957d48ef677f6eeb8215f372f52e48bb32426"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
vm-migration: Add versioned versions of snapshot & state API This will allow progressive porting of parts of the VMM to using versioned state. A new trait VersionMapped is introduced with a default implementation that returns an empty VersionMap to ease implementation. If a struct is updated the the trait will need to be fully implemented with VersionMapped::version_map() returning a new VersionMap handling the change. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-05 15:16:19 +00:00
[[package]]
name = "versionize"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7429cf68de8f091b667d27323ed323afd39584a56d533995b12ddd748e5e6ca9"
dependencies = [
"bincode",
"crc64",
"proc-macro2",
"quote",
"serde",
"serde_derive",
"syn",
"versionize_derive",
"vmm-sys-util",
]
[[package]]
name = "versionize_derive"
version = "0.1.4"
build: Use versionize_derive from Cloud Hypervisor fork This allows the use of #[derive(Versionize)] on packed structs. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-06 13:31:41 +00:00
source = "git+https://github.com/cloud-hypervisor/versionize_derive?branch=ch#ae35ef7a3ddabd3371ab8ac0193a383aff6e4b1b"
vm-migration: Add versioned versions of snapshot & state API This will allow progressive porting of parts of the VMM to using versioned state. A new trait VersionMapped is introduced with a default implementation that returns an empty VersionMap to ease implementation. If a struct is updated the the trait will need to be fully implemented with VersionMapped::version_map() returning a new VersionMap handling the change. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-05 15:16:19 +00:00
dependencies = [
"proc-macro2",
"quote",
"syn",
]
vmm: Support direct device assignment With the VFIO crate, we can now support directly assigned PCI devices into cloud-hypervisor guests. We support assigning multiple host devices, through the --device command line parameter. This parameter takes the host device sysfs path. Fixes: #60 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-07-15 09:42:40 +00:00
[[package]]
vfio: Rename to vfio-ioctls Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-08 15:27:05 +00:00
name = "vfio-bindings"
build: bump vfio-bindings from 0.2.0 to 0.3.1 Bumps [vfio-bindings](https://github.com/rust-vmm/vfio) from 0.2.0 to 0.3.1. - [Release notes](https://github.com/rust-vmm/vfio/releases) - [Commits](https://github.com/rust-vmm/vfio/commits/vfio-bindings-v0.3.1) --- updated-dependencies: - dependency-name: vfio-bindings dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-20 23:14:31 +00:00
version = "0.3.1"
pci: use vfio-bindings from crates.io This fixes `cargo vendor` throwing an error ``` $ cargo vendor error: failed to sync Caused by: found duplicate version of package `vfio-bindings v0.2.0` vendored from two sources: source 1: https://github.com/rust-vmm/vfio-bindings#f08cbcbf source 2: registry `https://github.com/rust-lang/crates.io-index` ``` Both sources are indeed same, the conflict is only cause by the different URLs. Signed-off-by: Anatol Belski <ab@php.net>
2020-08-05 11:53:09 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump vfio-bindings from 0.2.0 to 0.3.1 Bumps [vfio-bindings](https://github.com/rust-vmm/vfio) from 0.2.0 to 0.3.1. - [Release notes](https://github.com/rust-vmm/vfio/releases) - [Commits](https://github.com/rust-vmm/vfio/commits/vfio-bindings-v0.3.1) --- updated-dependencies: - dependency-name: vfio-bindings dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-20 23:14:31 +00:00
checksum = "43449b404c488f70507dca193debd4bea361fe8089869b947adc19720e464bce"
vfio: Rename to vfio-ioctls Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-08 15:27:05 +00:00
dependencies = [
"vmm-sys-util",
]
[[package]]
name = "vfio-ioctls"
vfio: Switch to the vfio-ioctls crate ch branch Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-12 14:36:07 +00:00
version = "0.1.0"
build: bump vfio-ioctls from `4630612` to `f75a77c` Bumps [vfio-ioctls](https://github.com/rust-vmm/vfio) from `4630612` to `f75a77c`. - [Release notes](https://github.com/rust-vmm/vfio/releases) - [Commits](https://github.com/rust-vmm/vfio/compare/4630612f2ff300e78b6d55be324fb5481aa84661...f75a77c1ab6349c105bc1462a65508726b4c2e0f) --- updated-dependencies: - dependency-name: vfio-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2022-02-16 09:32:03 +00:00
source = "git+https://github.com/rust-vmm/vfio?branch=main#f75a77c1ab6349c105bc1462a65508726b4c2e0f"
vmm: Support direct device assignment With the VFIO crate, we can now support directly assigned PCI devices into cloud-hypervisor guests. We support assigning multiple host devices, through the --device command line parameter. This parameter takes the host device sysfs path. Fixes: #60 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-07-15 09:42:40 +00:00
dependencies = [
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
"byteorder",
"kvm-bindings",
"kvm-ioctls",
build: bump vfio-ioctls from `bcf2e64` to `19e5b83` Bumps [vfio-ioctls](https://github.com/rust-vmm/vfio-ioctls) from `bcf2e64` to `19e5b83`. - [Release notes](https://github.com/rust-vmm/vfio-ioctls/releases) - [Commits](https://github.com/rust-vmm/vfio-ioctls/compare/bcf2e6486d44e342d49784813394bd5429d42a35...19e5b83ddfad430109ce3e8d51f4a24796099127) --- updated-dependencies: - dependency-name: vfio-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-01 01:51:39 +00:00
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
build: use vfio-ioctls that supports MSHV Disable default features and propagate hypervisor selection where necessary. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2021-09-02 09:44:08 +00:00
"mshv-bindings",
"mshv-ioctls",
build: bump vfio-ioctls from `bcf2e64` to `19e5b83` Bumps [vfio-ioctls](https://github.com/rust-vmm/vfio-ioctls) from `bcf2e64` to `19e5b83`. - [Release notes](https://github.com/rust-vmm/vfio-ioctls/releases) - [Commits](https://github.com/rust-vmm/vfio-ioctls/compare/bcf2e6486d44e342d49784813394bd5429d42a35...19e5b83ddfad430109ce3e8d51f4a24796099127) --- updated-dependencies: - dependency-name: vfio-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-01 01:51:39 +00:00
"thiserror",
pci: use vfio-bindings from crates.io This fixes `cargo vendor` throwing an error ``` $ cargo vendor error: failed to sync Caused by: found duplicate version of package `vfio-bindings v0.2.0` vendored from two sources: source 1: https://github.com/rust-vmm/vfio-bindings#f08cbcbf source 2: registry `https://github.com/rust-lang/crates.io-index` ``` Both sources are indeed same, the conflict is only cause by the different URLs. Signed-off-by: Anatol Belski <ab@php.net>
2020-08-05 11:53:09 +00:00
"vfio-bindings",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
vfio_user: Implement client side support Implement (most) of the client side (i.e. VMM side) of the vfio-user protocol: https://github.com/nutanix/libvfio-user/blob/master/docs/vfio-user.rst Items that are not implemented (because they are optimisations or unused due to alternative solutions: * VFIO_USER_DMA_READ/WRITE - this is a way for the server to read guest memory if the guest memory is not shared by fd where the client doesn't support it. However since we do support sharing the memory by fd this is not required. * VFIO_USER_GET_REGION_IO_FDS - an optimisation to bypass the VMM by having KVM talk directly to the backend using ioregionfd * VFIO_USER_DIRTY_PAGES - for the implementation of live migration Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-06-04 11:42:36 +00:00
"vmm-sys-util",
]
[[package]]
name = "vfio_user"
version = "0.1.0"
dependencies = [
"anyhow",
"libc",
"log",
"serde",
"serde_derive",
"serde_json",
"thiserror",
"vfio-bindings",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
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
"vmm-sys-util",
vmm: Support direct device assignment With the VFIO crate, we can now support directly assigned PCI devices into cloud-hypervisor guests. We support assigning multiple host devices, through the --device command line parameter. This parameter takes the host device sysfs path. Fixes: #60 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-07-15 09:42:40 +00:00
]
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
[[package]]
name = "vhdx"
version = "0.1.0"
dependencies = [
"byteorder",
"crc32c",
"libc",
"log",
"remain",
"thiserror",
"uuid",
"vmm-sys-util",
]
vm-virtio: Add vhost-user-fs support The vhost-user-fs or virtio-fs device allows files and directories to be shared between host and guest. This patch adds the implementation of this device to the cloud-hypervisor device model. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-21 18:54:53 +00:00
[[package]]
Cargo: switch vhost_rs to external crate As cloud-hypervisor/vhost crate (dragonball branch) is ready to be used, switch vhost_rs from internal crate to the external one. Signed-off-by: Eryu Guan <eguan@linux.alibaba.com>
2020-02-25 03:26:35 +00:00
name = "vhost"
build: bump vhost from 0.2.0 to 0.3.0 Bumps [vhost](https://github.com/rust-vmm/vhost) from 0.2.0 to 0.3.0. - [Release notes](https://github.com/rust-vmm/vhost/releases) - [Changelog](https://github.com/rust-vmm/vhost/blob/main/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/vhost/compare/v0.2.0...v0.3.0) --- updated-dependencies: - dependency-name: vhost dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-20 23:13:43 +00:00
version = "0.3.0"
deps: Move to vhost 0.2.0 There's no need to patch the vhost crate anymore since the fixes we were looking for have been released as part of 0.2.0 on crates.io. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-07 08:44:23 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump vhost from 0.2.0 to 0.3.0 Bumps [vhost](https://github.com/rust-vmm/vhost) from 0.2.0 to 0.3.0. - [Release notes](https://github.com/rust-vmm/vhost/releases) - [Changelog](https://github.com/rust-vmm/vhost/blob/main/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/vhost/compare/v0.2.0...v0.3.0) --- updated-dependencies: - dependency-name: vhost dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2021-12-20 23:13:43 +00:00
checksum = "3b56bf8f178fc500fe14505fca8b00dec76fc38f2304f461c8d9d7547982311d"
vm-virtio: Add vhost-user-fs support The vhost-user-fs or virtio-fs device allows files and directories to be shared between host and guest. This patch adds the implementation of this device to the cloud-hypervisor device model. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-21 18:54:53 +00:00
dependencies = [
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"bitflags",
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
"libc",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
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
"vmm-sys-util",
vm-virtio: Add vhost-user-fs support The vhost-user-fs or virtio-fs device allows files and directories to be shared between host and guest. This patch adds the implementation of this device to the cloud-hypervisor device model. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-21 18:54:53 +00:00
]
vhost_user_net: Rely on upstream vhost-user-backend crate Instead of relying on the local version of vhost-user-backend, this patch allows the block backend implementation to rely on the upstream version of the crate from rust-vmm. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-02-02 10:36:47 +00:00
[[package]]
name = "vhost-user-backend"
version = "0.1.0"
build: bump vhost-user-backend from `bbc892b` to `6e66d2c` Bumps [vhost-user-backend](https://github.com/rust-vmm/vhost-user-backend) from `bbc892b` to `6e66d2c`. - [Release notes](https://github.com/rust-vmm/vhost-user-backend/releases) - [Commits](https://github.com/rust-vmm/vhost-user-backend/compare/bbc892ba4526bdf8101252f7aa51832d1f2eeabd...6e66d2c1a4c460fa7306bd890e7a99e64a0254d6) --- updated-dependencies: - dependency-name: vhost-user-backend dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-03 23:13:08 +00:00
source = "git+https://github.com/rust-vmm/vhost-user-backend?branch=main#6e66d2c1a4c460fa7306bd890e7a99e64a0254d6"
vhost_user_net: Rely on upstream vhost-user-backend crate Instead of relying on the local version of vhost-user-backend, this patch allows the block backend implementation to rely on the upstream version of the crate from rust-vmm. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-02-02 10:36:47 +00:00
dependencies = [
"libc",
"log",
"vhost",
"virtio-bindings",
"virtio-queue",
"vm-memory",
"vmm-sys-util",
]
vhost_user_fs: Add new crate This new crate will be dedicated to vhost_user_fs specific code that can be used as a library from the vhost-user-fs daemon. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-31 17:16:28 +00:00
[[package]]
vhost_user_block: Refactor vhost_user_block backend code into a new crate Extract the majority of the code that provides the vhost-user-block backend into its own crate and port the binary to use it. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-01-20 16:10:21 +00:00
name = "vhost_user_block"
version = "0.1.0"
dependencies = [
vhost_user_block, virtio-devices, block_util: Extract common block code Extract the code that is used by vhost_user_block from the virtio-devices crate to remove the dependencies on unrequired functionality such as the virtio transports. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-14 09:43:33 +00:00
"block_util",
vhost_user_block: Move binary into vhost_user_block crate The binary is still built in the same location but the source code and the dependencies for it come from the vhost_user_block crate itself. The binary will be built with: `cargo build --all --bin vhost_user_block` or just `cargo build --all` Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-03 14:14:36 +00:00
"clap",
vhost_user_*: set up logging These crates are written to produce log messages using the error! macro, but their logs didn't actually go anywhere, which made it very difficult to debug when they're not working. I've used env_logger here because it's the same log implementation that the hypervisor crate uses. Signed-off-by: Alyssa Ross <hi@alyssa.is>
2021-08-04 19:35:56 +00:00
"env_logger",
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
"epoll",
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
vhost_user_net, vhost_user_block, option_parser: Remove vmm dependency Remove the vmm dependency from vhost_user_block and vhost_user_net where it was existing to use config::OptionParser. By moving the OptionParser to its own crate at the top-level we can remove the very heavy dependency that these vhost-user backends had. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-06 15:41:45 +00:00
"option_parser",
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
"qcow",
"vhost",
build: Use single version of vhost-user-backend Using multiple different versions breaks vendoring. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-03-03 15:45:05 +00:00
"vhost-user-backend",
build: Use same virtio-bindings version Consistently use the crates.io 0.1.0 version based on Linux 5.0.0 Fixes: #1192 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-05-20 10:13:06 +00:00
"virtio-bindings",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
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
"vmm-sys-util",
vhost_user_block: Refactor vhost_user_block backend code into a new crate Extract the majority of the code that provides the vhost-user-block backend into its own crate and port the binary to use it. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-01-20 16:10:21 +00:00
]
vhost_user_net: Refactor vhost_user_net backend code into a new crate Extract the majority of the code that provides the vhost-user-net backend into its own crate and port the binary to use it. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-01-20 16:10:21 +00:00
[[package]]
name = "vhost_user_net"
version = "0.1.0"
dependencies = [
vhost_user_net: Move binary into vhost_user_net crate The binary is still built in the same location but the source code and the dependencies for it come from the vhost_user_net crate itself. The binary will be built with: `cargo build --all --bin vhost_user_net` or just `cargo build --all` Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-03 14:14:36 +00:00
"clap",
vhost_user_*: set up logging These crates are written to produce log messages using the error! macro, but their logs didn't actually go anywhere, which made it very difficult to debug when they're not working. I've used env_logger here because it's the same log implementation that the hypervisor crate uses. Signed-off-by: Alyssa Ross <hi@alyssa.is>
2021-08-04 19:35:56 +00:00
"env_logger",
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
"epoll",
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
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
"net_util",
vhost_user_net, vhost_user_block, option_parser: Remove vmm dependency Remove the vmm dependency from vhost_user_block and vhost_user_net where it was existing to use config::OptionParser. By moving the OptionParser to its own crate at the top-level we can remove the very heavy dependency that these vhost-user backends had. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-06 15:41:45 +00:00
"option_parser",
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
"vhost",
build: Use single version of vhost-user-backend Using multiple different versions breaks vendoring. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-03-03 15:45:05 +00:00
"vhost-user-backend",
build: Use same virtio-bindings version Consistently use the crates.io 0.1.0 version based on Linux 5.0.0 Fixes: #1192 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-05-20 10:13:06 +00:00
"virtio-bindings",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
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
"vmm-sys-util",
vhost_user_net: Refactor vhost_user_net backend code into a new crate Extract the majority of the code that provides the vhost-user-net backend into its own crate and port the binary to use it. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-01-20 16:10:21 +00:00
]
Cargo: Move virtio-bindings to crates.io v0.1.0 was just published. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-10 07:38:42 +00:00
[[package]]
name = "virtio-bindings"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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
checksum = "3ff512178285488516ed85f15b5d0113a7cdb89e9e8a760b269ae4f02b84bd6b"
Cargo: Move virtio-bindings to crates.io v0.1.0 was just published. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-10 07:38:42 +00:00
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
[[package]]
name = "virtio-devices"
version = "0.1.0"
dependencies = [
"anyhow",
"arc-swap",
vhost_user_block, virtio-devices, block_util: Extract common block code Extract the code that is used by vhost_user_block from the virtio-devices crate to remove the dependencies on unrequired functionality such as the virtio transports. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-14 09:43:33 +00:00
"block_util",
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
"byteorder",
"epoll",
virtio-devices: Report events for virtio device activation and reset Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-02-18 15:10:51 +00:00
"event_monitor",
virtio-devices: Add an asynchronous virtio-blk device This introduces a new version of virtio-blk device. The default virtio-blk provides synchronous processing of the queues, while this new version relies on io_uring from the host kernel to provide an asynchronous processing of the queues. This new asynchronous version provides a huge performance improvement compared to the default synchronous version. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-07-30 10:40:09 +00:00
"io-uring",
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
"libc",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
"net_gen",
"net_util",
"pci",
virtio-devices: Move the 'rate_limiter' module to its own crate To support I/O throttling on virt-net devices, we need to use the 'rate_limiter' module from the 'net_utils' crate. Given the 'virtio-devices' crate has dependency on the 'net_utils', we will need to move the 'rate_limiter' module out of the 'virtio-devices' crate to avoid circular dependency issue. Considering the 'rate_limiter' is not virtio specific and could be reused for non virtio devices, we move it to its own crate. Signed-off-by: Bo Chen <chen.bo@intel.com>
2021-03-22 18:23:51 +00:00
"rate_limiter",
virtio-devices, vmm: Move to the seccompiler crate Fixes: #2929 Signed-off-by: Bo Chen <chen.bo@intel.com>
2021-08-17 03:40:11 +00:00
"seccompiler",
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
"serde",
"serde_derive",
"serde_json",
virtio-devices: Version state structures Version the state for device state for the virtio devices. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-06 13:34:31 +00:00
"versionize",
"versionize_derive",
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
"vhost",
"virtio-bindings",
Move Cloud Hypervisor to virtio-queue crate Relying on the vm-virtio/virtio-queue crate from rust-vmm which has been copied inside the Cloud Hypervisor tree, the entire codebase is moved to the new definition of a Queue and other related structures. The reason for this move is to follow the upstream until we get some agreement for the patches that we need on top of that to make it properly work with Cloud Hypervisor. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-21 10:41:16 +00:00
"virtio-queue",
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
"vm-allocator",
"vm-device",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
"vm-migration",
"vm-virtio",
"vmm-sys-util",
]
Move Cloud Hypervisor to virtio-queue crate Relying on the vm-virtio/virtio-queue crate from rust-vmm which has been copied inside the Cloud Hypervisor tree, the entire codebase is moved to the new definition of a Queue and other related structures. The reason for this move is to follow the upstream until we get some agreement for the patches that we need on top of that to make it properly work with Cloud Hypervisor. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-21 10:41:16 +00:00
[[package]]
name = "virtio-queue"
version = "0.1.0"
build: bump clap from 3.1.3 to 3.1.5 Bumps [clap](https://github.com/clap-rs/clap) from 3.1.3 to 3.1.5. - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/v3.1.3...v3.1.5) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-02 23:27:37 +00:00
source = "git+https://github.com/rust-vmm/vm-virtio?branch=main#bbb22d43558a76cc7cc9c262c4be870a9e682a86"
Move Cloud Hypervisor to virtio-queue crate Relying on the vm-virtio/virtio-queue crate from rust-vmm which has been copied inside the Cloud Hypervisor tree, the entire codebase is moved to the new definition of a Queue and other related structures. The reason for this move is to follow the upstream until we get some agreement for the patches that we need on top of that to make it properly work with Cloud Hypervisor. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-21 10:41:16 +00:00
dependencies = [
"log",
"vm-memory",
"vmm-sys-util",
]
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
[[package]]
name = "vm-allocator"
version = "0.1.0"
dependencies = [
build: Update Cargo.lock An update to the Cargo.lock file was missing from a previous commit. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-06-11 14:08:34 +00:00
"arch",
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
"libc",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
]
vm-device: Add new crate for virtio and VFIO agnostic traits The new crate vm-device is created here to host the definitions of traits not meant to be tied to virtio of VFIO specifically. We need to add a new trait to update external DMA mappings for devices, which is why the vm-device crate is the right fit for this. We can expect this crate to be extended later once the design gets approved from a rust-vmm perspective. In this specific use case, we can have some devices like VFIO or vhost-user ones requiring to be notified about mapping updates. This new trait ExternalDmaMapping will allow such devices to implement their own way to handle such event. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-07 16:57:19 +00:00
[[package]]
name = "vm-device"
version = "0.1.0"
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-18 14:30:54 +00:00
dependencies = [
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
"anyhow",
"serde",
"serde_derive",
"serde_json",
"thiserror",
vm-device: Move ExternalDmaMapping trait out of vfio-ioctls By moving the trait and its VFIO implementation out of vfio-ioctls, we give anticipate for the move to the vfio-ioctls from rust-vmm. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-02-23 13:47:56 +00:00
"vfio-ioctls",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
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
"vmm-sys-util",
vm-device: Initial Migratable trait The Migratable trait groups all expected capabilities of devices and components that can be migrated. For a component to be migrated, it must be able to pause and resume. Once paused, it should be able to provide a snapshot of itself. It should also be able to restore itself from a snaphot. As a consequence, the Migratable trait will be split between the Pausable and the Snapshotable traits. This commit only adds the Pausable one. All migratable devices will be tracked from the DeviceManager. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-18 14:30:54 +00:00
]
vm-device: Add new crate for virtio and VFIO agnostic traits The new crate vm-device is created here to host the definitions of traits not meant to be tied to virtio of VFIO specifically. We need to add a new trait to update external DMA mappings for devices, which is why the vm-device crate is the right fit for this. We can expect this crate to be extended later once the design gets approved from a rust-vmm perspective. In this specific use case, we can have some devices like VFIO or vhost-user ones requiring to be notified about mapping updates. This new trait ExternalDmaMapping will allow such devices to implement their own way to handle such event. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-07 16:57:19 +00:00
build: Bump vhost from `c4cd1d3` to `cc4da71` Bumps [vhost](https://github.com/rust-vmm/vhost) from `c4cd1d3` to `cc4da71`. - [Release notes](https://github.com/rust-vmm/vhost/releases) - [Commits](https://github.com/rust-vmm/vhost/compare/c4cd1d375e386069d0b781174de9f62ef41812e2...cc4da710ac68ca8ffe68cddcd80d562699445522) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-10 10:19:24 +00:00
[[package]]
name = "vm-fdt"
build: bump vm-fdt from `88554cf` to `d10837b` Bumps [vm-fdt](https://github.com/rust-vmm/vm-fdt) from `88554cf` to `d10837b`. - [Release notes](https://github.com/rust-vmm/vm-fdt/releases) - [Commits](https://github.com/rust-vmm/vm-fdt/compare/88554cfb0d62651b3d515bc8f40f84f944196015...d10837b6e94012a90178848df8c5f8515476aaab) --- updated-dependencies: - dependency-name: vm-fdt dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2021-11-01 23:09:38 +00:00
version = "0.2.0"
build: bump vm-fdt from `dccd69c` to `ca35d96` Bumps [vm-fdt](https://github.com/rust-vmm/vm-fdt) from `dccd69c` to `ca35d96`. - [Release notes](https://github.com/rust-vmm/vm-fdt/releases) - [Commits](https://github.com/rust-vmm/vm-fdt/compare/dccd69c9b23e9cca56ea9e3a8b009841c7579c88...ca35d96191f8232bd7ab8c3e72ec925bf04bd2e0) --- updated-dependencies: - dependency-name: vm-fdt dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-02 23:27:55 +00:00
source = "git+https://github.com/rust-vmm/vm-fdt?branch=main#ca35d96191f8232bd7ab8c3e72ec925bf04bd2e0"
build: Bump vhost from `c4cd1d3` to `cc4da71` Bumps [vhost](https://github.com/rust-vmm/vhost) from `c4cd1d3` to `cc4da71`. - [Release notes](https://github.com/rust-vmm/vhost/releases) - [Commits](https://github.com/rust-vmm/vhost/compare/c4cd1d375e386069d0b781174de9f62ef41812e2...cc4da710ac68ca8ffe68cddcd80d562699445522) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-10 10:19:24 +00:00
build: bump vhost from `37a6a8e` to `56ad2ae` Bumps [vhost](https://github.com/rust-vmm/vhost) from `37a6a8e` to `56ad2ae`. - [Release notes](https://github.com/rust-vmm/vhost/releases) - [Commits](https://github.com/rust-vmm/vhost/compare/37a6a8e46444e9e4b59be5bff82e5c22a879f0c4...56ad2ae4dd20405dd2cffc1c692646269a6604a7) --- updated-dependencies: - dependency-name: vhost dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-05 23:09:54 +00:00
[[package]]
name = "vm-memory"
deps: Bump vm-memory to 0.7.0 Updating Cloud Hypervisor to rely on vm-memory version 0.7.0. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-21 09:21:37 +00:00
version = "0.7.0"
build: bump vhost from `37a6a8e` to `56ad2ae` Bumps [vhost](https://github.com/rust-vmm/vhost) from `37a6a8e` to `56ad2ae`. - [Release notes](https://github.com/rust-vmm/vhost/releases) - [Commits](https://github.com/rust-vmm/vhost/compare/37a6a8e46444e9e4b59be5bff82e5c22a879f0c4...56ad2ae4dd20405dd2cffc1c692646269a6604a7) --- updated-dependencies: - dependency-name: vhost dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-05 23:09:54 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: Bump vm-memory to 0.7.0 Updating Cloud Hypervisor to rely on vm-memory version 0.7.0. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-12-21 09:21:37 +00:00
checksum = "339d4349c126fdcd87e034631d7274370cf19eb0e87b33166bcd956589fc72c5"
build: bump vhost from `37a6a8e` to `56ad2ae` Bumps [vhost](https://github.com/rust-vmm/vhost) from `37a6a8e` to `56ad2ae`. - [Release notes](https://github.com/rust-vmm/vhost/releases) - [Commits](https://github.com/rust-vmm/vhost/compare/37a6a8e46444e9e4b59be5bff82e5c22a879f0c4...56ad2ae4dd20405dd2cffc1c692646269a6604a7) --- updated-dependencies: - dependency-name: vhost dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-05 23:09:54 +00:00
dependencies = [
build: Move from patched vm-memory version to released version Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-08-06 07:46:17 +00:00
"arc-swap",
build: bump vhost from `37a6a8e` to `56ad2ae` Bumps [vhost](https://github.com/rust-vmm/vhost) from `37a6a8e` to `56ad2ae`. - [Release notes](https://github.com/rust-vmm/vhost/releases) - [Commits](https://github.com/rust-vmm/vhost/compare/37a6a8e46444e9e4b59be5bff82e5c22a879f0c4...56ad2ae4dd20405dd2cffc1c692646269a6604a7) --- updated-dependencies: - dependency-name: vhost dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-05 23:09:54 +00:00
"libc",
"winapi",
]
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"
dependencies = [
"anyhow",
"serde",
"serde_derive",
"serde_json",
"thiserror",
vm-migration: Add versioned versions of snapshot & state API This will allow progressive porting of parts of the VMM to using versioned state. A new trait VersionMapped is introduced with a default implementation that returns an empty VersionMap to ease implementation. If a struct is updated the the trait will need to be fully implemented with VersionMapped::version_map() returning a new VersionMap handling the change. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-05 15:16:19 +00:00
"versionize",
"versionize_derive",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
cloud-hypervisor: Call into the test_vm() routine test_vm is a dummy VM workload, we use it to test our initial VMM settings. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-22 16:05:02 +00:00
]
vmm: Use virtio-blk to support booting from disk image After the virtio-blk device support has been introduced in the previous commit, the vmm need to rely on this new device to boot from disk images instead of initrd built into the kernel. In order to achieve the proper support of virtio-blk, this commit had to handle a few things: - Register an ioevent fd for each virtqueue. This important to be notified from the virtio driver that something has been written on the queue. - Fix the retrieval of 64bits BAR address. This is needed to provide the right address which need to be registered as the notification address from the virtio driver. - Fix the write_bar and read_bar functions. They were both assuming to be provided with an address, from which they were trying to find the associated offset. But the reality is that the offset is directly provided by the Bus layer. - Register a new virtio-blk device as a virtio-pci device from the vm.rs code. When the VM is started, it expects a block device to be created, using this block device as the VM rootfs. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-06 17:27:40 +00:00
[[package]]
name = "vm-virtio"
version = "0.1.0"
dependencies = [
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
build: Use same virtio-bindings version Consistently use the crates.io 0.1.0 version based on Linux 5.0.0 Fixes: #1192 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-05-20 10:13:06 +00:00
"virtio-bindings",
Move Cloud Hypervisor to virtio-queue crate Relying on the vm-virtio/virtio-queue crate from rust-vmm which has been copied inside the Cloud Hypervisor tree, the entire codebase is moved to the new definition of a Queue and other related structures. The reason for this move is to follow the upstream until we get some agreement for the patches that we need on top of that to make it properly work with Cloud Hypervisor. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-21 10:41:16 +00:00
"virtio-queue",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
vmm: Use virtio-blk to support booting from disk image After the virtio-blk device support has been introduced in the previous commit, the vmm need to rely on this new device to boot from disk images instead of initrd built into the kernel. In order to achieve the proper support of virtio-blk, this commit had to handle a few things: - Register an ioevent fd for each virtqueue. This important to be notified from the virtio driver that something has been written on the queue. - Fix the retrieval of 64bits BAR address. This is needed to provide the right address which need to be registered as the notification address from the virtio driver. - Fix the write_bar and read_bar functions. They were both assuming to be provided with an address, from which they were trying to find the associated offset. But the reality is that the offset is directly provided by the Bus layer. - Register a new virtio-blk device as a virtio-pci device from the vm.rs code. When the VM is started, it expects a block device to be created, using this block device as the VM rootfs. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-06 17:27:40 +00:00
]
cloud-hypervisor: Call into the test_vm() routine test_vm is a dummy VM workload, we use it to test our initial VMM settings. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-22 16:05:02 +00:00
[[package]]
name = "vmm"
version = "0.1.0"
dependencies = [
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
"acpi_tables",
"anyhow",
"arc-swap",
"arch",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"bitflags",
vmm: Rely on virtio-blk io_uring when possible In case the host supports io_uring and the specific io_uring options needed, the VMM will choose the asynchronous version of virtio-blk. This will enable better I/O performances compared to the default synchronous version. This is also important to note the VMM won't be able to use the asynchronous version if the backend image is in QCOW format. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-07-30 10:44:05 +00:00
"block_util",
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
"clap",
"devices",
"epoll",
vmm: Use event!() for some key VM actions Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-02-17 11:24:36 +00:00
"event_monitor",
vmm: Add `Debuggable` trait implementation This commit adds initial gdb.rs implementation for `Debuggable` trait to describe a debuggable component. Some part of the trait bound implementations is based on the crosvm GDB stub code [1]. [1] https://github.com/google/crosvm/blob/main/src/gdb.rs Signed-off-by: Akira Moroo <retrage01@gmail.com>
2022-02-20 03:17:50 +00:00
"gdbstub",
"gdbstub_arch",
arch, pci, vmm: Initial switch to the hypervisor crate Start moving the vmm, arch and pci crates to being hypervisor agnostic by using the hypervisor trait and abstractions. This is not a complete switch and there are still some remaining KVM dependencies. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-02 02:29:54 +00:00
"hypervisor",
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
"lazy_static",
"libc",
"linux-loader",
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"log",
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
"micro_http",
"net_util",
vhost_user_net, vhost_user_block, option_parser: Remove vmm dependency Remove the vmm dependency from vhost_user_block and vhost_user_net where it was existing to use config::OptionParser. By moving the OptionParser to its own crate at the top-level we can remove the very heavy dependency that these vhost-user backends had. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-06 15:41:45 +00:00
"option_parser",
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
"pci",
"qcow",
virtio-devices, vmm: Move to the seccompiler crate Fixes: #2929 Signed-off-by: Bo Chen <chen.bo@intel.com>
2021-08-17 03:40:11 +00:00
"seccompiler",
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
"serde",
"serde_derive",
"serde_json",
"signal-hook",
vmm: Use thiserror/anyhow for vmm::Error This gives a nicer user experience and this error can now be used as the source for other errors based off this. See: #1910 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-10-26 16:11:02 +00:00
"thiserror",
deps: Update Cargo.lock to include uuid crate Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-06-09 13:00:07 +00:00
"uuid",
vmm: Version MemoryManager state Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-21 12:50:41 +00:00
"versionize",
"versionize_derive",
vfio: Rename to vfio-ioctls Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-08 15:27:05 +00:00
"vfio-ioctls",
vmm: pci: Move creation of vfio_user::Client to DeviceManager By moving this from the VfioUserPciDevice to DeviceManager the client can be reused for handling DMA mapping behind an IOMMU. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-08-11 10:19:33 +00:00
"vfio_user",
block_util, vhdx: vhdx crate integration with the cloud hypervisor vhdx_sync.rs in block_util implements traits to represent the vhdx crate as a supported block device in the cloud hypervisor. The vhdx is added to the block device list in device_manager.rs at the vmm crate so that it can automatically detect a vhdx disk and invoke the corresponding crate. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: Fazla Mehrab <akm.fazla.mehrab@intel.com>
2021-07-26 15:51:03 +00:00
"vhdx",
vm-virtio, virtio-devices: Split device implementation from virt queues Split the generic virtio code (queues and device type) from the VirtioDevice trait, transport and device implementations. This also simplifies the feature handling in vhost_user_backend as the vm-virtio crate is no longer has any features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-02 12:25:19 +00:00
"virtio-devices",
Move Cloud Hypervisor to virtio-queue crate Relying on the vm-virtio/virtio-queue crate from rust-vmm which has been copied inside the Cloud Hypervisor tree, the entire codebase is moved to the new definition of a Queue and other related structures. The reason for this move is to follow the upstream until we get some agreement for the patches that we need on top of that to make it properly work with Cloud Hypervisor. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-21 10:41:16 +00:00
"virtio-queue",
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
"vm-allocator",
"vm-device",
Revert "build: bump vm-memory from 0.6.0 to 0.7.0" This was causing some issues because of the use of 2 different versions for the vm-memmory crate. We'll wait for all dependencies to be properly resolved before we move to 0.7.0. This reverts commit 76b6c62d0766e46f80521c2dc24d532665db4be1. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-10-22 08:29:33 +00:00
"vm-memory",
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
"vm-migration",
"vm-virtio",
"vmm-sys-util",
vmm: Basic Vcpu implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 14:26:30 +00:00
]
Bump vmm-sys-utils to 0.2.0 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-23 07:44:42 +00:00
[[package]]
name = "vmm-sys-util"
build: bump vmm-sys-util from 0.8.0 to 0.9.0 Bumps [vmm-sys-util](https://github.com/rust-vmm/vmm-sys-util) from 0.8.0 to 0.9.0. - [Release notes](https://github.com/rust-vmm/vmm-sys-util/releases) - [Changelog](https://github.com/rust-vmm/vmm-sys-util/blob/main/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/vmm-sys-util/compare/v0.8.0...v0.9.0) --- updated-dependencies: - dependency-name: vmm-sys-util dependency-type: direct:production update-type: version-update:semver-minor ... This needed a bunch of manual updates as well, including vfio-ioctls and vhost crates. The vhost crate is being patched with the latest version from rust-vmm because the version 0.1.0 on crates.io doesn't include the patches we need yet. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-09-15 00:12:33 +00:00
version = "0.9.0"
Bump vmm-sys-utils to 0.2.0 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-23 07:44:42 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump vmm-sys-util from 0.8.0 to 0.9.0 Bumps [vmm-sys-util](https://github.com/rust-vmm/vmm-sys-util) from 0.8.0 to 0.9.0. - [Release notes](https://github.com/rust-vmm/vmm-sys-util/releases) - [Changelog](https://github.com/rust-vmm/vmm-sys-util/blob/main/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/vmm-sys-util/compare/v0.8.0...v0.9.0) --- updated-dependencies: - dependency-name: vmm-sys-util dependency-type: direct:production update-type: version-update:semver-minor ... This needed a bunch of manual updates as well, including vfio-ioctls and vhost crates. The vhost crate is being patched with the latest version from rust-vmm because the version 0.1.0 on crates.io doesn't include the patches we need yet. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-09-15 00:12:33 +00:00
checksum = "733537bded03aaa93543f785ae997727b30d1d9f4a03b7861d23290474242e11"
Bump vmm-sys-utils to 0.2.0 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-23 07:44:42 +00:00
dependencies = [
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"bitflags",
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
"libc",
Cargo: Update dependencies for the KVM serialization work We need the project to rely on kvm-bindings and kvm-ioctls branches which include the serde derive to be able to serialize and deserialize some KVM structures. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-02-17 14:28:24 +00:00
"serde",
"serde_derive",
Bump vmm-sys-utils to 0.2.0 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-23 07:44:42 +00:00
]
tests: Wait explicitly for vm shutdown w/ the 'wait-timeout' crate Instead of waiting blindly with fixed amount of sleeping time, we can use the `wait-timeout` crate to explicitly wait VM shutdown (with a timeout). It can reduces the execution time of some tests substantially. Also, this patch increases the `shutdown` timeout for 'test_reboot', which should fix the recent sporadic failures on this test. Signed-off-by: Bo Chen <chen.bo@intel.com>
2020-10-28 23:40:50 +00:00
[[package]]
name = "wait-timeout"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9f200f5b12eb75f8c1ed65abd4b2db8a6e1b138a20de009dacee265a2498f3f6"
dependencies = [
"libc",
]
build(deps): bump getrandom from 0.1.8 to 0.1.9 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.1.8 to 0.1.9. - [Release notes](https://github.com/rust-random/getrandom/releases) - [Changelog](https://github.com/rust-random/getrandom/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/getrandom/compare/v0.1.8...v0.1.9) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-14 16:19:06 +00:00
[[package]]
name = "wasi"
build(deps): bump dirs from 3.0.1 to 3.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/soc/dirs-rs/releases) - [Commits](https://github.com/soc/dirs-rs/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-04-23 22:44:20 +00:00
version = "0.10.2+wasi-snapshot-preview1"
build(deps): bump getrandom from 0.1.8 to 0.1.9 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.1.8 to 0.1.9. - [Release notes](https://github.com/rust-random/getrandom/releases) - [Changelog](https://github.com/rust-random/getrandom/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/getrandom/compare/v0.1.8...v0.1.9) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-14 16:19:06 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump dirs from 3.0.1 to 3.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 3.0.1 to 3.0.2. - [Release notes](https://github.com/soc/dirs-rs/releases) - [Commits](https://github.com/soc/dirs-rs/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-04-23 22:44:20 +00:00
checksum = "fd6fbd9a79829dd1ad0cc20627bf1ed606756a7f77edff7b66b7064f9cb327c6"
build(deps): bump getrandom from 0.1.8 to 0.1.9 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.1.8 to 0.1.9. - [Release notes](https://github.com/rust-random/getrandom/releases) - [Changelog](https://github.com/rust-random/getrandom/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/getrandom/compare/v0.1.8...v0.1.9) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-14 16:19:06 +00:00
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
[[package]]
name = "winapi"
build: Bulk upgrade dependencies There are several dependencies that need updating so update them manually rather than relying on dependabot. This will reduce the load on the CI. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-06 08:39:44 +00:00
version = "0.3.9"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk upgrade dependencies There are several dependencies that need updating so update them manually rather than relying on dependabot. This will reduce the load on the CI. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-06 08:39:44 +00:00
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
dependencies = [
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
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
[[package]]
name = "winapi-util"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
dependencies = [
build: Bump pnet from 0.27.2 to 0.28.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.27.2 to 0.28.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.27.2...v0.28.0) Signed-off-by: dependabot[bot] <support@github.com>
2021-05-17 07:46:31 +00:00
"winapi",
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
]
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
hypervisor: Modify toml file to add mshv-{bindings, ioctls) crates Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-03 22:43:48 +00:00
[[package]]
name = "zerocopy"
build: bump zerocopy from 0.6.0 to 0.6.1 Bumps zerocopy from 0.6.0 to 0.6.1. --- updated-dependencies: - dependency-name: zerocopy dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-11-11 23:12:56 +00:00
version = "0.6.1"
hypervisor: Modify toml file to add mshv-{bindings, ioctls) crates Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-03 22:43:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump zerocopy from 0.6.0 to 0.6.1 Bumps zerocopy from 0.6.0 to 0.6.1. --- updated-dependencies: - dependency-name: zerocopy dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-11-11 23:12:56 +00:00
checksum = "332f188cc1bcf1fe1064b8c58d150f497e697f49774aa846f2dc949d9a25f236"
hypervisor: Modify toml file to add mshv-{bindings, ioctls) crates Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-03 22:43:48 +00:00
dependencies = [
"byteorder",
"zerocopy-derive",
]
[[package]]
name = "zerocopy-derive"
build: bump zerocopy from 0.6.0 to 0.6.1 Bumps zerocopy from 0.6.0 to 0.6.1. --- updated-dependencies: - dependency-name: zerocopy dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-11-11 23:12:56 +00:00
version = "0.3.1"
hypervisor: Modify toml file to add mshv-{bindings, ioctls) crates Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-03 22:43:48 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: bump zerocopy from 0.6.0 to 0.6.1 Bumps zerocopy from 0.6.0 to 0.6.1. --- updated-dependencies: - dependency-name: zerocopy dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-11-11 23:12:56 +00:00
checksum = "a0fbc82b82efe24da867ee52e015e58178684bd9dd64c34e66bdf21da2582a9f"
hypervisor: Modify toml file to add mshv-{bindings, ioctls) crates Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-03 22:43:48 +00:00
dependencies = [
"proc-macro2",
"syn",
"synstructure",
]
Reference in New Issue Copy Permalink