External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-11-05 03:21:13 +00:00
Code Issues Packages Projects Releases Wiki Activity
d485896edd
cloud-hypervisor/Cargo.lock

3068 lines
70 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"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
source = "git+https://github.com/rust-vmm/acpi_tables?branch=main#ca1a473fe73cdd8eb49c1449faad7aaac06f32c2"
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
dependencies = [
build: Bump versions of acpi_tables and zerocopy The 'derive' feature of `zerocopy` crate now is optional and requires to be enabled explicitly [1]. Also, a version bump on `acpi_tables` is needed to reply on a single version of `zerocopy` to avoid compilation errors. [1] https://github.com/google/zerocopy/pull/176 Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-09-25 22:44:06 +00:00
"zerocopy",
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: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
[[package]]
name = "addr2line"
build: Bump backtrace from 0.3.67 to 0.3.71 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.67 to 0.3.71. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.67...0.3.71) --- updated-dependencies: - dependency-name: backtrace dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-01 23:35:54 +00:00
version = "0.21.0"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump backtrace from 0.3.67 to 0.3.71 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.67 to 0.3.71. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.67...0.3.71) --- updated-dependencies: - dependency-name: backtrace dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-01 23:35:54 +00:00
checksum = "8a30b2e23b9e17a9f90641c7ab1549cd9b44f296d3ccbf309d2863cfe398a0cb"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
dependencies = [
"gimli",
]
[[package]]
name = "adler"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.1.3"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "8e60d3430d3a69478ad0993f19238d2df97c507009a52b3c10addcd7f6bcb916"
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
]
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
[[package]]
name = "anstream"
build: Bump clap from 4.4.7 to 4.5.1 Bumps [clap](https://github.com/clap-rs/clap) from 4.4.7 to 4.5.1. - [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/clap_complete-v4.4.7...clap_complete-v4.5.1) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-29 20:08:49 +00:00
version = "0.6.13"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump clap from 4.4.7 to 4.5.1 Bumps [clap](https://github.com/clap-rs/clap) from 4.4.7 to 4.5.1. - [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/clap_complete-v4.4.7...clap_complete-v4.5.1) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-29 20:08:49 +00:00
checksum = "d96bd03f33fe50a863e394ee9718a706f988b9079b20c3784fb726e7678b62fb"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
dependencies = [
"anstyle",
"anstyle-parse",
"anstyle-query",
"anstyle-wincon",
"colorchoice",
"utf8parse",
]
[[package]]
name = "anstyle"
build: Bump anstyle from 1.0.1 to 1.0.6 Bumps [anstyle](https://github.com/rust-cli/anstyle) from 1.0.1 to 1.0.6. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-ls-v1.0.1...v1.0.6) --- updated-dependencies: - dependency-name: anstyle dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-14 23:41:38 +00:00
version = "1.0.6"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump anstyle from 1.0.1 to 1.0.6 Bumps [anstyle](https://github.com/rust-cli/anstyle) from 1.0.1 to 1.0.6. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-ls-v1.0.1...v1.0.6) --- updated-dependencies: - dependency-name: anstyle dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-14 23:41:38 +00:00
checksum = "8901269c6307e8d93993578286ac0edf7f195079ffff5ebdeea6a59ffb7e36bc"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
[[package]]
name = "anstyle-parse"
build: Bump anstyle-parse from 0.2.1 to 0.2.3 Bumps [anstyle-parse](https://github.com/rust-cli/anstyle) from 0.2.1 to 0.2.3. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-parse-v0.2.1...anstyle-parse-v0.2.3) --- updated-dependencies: - dependency-name: anstyle-parse dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-21 23:46:50 +00:00
version = "0.2.3"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump anstyle-parse from 0.2.1 to 0.2.3 Bumps [anstyle-parse](https://github.com/rust-cli/anstyle) from 0.2.1 to 0.2.3. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-parse-v0.2.1...anstyle-parse-v0.2.3) --- updated-dependencies: - dependency-name: anstyle-parse dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-21 23:46:50 +00:00
checksum = "c75ac65da39e5fe5ab759307499ddad880d724eed2f6ce5b5e8a26f4f387928c"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
dependencies = [
"utf8parse",
]
[[package]]
name = "anstyle-query"
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
version = "1.0.2"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
checksum = "e28923312444cdd728e4738b3f9c9cac739500909bb3d3c94b43551b16517648"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
dependencies = [
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
"windows-sys 0.52.0",
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
]
[[package]]
name = "anstyle-wincon"
build: Bump anstyle-wincon from 3.0.1 to 3.0.2 Bumps [anstyle-wincon](https://github.com/rust-cli/anstyle) from 3.0.1 to 3.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-wincon-v3.0.1...anstyle-wincon-v3.0.2) --- updated-dependencies: - dependency-name: anstyle-wincon dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-19 23:19:58 +00:00
version = "3.0.2"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump anstyle-wincon from 3.0.1 to 3.0.2 Bumps [anstyle-wincon](https://github.com/rust-cli/anstyle) from 3.0.1 to 3.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-wincon-v3.0.1...anstyle-wincon-v3.0.2) --- updated-dependencies: - dependency-name: anstyle-wincon dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-19 23:19:58 +00:00
checksum = "1cd54b81ec8d6180e24654d0b371ad22fc3dd083b6ff8ba325b72e00c87660a7"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
dependencies = [
"anstyle",
build: Bump anstyle-wincon from 3.0.1 to 3.0.2 Bumps [anstyle-wincon](https://github.com/rust-cli/anstyle) from 3.0.1 to 3.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-wincon-v3.0.1...anstyle-wincon-v3.0.2) --- updated-dependencies: - dependency-name: anstyle-wincon dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-19 23:19:58 +00:00
"windows-sys 0.52.0",
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.0.81"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "0952808a6c2afd1aa8947271f3a60f1a6763c7b912d210184c5149b5cf147247"
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 = [
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-util",
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
]
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.7.1"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "69f7f8c3906b62b754cd5326047894316021dcfe5a194c8ea52bdd94934a3457"
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 = [
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",
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, vmm: Expose platform uuid via SMBIOS Parse and set uuid. Signed-off-by: lizhaoxin1 <Lxiaoyouling@163.com> Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-08-04 03:34:26 +00:00
"uuid",
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",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +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
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "async-broadcast"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7c48ccdbf6ca6b121e0f586cbc0e73ae440e56c67c30fa0873b4e110d9c26d2b"
dependencies = [
build: Bump async-process from 1.7.0 to 1.8.0 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-28 23:47:38 +00:00
"event-listener 2.5.3",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"futures-core",
]
[[package]]
name = "async-channel"
build: Bump async-channel from 2.1.1 to 2.2.0 Bumps [async-channel](https://github.com/smol-rs/async-channel) from 2.1.1 to 2.2.0. - [Release notes](https://github.com/smol-rs/async-channel/releases) - [Changelog](https://github.com/smol-rs/async-channel/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-channel/compare/v2.1.1...v2.2.0) --- updated-dependencies: - dependency-name: async-channel dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-14 23:11:47 +00:00
version = "2.2.0"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump async-channel from 2.1.1 to 2.2.0 Bumps [async-channel](https://github.com/smol-rs/async-channel) from 2.1.1 to 2.2.0. - [Release notes](https://github.com/smol-rs/async-channel/releases) - [Changelog](https://github.com/smol-rs/async-channel/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-channel/compare/v2.1.1...v2.2.0) --- updated-dependencies: - dependency-name: async-channel dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-14 23:11:47 +00:00
checksum = "f28243a43d821d11341ab73c80bed182dc015c514b951616cf79bd4af39af0c3"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"concurrent-queue",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"event-listener 5.3.0",
"event-listener-strategy 0.5.1",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"futures-core",
build: Bump blocking from 1.3.1 to 1.5.1 Bumps [blocking](https://github.com/smol-rs/blocking) from 1.3.1 to 1.5.1. - [Release notes](https://github.com/smol-rs/blocking/releases) - [Changelog](https://github.com/smol-rs/blocking/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/blocking/compare/v1.3.1...v1.5.1) --- updated-dependencies: - dependency-name: blocking dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-20 23:43:13 +00:00
"pin-project-lite",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
]
[[package]]
name = "async-executor"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.9.1"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "10b3e585719c2358d2660232671ca8ca4ddb4be4ce8a1842d6c2dc8685303316"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"async-lock 3.3.0",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"async-task",
"concurrent-queue",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"fastrand 2.0.2",
"futures-lite 2.3.0",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"slab",
]
[[package]]
name = "async-fs"
version = "1.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "279cf904654eeebfa37ac9bb1598880884924aab82e290aa65c9e77a0e142e06"
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"async-lock 2.8.0",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"autocfg",
"blocking",
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
"futures-lite 1.13.0",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
]
[[package]]
name = "async-io"
version = "1.13.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0fc5b45d93ef0529756f812ca52e44c221b35341892d3dcc34132ac02f3dd2af"
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"async-lock 2.8.0",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"autocfg",
"cfg-if",
"concurrent-queue",
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
"futures-lite 1.13.0",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"log",
"parking",
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
"polling 2.8.0",
build: Bump rustix from 0.37.25 to 0.37.27 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.37.25 to 0.37.27. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.37.25...v0.37.27) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-20 23:18:57 +00:00
"rustix 0.37.27",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"slab",
"socket2",
"waker-fn",
]
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
[[package]]
name = "async-io"
version = "2.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dcccb0f599cfa2f8ace422d3555572f47424da5648a4382a9dd0310ff8210884"
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"async-lock 3.3.0",
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
"cfg-if",
"concurrent-queue",
"futures-io",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"futures-lite 2.3.0",
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
"parking",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"polling 3.6.0",
"rustix 0.38.32",
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
"slab",
"tracing",
"windows-sys 0.52.0",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "async-lock"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "2.8.0"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "287272293e9d8c41773cec55e365490fe034813a2f172f502d6ddcf75b2f582b"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
build: Bump async-process from 1.7.0 to 1.8.0 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-28 23:47:38 +00:00
"event-listener 2.5.3",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
]
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
[[package]]
name = "async-lock"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "3.3.0"
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "d034b430882f8381900d3fe6f0aaa3ad94f2cb4ac519b429692a1bc2dda4ae7b"
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"event-listener 4.0.3",
build: Bump async-channel from 2.1.1 to 2.2.0 Bumps [async-channel](https://github.com/smol-rs/async-channel) from 2.1.1 to 2.2.0. - [Release notes](https://github.com/smol-rs/async-channel/releases) - [Changelog](https://github.com/smol-rs/async-channel/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-channel/compare/v2.1.1...v2.2.0) --- updated-dependencies: - dependency-name: async-channel dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-14 23:11:47 +00:00
"event-listener-strategy 0.4.0",
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
"pin-project-lite",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "async-process"
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
version = "1.8.1"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
checksum = "ea6438ba0a08d81529c69b36700fa2f95837bfe3e776ab39cde9c14d9149da88"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
"async-io 1.13.0",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"async-lock 2.8.0",
build: Bump async-process from 1.7.0 to 1.8.0 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-28 23:47:38 +00:00
"async-signal",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"blocking",
"cfg-if",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"event-listener 3.1.0",
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
"futures-lite 1.13.0",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"rustix 0.38.32",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"windows-sys 0.48.0",
]
[[package]]
name = "async-recursion"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.1.0"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "30c5ef0ede93efbf733c1a727f3b6b5a1060bbedd5600183e66f6e4be4af0ec5"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"proc-macro2",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
]
build: Bump async-process from 1.7.0 to 1.8.0 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-28 23:47:38 +00:00
[[package]]
name = "async-signal"
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
version = "0.2.5"
build: Bump async-process from 1.7.0 to 1.8.0 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-28 23:47:38 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
checksum = "9e47d90f65a225c4527103a8d747001fc56e375203592b25ad103e1ca13124c5"
build: Bump async-process from 1.7.0 to 1.8.0 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-28 23:47:38 +00:00
dependencies = [
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
"async-io 2.3.2",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"async-lock 2.8.0",
build: Bump async-process from 1.7.0 to 1.8.0 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-28 23:47:38 +00:00
"atomic-waker",
"cfg-if",
"futures-core",
"futures-io",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"rustix 0.38.32",
build: Bump async-process from 1.7.0 to 1.8.0 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-28 23:47:38 +00:00
"signal-hook-registry",
"slab",
"windows-sys 0.48.0",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "async-task"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "4.7.0"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "fbb36e985947064623dbd357f727af08ffd077f93d696782f3c56365fa2e2799"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "async-trait"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.1.79"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "a507401cad91ec6a857ed5513a2073c82a9b9048762b885bb98655b306964681"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"proc-macro2",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
]
[[package]]
name = "atomic-waker"
build: Bump atomic-waker from 1.1.1 to 1.1.2 Bumps [atomic-waker](https://github.com/smol-rs/atomic-waker) from 1.1.1 to 1.1.2. - [Release notes](https://github.com/smol-rs/atomic-waker/releases) - [Changelog](https://github.com/smol-rs/atomic-waker/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/atomic-waker/compare/v1.1.1...v1.1.2) --- updated-dependencies: - dependency-name: atomic-waker dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-10-02 23:25:27 +00:00
version = "1.1.2"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump atomic-waker from 1.1.1 to 1.1.2 Bumps [atomic-waker](https://github.com/smol-rs/atomic-waker) from 1.1.1 to 1.1.2. - [Release notes](https://github.com/smol-rs/atomic-waker/releases) - [Changelog](https://github.com/smol-rs/atomic-waker/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/atomic-waker/compare/v1.1.1...v1.1.2) --- updated-dependencies: - dependency-name: atomic-waker dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-10-02 23:25:27 +00:00
checksum = "1505bd5d3d116872e7271a6d4e16d81d0c8570876c8de68093a09ac269d8aac0"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.2.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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "f1fdabc7756949593fe60f30ec81974b613357de856987752631dea1e3394c80"
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
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
[[package]]
name = "backtrace"
build: Bump backtrace from 0.3.67 to 0.3.71 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.67 to 0.3.71. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.67...0.3.71) --- updated-dependencies: - dependency-name: backtrace dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-01 23:35:54 +00:00
version = "0.3.71"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump backtrace from 0.3.67 to 0.3.71 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.67 to 0.3.71. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.67...0.3.71) --- updated-dependencies: - dependency-name: backtrace dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-01 23:35:54 +00:00
checksum = "26b05800d2e817c8b3b4b54abd461726265fa9789ae34330622f2db9ee696f9d"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
dependencies = [
"addr2line",
"cc",
"cfg-if",
"libc",
"miniz_oxide",
"object",
"rustc-demangle",
]
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",
]
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
[[package]]
name = "bitfield-struct"
build: Bump bitfield-struct from 0.5.4 to 0.5.6 Bumps [bitfield-struct](https://github.com/wrenger/bitfield-struct-rs) from 0.5.4 to 0.5.6. - [Release notes](https://github.com/wrenger/bitfield-struct-rs/releases) - [Commits](https://github.com/wrenger/bitfield-struct-rs/compare/0.5.4...0.5.6) --- updated-dependencies: - dependency-name: bitfield-struct dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-15 23:24:22 +00:00
version = "0.5.6"
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump bitfield-struct from 0.5.4 to 0.5.6 Bumps [bitfield-struct](https://github.com/wrenger/bitfield-struct-rs) from 0.5.4 to 0.5.6. - [Release notes](https://github.com/wrenger/bitfield-struct-rs/releases) - [Commits](https://github.com/wrenger/bitfield-struct-rs/compare/0.5.4...0.5.6) --- updated-dependencies: - dependency-name: bitfield-struct dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-15 23:24:22 +00:00
checksum = "a26b8cea8bb6a81b75a84603b9e096f05fa86db057904ef29be1deee900532bd"
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
dependencies = [
"proc-macro2",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
]
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
build: Bump bitflags from 1.3.2 to 2.3.2 Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.2 to 2.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.2...2.3.2) --- updated-dependencies: - dependency-name: bitflags dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2023-06-16 00:54:27 +00:00
[[package]]
name = "bitflags"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "2.5.0"
build: Bump bitflags from 1.3.2 to 2.3.2 Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.2 to 2.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.2...2.3.2) --- updated-dependencies: - dependency-name: bitflags dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2023-06-16 00:54:27 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "cf4b9d6a944f767f8e5e0db018570623c85f3d925ac718db4e06d0187adb21c1"
build: Bump bitflags from 1.3.2 to 2.3.2 Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.2 to 2.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.2...2.3.2) --- updated-dependencies: - dependency-name: bitflags dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2023-06-16 00:54:27 +00:00
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
block: merge qcow, vhdx and block_util into block crate This commit merges crates `qcow`, `vhdx` and `block_util` into the crate `block`, which can allow `qcow` to use functions from `block_util` without introducing a circular crate dependency. This commit is based on crosvm implementation: https://chromium.googlesource.com/crosvm/crosvm/+/f2eecc4152eca8d395566cffa2c102ec090a152d Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
2023-07-12 02:24:28 +00:00
name = "block"
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
version = "0.1.0"
dependencies = [
block: merge qcow, vhdx and block_util into block crate This commit merges crates `qcow`, `vhdx` and `block_util` into the crate `block`, which can allow `qcow` to use functions from `block_util` without introducing a circular crate dependency. This commit is based on crosvm implementation: https://chromium.googlesource.com/crosvm/crosvm/+/f2eecc4152eca8d395566cffa2c102ec090a152d Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
2023-07-12 02:24:28 +00:00
"byteorder",
block: Replace use of crc32c crate with crc-any According to crates.io the crc-any crate is actively maintained which avoids issues with the crc32c crate and the nightly compiler. Fixes: #6168 Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-02-06 20:48:47 +00:00
"crc-any",
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: merge qcow, vhdx and block_util into block crate This commit merges crates `qcow`, `vhdx` and `block_util` into the crate `block`, which can allow `qcow` to use functions from `block_util` without introducing a circular crate dependency. This commit is based on crosvm implementation: https://chromium.googlesource.com/crosvm/crosvm/+/f2eecc4152eca8d395566cffa2c102ec090a152d Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
2023-07-12 02:24:28 +00:00
"remain",
block_util: Use SmallVec for I/O requests The number of buffers in the request is usually one so by using SmallVec the number of heap allocations can be significantly reduced. DHAT reports: Before: dhat: Total: 1,166,412 bytes in 40,383 blocks After: dhat: Total: 623,852 bytes in 8,157 blocks Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-10 12:45:30 +00:00
"smallvec",
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",
block: merge qcow, vhdx and block_util into block crate This commit merges crates `qcow`, `vhdx` and `block_util` into the crate `block`, which can allow `qcow` to use functions from `block_util` without introducing a circular crate dependency. This commit is based on crosvm implementation: https://chromium.googlesource.com/crosvm/crosvm/+/f2eecc4152eca8d395566cffa2c102ec090a152d Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
2023-07-12 02:24:28 +00:00
"uuid",
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",
build: Bulk update rust-vmm dependencies Bump to the latest rust-vmm crates, including vm-memory, vfio, vfio-bindings, vfio-user, virtio-bindings, virtio-queue, linux-loader, vhost, and vhost-user-backend, Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-05-19 16:12:25 +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",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +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
]
block: merge qcow, vhdx and block_util into block crate This commit merges crates `qcow`, `vhdx` and `block_util` into the crate `block`, which can allow `qcow` to use functions from `block_util` without introducing a circular crate dependency. This commit is based on crosvm implementation: https://chromium.googlesource.com/crosvm/crosvm/+/f2eecc4152eca8d395566cffa2c102ec090a152d Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
2023-07-12 02:24:28 +00:00
[[package]]
name = "block-buffer"
version = "0.10.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3078c7629b62d3f0439517fa394996acacc5cbc91c5a20d8c658e77abd503a71"
dependencies = [
"generic-array",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "blocking"
build: Bump blocking from 1.3.1 to 1.5.1 Bumps [blocking](https://github.com/smol-rs/blocking) from 1.3.1 to 1.5.1. - [Release notes](https://github.com/smol-rs/blocking/releases) - [Changelog](https://github.com/smol-rs/blocking/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/blocking/compare/v1.3.1...v1.5.1) --- updated-dependencies: - dependency-name: blocking dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-20 23:43:13 +00:00
version = "1.5.1"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump blocking from 1.3.1 to 1.5.1 Bumps [blocking](https://github.com/smol-rs/blocking) from 1.3.1 to 1.5.1. - [Release notes](https://github.com/smol-rs/blocking/releases) - [Changelog](https://github.com/smol-rs/blocking/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/blocking/compare/v1.3.1...v1.5.1) --- updated-dependencies: - dependency-name: blocking dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-20 23:43:13 +00:00
checksum = "6a37913e8dc4ddcc604f0c6d3bf2887c995153af3611de9e23c352b44c1b9118"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"async-channel",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"async-lock 3.3.0",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"async-task",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"fastrand 2.0.2",
build: Bump blocking from 1.3.1 to 1.5.1 Bumps [blocking](https://github.com/smol-rs/blocking) from 1.3.1 to 1.5.1. - [Release notes](https://github.com/smol-rs/blocking/releases) - [Changelog](https://github.com/smol-rs/blocking/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/blocking/compare/v1.3.1...v1.5.1) --- updated-dependencies: - dependency-name: blocking dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-20 23:43:13 +00:00
"futures-io",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"futures-lite 2.3.0",
build: Bump blocking from 1.3.1 to 1.5.1 Bumps [blocking](https://github.com/smol-rs/blocking) from 1.3.1 to 1.5.1. - [Release notes](https://github.com/smol-rs/blocking/releases) - [Changelog](https://github.com/smol-rs/blocking/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/blocking/compare/v1.3.1...v1.5.1) --- updated-dependencies: - dependency-name: blocking dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-20 23:43:13 +00:00
"piper",
"tracing",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
]
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
[[package]]
name = "bumpalo"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "3.15.4"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "7ff69b9dd49fd426c69a0db9fc04dd934cdb6645ff000864d98f7e2af8830eaa"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +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: Bump byteorder from 1.4.3 to 1.5.0 Bumps [byteorder](https://github.com/BurntSushi/byteorder) from 1.4.3 to 1.5.0. - [Changelog](https://github.com/BurntSushi/byteorder/blob/master/CHANGELOG.md) - [Commits](https://github.com/BurntSushi/byteorder/compare/1.4.3...1.5.0) --- updated-dependencies: - dependency-name: byteorder dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-29 23:33:33 +00:00
version = "1.5.0"
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: Bump byteorder from 1.4.3 to 1.5.0 Bumps [byteorder](https://github.com/BurntSushi/byteorder) from 1.4.3 to 1.5.0. - [Changelog](https://github.com/BurntSushi/byteorder/blob/master/CHANGELOG.md) - [Commits](https://github.com/BurntSushi/byteorder/compare/1.4.3...1.5.0) --- updated-dependencies: - dependency-name: byteorder dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-29 23:33:33 +00:00
checksum = "1fd0f2584146f6f2ef48085050886acf353beff7305ebd1ae69500e27c67f64b"
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.83 to 1.0.90 Bumps [cc](https://github.com/rust-lang/cc-rs) from 1.0.83 to 1.0.90. - [Release notes](https://github.com/rust-lang/cc-rs/releases) - [Commits](https://github.com/rust-lang/cc-rs/compare/1.0.83...1.0.90) --- updated-dependencies: - dependency-name: cc dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-20 23:51:03 +00:00
version = "1.0.90"
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.83 to 1.0.90 Bumps [cc](https://github.com/rust-lang/cc-rs) from 1.0.83 to 1.0.90. - [Release notes](https://github.com/rust-lang/cc-rs/releases) - [Commits](https://github.com/rust-lang/cc-rs/compare/1.0.83...1.0.90) --- updated-dependencies: - dependency-name: cc dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-20 23:51:03 +00:00
checksum = "8cd6604a82acf3039f1144f54b8eb34e91ffba622051189e71b781822d5ee1f5"
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"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
[[package]]
name = "clap"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "4.5.4"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "90bc066a67923782aa8515dbaea16946c5bcc5addbd668bb80af688e53e548a0"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
dependencies = [
"clap_builder",
]
[[package]]
name = "clap_builder"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "4.5.2"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "ae129e2e766ae0ec03484e609954119f123cc1fe650337e155d03b022f24f7b4"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
dependencies = [
"anstream",
"anstyle",
"clap_lex",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"strsim 0.11.1",
vhost_user_net: switch to clap Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-09-21 15:30:23 +00:00
"terminal_size",
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
]
[[package]]
name = "clap_lex"
build: Bump clap from 4.4.7 to 4.5.1 Bumps [clap](https://github.com/clap-rs/clap) from 4.4.7 to 4.5.1. - [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/clap_complete-v4.4.7...clap_complete-v4.5.1) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-29 20:08:49 +00:00
version = "0.7.0"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump clap from 4.4.7 to 4.5.1 Bumps [clap](https://github.com/clap-rs/clap) from 4.4.7 to 4.5.1. - [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/clap_complete-v4.4.7...clap_complete-v4.5.1) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-29 20:08:49 +00:00
checksum = "98cc8fbded0c607b7ba9dd60cd98df59af97e84d24e49c8557331cfc26d301ce"
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +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 v38.0 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-02-15 00:12:19 +00:00
version = "38.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",
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
"clap",
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
"dhat",
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
"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",
tests: switch from lazy_static to once_cell Once_cell does not require using macro and is slated to become part of Rust std at some point. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-06-20 14:05:17 +00:00
"once_cell",
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",
tpm: Add library module Add structures and related methods to process Ctrl requests and responses from swtpm to tpm library. Signed-off-by: Praveen K Paladugu <prapal@linux.microsoft.com> Co-authored-by: Sean Yoo <t-seanyoo@microsoft.com>
2022-09-08 06:02:26 +00:00
"tpm",
tracing: Tracing infrastructure Add a new feature "tracing" that enables tracing functionality via the "tracer" crate (sadly features and crates cannot share the same name.) Setup: tracer::start() The main functionality is a tracer::trace_scope()! macro that will add trace points for the duration of the scope. Tracing events are per thread. Finish: tracer::end() this will write the trace file (pretty printed JSON) to a file in the current directory. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-06-21 14:01:26 +00:00
"tracer",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"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",
ch-remote: full support for calling the D-Bus API Support calling into the D-Bus API in a non-breaking way. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-29 12:08:04 +00:00
"zbus",
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
]
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
[[package]]
name = "colorchoice"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "acbf1af155f9b9ef647e42cdc158db4b64a1b61f743629225fde6f3e0be2a7c7"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "concurrent-queue"
build: Bump concurrent-queue from 2.3.0 to 2.4.0 Bumps [concurrent-queue](https://github.com/smol-rs/concurrent-queue) from 2.3.0 to 2.4.0. - [Release notes](https://github.com/smol-rs/concurrent-queue/releases) - [Changelog](https://github.com/smol-rs/concurrent-queue/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/concurrent-queue/compare/v2.3.0...v2.4.0) --- updated-dependencies: - dependency-name: concurrent-queue dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-29 23:07:22 +00:00
version = "2.4.0"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump concurrent-queue from 2.3.0 to 2.4.0 Bumps [concurrent-queue](https://github.com/smol-rs/concurrent-queue) from 2.3.0 to 2.4.0. - [Release notes](https://github.com/smol-rs/concurrent-queue/releases) - [Changelog](https://github.com/smol-rs/concurrent-queue/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/concurrent-queue/compare/v2.3.0...v2.4.0) --- updated-dependencies: - dependency-name: concurrent-queue dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-29 23:07:22 +00:00
checksum = "d16048cd947b08fa32c24458a22f5dc5e835264f689f4f5653210c69fd107363"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"crossbeam-utils",
]
[[package]]
name = "cpufeatures"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.2.12"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "53fe5e26ff1b7aef8bca9c6080520cfb8d9333c7568e1829cef191a9723e5504"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"libc",
]
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]]
block: Replace use of crc32c crate with crc-any According to crates.io the crc-any crate is actively maintained which avoids issues with the crc32c crate and the nightly compiler. Fixes: #6168 Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-02-06 20:48:47 +00:00
name = "crc-any"
version = "2.4.4"
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"
block: Replace use of crc32c crate with crc-any According to crates.io the crc-any crate is actively maintained which avoids issues with the crc32c crate and the nightly compiler. Fixes: #6168 Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-02-06 20:48:47 +00:00
checksum = "c01a5e1f881f6fb6099a7bdf949e946719fd4f1fefa56264890574febf0eb6d0"
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 = [
block: Replace use of crc32c crate with crc-any According to crates.io the crc-any crate is actively maintained which avoids issues with the crc32c crate and the nightly compiler. Fixes: #6168 Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-02-06 20:48:47 +00:00
"debug-helper",
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
]
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
[[package]]
name = "crc32fast"
build: Bump crc32fast from 1.3.2 to 1.4.0 Bumps [crc32fast](https://github.com/srijs/rust-crc32fast) from 1.3.2 to 1.4.0. - [Commits](https://github.com/srijs/rust-crc32fast/compare/v1.3.2...v1.4.0) --- updated-dependencies: - dependency-name: crc32fast dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-07 23:38:05 +00:00
version = "1.4.0"
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump crc32fast from 1.3.2 to 1.4.0 Bumps [crc32fast](https://github.com/srijs/rust-crc32fast) from 1.3.2 to 1.4.0. - [Commits](https://github.com/srijs/rust-crc32fast/compare/v1.3.2...v1.4.0) --- updated-dependencies: - dependency-name: crc32fast dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-07 23:38:05 +00:00
checksum = "b3855a8a784b474f333699ef2bbca9db2c4a1f6d9088a90a2d25b1eb53111eaa"
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
dependencies = [
"cfg-if",
]
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"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
version = "2.0.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
checksum = "2707e3afba5e19b75d582d88bc79237418f2a2a2d673d01cf9b03633b46e98f3"
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
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "crossbeam-utils"
build: Bump crossbeam-utils from 0.8.16 to 0.8.19 Bumps [crossbeam-utils](https://github.com/crossbeam-rs/crossbeam) from 0.8.16 to 0.8.19. - [Release notes](https://github.com/crossbeam-rs/crossbeam/releases) - [Changelog](https://github.com/crossbeam-rs/crossbeam/blob/master/CHANGELOG.md) - [Commits](https://github.com/crossbeam-rs/crossbeam/compare/crossbeam-utils-0.8.16...crossbeam-utils-0.8.19) --- updated-dependencies: - dependency-name: crossbeam-utils dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-02 23:35:14 +00:00
version = "0.8.19"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump crossbeam-utils from 0.8.16 to 0.8.19 Bumps [crossbeam-utils](https://github.com/crossbeam-rs/crossbeam) from 0.8.16 to 0.8.19. - [Release notes](https://github.com/crossbeam-rs/crossbeam/releases) - [Changelog](https://github.com/crossbeam-rs/crossbeam/blob/master/CHANGELOG.md) - [Commits](https://github.com/crossbeam-rs/crossbeam/compare/crossbeam-utils-0.8.16...crossbeam-utils-0.8.19) --- updated-dependencies: - dependency-name: crossbeam-utils dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-02 23:35:14 +00:00
checksum = "248e3bacc7dc6baa3b21e405ee045c3047101a49145e7e9eca583ab4c2ca5345"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "crypto-common"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1bfb12502f3fc46cca1bb51ac28df9d618d813cdc3d2f25b9fe775a34af26bb3"
dependencies = [
"generic-array",
"typenum",
]
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
[[package]]
name = "darling"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.20.8"
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "54e36fcd13ed84ffdfda6f5be89b31287cbb80c439841fe69e04841435464391"
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
dependencies = [
"darling_core",
"darling_macro",
]
[[package]]
name = "darling_core"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.20.8"
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "9c2cf1c23a687a1feeb728783b993c4e1ad83d99f351801977dd809b48d0a70f"
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
dependencies = [
"fnv",
"ident_case",
"proc-macro2",
"quote",
build: Bump clap from 4.4.7 to 4.5.1 Bumps [clap](https://github.com/clap-rs/clap) from 4.4.7 to 4.5.1. - [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/clap_complete-v4.4.7...clap_complete-v4.5.1) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-29 20:08:49 +00:00
"strsim 0.10.0",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
]
[[package]]
name = "darling_macro"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.20.8"
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "a668eda54683121533a393014d8692171709ff57a7d61f187b6e782719f8933f"
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
dependencies = [
"darling_core",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
]
block: Replace use of crc32c crate with crc-any According to crates.io the crc-any crate is actively maintained which avoids issues with the crc32c crate and the nightly compiler. Fixes: #6168 Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-02-06 20:48:47 +00:00
[[package]]
name = "debug-helper"
version = "0.3.13"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f578e8e2c440e7297e008bb5486a3a8a194775224bbc23729b0dbdfaeebf162e"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "derivative"
version = "2.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fcc3dd5e9e9c0b295d6e1e4d811fb6f157d5ffd784b8d202fc62eac8035a770b"
dependencies = [
"proc-macro2",
"quote",
"syn 1.0.109",
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
]
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"bitflags 2.5.0",
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",
devices: pvpanic: Add pci configuration for pvpanic device Implemetion of BusDevice and PciDevice trait for pvpanic device. Pvpanic device can be implemented as an ISA device or as a PCI device, we choose PCI device for now. Signed-off-by: Yi Wang <foxywang@tencent.com>
2023-06-14 13:04:07 +00:00
"event_monitor",
aarch64: Simplify GIC related structs definition Combined the `GicDevice` struct in `arch` crate and the `Gic` struct in `devices` crate. After moving the KVM specific code for GIC in `arch`, a very thin wapper layer `GicDevice` was left in `arch` crate. It is easy to combine it with the `Gic` in `devices` crate. Signed-off-by: Michael Zhao <michael.zhao@arm.com>
2022-06-01 05:24:12 +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",
devices: pvpanic: Add pci configuration for pvpanic device Implemetion of BusDevice and PciDevice trait for pvpanic device. Pvpanic device can be implemented as an ISA device or as a PCI device, we choose PCI device for now. Signed-off-by: Yi Wang <foxywang@tencent.com>
2023-06-14 13:04:07 +00:00
"pci",
devices: Add tpm device This device emulates a tpm device in cloud-hypervisor. Read and write support to miminal set of control registers is supported. Non-control commands will be processed as reads and write to CRB_DATA_BUFFER. Reads and Writes to this data buffer are forwarded to swtpm via the configured data_fd. Signed-off-by: Praveen K Paladugu <prapal@linux.microsoft.com> Co-authored-by: Sean Yoo <t-seanyoo@microsoft.com>
2022-09-12 20:46:03 +00:00
"thiserror",
"tpm",
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",
devices: pvpanic: Add pci configuration for pvpanic device Implemetion of BusDevice and PciDevice trait for pvpanic device. Pvpanic device can be implemented as an ISA device or as a PCI device, we choose PCI device for now. Signed-off-by: Yi Wang <foxywang@tencent.com>
2023-06-14 13:04:07 +00:00
"vm-allocator",
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",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +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: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
[[package]]
name = "dhat"
build: Bump dhat from 0.3.2 to 0.3.3 Bumps [dhat](https://github.com/nnethercote/dhat-rs) from 0.3.2 to 0.3.3. - [Release notes](https://github.com/nnethercote/dhat-rs/releases) - [Commits](https://github.com/nnethercote/dhat-rs/compare/0.3.2...0.3.3) --- updated-dependencies: - dependency-name: dhat dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-12 23:50:24 +00:00
version = "0.3.3"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump dhat from 0.3.2 to 0.3.3 Bumps [dhat](https://github.com/nnethercote/dhat-rs) from 0.3.2 to 0.3.3. - [Release notes](https://github.com/nnethercote/dhat-rs/releases) - [Commits](https://github.com/nnethercote/dhat-rs/compare/0.3.2...0.3.3) --- updated-dependencies: - dependency-name: dhat dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-12 23:50:24 +00:00
checksum = "98cd11d84628e233de0ce467de10b8633f4ddaecafadefc86e13b84b8739b827"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
dependencies = [
"backtrace",
"lazy_static",
"mintex",
"parking_lot 0.12.1",
"rustc-hash",
"serde",
"serde_json",
"thousands",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "digest"
version = "0.10.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9ed9a281f7bc9b7576e61468ba615a66a5c8cfdff42420a70aa82701a3b1e292"
dependencies = [
"block-buffer",
"crypto-common",
]
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"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
version = "5.0.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
checksum = "44c45a9d03d6676652bcb5e724c7e988de1acad23a711b5217ab9cbecbec2225"
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
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"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
version = "0.4.1"
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"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
checksum = "520f05a5cbd335fae5a99ff7a6ab8627577660ee5cfd6a94a6a929b52ff0321c"
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",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"option-ext",
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
"redox_users",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"windows-sys 0.48.0",
]
[[package]]
name = "enumflags2"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.7.9"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "3278c9d5fb675e0a51dabcf4c0d355f692b064171535ba72361be1528a9d8e8d"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"enumflags2_derive",
"serde",
]
[[package]]
name = "enumflags2_derive"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.7.9"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "5c785274071b1b420972453b306eeca06acf4633829db4223b58a2a8c5953bc4"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"proc-macro2",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.10.2"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "4cd405aab171cb85d6735e5c8d9db038c17d3ca007a4d2c25f337935c3d90580"
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 = [
"humantime",
misc: Bulk update dependencies In particular update to latest linux-loader release and point to latest vfio repository for both crates hosted there. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-12-07 17:39:14 +00:00
"is-terminal",
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: Bump epoll from 4.3.1 to 4.3.3 Bumps [epoll](https://github.com/nathansizemore/epoll) from 4.3.1 to 4.3.3. - [Release notes](https://github.com/nathansizemore/epoll/releases) - [Commits](https://github.com/nathansizemore/epoll/compare/4.3.1...4.3.3) --- updated-dependencies: - dependency-name: epoll dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-07-04 23:04:49 +00:00
version = "4.3.3"
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 epoll from 4.3.1 to 4.3.3 Bumps [epoll](https://github.com/nathansizemore/epoll) from 4.3.1 to 4.3.3. - [Release notes](https://github.com/nathansizemore/epoll/releases) - [Commits](https://github.com/nathansizemore/epoll/compare/4.3.1...4.3.3) --- updated-dependencies: - dependency-name: epoll dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-07-04 23:04:49 +00:00
checksum = "74351c3392ea1ff6cd2628e0042d268ac2371cb613252ff383b6dfa50d22fa79"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"bitflags 2.5.0",
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
]
build: Bump toml_edit from 0.19.8 to 0.19.15 Bumps [toml_edit](https://github.com/toml-rs/toml) from 0.19.8 to 0.19.15. - [Commits](https://github.com/toml-rs/toml/compare/v0.19.8...v0.19.15) --- updated-dependencies: - dependency-name: toml_edit dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-10-31 17:16:45 +00:00
[[package]]
name = "equivalent"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5443807d6dff69373d433ab9ef5378ad8df50ca6298caf15de6e52e24aaf54d5"
build: Bump textwrap from 0.15.0 to 0.15.1 Bumps [textwrap](https://github.com/mgeisler/textwrap) from 0.15.0 to 0.15.1. - [Release notes](https://github.com/mgeisler/textwrap/releases) - [Changelog](https://github.com/mgeisler/textwrap/blob/master/CHANGELOG.md) - [Commits](https://github.com/mgeisler/textwrap/compare/0.15.0...0.15.1) --- updated-dependencies: - dependency-name: textwrap dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-16 00:45:44 +00:00
[[package]]
name = "errno"
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
version = "0.3.8"
build: Bump textwrap from 0.15.0 to 0.15.1 Bumps [textwrap](https://github.com/mgeisler/textwrap) from 0.15.0 to 0.15.1. - [Release notes](https://github.com/mgeisler/textwrap/releases) - [Changelog](https://github.com/mgeisler/textwrap/blob/master/CHANGELOG.md) - [Commits](https://github.com/mgeisler/textwrap/compare/0.15.0...0.15.1) --- updated-dependencies: - dependency-name: textwrap dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-16 00:45:44 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
checksum = "a258e46cdc063eb8519c00b9fc845fc47bcfca4130e2f08e88665ceda8474245"
build: Bump textwrap from 0.15.0 to 0.15.1 Bumps [textwrap](https://github.com/mgeisler/textwrap) from 0.15.0 to 0.15.1. - [Release notes](https://github.com/mgeisler/textwrap/releases) - [Changelog](https://github.com/mgeisler/textwrap/blob/master/CHANGELOG.md) - [Commits](https://github.com/mgeisler/textwrap/compare/0.15.0...0.15.1) --- updated-dependencies: - dependency-name: textwrap dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-16 00:45:44 +00:00
dependencies = [
"libc",
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
"windows-sys 0.52.0",
build: Bump textwrap from 0.15.0 to 0.15.1 Bumps [textwrap](https://github.com/mgeisler/textwrap) from 0.15.0 to 0.15.1. - [Release notes](https://github.com/mgeisler/textwrap/releases) - [Changelog](https://github.com/mgeisler/textwrap/blob/master/CHANGELOG.md) - [Commits](https://github.com/mgeisler/textwrap/compare/0.15.0...0.15.1) --- updated-dependencies: - dependency-name: textwrap dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-16 00:45:44 +00:00
]
[[package]]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
name = "event-listener"
version = "2.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0206175f82b8d6bf6652ff7d71a1e27fd2e4efde587fd368662814d6ec1d9ce0"
build: Bump async-process from 1.7.0 to 1.8.0 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-28 23:47:38 +00:00
[[package]]
name = "event-listener"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "3.1.0"
build: Bump async-process from 1.7.0 to 1.8.0 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-28 23:47:38 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "d93877bcde0eb80ca09131a08d23f0a5c18a620b01db137dba666d18cd9b30c2"
build: Bump async-process from 1.7.0 to 1.8.0 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-28 23:47:38 +00:00
dependencies = [
"concurrent-queue",
"parking",
"pin-project-lite",
]
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
[[package]]
name = "event-listener"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "4.0.3"
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "67b215c49b2b248c855fb73579eb1f4f26c38ffdc12973e20e07b91d78d5646e"
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
dependencies = [
"concurrent-queue",
"parking",
"pin-project-lite",
]
build: Bump async-channel from 2.1.1 to 2.2.0 Bumps [async-channel](https://github.com/smol-rs/async-channel) from 2.1.1 to 2.2.0. - [Release notes](https://github.com/smol-rs/async-channel/releases) - [Changelog](https://github.com/smol-rs/async-channel/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-channel/compare/v2.1.1...v2.2.0) --- updated-dependencies: - dependency-name: async-channel dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-14 23:11:47 +00:00
[[package]]
name = "event-listener"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "5.3.0"
build: Bump async-channel from 2.1.1 to 2.2.0 Bumps [async-channel](https://github.com/smol-rs/async-channel) from 2.1.1 to 2.2.0. - [Release notes](https://github.com/smol-rs/async-channel/releases) - [Changelog](https://github.com/smol-rs/async-channel/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-channel/compare/v2.1.1...v2.2.0) --- updated-dependencies: - dependency-name: async-channel dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-14 23:11:47 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "6d9944b8ca13534cdfb2800775f8dd4902ff3fc75a50101466decadfdf322a24"
build: Bump async-channel from 2.1.1 to 2.2.0 Bumps [async-channel](https://github.com/smol-rs/async-channel) from 2.1.1 to 2.2.0. - [Release notes](https://github.com/smol-rs/async-channel/releases) - [Changelog](https://github.com/smol-rs/async-channel/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-channel/compare/v2.1.1...v2.2.0) --- updated-dependencies: - dependency-name: async-channel dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-14 23:11:47 +00:00
dependencies = [
"concurrent-queue",
"parking",
"pin-project-lite",
]
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
[[package]]
name = "event-listener-strategy"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "958e4d70b6d5e81971bebec42271ec641e7ff4e170a6fa605f2b8a8b65cb97d3"
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"event-listener 4.0.3",
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
"pin-project-lite",
]
build: Bump async-channel from 2.1.1 to 2.2.0 Bumps [async-channel](https://github.com/smol-rs/async-channel) from 2.1.1 to 2.2.0. - [Release notes](https://github.com/smol-rs/async-channel/releases) - [Changelog](https://github.com/smol-rs/async-channel/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-channel/compare/v2.1.1...v2.2.0) --- updated-dependencies: - dependency-name: async-channel dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-14 23:11:47 +00:00
[[package]]
name = "event-listener-strategy"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.5.1"
build: Bump async-channel from 2.1.1 to 2.2.0 Bumps [async-channel](https://github.com/smol-rs/async-channel) from 2.1.1 to 2.2.0. - [Release notes](https://github.com/smol-rs/async-channel/releases) - [Changelog](https://github.com/smol-rs/async-channel/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-channel/compare/v2.1.1...v2.2.0) --- updated-dependencies: - dependency-name: async-channel dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-14 23:11:47 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "332f51cb23d20b0de8458b86580878211da09bcd4503cb579c225b3d124cabb3"
build: Bump async-channel from 2.1.1 to 2.2.0 Bumps [async-channel](https://github.com/smol-rs/async-channel) from 2.1.1 to 2.2.0. - [Release notes](https://github.com/smol-rs/async-channel/releases) - [Changelog](https://github.com/smol-rs/async-channel/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-channel/compare/v2.1.1...v2.2.0) --- updated-dependencies: - dependency-name: async-channel dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-14 23:11:47 +00:00
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"event-listener 5.3.0",
build: Bump async-channel from 2.1.1 to 2.2.0 Bumps [async-channel](https://github.com/smol-rs/async-channel) from 2.1.1 to 2.2.0. - [Release notes](https://github.com/smol-rs/async-channel/releases) - [Changelog](https://github.com/smol-rs/async-channel/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-channel/compare/v2.1.1...v2.2.0) --- updated-dependencies: - dependency-name: async-channel dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-14 23:11:47 +00:00
"pin-project-lite",
]
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 = [
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
"flume",
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
"libc",
event_monitor: Replace unsound `static mut MONITOR` See discussion in https://github.com/rust-lang/rust/issues/53639. This came up during an internal review. Signed-off-by: Christian Blichmann <cblichmann@google.com>
2023-09-14 09:19:12 +00:00
"once_cell",
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
"serde",
"serde_json",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "fastrand"
version = "1.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e51093e27b0797c359783294ca4f0a911c270184cb10f85783b118614a1501be"
dependencies = [
"instant",
]
build: Bump tempfile from 3.5.0 to 3.7.1 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.5.0 to 3.7.1. - [Changelog](https://github.com/Stebalien/tempfile/blob/master/CHANGELOG.md) - [Commits](https://github.com/Stebalien/tempfile/compare/v3.5.0...v3.7.1) --- updated-dependencies: - dependency-name: tempfile dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-17 23:13:33 +00:00
[[package]]
name = "fastrand"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "2.0.2"
build: Bump tempfile from 3.5.0 to 3.7.1 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.5.0 to 3.7.1. - [Changelog](https://github.com/Stebalien/tempfile/blob/master/CHANGELOG.md) - [Commits](https://github.com/Stebalien/tempfile/compare/v3.5.0...v3.7.1) --- updated-dependencies: - dependency-name: tempfile dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-17 23:13:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "658bd65b1cf4c852a3cc96f18a8ce7b5640f6b703f905c7d74532294c2a63984"
build: Bump tempfile from 3.5.0 to 3.7.1 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.5.0 to 3.7.1. - [Changelog](https://github.com/Stebalien/tempfile/blob/master/CHANGELOG.md) - [Commits](https://github.com/Stebalien/tempfile/compare/v3.5.0...v3.7.1) --- updated-dependencies: - dependency-name: tempfile dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-17 23:13:33 +00:00
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"
build: Bump fdt from 0.1.4 to 0.1.5 Bumps [fdt](https://github.com/repnop/fdt) from 0.1.4 to 0.1.5. - [Release notes](https://github.com/repnop/fdt/releases) - [Commits](https://github.com/repnop/fdt/commits) --- updated-dependencies: - dependency-name: fdt dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-15 23:58:36 +00:00
version = "0.1.5"
build: Add missing Cargo.lock change Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-06-18 14:24:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump fdt from 0.1.4 to 0.1.5 Bumps [fdt](https://github.com/repnop/fdt) from 0.1.4 to 0.1.5. - [Release notes](https://github.com/repnop/fdt/releases) - [Commits](https://github.com/repnop/fdt/commits) --- updated-dependencies: - dependency-name: fdt dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-15 23:58:36 +00:00
checksum = "784a4df722dc6267a04af36895398f59d21d07dce47232adf31ec0ff2fa45e67"
build: Add missing Cargo.lock change Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-06-18 14:24:33 +00:00
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
[[package]]
name = "flume"
version = "0.10.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1657b4441c3403d9f7b3409e47575237dac27b1b5726df654a6ecbf92f0f7577"
dependencies = [
"futures-core",
"futures-sink",
"nanorand",
"pin-project",
"spin",
]
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
[[package]]
name = "fnv"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "futures"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
version = "0.3.30"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
checksum = "645c6916888f6cb6350d2550b80fb63e734897a8498abe35cfb732b6487804b0"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"futures-channel",
"futures-core",
"futures-executor",
"futures-io",
"futures-sink",
"futures-task",
"futures-util",
]
[[package]]
name = "futures-channel"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
version = "0.3.30"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
checksum = "eac8f7d7865dcb88bd4373ab671c8cf4508703796caa2b1985a9ca867b3fcb78"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"futures-core",
"futures-sink",
]
[[package]]
name = "futures-core"
build: Bump futures-core from 0.3.29 to 0.3.30 Bumps [futures-core](https://github.com/rust-lang/futures-rs) from 0.3.29 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.29...0.3.30) --- updated-dependencies: - dependency-name: futures-core dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-04 23:31:33 +00:00
version = "0.3.30"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump futures-core from 0.3.29 to 0.3.30 Bumps [futures-core](https://github.com/rust-lang/futures-rs) from 0.3.29 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.29...0.3.30) --- updated-dependencies: - dependency-name: futures-core dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-04 23:31:33 +00:00
checksum = "dfc6580bb841c5a68e9ef15c77ccc837b40a7504914d52e47b8b0e9bbda25a1d"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "futures-executor"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
version = "0.3.30"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
checksum = "a576fc72ae164fca6b9db127eaa9a9dda0d61316034f33a0a0d4eda41f02b01d"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"futures-core",
"futures-task",
"futures-util",
]
[[package]]
name = "futures-io"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
version = "0.3.30"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
checksum = "a44623e20b9681a318efdd71c299b6b222ed6f231972bfe2f224ebad6311f0c1"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "futures-lite"
version = "1.13.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "49a9d51ce47660b1e808d3c990b4709f2f415d928835a17dfd16991515c46bce"
dependencies = [
build: Bump tempfile from 3.5.0 to 3.7.1 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.5.0 to 3.7.1. - [Changelog](https://github.com/Stebalien/tempfile/blob/master/CHANGELOG.md) - [Commits](https://github.com/Stebalien/tempfile/compare/v3.5.0...v3.7.1) --- updated-dependencies: - dependency-name: tempfile dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-17 23:13:33 +00:00
"fastrand 1.9.0",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"futures-core",
"futures-io",
"memchr",
"parking",
"pin-project-lite",
"waker-fn",
]
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
[[package]]
name = "futures-lite"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "2.3.0"
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "52527eb5074e35e9339c6b4e8d12600c7128b68fb25dcb9fa9dec18f7c25f3a5"
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"fastrand 2.0.2",
build: Bump async-executor from 1.5.1 to 1.8.0 Bumps [async-executor](https://github.com/smol-rs/async-executor) from 1.5.1 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-executor/releases) - [Changelog](https://github.com/smol-rs/async-executor/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-executor/compare/v1.5.1...v1.8.0) --- updated-dependencies: - dependency-name: async-executor dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-13 23:57:50 +00:00
"futures-core",
"futures-io",
"parking",
"pin-project-lite",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "futures-macro"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
version = "0.3.30"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
checksum = "87750cf4b7a4c0625b1529e4c543c2182106e4dedc60a2a6455e00d212c489ac"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"proc-macro2",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
]
[[package]]
name = "futures-sink"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
version = "0.3.30"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
checksum = "9fb8e00e87438d937621c1c6269e53f536c14d3fbd6a042bb24879e57d474fb5"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "futures-task"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
version = "0.3.30"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
checksum = "38d84fa142264698cdce1a9f9172cf383a0c82de1bddcf3092901442c4097004"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "futures-util"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
version = "0.3.30"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump futures from 0.3.28 to 0.3.30 Bumps [futures](https://github.com/rust-lang/futures-rs) from 0.3.28 to 0.3.30. - [Release notes](https://github.com/rust-lang/futures-rs/releases) - [Changelog](https://github.com/rust-lang/futures-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/futures-rs/compare/0.3.28...0.3.30) --- updated-dependencies: - dependency-name: futures dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 09:27:32 +00:00
checksum = "3d6401deb83407ab3da39eba7e33987a73c3df0c82b4bb5813ee871c19c41d48"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"futures-channel",
"futures-core",
"futures-io",
"futures-macro",
"futures-sink",
"futures-task",
"memchr",
"pin-project-lite",
"pin-utils",
"slab",
]
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.7.0 to 0.7.1 Bumps [gdbstub](https://github.com/daniel5151/gdbstub) from 0.7.0 to 0.7.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.7.0...0.7.1) --- updated-dependencies: - dependency-name: gdbstub dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-25 23:27:07 +00:00
version = "0.7.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.7.0 to 0.7.1 Bumps [gdbstub](https://github.com/daniel5151/gdbstub) from 0.7.0 to 0.7.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.7.0...0.7.1) --- updated-dependencies: - dependency-name: gdbstub dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-25 23:27:07 +00:00
checksum = "6341b3480afbb34eaefc7f92713bc92f2d83e338aaa1c44192f9c2956f4a4903"
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 = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"bitflags 2.5.0",
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
"cfg-if",
"log",
"managed",
"num-traits",
"paste",
]
[[package]]
name = "gdbstub_arch"
build: Bump gdbstub and gdbstub_arch This commit also makes changes due to the breaking API changes from the `gdbstub` crate [1]. [1] https://github.com/daniel5151/gdbstub/releases/tag/0.7.0 Fix: #5997 Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-12-01 23:36:37 +00:00
version = "0.3.0"
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 and gdbstub_arch This commit also makes changes due to the breaking API changes from the `gdbstub` crate [1]. [1] https://github.com/daniel5151/gdbstub/releases/tag/0.7.0 Fix: #5997 Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-12-01 23:36:37 +00:00
checksum = "4e3b1357bd3203fc09a6601327ae0ab38865d14231d0b65d3143f5762cc7977d"
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",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "generic-array"
version = "0.14.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "85649ca51fd72272d7821adaf274ad91c288277713d9c18820d8499a7ff69e9a"
dependencies = [
"typenum",
"version_check",
]
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.2.13"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "a06fddc2749e0528d2813f95e050e87e52c8cbbae56223b9babf73b3e53b0cc6"
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",
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
"js-sys",
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",
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
"wasm-bindgen",
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: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
[[package]]
name = "gimli"
build: Bump backtrace from 0.3.67 to 0.3.71 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.67 to 0.3.71. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.67...0.3.71) --- updated-dependencies: - dependency-name: backtrace dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-01 23:35:54 +00:00
version = "0.28.1"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump backtrace from 0.3.67 to 0.3.71 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.67 to 0.3.71. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.67...0.3.71) --- updated-dependencies: - dependency-name: backtrace dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-01 23:35:54 +00:00
checksum = "4271d37baee1b8c7e4b708028c57d816cf9d2434acb33a549475f78c181f6253"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +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: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
version = "0.3.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: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
checksum = "d2fabcfbdc87f4758337ca535fb41a6d701b65693ce38287d856d1674551ec9b"
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: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "hashbrown"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.14.3"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "290f1a1d9242c78d09ce40a5e87e7554ee637af1351968159f4952f028f75604"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
[[package]]
name = "hermit-abi"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.3.9"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "d231dfb89cfffdbc30e7fc41579ed6066ad03abda9e567ccafae602b97ec5024"
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
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "hex"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7f24254aa9a54b5c858eaee2f5bccdb46aaf0e486a595ed5fd8f86ba55232a70"
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: provide a generic LapicState structure This requires making get/set_lapic_reg part of the type. For the moment we cannot provide a default variant for the new type, because picking one will be wrong for the other hypervisor, so I just drop the test cases that requires LapicState::default(). Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-18 15:47:51 +00:00
"byteorder",
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: 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 API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
"igvm",
"igvm_defs",
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",
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
"serde_with",
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
"thiserror",
hypervisor, vmm: use new vfio-ioctls Use the new vfio-ioctls APIs. Drop Cloud Hypervisor's Device trait since it is no longer needed. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-21 13:15:15 +00:00
"vfio-ioctls",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +00:00
"vm-memory",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-util",
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
]
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.21.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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "7c447cff8c7f384a7d4f741cfcff32f75f3ad02b406432e8d6c878d56b1edf6b"
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",
]
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
[[package]]
name = "ident_case"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b9e0384b61958566e926dc50660321d12159025e767c18e043daf26b70104c39"
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
[[package]]
name = "igvm"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.1.9"
source = "git+https://github.com/microsoft/igvm?branch=main#494aac2318df4111a2737d360ea46f74f5350223"
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
dependencies = [
"bitfield-struct",
"crc32fast",
"hex",
"igvm_defs",
"open-enum",
"range_map_vec",
"thiserror",
"tracing",
"zerocopy",
]
[[package]]
name = "igvm_defs"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.1.9"
source = "git+https://github.com/microsoft/igvm?branch=main#494aac2318df4111a2737d360ea46f74f5350223"
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
dependencies = [
"bitfield-struct",
"open-enum",
"static_assertions",
"zerocopy",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "indexmap"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "2.2.6"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "168fb715dda47215e360912c096649d23d58bf392ac62f73919e831745e40f26"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
build: Bump toml_edit from 0.19.8 to 0.19.15 Bumps [toml_edit](https://github.com/toml-rs/toml) from 0.19.8 to 0.19.15. - [Commits](https://github.com/toml-rs/toml/compare/v0.19.8...v0.19.15) --- updated-dependencies: - dependency-name: toml_edit dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-10-31 17:16:45 +00:00
"equivalent",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"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",
]
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
[[package]]
name = "io-lifetimes"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
version = "1.0.11"
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
checksum = "eae7b9aee968036d54dce06cebaefd919e4472e753296daccd6d344e3e2df0c2"
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
dependencies = [
build: Bump io-lifetimes from 1.0.4 to 1.0.10 Bumps [io-lifetimes](https://github.com/sunfishcode/io-lifetimes) from 1.0.4 to 1.0.10. - [Release notes](https://github.com/sunfishcode/io-lifetimes/releases) - [Commits](https://github.com/sunfishcode/io-lifetimes/compare/1.0.4...v1.0.10) --- updated-dependencies: - dependency-name: io-lifetimes dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-14 23:57:20 +00:00
"hermit-abi",
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
"libc",
build: Bump io-lifetimes from 1.0.4 to 1.0.10 Bumps [io-lifetimes](https://github.com/sunfishcode/io-lifetimes) from 1.0.4 to 1.0.10. - [Release notes](https://github.com/sunfishcode/io-lifetimes/releases) - [Commits](https://github.com/sunfishcode/io-lifetimes/compare/1.0.4...v1.0.10) --- updated-dependencies: - dependency-name: io-lifetimes dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-14 23:57:20 +00:00
"windows-sys 0.48.0",
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
]
build: Bump textwrap from 0.15.0 to 0.15.1 Bumps [textwrap](https://github.com/mgeisler/textwrap) from 0.15.0 to 0.15.1. - [Release notes](https://github.com/mgeisler/textwrap/releases) - [Changelog](https://github.com/mgeisler/textwrap/blob/master/CHANGELOG.md) - [Commits](https://github.com/mgeisler/textwrap/compare/0.15.0...0.15.1) --- updated-dependencies: - dependency-name: textwrap dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-16 00:45:44 +00:00
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.6.3"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "a9febecd4aebbe9c7c23c8e536e966805fdf09944c8a915e7991ee51acb67087"
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 bitflags from 1.3.2 to 2.3.2 Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.2 to 2.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.2...2.3.2) --- updated-dependencies: - dependency-name: bitflags dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2023-06-16 00:54:27 +00:00
"bitflags 1.3.2",
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: bump pnet from 0.29.0 to 0.30.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.29.0 to 0.30.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.29.0...v0.30.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-05-24 16:00:10 +00:00
[[package]]
name = "ipnetwork"
build: Bump pnet and pnet_datalink from 0.31.0 to 0.33.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.31.0 to 0.33.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.31.0...v0.33.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: Bo Chen <chen.bo@intel.com> Signed-off-by: dependabot[bot] <support@github.com>
2023-02-03 23:02:15 +00:00
version = "0.20.0"
build: bump pnet from 0.29.0 to 0.30.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.29.0 to 0.30.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.29.0...v0.30.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-05-24 16:00:10 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump pnet and pnet_datalink from 0.31.0 to 0.33.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.31.0 to 0.33.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.31.0...v0.33.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: Bo Chen <chen.bo@intel.com> Signed-off-by: dependabot[bot] <support@github.com>
2023-02-03 23:02:15 +00:00
checksum = "bf466541e9d546596ee94f9f69590f89473455f88372423e0008fc1a7daf100e"
build: bump pnet from 0.29.0 to 0.30.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.29.0 to 0.30.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.29.0...v0.30.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-05-24 16:00:10 +00:00
dependencies = [
"serde",
]
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
[[package]]
name = "is-terminal"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.4.12"
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "f23ff5ef2b80d608d61efee834934d862cd92461afc0560dedf493e4c033738b"
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
dependencies = [
misc: Bulk update dependencies In particular update to latest linux-loader release and point to latest vfio repository for both crates hosted there. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-12-07 17:39:14 +00:00
"hermit-abi",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"libc",
"windows-sys 0.52.0",
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08: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 = "itoa"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.0.11"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "49f1f14873335454500d59611f1cf4a4b0f786f9ac11f4312a78e4cf2566695b"
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
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
[[package]]
name = "js-sys"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.3.69"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "29c15563dc2726973df627357ce0c9ddddbea194836909d655df6a75d2cf296d"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
dependencies = [
"wasm-bindgen",
]
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"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
version = "0.7.0"
source = "git+https://github.com/cloud-hypervisor/kvm-bindings?branch=ch-v0.7.0#2dcf85d4f8aa55befcaa996b699ddb18ec9ed059"
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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +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 vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
version = "0.16.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9002dff009755414f22b962ec6ae6980b07d6d8b06e5297b1062019d72bd6a8c"
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 = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"bitflags 2.5.0",
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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"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.151 to 0.2.153 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.151 to 0.2.153. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.151...0.2.153) --- updated-dependencies: - dependency-name: libc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 23:15:53 +00:00
version = "0.2.153"
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.151 to 0.2.153 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.151 to 0.2.153. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.151...0.2.153) --- updated-dependencies: - dependency-name: libc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 23:15:53 +00:00
checksum = "9c198f91728a82281a64e1f4f9eeb25d82cb32a5de251c6bd1b5154d63a8e7bd"
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: Bump redox_users from 0.4.3 to 0.4.4 Bumps redox_users from 0.4.3 to 0.4.4. --- updated-dependencies: - dependency-name: redox_users dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-13 23:56:41 +00:00
[[package]]
name = "libredox"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.1.3"
build: Bump redox_users from 0.4.3 to 0.4.4 Bumps redox_users from 0.4.3 to 0.4.4. --- updated-dependencies: - dependency-name: redox_users dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-13 23:56:41 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "c0ff37bd590ca25063e35af745c343cb7a0271906fb7b37e4813e8f79f00268d"
build: Bump redox_users from 0.4.3 to 0.4.4 Bumps redox_users from 0.4.3 to 0.4.4. --- updated-dependencies: - dependency-name: redox_users dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-13 23:56:41 +00:00
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"bitflags 2.5.0",
build: Bump redox_users from 0.4.3 to 0.4.4 Bumps redox_users from 0.4.3 to 0.4.4. --- updated-dependencies: - dependency-name: redox_users dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-13 23:56:41 +00:00
"libc",
]
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 ssh2 from 0.9.3 to 0.9.4 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.3 to 0.9.4. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.3...0.9.4) --- updated-dependencies: - dependency-name: ssh2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-01-25 23:04:36 +00:00
version = "0.3.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: Bump ssh2 from 0.9.3 to 0.9.4 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.3 to 0.9.4. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.3...0.9.4) --- updated-dependencies: - dependency-name: ssh2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-01-25 23:04:36 +00:00
checksum = "2dc8a030b787e2119a731f1951d6a773e2280c660f8ec4b0f5e1505a386e71ee"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.1.16"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "5e143b5e666b2695d28f6bca6497720813f699c9602dd7f5cac91008b8ada7f9"
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 vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
version = "0.11.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 vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
checksum = "eb68dd3452f25a8defaf0ae593509cff0c777683e4d8924f59ac7c5f89267a83"
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 = [
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +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: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
[[package]]
name = "linux-raw-sys"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
version = "0.3.8"
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
checksum = "ef53942eb7bf7ff43a617b3e2c1c4a5ecf5944a7c1bc12d7ee39bbb15e5c1519"
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
build: Bump tempfile from 3.5.0 to 3.7.1 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.5.0 to 3.7.1. - [Changelog](https://github.com/Stebalien/tempfile/blob/master/CHANGELOG.md) - [Commits](https://github.com/Stebalien/tempfile/compare/v3.5.0...v3.7.1) --- updated-dependencies: - dependency-name: tempfile dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-17 23:13:33 +00:00
[[package]]
name = "linux-raw-sys"
build: Bump rustix from 0.38.8 to 0.38.25 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-25 23:11:18 +00:00
version = "0.4.13"
build: Bump tempfile from 3.5.0 to 3.7.1 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.5.0 to 3.7.1. - [Changelog](https://github.com/Stebalien/tempfile/blob/master/CHANGELOG.md) - [Commits](https://github.com/Stebalien/tempfile/compare/v3.5.0...v3.7.1) --- updated-dependencies: - dependency-name: tempfile dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-17 23:13:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump rustix from 0.38.8 to 0.38.25 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-25 23:11:18 +00:00
checksum = "01cda141df6706de531b6c46c3a33ecca755538219bd484262fa09410c13539c"
build: Bump tempfile from 3.5.0 to 3.7.1 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.5.0 to 3.7.1. - [Changelog](https://github.com/Stebalien/tempfile/blob/master/CHANGELOG.md) - [Commits](https://github.com/Stebalien/tempfile/compare/v3.5.0...v3.7.1) --- updated-dependencies: - dependency-name: tempfile dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-17 23:13: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 = "lock_api"
build: Bump lock_api from 0.4.10 to 0.4.11 Bumps [lock_api](https://github.com/Amanieu/parking_lot) from 0.4.10 to 0.4.11. - [Changelog](https://github.com/Amanieu/parking_lot/blob/master/CHANGELOG.md) - [Commits](https://github.com/Amanieu/parking_lot/compare/lock_api-0.4.10...lock_api-0.4.11) --- updated-dependencies: - dependency-name: lock_api dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-11 23:37:31 +00:00
version = "0.4.11"
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.10 to 0.4.11 Bumps [lock_api](https://github.com/Amanieu/parking_lot) from 0.4.10 to 0.4.11. - [Changelog](https://github.com/Amanieu/parking_lot/blob/master/CHANGELOG.md) - [Commits](https://github.com/Amanieu/parking_lot/compare/lock_api-0.4.10...lock_api-0.4.11) --- updated-dependencies: - dependency-name: lock_api dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-11 23:37:31 +00:00
checksum = "3c168f8615b12bc01f9c17e2eb0cc07dcae1940121185446edc3744920e8ef45"
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 lock_api from 0.4.6 to 0.4.7 Bumps [lock_api](https://github.com/Amanieu/parking_lot) from 0.4.6 to 0.4.7. - [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.6...lock_api-0.4.7) --- updated-dependencies: - dependency-name: lock_api dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-30 23:45:47 +00:00
"autocfg",
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.4.21"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "90ed8c1e510134f979dbc4f070f87d4313098b704861a105fe34231c70a3901c"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "2.7.2"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "6c8640c5d730cb13ebd907d8d04b52f55ac9a2eec55b440c8892f40d56c76c1d"
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: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "memoffset"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5de893c32cde5f383baa4c04c5d6dbdd735cfd4a794b0debdb2bb1b421da5ff4"
dependencies = [
"autocfg",
]
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
[[package]]
name = "memoffset"
version = "0.9.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "488016bfae457b036d996092f6cb448677611ce4449e970ceaf42695203f218a"
dependencies = [
"autocfg",
]
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"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
source = "git+https://github.com/firecracker-microvm/micro-http?branch=main#ef43cef7162a55a6790d528a5e76b4fe2da22de0"
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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"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
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
[[package]]
name = "miniz_oxide"
build: Bump backtrace from 0.3.67 to 0.3.71 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.67 to 0.3.71. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.67...0.3.71) --- updated-dependencies: - dependency-name: backtrace dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-01 23:35:54 +00:00
version = "0.7.2"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump backtrace from 0.3.67 to 0.3.71 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.67 to 0.3.71. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.67...0.3.71) --- updated-dependencies: - dependency-name: backtrace dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-01 23:35:54 +00:00
checksum = "9d811f3e15f28568be3407c8e7fdb6514c1cda3cb30683f15b6a1a1dc4ea14a7"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
dependencies = [
"adler",
]
[[package]]
name = "mintex"
build: Bump mintex from 0.1.2 to 0.1.3 Bumps [mintex](https://github.com/garypen/mintex) from 0.1.2 to 0.1.3. - [Commits](https://github.com/garypen/mintex/compare/v0.1.2...v0.1.3) --- updated-dependencies: - dependency-name: mintex dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-23 23:53:59 +00:00
version = "0.1.3"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump mintex from 0.1.2 to 0.1.3 Bumps [mintex](https://github.com/garypen/mintex) from 0.1.2 to 0.1.3. - [Commits](https://github.com/garypen/mintex/compare/v0.1.2...v0.1.3) --- updated-dependencies: - dependency-name: mintex dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-23 23:53:59 +00:00
checksum = "9bec4598fddb13cc7b528819e697852653252b760f1228b7642679bf2ff2cd07"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +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"
build: bump mshv-ioctls from `8094002` to `0106c24` Bumps [mshv-ioctls](https://github.com/rust-vmm/mshv) from `8094002` to `0106c24`. - [Release notes](https://github.com/rust-vmm/mshv/releases) - [Commits](https://github.com/rust-vmm/mshv/compare/80940020f111fac79807ba25b565855c786ebcdd...0106c24a2632a591a87c7bdb2c96f4f2bcc2d9eb) --- updated-dependencies: - dependency-name: mshv-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-07 23:08:42 +00:00
version = "0.1.1"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
source = "git+https://github.com/rust-vmm/mshv?branch=main#d9ec6ec4565f7d291b61a6f39bdb7e29c5a1f8e4"
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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-util",
build: Bump versions of acpi_tables and zerocopy The 'derive' feature of `zerocopy` crate now is optional and requires to be enabled explicitly [1]. Also, a version bump on `acpi_tables` is needed to reply on a single version of `zerocopy` to avoid compilation errors. [1] https://github.com/google/zerocopy/pull/176 Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-09-25 22:44:06 +00:00
"zerocopy",
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-ioctls"
build: bump mshv-ioctls from `8094002` to `0106c24` Bumps [mshv-ioctls](https://github.com/rust-vmm/mshv) from `8094002` to `0106c24`. - [Release notes](https://github.com/rust-vmm/mshv/releases) - [Commits](https://github.com/rust-vmm/mshv/compare/80940020f111fac79807ba25b565855c786ebcdd...0106c24a2632a591a87c7bdb2c96f4f2bcc2d9eb) --- updated-dependencies: - dependency-name: mshv-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-07 23:08:42 +00:00
version = "0.1.1"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
source = "git+https://github.com/rust-vmm/mshv?branch=main#d9ec6ec4565f7d291b61a6f39bdb7e29c5a1f8e4"
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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-util",
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
]
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
[[package]]
name = "nanorand"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6a51313c5820b0b02bd422f4b44776fbf47961755c74ce64afc73bfad10226c3"
dependencies = [
"getrandom",
]
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 = [
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +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
"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",
net_util: switch from lazy_static to once_cell Once_cell does not require using macro and is slated to become part of Rust std at some point. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-06-20 14:10:55 +00:00
"once_cell",
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",
build: bump pnet from 0.30.0 to 0.31.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.30.0 to 0.31.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.30.0...v0.31.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: dependabot[bot] <support@github.com>
2022-06-03 01:16:58 +00:00
"pnet_datalink",
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: Derive thiserror::Error Signed-off-by: Bo Chen <chen.bo@intel.com>
2022-08-10 21:58:36 +00:00
"thiserror",
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",
build: Bulk update rust-vmm dependencies Bump to the latest rust-vmm crates, including vm-memory, vfio, vfio-bindings, vfio-user, virtio-bindings, virtio-queue, linux-loader, vhost, and vhost-user-backend, Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-05-19 16:12:25 +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",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +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: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "nix"
build: Bump nix from 0.26.2 to 0.26.4 Bumps [nix](https://github.com/nix-rust/nix) from 0.26.2 to 0.26.4. - [Changelog](https://github.com/nix-rust/nix/blob/v0.26.4/CHANGELOG.md) - [Commits](https://github.com/nix-rust/nix/compare/v0.26.2...v0.26.4) --- updated-dependencies: - dependency-name: nix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-01 23:05:53 +00:00
version = "0.26.4"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump nix from 0.26.2 to 0.26.4 Bumps [nix](https://github.com/nix-rust/nix) from 0.26.2 to 0.26.4. - [Changelog](https://github.com/nix-rust/nix/blob/v0.26.4/CHANGELOG.md) - [Commits](https://github.com/nix-rust/nix/compare/v0.26.2...v0.26.4) --- updated-dependencies: - dependency-name: nix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-01 23:05:53 +00:00
checksum = "598beaf3cc6fdd9a5dfb1630c2800c7acd31df7aaf0f565796fba2b53ca1af1b"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
build: Bump bitflags from 1.3.2 to 2.3.2 Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.2 to 2.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.2...2.3.2) --- updated-dependencies: - dependency-name: bitflags dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2023-06-16 00:54:27 +00:00
"bitflags 1.3.2",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"cfg-if",
"libc",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"memoffset 0.7.1",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
]
build: bump pnet from 0.29.0 to 0.30.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.29.0 to 0.30.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.29.0...v0.30.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-05-24 16:00:10 +00:00
[[package]]
name = "no-std-net"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "43794a0ace135be66a25d3ae77d41b91615fb68ae937f904090203e81f755b65"
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"
build: Bump num-traits from 0.2.17 to 0.2.18 Bumps [num-traits](https://github.com/rust-num/num-traits) from 0.2.17 to 0.2.18. - [Changelog](https://github.com/rust-num/num-traits/blob/master/RELEASES.md) - [Commits](https://github.com/rust-num/num-traits/compare/num-traits-0.2.17...num-traits-0.2.18) --- updated-dependencies: - dependency-name: num-traits dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-19 23:11:12 +00:00
version = "0.2.18"
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 num-traits from 0.2.17 to 0.2.18 Bumps [num-traits](https://github.com/rust-num/num-traits) from 0.2.17 to 0.2.18. - [Changelog](https://github.com/rust-num/num-traits/blob/master/RELEASES.md) - [Commits](https://github.com/rust-num/num-traits/compare/num-traits-0.2.17...num-traits-0.2.18) --- updated-dependencies: - dependency-name: num-traits dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-19 23:11:12 +00:00
checksum = "da0df0e5185db44f69b44f26786fe401b6c293d1907744beaa7fa62b2e5a517a"
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 = [
"autocfg",
]
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
[[package]]
name = "object"
build: Bump backtrace from 0.3.67 to 0.3.71 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.67 to 0.3.71. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.67...0.3.71) --- updated-dependencies: - dependency-name: backtrace dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-01 23:35:54 +00:00
version = "0.32.2"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump backtrace from 0.3.67 to 0.3.71 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.67 to 0.3.71. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.67...0.3.71) --- updated-dependencies: - dependency-name: backtrace dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-01 23:35:54 +00:00
checksum = "a6a622008b6e321afc04970976f62ee297fdbaa6f95318ca343e3eebb9648441"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
dependencies = [
"memchr",
]
build: bump clap from 3.1.18 to 3.2.4 Bumps [clap](https://github.com/clap-rs/clap) from 3.1.18 to 3.2.4. - [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.18...v3.2.4) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-06-14 23:15:28 +00:00
[[package]]
name = "once_cell"
build: Bump once_cell from 1.18.0 to 1.19.0 Bumps [once_cell](https://github.com/matklad/once_cell) from 1.18.0 to 1.19.0. - [Changelog](https://github.com/matklad/once_cell/blob/master/CHANGELOG.md) - [Commits](https://github.com/matklad/once_cell/compare/v1.18.0...v1.19.0) --- updated-dependencies: - dependency-name: once_cell dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-21 23:35:50 +00:00
version = "1.19.0"
build: bump clap from 3.1.18 to 3.2.4 Bumps [clap](https://github.com/clap-rs/clap) from 3.1.18 to 3.2.4. - [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.18...v3.2.4) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-06-14 23:15:28 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump once_cell from 1.18.0 to 1.19.0 Bumps [once_cell](https://github.com/matklad/once_cell) from 1.18.0 to 1.19.0. - [Changelog](https://github.com/matklad/once_cell/blob/master/CHANGELOG.md) - [Commits](https://github.com/matklad/once_cell/compare/v1.18.0...v1.19.0) --- updated-dependencies: - dependency-name: once_cell dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-21 23:35:50 +00:00
checksum = "3fdb12b2476b595f9358c5161aa467c2438859caa136dec86c26fdd2efe17b92"
build: bump clap from 3.1.18 to 3.2.4 Bumps [clap](https://github.com/clap-rs/clap) from 3.1.18 to 3.2.4. - [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.18...v3.2.4) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-06-14 23:15:28 +00:00
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
[[package]]
name = "open-enum"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.4.1"
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "ba485b94b3e73fa752d98cfcab74647a4a537269682cc1ee5256aa020432506d"
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
dependencies = [
"open-enum-derive",
]
[[package]]
name = "open-enum-derive"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.4.1"
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "fed1c261430059cab8b2b51eec42a3c15750439ec6c013cd8fe41d4a450de776"
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
dependencies = [
"proc-macro2",
"quote",
"syn 1.0.109",
]
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"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "300.2.3+3.2.1"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "5cff92b6f71555b61bb9315f7c64da3ca43d87531622120fea0195fc761b4843"
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
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.9.102"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "c597637d56fbc83893a35eb0dd04b2b8e7a50c91e64e9493e398b5df4fb45fa2"
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",
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
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "option-ext"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "04744f49eae99ab78e0d5c0b603ab218f515ea8cfe5a456d7629ad883a3b6e7d"
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"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "ordered-stream"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9aa2b01e1d916879f73a53d01d1d6cee68adbb31d6d9177a8cfce093cced1d50"
dependencies = [
"futures-core",
"pin-project-lite",
]
[[package]]
name = "parking"
build: Bump parking from 2.1.1 to 2.2.0 Bumps [parking](https://github.com/smol-rs/parking) from 2.1.1 to 2.2.0. - [Release notes](https://github.com/smol-rs/parking/releases) - [Changelog](https://github.com/smol-rs/parking/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/parking/compare/v2.1.1...v2.2.0) --- updated-dependencies: - dependency-name: parking dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-03 23:32:35 +00:00
version = "2.2.0"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump parking from 2.1.1 to 2.2.0 Bumps [parking](https://github.com/smol-rs/parking) from 2.1.1 to 2.2.0. - [Release notes](https://github.com/smol-rs/parking/releases) - [Changelog](https://github.com/smol-rs/parking/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/parking/compare/v2.1.1...v2.2.0) --- updated-dependencies: - dependency-name: parking dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-03 23:32:35 +00:00
checksum = "bb813b8af86854136c6922af0598d719255ecb2179515e6e7730d468f05c9cae"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +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 = "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",
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
"parking_lot_core 0.8.6",
]
[[package]]
name = "parking_lot"
version = "0.12.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3742b2c103b9f06bc9fff0a37ff4912935851bee6d36f3c02bcc755bcfec228f"
dependencies = [
"lock_api",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"parking_lot_core 0.9.9",
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: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
version = "0.8.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: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
checksum = "60a2cfe6f0ad2bfc16aefa463b497d5c7a5ecd44a23efa72aa342d90177356dc"
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",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"redox_syscall 0.2.16",
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
]
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
[[package]]
name = "parking_lot_core"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.9.9"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "4c42a9226546d68acdd9c0a280d17ce19bfe27a46bf68784e4066115788d008e"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
dependencies = [
"cfg-if",
"libc",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"redox_syscall 0.4.1",
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
"smallvec",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"windows-targets 0.48.5",
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +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"
build: Bump paste from 1.0.12 to 1.0.14 Bumps [paste](https://github.com/dtolnay/paste) from 1.0.12 to 1.0.14. - [Release notes](https://github.com/dtolnay/paste/releases) - [Commits](https://github.com/dtolnay/paste/compare/1.0.12...1.0.14) --- updated-dependencies: - dependency-name: paste dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-10-26 23:47:35 +00:00
version = "1.0.14"
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 paste from 1.0.12 to 1.0.14 Bumps [paste](https://github.com/dtolnay/paste) from 1.0.12 to 1.0.14. - [Release notes](https://github.com/dtolnay/paste/releases) - [Commits](https://github.com/dtolnay/paste/compare/1.0.12...1.0.14) --- updated-dependencies: - dependency-name: paste dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-10-26 23:47:35 +00:00
checksum = "de3145af08024dea9fa9914f381a17b8fc6034dfb00f3a84013f7ff43f29ed4c"
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
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",
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",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +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: switch to clap Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-09-21 15:55:41 +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",
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",
]
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
[[package]]
name = "pin-project"
build: Bump pin-project from 1.1.4 to 1.1.5 Bumps [pin-project](https://github.com/taiki-e/pin-project) from 1.1.4 to 1.1.5. - [Release notes](https://github.com/taiki-e/pin-project/releases) - [Changelog](https://github.com/taiki-e/pin-project/blob/main/CHANGELOG.md) - [Commits](https://github.com/taiki-e/pin-project/compare/v1.1.4...v1.1.5) --- updated-dependencies: - dependency-name: pin-project dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-18 23:09:21 +00:00
version = "1.1.5"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump pin-project from 1.1.4 to 1.1.5 Bumps [pin-project](https://github.com/taiki-e/pin-project) from 1.1.4 to 1.1.5. - [Release notes](https://github.com/taiki-e/pin-project/releases) - [Changelog](https://github.com/taiki-e/pin-project/blob/main/CHANGELOG.md) - [Commits](https://github.com/taiki-e/pin-project/compare/v1.1.4...v1.1.5) --- updated-dependencies: - dependency-name: pin-project dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-18 23:09:21 +00:00
checksum = "b6bf43b791c5b9e34c3d182969b4abb522f9343702850a2e57f460d00d09b4b3"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
dependencies = [
"pin-project-internal",
]
[[package]]
name = "pin-project-internal"
build: Bump pin-project from 1.1.4 to 1.1.5 Bumps [pin-project](https://github.com/taiki-e/pin-project) from 1.1.4 to 1.1.5. - [Release notes](https://github.com/taiki-e/pin-project/releases) - [Changelog](https://github.com/taiki-e/pin-project/blob/main/CHANGELOG.md) - [Commits](https://github.com/taiki-e/pin-project/compare/v1.1.4...v1.1.5) --- updated-dependencies: - dependency-name: pin-project dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-18 23:09:21 +00:00
version = "1.1.5"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump pin-project from 1.1.4 to 1.1.5 Bumps [pin-project](https://github.com/taiki-e/pin-project) from 1.1.4 to 1.1.5. - [Release notes](https://github.com/taiki-e/pin-project/releases) - [Changelog](https://github.com/taiki-e/pin-project/blob/main/CHANGELOG.md) - [Commits](https://github.com/taiki-e/pin-project/compare/v1.1.4...v1.1.5) --- updated-dependencies: - dependency-name: pin-project dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-18 23:09:21 +00:00
checksum = "2f38a4412a78282e09a2cf38d195ea5420d15ba0602cb375210efbc877243965"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
dependencies = [
"proc-macro2",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "pin-project-lite"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.2.14"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "bda66fc9667c18cb2758a2ac84d1167245054bcf85d5d1aaa6923f45801bdd02"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "pin-utils"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
build: Bump blocking from 1.3.1 to 1.5.1 Bumps [blocking](https://github.com/smol-rs/blocking) from 1.3.1 to 1.5.1. - [Release notes](https://github.com/smol-rs/blocking/releases) - [Changelog](https://github.com/smol-rs/blocking/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/blocking/compare/v1.3.1...v1.5.1) --- updated-dependencies: - dependency-name: blocking dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-20 23:43:13 +00:00
[[package]]
name = "piper"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "668d31b1c4eba19242f2088b2bf3316b82ca31082a8335764db4e083db7485d4"
dependencies = [
"atomic-waker",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"fastrand 2.0.2",
build: Bump blocking from 1.3.1 to 1.5.1 Bumps [blocking](https://github.com/smol-rs/blocking) from 1.3.1 to 1.5.1. - [Release notes](https://github.com/smol-rs/blocking/releases) - [Changelog](https://github.com/smol-rs/blocking/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/blocking/compare/v1.3.1...v1.5.1) --- updated-dependencies: - dependency-name: blocking dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-20 23:43:13 +00:00
"futures-io",
]
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.27 to 0.3.30 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.27 to 0.3.30. - [Changelog](https://github.com/rust-lang/pkg-config-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/pkg-config-rs/compare/0.3.27...0.3.30) --- updated-dependencies: - dependency-name: pkg-config dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-22 12:59:27 +00:00
version = "0.3.30"
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.27 to 0.3.30 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.27 to 0.3.30. - [Changelog](https://github.com/rust-lang/pkg-config-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/pkg-config-rs/compare/0.3.27...0.3.30) --- updated-dependencies: - dependency-name: pkg-config dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-22 12:59:27 +00:00
checksum = "d231b230927b5e4ad203db57bbcbee2802f6bce620b1e4a9024a07d94e2907ec"
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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
version = "0.34.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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
checksum = "130c5b738eeda2dc5796fe2671e49027e6935e817ab51b930a36ec9e6a206a64"
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 and pnet_datalink from 0.31.0 to 0.33.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.31.0 to 0.33.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.31.0...v0.33.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: Bo Chen <chen.bo@intel.com> Signed-off-by: dependabot[bot] <support@github.com>
2023-02-03 23:02:15 +00:00
"ipnetwork",
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",
"pnet_datalink",
"pnet_packet",
build: Bump pnet and pnet_datalink from 0.31.0 to 0.33.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.31.0 to 0.33.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.31.0...v0.33.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: Bo Chen <chen.bo@intel.com> Signed-off-by: dependabot[bot] <support@github.com>
2023-02-03 23:02:15 +00:00
"pnet_sys",
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_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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
version = "0.34.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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
checksum = "fe4cf6fb3ab38b68d01ab2aea03ed3d1132b4868fa4e06285f29f16da01c5f4c"
build: bump pnet from 0.29.0 to 0.30.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.29.0 to 0.30.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.29.0...v0.30.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-05-24 16:00:10 +00:00
dependencies = [
"no-std-net",
]
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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
version = "0.34.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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
checksum = "ad5854abf0067ebbd3967f7d45ebc8976ff577ff0c7bd101c4973ae3c70f98fe"
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.30.0 to 0.31.0 Bumps [pnet](https://github.com/libpnet/libpnet) from 0.30.0 to 0.31.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/compare/v0.30.0...v0.31.0) --- updated-dependencies: - dependency-name: pnet dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> Signed-off-by: dependabot[bot] <support@github.com>
2022-06-03 01:16:58 +00:00
"ipnetwork",
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_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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
version = "0.34.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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
checksum = "688b17499eee04a0408aca0aa5cba5fc86401d7216de8a63fdf7a4c227871804"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
version = "0.34.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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
checksum = "eea925b72f4bd37f8eab0f221bbe4c78b63498350c983ffa9dd4bcde7e030f56"
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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
version = "0.34.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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
checksum = "a9a005825396b7fe7a38a8e288dbc342d5034dac80c15212436424fef8ea90ba"
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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
version = "0.34.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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
checksum = "417c0becd1b573f6d544f73671070b039051e5ad819cc64aa96377b536128d00"
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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
version = "0.34.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/pnet_datalink from 0.33.0 to 0.34.0 Bump these crates need to be bumped together to avoid build issues from shared structures. Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-08 23:25:38 +00:00
checksum = "2637e14d7de974ee2f74393afccbc8704f3e54e6eb31488715e72481d1662cc3"
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
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "polling"
version = "2.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4b2d323e8ca7996b3e23126511a523f7e62924d93ecd5ae73b333815b0eb3dce"
dependencies = [
"autocfg",
build: Bump bitflags from 1.3.2 to 2.3.2 Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.2 to 2.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.2...2.3.2) --- updated-dependencies: - dependency-name: bitflags dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2023-06-16 00:54:27 +00:00
"bitflags 1.3.2",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"cfg-if",
"concurrent-queue",
"libc",
"log",
"pin-project-lite",
"windows-sys 0.48.0",
]
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
[[package]]
name = "polling"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "3.6.0"
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "e0c976a60b2d7e99d6f229e414670a9b85d13ac305cc6d1e9c134de58c5aaaf6"
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
dependencies = [
"cfg-if",
"concurrent-queue",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"hermit-abi",
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
"pin-project-lite",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"rustix 0.38.32",
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
"tracing",
"windows-sys 0.52.0",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "ppv-lite86"
version = "0.2.17"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5b40af805b3121feab8a3c29f04d8ad262fa8e0561883e7653e024ae4479e6de"
[[package]]
name = "proc-macro-crate"
version = "1.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7f4c021e1093a56626774e81216a4ce732a735e5bad4868a03f3ed65ca0c3919"
dependencies = [
"once_cell",
"toml_edit",
]
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.0.79"
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 update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "e835ff2298f5721608eb1a980ecaee1aef2c132bf95ecc026a11b7bf3c01c02e"
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 syn from 1.0.94 to 1.0.95 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.94 to 1.0.95. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.94...1.0.95) --- updated-dependencies: - dependency-name: syn dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-05-16 23:12:33 +00:00
"unicode-ident",
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 serde from 1.0.193 to 1.0.196 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.193 to 1.0.196. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.193...v1.0.196) --- updated-dependencies: - dependency-name: serde dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-09 23:04:35 +00:00
version = "1.0.35"
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 serde from 1.0.193 to 1.0.196 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.193 to 1.0.196. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.193...v1.0.196) --- updated-dependencies: - dependency-name: serde dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-09 23:04:35 +00:00
checksum = "291ec9ab5efd934aaf503a6466c5d5251535d108ee747472c3977cc5acc868ef"
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
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "rand"
version = "0.8.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "34af8d1a0e25924bc5b7c43c079c942339d8f0a8b57c39049bef581b46327404"
dependencies = [
"libc",
"rand_chacha",
"rand_core",
]
[[package]]
name = "rand_chacha"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e6c10a63a0fa32252be49d21e7709d4d4baf8d231c2dbce1eaa8141b9b127d88"
dependencies = [
"ppv-lite86",
"rand_core",
]
[[package]]
name = "rand_core"
version = "0.6.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ec0be4795e2f6a28069bec0b5ff3e2ac9bafc99e6a9a7dc3547996c5c816922c"
dependencies = [
"getrandom",
]
hypervisor: Add API to complete isolated import This is the function that needs to be called by the VMM to inform the MSHV that isolation is complete and inform PSP about this completion. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-13 19:58:56 +00:00
[[package]]
name = "range_map_vec"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8edc89eaa583cf6bc4c6ef16a219f0a60d342ca3bf0eae793560038ac8af1795"
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 = [
rate_limiter: add RateLimiterGroup Add a 'rate_limiter/group' module that defines the RateLimiterGroup and a RateLimiterGroupHandle types. The RateLimiterGroupHandle can be used in place of a RateLimiter to limit the aggregate bandwidth and/or ops of multiple virtio-blk or virtio-net queues. Each RateLimiterGroup has an associated worker thread that broadcasts an event to each RateLimiterGroupHandle when a RateLimiter is unblocked. Signed-off-by: Thomas Barrett <tbarrett@crusoeenergy.com>
2023-12-13 21:13:10 +00:00
"epoll",
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
"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",
rate_limiter: add RateLimiterGroup Add a 'rate_limiter/group' module that defines the RateLimiterGroup and a RateLimiterGroupHandle types. The RateLimiterGroupHandle can be used in place of a RateLimiter to limit the aggregate bandwidth and/or ops of multiple virtio-blk or virtio-net queues. Each RateLimiterGroup has an associated worker thread that broadcasts an event to each RateLimiterGroupHandle when a RateLimiter is unblocked. Signed-off-by: Thomas Barrett <tbarrett@crusoeenergy.com>
2023-12-13 21:13:10 +00:00
"thiserror",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-util",
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
]
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.15 to 0.2.16 Bumps redox_syscall from 0.2.15 to 0.2.16. --- updated-dependencies: - dependency-name: redox_syscall dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-27 23:54:15 +00:00
version = "0.2.16"
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.15 to 0.2.16 Bumps redox_syscall from 0.2.15 to 0.2.16. --- updated-dependencies: - dependency-name: redox_syscall dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-27 23:54:15 +00:00
checksum = "fb5a58c1855b4b6819d59012155603f0b22ad30cad752600aadfcb695265519a"
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 bitflags from 1.3.2 to 2.3.2 Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.2 to 2.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.2...2.3.2) --- updated-dependencies: - dependency-name: bitflags dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2023-06-16 00:54:27 +00:00
"bitflags 1.3.2",
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
]
build: Bump redox_users from 0.4.3 to 0.4.4 Bumps redox_users from 0.4.3 to 0.4.4. --- updated-dependencies: - dependency-name: redox_users dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-13 23:56:41 +00:00
[[package]]
name = "redox_syscall"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4722d768eff46b75989dd134e5c353f0d6296e5aaa3132e776cbdb56be7731aa"
dependencies = [
"bitflags 1.3.2",
]
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.4.5"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "bd283d9651eeda4b2a83a43c1c91b266c40fd76ecd39a50a8c630ae69dc72891"
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 redox_users from 0.4.3 to 0.4.4 Bumps redox_users from 0.4.3 to 0.4.4. --- updated-dependencies: - dependency-name: redox_users dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-13 23:56:41 +00:00
"libredox",
build: bump redox_users from 0.4.0 to 0.4.2 Bumps redox_users from 0.4.0 to 0.4.2. --- updated-dependencies: - dependency-name: redox_users dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-03-17 23:11:31 +00:00
"thiserror",
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.10.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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "c117dbdfde9c8308975b6a18d71f3f385c89461f7b3fb054288ecf2a2058ba4c"
build: Bump regex from 1.8.3 to 1.9.1 Bumps [regex](https://github.com/rust-lang/regex) from 1.8.3 to 1.9.1. - [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.8.3...1.9.1) --- updated-dependencies: - dependency-name: regex dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-07-12 23:39:06 +00:00
dependencies = [
"aho-corasick",
"memchr",
"regex-automata",
"regex-syntax",
]
[[package]]
name = "regex-automata"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.4.6"
build: Bump regex from 1.8.3 to 1.9.1 Bumps [regex](https://github.com/rust-lang/regex) from 1.8.3 to 1.9.1. - [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.8.3...1.9.1) --- updated-dependencies: - dependency-name: regex dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-07-12 23:39:06 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "86b83b8b9847f9bf95ef68afb0b8e6cdb80f498442f5179a29fad448fcc1eaea"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.8.3"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "adad44e29e4c806119491a7f06f03de4d1af22c3a680dd47f1e6e179439d1f56"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.2.13"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "ad9f2390298a947ee0aa6073d440e221c0726188cfbcdf9604addb6ee393eb4a"
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",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
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: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
[[package]]
name = "rustc-demangle"
build: Bump rustc-demangle from 0.1.21 to 0.1.23 Bumps [rustc-demangle](https://github.com/alexcrichton/rustc-demangle) from 0.1.21 to 0.1.23. - [Release notes](https://github.com/alexcrichton/rustc-demangle/releases) - [Commits](https://github.com/alexcrichton/rustc-demangle/compare/0.1.21...0.1.23) --- updated-dependencies: - dependency-name: rustc-demangle dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-25 23:57:47 +00:00
version = "0.1.23"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump rustc-demangle from 0.1.21 to 0.1.23 Bumps [rustc-demangle](https://github.com/alexcrichton/rustc-demangle) from 0.1.21 to 0.1.23. - [Release notes](https://github.com/alexcrichton/rustc-demangle/releases) - [Commits](https://github.com/alexcrichton/rustc-demangle/compare/0.1.21...0.1.23) --- updated-dependencies: - dependency-name: rustc-demangle dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-25 23:57:47 +00:00
checksum = "d626bb9dae77e28219937af045c257c28bfd3f69333c512553507f5f9798cb76"
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
[[package]]
name = "rustc-hash"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
build: Bulk update dependencies Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-28 13:08:13 +00:00
[[package]]
name = "rustix"
build: Bump rustix from 0.37.25 to 0.37.27 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.37.25 to 0.37.27. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.37.25...v0.37.27) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-20 23:18:57 +00:00
version = "0.37.27"
build: Bump textwrap from 0.15.0 to 0.15.1 Bumps [textwrap](https://github.com/mgeisler/textwrap) from 0.15.0 to 0.15.1. - [Release notes](https://github.com/mgeisler/textwrap/releases) - [Changelog](https://github.com/mgeisler/textwrap/blob/master/CHANGELOG.md) - [Commits](https://github.com/mgeisler/textwrap/compare/0.15.0...0.15.1) --- updated-dependencies: - dependency-name: textwrap dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-16 00:45:44 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump rustix from 0.37.25 to 0.37.27 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.37.25 to 0.37.27. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.37.25...v0.37.27) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-20 23:18:57 +00:00
checksum = "fea8ca367a3a01fe35e6943c400addf443c0f57670e6ec51196f71a4b8762dd2"
build: Bump textwrap from 0.15.0 to 0.15.1 Bumps [textwrap](https://github.com/mgeisler/textwrap) from 0.15.0 to 0.15.1. - [Release notes](https://github.com/mgeisler/textwrap/releases) - [Changelog](https://github.com/mgeisler/textwrap/blob/master/CHANGELOG.md) - [Commits](https://github.com/mgeisler/textwrap/compare/0.15.0...0.15.1) --- updated-dependencies: - dependency-name: textwrap dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-16 00:45:44 +00:00
dependencies = [
build: Bump bitflags from 1.3.2 to 2.3.2 Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.2 to 2.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.2...2.3.2) --- updated-dependencies: - dependency-name: bitflags dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2023-06-16 00:54:27 +00:00
"bitflags 1.3.2",
build: Bump textwrap from 0.15.0 to 0.15.1 Bumps [textwrap](https://github.com/mgeisler/textwrap) from 0.15.0 to 0.15.1. - [Release notes](https://github.com/mgeisler/textwrap/releases) - [Changelog](https://github.com/mgeisler/textwrap/blob/master/CHANGELOG.md) - [Commits](https://github.com/mgeisler/textwrap/compare/0.15.0...0.15.1) --- updated-dependencies: - dependency-name: textwrap dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-16 00:45:44 +00:00
"errno",
build: Bump terminal_size from 0.2.2 to 0.2.3 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.2 to 0.2.3. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.2...v0.2.3) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-30 23:25:54 +00:00
"io-lifetimes",
build: Bump textwrap from 0.15.0 to 0.15.1 Bumps [textwrap](https://github.com/mgeisler/textwrap) from 0.15.0 to 0.15.1. - [Release notes](https://github.com/mgeisler/textwrap/releases) - [Changelog](https://github.com/mgeisler/textwrap/blob/master/CHANGELOG.md) - [Commits](https://github.com/mgeisler/textwrap/compare/0.15.0...0.15.1) --- updated-dependencies: - dependency-name: textwrap dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-16 00:45:44 +00:00
"libc",
build: Bump tempfile from 3.5.0 to 3.7.1 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.5.0 to 3.7.1. - [Changelog](https://github.com/Stebalien/tempfile/blob/master/CHANGELOG.md) - [Commits](https://github.com/Stebalien/tempfile/compare/v3.5.0...v3.7.1) --- updated-dependencies: - dependency-name: tempfile dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-17 23:13:33 +00:00
"linux-raw-sys 0.3.8",
"windows-sys 0.48.0",
]
[[package]]
name = "rustix"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.38.32"
build: Bump tempfile from 3.5.0 to 3.7.1 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.5.0 to 3.7.1. - [Changelog](https://github.com/Stebalien/tempfile/blob/master/CHANGELOG.md) - [Commits](https://github.com/Stebalien/tempfile/compare/v3.5.0...v3.7.1) --- updated-dependencies: - dependency-name: tempfile dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-17 23:13:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "65e04861e65f21776e67888bfbea442b3642beaa0138fdb1dd7a84a52dffdb89"
build: Bump tempfile from 3.5.0 to 3.7.1 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.5.0 to 3.7.1. - [Changelog](https://github.com/Stebalien/tempfile/blob/master/CHANGELOG.md) - [Commits](https://github.com/Stebalien/tempfile/compare/v3.5.0...v3.7.1) --- updated-dependencies: - dependency-name: tempfile dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-17 23:13:33 +00:00
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"bitflags 2.5.0",
build: Bump tempfile from 3.5.0 to 3.7.1 Bumps [tempfile](https://github.com/Stebalien/tempfile) from 3.5.0 to 3.7.1. - [Changelog](https://github.com/Stebalien/tempfile/blob/master/CHANGELOG.md) - [Commits](https://github.com/Stebalien/tempfile/compare/v3.5.0...v3.7.1) --- updated-dependencies: - dependency-name: tempfile dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-17 23:13:33 +00:00
"errno",
"libc",
build: Bump rustix from 0.38.8 to 0.38.25 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-25 23:11:18 +00:00
"linux-raw-sys 0.4.13",
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
"windows-sys 0.52.0",
build: Bump textwrap from 0.15.0 to 0.15.1 Bumps [textwrap](https://github.com/mgeisler/textwrap) from 0.15.0 to 0.15.1. - [Release notes](https://github.com/mgeisler/textwrap/releases) - [Changelog](https://github.com/mgeisler/textwrap/blob/master/CHANGELOG.md) - [Commits](https://github.com/mgeisler/textwrap/compare/0.15.0...0.15.1) --- updated-dependencies: - dependency-name: textwrap dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-09-16 00:45:44 +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 = "ryu"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.0.17"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "e86697c916019a8588c99b5fac3cead74ec0b4b819707a682fd4d23fa0ce1ba1"
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: Bump scopeguard from 1.1.0 to 1.2.0 Bumps [scopeguard](https://github.com/bluss/scopeguard) from 1.1.0 to 1.2.0. - [Commits](https://github.com/bluss/scopeguard/compare/v1.1.0...v1.2.0) --- updated-dependencies: - dependency-name: scopeguard dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-07 23:27:41 +00:00
version = "1.2.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 scopeguard from 1.1.0 to 1.2.0 Bumps [scopeguard](https://github.com/bluss/scopeguard) from 1.1.0 to 1.2.0. - [Commits](https://github.com/bluss/scopeguard/compare/v1.1.0...v1.2.0) --- updated-dependencies: - dependency-name: scopeguard dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-07 23:27:41 +00:00
checksum = "94143f37725109f92c262ed2cf5e59bce7498c01bcc1502d7b9afe439a4e9f49"
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: Bump seccompiler from 0.3.0 to 0.4.0 Bumps [seccompiler](https://github.com/rust-vmm/seccompiler) from 0.3.0 to 0.4.0. - [Release notes](https://github.com/rust-vmm/seccompiler/releases) - [Changelog](https://github.com/rust-vmm/seccompiler/blob/main/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/seccompiler/compare/seccompiler-v0.3.0...v0.4.0) --- updated-dependencies: - dependency-name: seccompiler dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-10-30 18:31:10 +00:00
version = "0.4.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump seccompiler from 0.3.0 to 0.4.0 Bumps [seccompiler](https://github.com/rust-vmm/seccompiler) from 0.3.0 to 0.4.0. - [Release notes](https://github.com/rust-vmm/seccompiler/releases) - [Changelog](https://github.com/rust-vmm/seccompiler/blob/main/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/seccompiler/compare/seccompiler-v0.3.0...v0.4.0) --- updated-dependencies: - dependency-name: seccompiler dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-10-30 18:31:10 +00:00
checksum = "345a3e4dddf721a478089d4697b83c6c0a8f5bf16086f6c13397e4534eb6e2e5"
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
]
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.0.197"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "3fb1c873e1b9b056a4dc4c0c198b24c3ffa059243875552b2bd0933b1aee4ce2"
cargo: Clean up serde dependencies There is no need to include serde_derive separately, as it can be specified as serde feature instead. Signed-off-by: Maksym Pavlenko <pavlenko.maksym@gmail.com>
2022-05-17 21:04:38 +00:00
dependencies = [
"serde_derive",
]
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.0.197"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "7eb0b34b42edc17f6b7cac84a52a1c5f0e1bb2227e997ca9011ea3dd34e8610b"
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",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.0.115"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "12dc5c46daa8e9fdf4f5e71b6cf9a53f2487da0e86e55808e2d35539666497dd"
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
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "serde_repr"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.1.18"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "0b2e6b945e9d3df726b65d6ee24060aff8e3533d431f677a9695db04eff9dfdb"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"proc-macro2",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
]
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
[[package]]
name = "serde_with"
build: Bump serde_with from 3.6.1 to 3.7.0 Bumps [serde_with](https://github.com/jonasbb/serde_with) from 3.6.1 to 3.7.0. - [Release notes](https://github.com/jonasbb/serde_with/releases) - [Commits](https://github.com/jonasbb/serde_with/compare/v3.6.1...v3.7.0) --- updated-dependencies: - dependency-name: serde_with dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-22 23:25:11 +00:00
version = "3.7.0"
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump serde_with from 3.6.1 to 3.7.0 Bumps [serde_with](https://github.com/jonasbb/serde_with) from 3.6.1 to 3.7.0. - [Release notes](https://github.com/jonasbb/serde_with/releases) - [Commits](https://github.com/jonasbb/serde_with/compare/v3.6.1...v3.7.0) --- updated-dependencies: - dependency-name: serde_with dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-22 23:25:11 +00:00
checksum = "ee80b0e361bbf88fd2f6e242ccd19cfda072cb0faa6ae694ecee08199938569a"
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
dependencies = [
"serde",
build: Bump serde_with from 3.4.0 to 3.6.1 Bumps [serde_with](https://github.com/jonasbb/serde_with) from 3.4.0 to 3.6.1. - [Release notes](https://github.com/jonasbb/serde_with/releases) - [Commits](https://github.com/jonasbb/serde_with/compare/v3.4.0...v3.6.1) --- updated-dependencies: - dependency-name: serde_with dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-05 23:34:57 +00:00
"serde_derive",
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
"serde_with_macros",
]
[[package]]
name = "serde_with_macros"
build: Bump serde_with from 3.6.1 to 3.7.0 Bumps [serde_with](https://github.com/jonasbb/serde_with) from 3.6.1 to 3.7.0. - [Release notes](https://github.com/jonasbb/serde_with/releases) - [Commits](https://github.com/jonasbb/serde_with/compare/v3.6.1...v3.7.0) --- updated-dependencies: - dependency-name: serde_with dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-22 23:25:11 +00:00
version = "3.7.0"
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump serde_with from 3.6.1 to 3.7.0 Bumps [serde_with](https://github.com/jonasbb/serde_with) from 3.6.1 to 3.7.0. - [Release notes](https://github.com/jonasbb/serde_with/releases) - [Commits](https://github.com/jonasbb/serde_with/compare/v3.6.1...v3.7.0) --- updated-dependencies: - dependency-name: serde_with dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-22 23:25:11 +00:00
checksum = "6561dc161a9224638a31d876ccdfefbc1df91d3f3a8342eddb35f055d48c7655"
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
dependencies = [
"darling",
"proc-macro2",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
hypervisor: use serde_with with LapicState Drop the hand-rolled serializer and deserializer. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-07-28 11:18:08 +00:00
]
vmm: Move SerialBuffer to its own crate We want to be able to reuse the SerialBuffer from the virtio-devices crate, particularly from the virtio-console implementation. That's why we move the SerialBuffer definition to its own crate so that it can be accessed from both vmm and virtio-devices crates, without creating any cyclic dependency. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-08-25 08:26:59 +00:00
[[package]]
name = "serial_buffer"
version = "0.1.0"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "sha1"
build: Bump sha1 from 0.10.5 to 0.10.6 Bumps [sha1](https://github.com/RustCrypto/hashes) from 0.10.5 to 0.10.6. - [Commits](https://github.com/RustCrypto/hashes/compare/sha1-v0.10.5...sha1-v0.10.6) --- updated-dependencies: - dependency-name: sha1 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-10-05 23:26:42 +00:00
version = "0.10.6"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump sha1 from 0.10.5 to 0.10.6 Bumps [sha1](https://github.com/RustCrypto/hashes) from 0.10.5 to 0.10.6. - [Commits](https://github.com/RustCrypto/hashes/compare/sha1-v0.10.5...sha1-v0.10.6) --- updated-dependencies: - dependency-name: sha1 dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-10-05 23:26:42 +00:00
checksum = "e3bf829a2d51ab4a5ddf1352d8470c140cadc8301b2ae1789db023f01cedd6ba"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"cfg-if",
"cpufeatures",
"digest",
]
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.15 to 0.3.17 Bumps [signal-hook](https://github.com/vorner/signal-hook) from 0.3.15 to 0.3.17. - [Changelog](https://github.com/vorner/signal-hook/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/signal-hook/compare/v0.3.15...v0.3.17) --- updated-dependencies: - dependency-name: signal-hook dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-01 23:45:19 +00:00
version = "0.3.17"
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.15 to 0.3.17 Bumps [signal-hook](https://github.com/vorner/signal-hook) from 0.3.15 to 0.3.17. - [Changelog](https://github.com/vorner/signal-hook/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/signal-hook/compare/v0.3.15...v0.3.17) --- updated-dependencies: - dependency-name: signal-hook dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-01 23:45:19 +00:00
checksum = "8621587d4798caf8eb44879d42e56b9a93ea5dcd315a6487c357130095b62801"
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-registry from 1.4.0 to 1.4.1 Bumps [signal-hook-registry](https://github.com/vorner/signal-hook) from 1.4.0 to 1.4.1. - [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/registry-v1.4.0...registry-v1.4.1) --- updated-dependencies: - dependency-name: signal-hook-registry dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-20 23:59:27 +00:00
version = "1.4.1"
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-registry from 1.4.0 to 1.4.1 Bumps [signal-hook-registry](https://github.com/vorner/signal-hook) from 1.4.0 to 1.4.1. - [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/registry-v1.4.0...registry-v1.4.1) --- updated-dependencies: - dependency-name: signal-hook-registry dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-20 23:59:27 +00:00
checksum = "d8229b473baa5980ac72ef434c4415e70c4b5e71b423043adb4ba059f89c99a1"
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
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "slab"
build: Bump slab from 0.4.8 to 0.4.9 Bumps [slab](https://github.com/tokio-rs/slab) from 0.4.8 to 0.4.9. - [Release notes](https://github.com/tokio-rs/slab/releases) - [Changelog](https://github.com/tokio-rs/slab/blob/master/CHANGELOG.md) - [Commits](https://github.com/tokio-rs/slab/compare/v0.4.8...v0.4.9) --- updated-dependencies: - dependency-name: slab dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-07 10:44:09 +00:00
version = "0.4.9"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump slab from 0.4.8 to 0.4.9 Bumps [slab](https://github.com/tokio-rs/slab) from 0.4.8 to 0.4.9. - [Release notes](https://github.com/tokio-rs/slab/releases) - [Changelog](https://github.com/tokio-rs/slab/blob/master/CHANGELOG.md) - [Commits](https://github.com/tokio-rs/slab/compare/v0.4.8...v0.4.9) --- updated-dependencies: - dependency-name: slab dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-07 10:44:09 +00:00
checksum = "8f92a496fb766b417c996b9c5e57daf2f7ad3b0bebe1ccfca4856390e3d3bb67"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"autocfg",
]
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.13.1 to 1.13.2 Bumps [smallvec](https://github.com/servo/rust-smallvec) from 1.13.1 to 1.13.2. - [Release notes](https://github.com/servo/rust-smallvec/releases) - [Commits](https://github.com/servo/rust-smallvec/compare/v1.13.1...v1.13.2) --- updated-dependencies: - dependency-name: smallvec dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-26 23:48:52 +00:00
version = "1.13.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 smallvec from 1.13.1 to 1.13.2 Bumps [smallvec](https://github.com/servo/rust-smallvec) from 1.13.1 to 1.13.2. - [Release notes](https://github.com/servo/rust-smallvec/releases) - [Commits](https://github.com/servo/rust-smallvec/compare/v1.13.1...v1.13.2) --- updated-dependencies: - dependency-name: smallvec dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-26 23:48:52 +00:00
checksum = "3c5e1a9a646d36c3599cd173a41282daf47c44583ad367b8e6837255952e5c67"
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: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "socket2"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.4.10"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "9f7916fc008ca5542385b89a3d3ce689953c143e9304a9bf8beec1de48994c0d"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"libc",
"winapi",
]
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
[[package]]
name = "spin"
version = "0.9.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6980e8d7511241f8acf4aebddbb1ff938df5eebe98691418c4468d0b72a96a67"
dependencies = [
"lock_api",
]
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.3 to 0.9.4 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.3 to 0.9.4. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.3...0.9.4) --- updated-dependencies: - dependency-name: ssh2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-01-25 23:04:36 +00:00
version = "0.9.4"
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.3 to 0.9.4 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.9.3 to 0.9.4. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.9.3...0.9.4) --- updated-dependencies: - dependency-name: ssh2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-01-25 23:04:36 +00:00
checksum = "e7fe461910559f6d5604c3731d00d2aafc4a83d1665922e280f42f9a168d5455"
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 bitflags from 1.3.2 to 2.3.2 Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.2 to 2.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.2...2.3.2) --- updated-dependencies: - dependency-name: bitflags dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2023-06-16 00:54:27 +00:00
"bitflags 1.3.2",
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",
build: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
"parking_lot 0.11.2",
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
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "static_assertions"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a2eb9349b6444b326872e140eb1cf5e7c522154d69e7a0ffb0fb81c06b37543f"
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: Bump clap from 4.4.7 to 4.5.1 Bumps [clap](https://github.com/clap-rs/clap) from 4.4.7 to 4.5.1. - [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/clap_complete-v4.4.7...clap_complete-v4.5.1) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-29 20:08:49 +00:00
[[package]]
name = "strsim"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.11.1"
build: Bump clap from 4.4.7 to 4.5.1 Bumps [clap](https://github.com/clap-rs/clap) from 4.4.7 to 4.5.1. - [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/clap_complete-v4.4.7...clap_complete-v4.5.1) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-29 20:08:49 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "7da8b5736845d9f2fcb837ea5d9e2628564b3b043a70948a3f0b778838c5fb4f"
build: Bump clap from 4.4.7 to 4.5.1 Bumps [clap](https://github.com/clap-rs/clap) from 4.4.7 to 4.5.1. - [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/clap_complete-v4.4.7...clap_complete-v4.5.1) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-29 20:08:49 +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"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
version = "1.0.109"
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"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
checksum = "72b64191b275b66ffe2469e8af2c1cfe3bafa67b529ead792a6d0160888b4237"
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 syn from 1.0.94 to 1.0.95 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.94 to 1.0.95. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.94...1.0.95) --- updated-dependencies: - dependency-name: syn dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-05-16 23:12:33 +00:00
"unicode-ident",
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
]
build: Bump thiserror from 1.0.39 to 1.0.40 Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.39 to 1.0.40. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.39...1.0.40) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-05-23 23:58:01 +00:00
[[package]]
name = "syn"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "2.0.58"
build: Bump thiserror from 1.0.39 to 1.0.40 Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.39 to 1.0.40. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.39...1.0.40) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-05-23 23:58:01 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "44cfb93f38070beee36b3fef7d4f5a16f27751d94b187b666a5cc5e9b0d30687"
build: Bump thiserror from 1.0.39 to 1.0.40 Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.39 to 1.0.40. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.39...1.0.40) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-05-23 23:58:01 +00:00
dependencies = [
"proc-macro2",
"quote",
"unicode-ident",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "tempfile"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "3.10.1"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "85b77fafb263dd9d05cbeac119526425676db3784113aa9295c88498cbf8bff1"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"cfg-if",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"fastrand 2.0.2",
"rustix 0.38.32",
"windows-sys 0.52.0",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.4.1"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "06794f8f6c5c898b3275aebefa6b8a1cb24cd2c6c79397ab15774837a0bc5755"
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
]
vhost_user_net: switch to clap Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-09-21 15:30:23 +00:00
[[package]]
name = "terminal_size"
build: Bump clap from 4.3.11 to 4.4.7 Bumps [clap](https://github.com/clap-rs/clap) from 4.3.11 to 4.4.7. - [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/v4.3.11...v4.4.7) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-08 16:24:34 +00:00
version = "0.3.0"
vhost_user_net: switch to clap Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-09-21 15:30:23 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump clap from 4.3.11 to 4.4.7 Bumps [clap](https://github.com/clap-rs/clap) from 4.3.11 to 4.4.7. - [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/v4.3.11...v4.4.7) --- updated-dependencies: - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-08 16:24:34 +00:00
checksum = "21bebf2b7c9e0a515f6e0f8c51dc0f8e4696391e6f1ff30379559f8365fb0df7"
vhost_user_net: switch to clap Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-09-21 15:30:23 +00:00
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"rustix 0.38.32",
vhost_user_net: switch to clap Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-09-21 15:30:23 +00:00
"windows-sys 0.48.0",
]
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",
"libc",
tests: switch from lazy_static to once_cell Once_cell does not require using macro and is slated to become part of Rust std at some point. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-06-20 14:05:17 +00:00
"once_cell",
performance-metrics: Move some helper functions to test_infra The helper functions for measuring and parsing the performance of virtio-net and virtio-block devices are moved to the `test_infra` crate so that they be reused for integration tests of rate limiter. Signed-off-by: Bo Chen <chen.bo@intel.com>
2022-08-24 18:44:30 +00:00
"serde",
"serde_json",
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
"ssh2",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-util",
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
"wait-timeout",
]
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.0.58"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "03468839009160513471e86a034bb2c5c0e4baae3b43f79ffc55c4a5427b3297"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.0.58"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "c61f3ba182994efc43764a46c018c347bc492c79f024e705f46567b418f6d4f7"
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",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
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: Add optional dhat heap profiling Add new "dhat-heap" build feature which enables dhat heap profiling. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2023-01-17 12:53:55 +00:00
[[package]]
name = "thousands"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3bf63baf9f5039dadc247375c29eb13706706cfde997d0330d05aa63a77d8820"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "toml_datetime"
build: Bump toml_datetime from 0.6.3 to 0.6.5 Bumps [toml_datetime](https://github.com/toml-rs/toml) from 0.6.3 to 0.6.5. - [Commits](https://github.com/toml-rs/toml/compare/toml_datetime-v0.6.3...toml_datetime-v0.6.5) --- updated-dependencies: - dependency-name: toml_datetime dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-27 23:26:30 +00:00
version = "0.6.5"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump toml_datetime from 0.6.3 to 0.6.5 Bumps [toml_datetime](https://github.com/toml-rs/toml) from 0.6.3 to 0.6.5. - [Commits](https://github.com/toml-rs/toml/compare/toml_datetime-v0.6.3...toml_datetime-v0.6.5) --- updated-dependencies: - dependency-name: toml_datetime dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-27 23:26:30 +00:00
checksum = "3550f4e9685620ac18a50ed434eb3aec30db8ba93b0287467bca5826ea25baf1"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "toml_edit"
build: Bump toml_edit from 0.19.8 to 0.19.15 Bumps [toml_edit](https://github.com/toml-rs/toml) from 0.19.8 to 0.19.15. - [Commits](https://github.com/toml-rs/toml/compare/v0.19.8...v0.19.15) --- updated-dependencies: - dependency-name: toml_edit dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-10-31 17:16:45 +00:00
version = "0.19.15"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump toml_edit from 0.19.8 to 0.19.15 Bumps [toml_edit](https://github.com/toml-rs/toml) from 0.19.8 to 0.19.15. - [Commits](https://github.com/toml-rs/toml/compare/v0.19.8...v0.19.15) --- updated-dependencies: - dependency-name: toml_edit dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-10-31 17:16:45 +00:00
checksum = "1b5bb770da30e5cbfde35a2d7b9b8a2c4b8ef89548a7a6aeab5c9a576e3e7421"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"indexmap",
"toml_datetime",
"winnow",
]
tpm: Add library module Add structures and related methods to process Ctrl requests and responses from swtpm to tpm library. Signed-off-by: Praveen K Paladugu <prapal@linux.microsoft.com> Co-authored-by: Sean Yoo <t-seanyoo@microsoft.com>
2022-09-08 06:02:26 +00:00
[[package]]
name = "tpm"
version = "0.1.0"
dependencies = [
"anyhow",
"byteorder",
tpm: Add socket module Add SocketDev struct. Methods in SocketDev will be used to read & write to Ctrl channel created by swtpm. Signed-off-by: Praveen K Paladugu <prapal@linux.microsoft.com> Co-authored-by: Sean Yoo <t-seanyoo@microsoft.com>
2022-09-09 03:31:56 +00:00
"libc",
tpm: Add library module Add structures and related methods to process Ctrl requests and responses from swtpm to tpm library. Signed-off-by: Praveen K Paladugu <prapal@linux.microsoft.com> Co-authored-by: Sean Yoo <t-seanyoo@microsoft.com>
2022-09-08 06:02:26 +00:00
"log",
tpm: Add recv timeout while running recvmsg If swtpm becomes unresponsive, guest gets blocked at "recvmsg" on tpm's data FD. This change adds a timeout to the data fd socket. If swtpm becomes unresponsive guest waits for "timeout" (secs) and continues to run after returning an I/O error to tpm commands. Signed-off-by: Praveen K Paladugu <prapal@linux.microsoft.com>
2023-01-31 17:45:02 +00:00
"net_gen",
tpm: Add library module Add structures and related methods to process Ctrl requests and responses from swtpm to tpm library. Signed-off-by: Praveen K Paladugu <prapal@linux.microsoft.com> Co-authored-by: Sean Yoo <t-seanyoo@microsoft.com>
2022-09-08 06:02:26 +00:00
"thiserror",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-util",
tpm: Add library module Add structures and related methods to process Ctrl requests and responses from swtpm to tpm library. Signed-off-by: Praveen K Paladugu <prapal@linux.microsoft.com> Co-authored-by: Sean Yoo <t-seanyoo@microsoft.com>
2022-09-08 06:02:26 +00:00
]
tracing: Tracing infrastructure Add a new feature "tracing" that enables tracing functionality via the "tracer" crate (sadly features and crates cannot share the same name.) Setup: tracer::start() The main functionality is a tracer::trace_scope()! macro that will add trace points for the duration of the scope. Tracing events are per thread. Finish: tracer::end() this will write the trace file (pretty printed JSON) to a file in the current directory. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-06-21 14:01:26 +00:00
[[package]]
name = "tracer"
version = "0.1.0"
dependencies = [
"libc",
"log",
"once_cell",
"serde",
"serde_json",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "tracing"
build: Bump tracing from 0.1.37 to 0.1.40 Bumps [tracing](https://github.com/tokio-rs/tracing) from 0.1.37 to 0.1.40. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-0.1.37...tracing-0.1.40) --- updated-dependencies: - dependency-name: tracing dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-18 23:14:00 +00:00
version = "0.1.40"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump tracing from 0.1.37 to 0.1.40 Bumps [tracing](https://github.com/tokio-rs/tracing) from 0.1.37 to 0.1.40. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-0.1.37...tracing-0.1.40) --- updated-dependencies: - dependency-name: tracing dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-18 23:14:00 +00:00
checksum = "c3523ab5a71916ccf420eebdf5521fcef02141234bbc0b8a49f2fdc4544364ef"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"pin-project-lite",
"tracing-attributes",
"tracing-core",
]
[[package]]
name = "tracing-attributes"
build: Bump tracing from 0.1.37 to 0.1.40 Bumps [tracing](https://github.com/tokio-rs/tracing) from 0.1.37 to 0.1.40. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-0.1.37...tracing-0.1.40) --- updated-dependencies: - dependency-name: tracing dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-18 23:14:00 +00:00
version = "0.1.27"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump tracing from 0.1.37 to 0.1.40 Bumps [tracing](https://github.com/tokio-rs/tracing) from 0.1.37 to 0.1.40. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-0.1.37...tracing-0.1.40) --- updated-dependencies: - dependency-name: tracing dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-18 23:14:00 +00:00
checksum = "34704c8d6ebcbc939824180af020566b01a7c01f80641264eba0999f6c2b6be7"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"proc-macro2",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
]
[[package]]
name = "tracing-core"
build: Bump tracing from 0.1.37 to 0.1.40 Bumps [tracing](https://github.com/tokio-rs/tracing) from 0.1.37 to 0.1.40. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-0.1.37...tracing-0.1.40) --- updated-dependencies: - dependency-name: tracing dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-18 23:14:00 +00:00
version = "0.1.32"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump tracing from 0.1.37 to 0.1.40 Bumps [tracing](https://github.com/tokio-rs/tracing) from 0.1.37 to 0.1.40. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-0.1.37...tracing-0.1.40) --- updated-dependencies: - dependency-name: tracing dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-18 23:14:00 +00:00
checksum = "c06d3da6113f116aaee68e4d601191614c9053067f9ab7f6edbcb161237daa54"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"once_cell",
]
[[package]]
name = "typenum"
build: Bump typenum from 1.16.0 to 1.17.0 Bumps [typenum](https://github.com/paholg/typenum) from 1.16.0 to 1.17.0. - [Release notes](https://github.com/paholg/typenum/releases) - [Changelog](https://github.com/paholg/typenum/blob/main/CHANGELOG.md) - [Commits](https://github.com/paholg/typenum/compare/v1.16.0...v1.17.0) --- updated-dependencies: - dependency-name: typenum dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-10-27 23:11:40 +00:00
version = "1.17.0"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump typenum from 1.16.0 to 1.17.0 Bumps [typenum](https://github.com/paholg/typenum) from 1.16.0 to 1.17.0. - [Release notes](https://github.com/paholg/typenum/releases) - [Changelog](https://github.com/paholg/typenum/blob/main/CHANGELOG.md) - [Commits](https://github.com/paholg/typenum/compare/v1.16.0...v1.17.0) --- updated-dependencies: - dependency-name: typenum dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-10-27 23:11:40 +00:00
checksum = "42ff0bf0c66b8238c6f3b578df37d0b7848e55df8577b3f74f92a69acceeb825"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "uds_windows"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.1.0"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "89daebc3e6fd160ac4aa9fc8b3bf71e1f74fbf92367ae71fb83a037e8bf164b9"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"memoffset 0.9.1",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"tempfile",
"winapi",
]
build: bump syn from 1.0.94 to 1.0.95 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.94 to 1.0.95. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.94...1.0.95) --- updated-dependencies: - dependency-name: syn dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-05-16 23:12:33 +00:00
[[package]]
name = "unicode-ident"
build: Bump unicode-ident from 1.0.11 to 1.0.12 Bumps [unicode-ident](https://github.com/dtolnay/unicode-ident) from 1.0.11 to 1.0.12. - [Release notes](https://github.com/dtolnay/unicode-ident/releases) - [Commits](https://github.com/dtolnay/unicode-ident/compare/1.0.11...1.0.12) --- updated-dependencies: - dependency-name: unicode-ident dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-02 23:24:04 +00:00
version = "1.0.12"
build: bump syn from 1.0.94 to 1.0.95 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.94 to 1.0.95. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.94...1.0.95) --- updated-dependencies: - dependency-name: syn dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-05-16 23:12:33 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump unicode-ident from 1.0.11 to 1.0.12 Bumps [unicode-ident](https://github.com/dtolnay/unicode-ident) from 1.0.11 to 1.0.12. - [Release notes](https://github.com/dtolnay/unicode-ident/releases) - [Commits](https://github.com/dtolnay/unicode-ident/compare/1.0.11...1.0.12) --- updated-dependencies: - dependency-name: unicode-ident dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-02 23:24:04 +00:00
checksum = "3354b9ac3fae1ff6755cb6db53683adb661634f67557942dea4facebec0fee4b"
build: bump syn from 1.0.94 to 1.0.95 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.94 to 1.0.95. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.94...1.0.95) --- updated-dependencies: - dependency-name: syn dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-05-16 23:12:33 +00:00
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
[[package]]
name = "utf8parse"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "711b9620af191e0cdc7468a8d14e709c3dcdb115b36f838e601583af800a370a"
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"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "1.8.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "a183cf7feeba97b4dd1c0d46788634f6221d87fa961b305bed08c851829efcc0"
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
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "version_check"
version = "0.9.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "49874b5167b65d7193b8aba1567f5c7d93d001cafc34600cee003eda787e483f"
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"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
version = "0.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
checksum = "62929d59c7f6730b7298fcb363760550f4db6e353fbac4076d447d0e82799d6d"
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 = [
"bincode",
"crc64",
"proc-macro2",
"quote",
"serde",
"serde_derive",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"syn 1.0.109",
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_derive",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-util",
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_derive"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
version = "0.1.6"
source = "git+https://github.com/cloud-hypervisor/versionize_derive?branch=ch-0.1.6#7906da996152e2d0ab08f5526440683bf3ca7834"
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",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"syn 1.0.109",
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
]
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"
misc: Bulk update dependencies In particular update to latest linux-loader release and point to latest vfio repository for both crates hosted there. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-12-07 17:39:14 +00:00
version = "0.4.0"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
source = "git+https://github.com/rust-vmm/vfio?branch=main#0daff4d4c159e842cf18b8b90457a45032b2df5a"
vfio: Rename to vfio-ioctls Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-08 15:27:05 +00:00
dependencies = [
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-util",
vfio: Rename to vfio-ioctls Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-08 15:27:05 +00:00
]
[[package]]
name = "vfio-ioctls"
misc: Bulk update dependencies In particular update to latest linux-loader release and point to latest vfio repository for both crates hosted there. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-12-07 17:39:14 +00:00
version = "0.2.0"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
source = "git+https://github.com/rust-vmm/vfio?branch=main#0daff4d4c159e842cf18b8b90457a45032b2df5a"
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",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +00:00
"vm-memory",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-util",
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
]
[[package]]
name = "vfio_user"
version = "0.1.0"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
source = "git+https://github.com/rust-vmm/vfio-user?branch=main#a1f6e52829e069b6d698b2cfeecac742e4653186"
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
dependencies = [
build: Bump bitflags from 1.3.2 to 2.3.2 Bumps [bitflags](https://github.com/bitflags/bitflags) from 1.3.2 to 2.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.2...2.3.2) --- updated-dependencies: - dependency-name: bitflags dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2023-06-16 00:54:27 +00:00
"bitflags 1.3.2",
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
"libc",
"log",
"serde",
"serde_derive",
"serde_json",
"thiserror",
"vfio-bindings",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +00:00
"vm-memory",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +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
]
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 vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
version = "0.10.0"
build: Bump vm-memory and its consumers Update to the latest vm-memory and all the crates that also depend upon it. Fix some deprecation warnings. Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2023-09-07 12:21:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
checksum = "2b64e816d0d49769fbfaa1494eb77cc2a3ddc526ead05c7f922cb7d64106286f"
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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"bitflags 2.5.0",
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: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +00:00
"vm-memory",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +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"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
version = "0.13.1"
build: Move to released versions of vhost and vhost-user-backend crates Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-11-30 10:55:11 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
checksum = "72c8c447d076ac508d78cb45664d203df7989e891656dce260a7e93d72352c9a"
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",
build: Bulk update rust-vmm dependencies Bump to the latest rust-vmm crates, including vm-memory, vfio, vfio-bindings, vfio-user, virtio-bindings, virtio-queue, linux-loader, vhost, and vhost-user-backend, Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-05-19 16:12:25 +00:00
"virtio-bindings",
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
"virtio-queue",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +00:00
"vm-memory",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-util",
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
]
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 = [
block: merge qcow, vhdx and block_util into block crate This commit merges crates `qcow`, `vhdx` and `block_util` into the crate `block`, which can allow `qcow` to use functions from `block_util` without introducing a circular crate dependency. This commit is based on crosvm implementation: https://chromium.googlesource.com/crosvm/crosvm/+/f2eecc4152eca8d395566cffa2c102ec090a152d Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
2023-07-12 02:24:28 +00:00
"block",
vhost_user_blk: switch to clap Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-09-21 15:35:44 +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
"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: Bulk update rust-vmm dependencies Bump to the latest rust-vmm crates, including vm-memory, vfio, vfio-bindings, vfio-user, virtio-bindings, virtio-queue, linux-loader, vhost, and vhost-user-backend, Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-05-19 16:12:25 +00:00
"virtio-bindings",
virtio: Port codebase to the latest virtio-queue version The new virtio-queue version introduced some breaking changes which need to be addressed so that Cloud Hypervisor can still work with this version. The most important change is about removing a handle to the guest memory from the Queue, meaning the caller has to provide the guest memory handle for multiple methods from the QueueT trait. One interesting aspect is that QueueT has been widely extended to provide every getter and setter we need to access and update the Queue structure without having direct access to its internal fields. This patch ports all the virtio and vhost-user devices to this new crate definition. It also updates both vhost-user-block and vhost-user-net backends based on the updated vhost-user-backend crate. It also updates the fuzz directory. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-07-06 14:08:08 +00:00
"virtio-queue",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +00:00
"vm-memory",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +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: switch to clap Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-09-21 15:30:23 +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: Bulk update rust-vmm dependencies Bump to the latest rust-vmm crates, including vm-memory, vfio, vfio-bindings, vfio-user, virtio-bindings, virtio-queue, linux-loader, vhost, and vhost-user-backend, Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-05-19 16:12:25 +00:00
"virtio-bindings",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +00:00
"vm-memory",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +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
]
build: Bump virtio-bindings from 0.1.0 to 0.2.0 Bumps [virtio-bindings](https://github.com/rust-vmm/vm-virtio) from 0.1.0 to 0.2.0. - [Release notes](https://github.com/rust-vmm/vm-virtio/releases) - [Commits](https://github.com/rust-vmm/vm-virtio/compare/virtio-queue-v0.1.0...virtio-bindings-v0.2.0) --- updated-dependencies: - dependency-name: virtio-bindings dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-21 23:58:46 +00:00
[[package]]
name = "virtio-bindings"
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +00:00
version = "0.2.2"
build: Bump virtio-bindings from 0.1.0 to 0.2.0 Bumps [virtio-bindings](https://github.com/rust-vmm/vm-virtio) from 0.1.0 to 0.2.0. - [Release notes](https://github.com/rust-vmm/vm-virtio/releases) - [Commits](https://github.com/rust-vmm/vm-virtio/compare/virtio-queue-v0.1.0...virtio-bindings-v0.2.0) --- updated-dependencies: - dependency-name: virtio-bindings dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-21 23:58:46 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +00:00
checksum = "878bcb1b2812a10c30d53b0ed054999de3d98f25ece91fc173973f9c57aaae86"
build: Bump virtio-bindings from 0.1.0 to 0.2.0 Bumps [virtio-bindings](https://github.com/rust-vmm/vm-virtio) from 0.1.0 to 0.2.0. - [Release notes](https://github.com/rust-vmm/vm-virtio/releases) - [Commits](https://github.com/rust-vmm/vm-virtio/compare/virtio-queue-v0.1.0...virtio-bindings-v0.2.0) --- updated-dependencies: - dependency-name: virtio-bindings dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-21 23:58:46 +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",
block: merge qcow, vhdx and block_util into block crate This commit merges crates `qcow`, `vhdx` and `block_util` into the crate `block`, which can allow `qcow` to use functions from `block_util` without introducing a circular crate dependency. This commit is based on crosvm implementation: https://chromium.googlesource.com/crosvm/crosvm/+/f2eecc4152eca8d395566cffa2c102ec090a152d Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
2023-07-12 02:24:28 +00:00
"block",
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",
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_json",
vmm: Move SerialBuffer to its own crate We want to be able to reuse the SerialBuffer from the virtio-devices crate, particularly from the virtio-console implementation. That's why we move the SerialBuffer definition to its own crate so that it can be accessed from both vmm and virtio-devices crates, without creating any cyclic dependency. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-08-25 08:26:59 +00:00
"serial_buffer",
virtio-devices: Add Vdpa device vDPA is a kernel framework introduced fairly recently in order to handle devices complying with virtio specification on their datapath, while the control path is vendor specific. For the datapath, that means the virtqueues are handled through DMA directly between the hardware and the guest, while the control path goes through the vDPA framework, eventually exposed through a vhost-vdpa device. vDPA, like VFIO, aims at achieving baremetal performance for devices that are passed into a VM. But unlike VFIO, it provides a simpler/better framework for achieving migration. Because the DMA accesses between the device and the guest are going through virtio queues, migration can be achieved way more easily, and doesn't require each device driver to implement the migration support. In the VFIO case, each vendor is expected to provide an implementation of the VFIO migration framework, which makes things harder as it must be done for each and every device. So to summarize the point is to support migration for hardware devices through which we can achieve baremetal performances. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-03-07 14:34:44 +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",
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",
build: Bulk update rust-vmm dependencies Bump to the latest rust-vmm crates, including vm-memory, vfio, vfio-bindings, vfio-user, virtio-bindings, virtio-queue, linux-loader, vhost, and vhost-user-backend, Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-05-19 16:12:25 +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",
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",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-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
]
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"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
version = "0.11.0"
deps: Move to latest vm-virtio and vhost-user-backend releases Move to release version v0.2.0 for both vm-virtio and vhost-user-backend crates rather than relying on their main branch, as they might be subject to breaking changes. Fixes #3800 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-03-07 12:47:51 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
checksum = "e3f69a13d6610db9312acbb438b0390362af905d37634a2106be70c0f734986d"
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",
build: Bulk update rust-vmm dependencies Bump to the latest rust-vmm crates, including vm-memory, vfio, vfio-bindings, vfio-user, virtio-bindings, virtio-queue, linux-loader, vhost, and vhost-user-backend, Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-05-19 16:12:25 +00:00
"virtio-bindings",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +00:00
"vm-memory",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"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
]
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",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +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",
hypervisor, vm-device: Relocate InterruptSourceConfig Move this enum from vm-device to hypervisor crate so that hypervisor crate does not gain an extra dependency. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-05-10 21:23:18 +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
"serde",
"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",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +00:00
"vm-memory",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.3.0"
source = "git+https://github.com/rust-vmm/vm-fdt?branch=main#982fb8d9c8cd7f53520d7e304b39ff307fa3a641"
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 vfio-ioctls from `847b0aa` to `59c604f` Bumps [vfio-ioctls](https://github.com/rust-vmm/vfio) from `847b0aa` to `59c604f`. - [Release notes](https://github.com/rust-vmm/vfio/releases) - [Commits](https://github.com/rust-vmm/vfio/compare/847b0aa504ac6367efe42ba7e96a2d050737d4f0...59c604fa6e42080f0a47c124ba29454fe4cb7475) --- updated-dependencies: - dependency-name: vfio-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-10 23:33:49 +00:00
[[package]]
name = "vm-memory"
build: Bump vm-memory from 0.14.0 to 0.14.1 Bumps [vm-memory](https://github.com/rust-vmm/vm-memory) from 0.14.0 to 0.14.1. - [Release notes](https://github.com/rust-vmm/vm-memory/releases) - [Changelog](https://github.com/rust-vmm/vm-memory/blob/v0.14.1/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/vm-memory/compare/v0.14.0...v0.14.1) --- updated-dependencies: - dependency-name: vm-memory dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-02 23:22:11 +00:00
version = "0.14.1"
build: Bump vfio-ioctls from `847b0aa` to `59c604f` Bumps [vfio-ioctls](https://github.com/rust-vmm/vfio) from `847b0aa` to `59c604f`. - [Release notes](https://github.com/rust-vmm/vfio/releases) - [Commits](https://github.com/rust-vmm/vfio/compare/847b0aa504ac6367efe42ba7e96a2d050737d4f0...59c604fa6e42080f0a47c124ba29454fe4cb7475) --- updated-dependencies: - dependency-name: vfio-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-10 23:33:49 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump vm-memory from 0.14.0 to 0.14.1 Bumps [vm-memory](https://github.com/rust-vmm/vm-memory) from 0.14.0 to 0.14.1. - [Release notes](https://github.com/rust-vmm/vm-memory/releases) - [Changelog](https://github.com/rust-vmm/vm-memory/blob/v0.14.1/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/vm-memory/compare/v0.14.0...v0.14.1) --- updated-dependencies: - dependency-name: vm-memory dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-02 23:22:11 +00:00
checksum = "3c3aba5064cc5f6f7740cddc8dae34d2d9a311cac69b60d942af7f3ab8fc49f4"
build: Bump vfio-ioctls from `847b0aa` to `59c604f` Bumps [vfio-ioctls](https://github.com/rust-vmm/vfio) from `847b0aa` to `59c604f`. - [Release notes](https://github.com/rust-vmm/vfio/releases) - [Commits](https://github.com/rust-vmm/vfio/compare/847b0aa504ac6367efe42ba7e96a2d050737d4f0...59c604fa6e42080f0a47c124ba29454fe4cb7475) --- updated-dependencies: - dependency-name: vfio-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-10 23:33:49 +00:00
dependencies = [
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +00:00
"arc-swap",
build: Bump vfio-ioctls from `847b0aa` to `59c604f` Bumps [vfio-ioctls](https://github.com/rust-vmm/vfio) from `847b0aa` to `59c604f`. - [Release notes](https://github.com/rust-vmm/vfio/releases) - [Commits](https://github.com/rust-vmm/vfio/compare/847b0aa504ac6367efe42ba7e96a2d050737d4f0...59c604fa6e42080f0a47c124ba29454fe4cb7475) --- updated-dependencies: - dependency-name: vfio-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-10 23:33:49 +00:00
"libc",
"thiserror",
"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_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",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +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",
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",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +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: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"bitflags 2.5.0",
block: merge qcow, vhdx and block_util into block crate This commit merges crates `qcow`, `vhdx` and `block_util` into the crate `block`, which can allow `qcow` to use functions from `block_util` without introducing a circular crate dependency. This commit is based on crosvm implementation: https://chromium.googlesource.com/crosvm/crosvm/+/f2eecc4152eca8d395566cffa2c102ec090a152d Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
2023-07-12 02:24:28 +00:00
"block",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"blocking",
vmm: Refactor VM creation workflow This refactoring is required to add support for creating SEV-SNP enabled VM. Signed-off-by: Jinank Jain <jinankjain@microsoft.com>
2022-12-20 04:39:20 +00:00
"cfg-if",
main: switch command parsing to use clap Partially revert 111225a2a562a465838219a82611b82393308ae7 and add the new dbus and pvpanic arguments. As we are switching back to clap observe the following changes. A few examples: 1. `-v -v -v` needs to be written as`-vvv` 2. `--disk D1 --disk D2` and others need to be written as `--disk D1 D2`. 3. `--option value` needs to be written as `--option=value.` Change integration tests to adapt to the breaking changes. Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
2023-07-08 01:38:51 +00:00
"clap",
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
"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: dbus: broadcast `event_monitor` events over the DBus API This commit builds on top of the `Monitor::subscribe` function and makes it possible to broadcast events published from `event-monitor` over D-Bus. The broadcasting functionality is enabled if the D-Bus API is enabled and users who wish to also enable the file based `event-monitor` can do so with the CLI arg `--event-monitor`. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-08-13 20:32:44 +00:00
"flume",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"futures",
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",
vmm: Add igvm module and loader module vmm: Add igvm module and loader module Add a separate module named igvm to the vmm crate with definitions to parse and load igvm to the guest memory. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-10 23:08:22 +00:00
"hex",
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",
vmm: Add igvm module and loader module vmm: Add igvm module and loader module Add a separate module named igvm to the vmm crate with definitions to parse and load igvm to the guest memory. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-10 23:08:22 +00:00
"igvm",
"igvm_defs",
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",
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",
vmm: Add igvm module and loader module vmm: Add igvm module and loader module Add a separate module named igvm to the vmm crate with definitions to parse and load igvm to the guest memory. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-10 23:08:22 +00:00
"mshv-bindings",
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",
vmm: switch from lazy_static to once_cell Once_cell does not require using macro and is slated to become part of Rust std at some point. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-06-20 13:53:39 +00:00
"once_cell",
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",
vmm: Add igvm module and loader module vmm: Add igvm module and loader module Add a separate module named igvm to the vmm crate with definitions to parse and load igvm to the guest memory. Signed-off-by: Jinank Jain <jinankjain@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2023-10-10 23:08:22 +00:00
"range_map_vec",
vmm: use RateLimiterGroup for virtio-blk devices Add a 'rate_limit_groups' field to VmConfig that defines a set of named RateLimiterGroups. When the 'rate_limit_group' field of DiskConfig is defined, all virtio-blk queues will be rate-limited by a shared RateLimiterGroup. The lifecycle of all RateLimiterGroups is tied to the Vm. A RateLimiterGroup may exist even if no Disks are configured to use the RateLimiterGroup. Disks may be hot-added or hot-removed from the RateLimiterGroup. When the 'rate_limiter' field of DiskConfig is defined, we construct an anonymous RateLimiterGroup whose lifecycle is tied to the Disk. This is primarily done for api backwards compatability. Importantly, the behavior is not the same! This implementation rate_limits the aggregate bandwidth / iops of an individual disk rather than the bandwidth / iops of an individual queue of a disk. When neither the 'rate_limit_group' or the 'rate_limiter' fields of DiskConfig is defined, the Disk is not rate-limited. Signed-off-by: Thomas Barrett <tbarrett@crusoeenergy.com>
2023-12-07 19:45:08 +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-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",
vmm: Move SerialBuffer to its own crate We want to be able to reuse the SerialBuffer from the virtio-devices crate, particularly from the virtio-console implementation. That's why we move the SerialBuffer definition to its own crate so that it can be accessed from both vmm and virtio-devices crates, without creating any cyclic dependency. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2022-08-25 08:26:59 +00:00
"serial_buffer",
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
"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",
tracing: Tracing infrastructure Add a new feature "tracing" that enables tracing functionality via the "tracer" crate (sadly features and crates cannot share the same name.) Setup: tracer::start() The main functionality is a tracer::trace_scope()! macro that will add trace points for the duration of the scope. Tracing events are per thread. Finish: tracer::end() this will write the trace file (pretty printed JSON) to a file in the current directory. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2022-06-21 14:01:26 +00:00
"tracer",
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",
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",
build: Upgrade vm-memory crates and its consumers Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-11-07 19:37:23 +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",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"vmm-sys-util",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"zbus",
build: Bump versions of acpi_tables and zerocopy The 'derive' feature of `zerocopy` crate now is optional and requires to be enabled explicitly [1]. Also, a version bump on `acpi_tables` is needed to reply on a single version of `zerocopy` to avoid compilation errors. [1] https://github.com/google/zerocopy/pull/176 Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-09-25 22:44:06 +00:00
"zerocopy",
vmm: Basic Vcpu implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 14:26:30 +00:00
]
build: Bump micro_http from `a4d632f` to `e75dfa1` Bumps [micro_http](https://github.com/firecracker-microvm/micro-http) from `a4d632f` to `e75dfa1`. - [Commits](https://github.com/firecracker-microvm/micro-http/compare/a4d632f2c5ea45712c0d2002dc909a63879e85c3...e75dfa1eeea23b69caa7407bc2c3a76d7b7262fb) --- updated-dependencies: - dependency-name: micro_http dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-03 23:11:06 +00:00
[[package]]
name = "vmm-sys-util"
version = "0.12.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1d1435039746e20da4f8d507a72ee1b916f7b4b05af7a91c093d2c6561934ede"
dependencies = [
"bitflags 1.3.2",
"libc",
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
"serde",
"serde_derive",
build: Bump micro_http from `a4d632f` to `e75dfa1` Bumps [micro_http](https://github.com/firecracker-microvm/micro-http) from `a4d632f` to `e75dfa1`. - [Commits](https://github.com/firecracker-microvm/micro-http/compare/a4d632f2c5ea45712c0d2002dc909a63879e85c3...e75dfa1eeea23b69caa7407bc2c3a76d7b7262fb) --- updated-dependencies: - dependency-name: micro_http dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-03 23:11:06 +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",
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "waker-fn"
build: Bump waker-fn from 1.1.0 to 1.1.1 Bumps [waker-fn](https://github.com/smol-rs/waker-fn) from 1.1.0 to 1.1.1. - [Release notes](https://github.com/smol-rs/waker-fn/releases) - [Changelog](https://github.com/smol-rs/waker-fn/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/waker-fn/compare/v1.1.0...v1.1.1) --- updated-dependencies: - dependency-name: waker-fn dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-25 23:40:36 +00:00
version = "1.1.1"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump waker-fn from 1.1.0 to 1.1.1 Bumps [waker-fn](https://github.com/smol-rs/waker-fn) from 1.1.0 to 1.1.1. - [Release notes](https://github.com/smol-rs/waker-fn/releases) - [Changelog](https://github.com/smol-rs/waker-fn/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/waker-fn/compare/v1.1.0...v1.1.1) --- updated-dependencies: - dependency-name: waker-fn dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-25 23:40:36 +00:00
checksum = "f3c4517f54858c779bbcbf228f4fca63d121bf85fbecb2dc578cdf4a39395690"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
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: bump getrandom from 0.2.6 to 0.2.7 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.2.6 to 0.2.7. - [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.6...v0.2.7) --- updated-dependencies: - dependency-name: getrandom dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-06-14 08:11:04 +00:00
version = "0.11.0+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: bump getrandom from 0.2.6 to 0.2.7 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.2.6 to 0.2.7. - [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.6...v0.2.7) --- updated-dependencies: - dependency-name: getrandom dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-06-14 08:11:04 +00:00
checksum = "9c8d87e72b64a3b4db28d11ce29237c246188f4f51057d65a7eab63b7987e423"
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
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
[[package]]
name = "wasm-bindgen"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.2.92"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "4be2531df63900aeb2bca0daaaddec08491ee64ceecbee5076636a3b026795a8"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
dependencies = [
"cfg-if",
"wasm-bindgen-macro",
]
[[package]]
name = "wasm-bindgen-backend"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.2.92"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "614d787b966d3989fa7bb98a654e369c762374fd3213d212cfc0251257e747da"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
dependencies = [
"bumpalo",
"log",
"once_cell",
"proc-macro2",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-macro"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.2.92"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "a1f8823de937b71b9460c0c34e25f3da88250760bec0ebac694b49997550d726"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
dependencies = [
"quote",
"wasm-bindgen-macro-support",
]
[[package]]
name = "wasm-bindgen-macro-support"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.2.92"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "e94f17b526d0a461a191c78ea52bbce64071ed5c04c9ffe424dcb38f74171bb7"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
dependencies = [
"proc-macro2",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
"wasm-bindgen-backend",
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-shared"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.2.92"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "af190c94f2773fdb3729c55b007a722abb5384da03bc0986df4c289bf5567e96"
event_monitor: refactor the implementation to support concurrent access This patch modifies `event_monitor` to ensure that concurrent access to `event_log` from multiple threads is safe. Previously, the `event_log` function would acquire a reference to the event log file and write to it without doing any synchronization, which made it prone to data races. This issue likely went under the radar because the relevant `SAFETY` comment on the unsafe block was incomplete. The new implementation spawns a dedicated thread named `event-monitor` solely for writing to the file. It uses the MPMC channel exposed by `flume` to pass messages to the `event-monitor` thread. Since `flume::Sender<T>` implements `Sync`, it is safe for multiple threads to share it and send messages to the `event-monitor` thread. This is not possible with `std::sync::mpsc::Sender<T>` since it's `!Sync`, meaning it is not safe for it to be shared between different threads. The `event_monitor::set_monitor` function now only initializes the required global state and returns an instance of the `Monitor` struct. This decouples the actual logging logic from the `event_monitor` crate. The `event-monitor` thread is then spawned by the `vmm` crate. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-29 21:53:36 +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"
build: Bump winapi-util from 0.1.5 to 0.1.6 Bumps [winapi-util](https://github.com/BurntSushi/winapi-util) from 0.1.5 to 0.1.6. - [Commits](https://github.com/BurntSushi/winapi-util/compare/winapi-util-0.1.5...0.1.6) --- updated-dependencies: - dependency-name: winapi-util dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-10-31 23:05:21 +00:00
version = "0.1.6"
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 winapi-util from 0.1.5 to 0.1.6 Bumps [winapi-util](https://github.com/BurntSushi/winapi-util) from 0.1.5 to 0.1.6. - [Commits](https://github.com/BurntSushi/winapi-util/compare/winapi-util-0.1.5...0.1.6) --- updated-dependencies: - dependency-name: winapi-util dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-10-31 23:05:21 +00:00
checksum = "f29e6f9198ba0d26b4c9f07dbe6f9ed633e1f3d5b8b414090084349e46a52596"
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 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
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
[[package]]
name = "windows-sys"
version = "0.48.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "677d2418bec65e3338edb076e806bc1ec15693c5d0104683f2efe857f61056a9"
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"windows-targets 0.48.5",
build: Bump rustix from 0.36.7 to 0.36.8 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.7 to 0.36.8. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.7...v0.36.8) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-06 23:03:49 +00:00
]
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
[[package]]
name = "windows-sys"
version = "0.52.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "282be5f36a8ce781fad8c8ae18fa3f9beff57ec1b52cb3de0789201425d9a33d"
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"windows-targets 0.52.4",
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
]
build: Bump rustix from 0.36.7 to 0.36.8 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.7 to 0.36.8. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.7...v0.36.8) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-06 23:03:49 +00:00
[[package]]
name = "windows-targets"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.48.5"
build: Bump rustix from 0.36.7 to 0.36.8 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.7 to 0.36.8. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.7...v0.36.8) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-06 23:03:49 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "9a2fa6e2155d7247be68c096456083145c183cbbbc2764150dda45a87197940c"
build: Bump rustix from 0.36.7 to 0.36.8 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.7 to 0.36.8. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.7...v0.36.8) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-06 23:03:49 +00:00
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"windows_aarch64_gnullvm 0.48.5",
"windows_aarch64_msvc 0.48.5",
"windows_i686_gnu 0.48.5",
"windows_i686_msvc 0.48.5",
"windows_x86_64_gnu 0.48.5",
"windows_x86_64_gnullvm 0.48.5",
"windows_x86_64_msvc 0.48.5",
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
]
[[package]]
name = "windows-targets"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.52.4"
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "7dd37b7e5ab9018759f893a1952c9420d060016fc19a472b4bb20d1bdd694d1b"
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
dependencies = [
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"windows_aarch64_gnullvm 0.52.4",
"windows_aarch64_msvc 0.52.4",
"windows_i686_gnu 0.52.4",
"windows_i686_msvc 0.52.4",
"windows_x86_64_gnu 0.52.4",
"windows_x86_64_gnullvm 0.52.4",
"windows_x86_64_msvc 0.52.4",
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
]
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
[[package]]
name = "windows_aarch64_gnullvm"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.48.5"
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "2b38e32f0abccf9987a4e3079dfb67dcd799fb61361e53e2882c3cbaf0d905d8"
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
[[package]]
name = "windows_aarch64_gnullvm"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.52.4"
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "bcf46cf4c365c6f2d1cc93ce535f2c8b244591df96ceee75d8e83deb70a9cac9"
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
[[package]]
name = "windows_aarch64_msvc"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.48.5"
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "dc35310971f3b2dbbf3f0690a219f40e2d9afcf64f9ab7cc1be722937c26b4bc"
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
[[package]]
name = "windows_aarch64_msvc"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.52.4"
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "da9f259dd3bcf6990b55bffd094c4f7235817ba4ceebde8e6d11cd0c5633b675"
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
[[package]]
name = "windows_i686_gnu"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.48.5"
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "a75915e7def60c94dcef72200b9a8e58e5091744960da64ec734a6c6e9b3743e"
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
[[package]]
name = "windows_i686_gnu"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.52.4"
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "b474d8268f99e0995f25b9f095bc7434632601028cf86590aea5c8a5cb7801d3"
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
[[package]]
name = "windows_i686_msvc"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.48.5"
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "8f55c233f70c4b27f66c523580f78f1004e8b5a8b659e05a4eb49d4166cca406"
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
[[package]]
name = "windows_i686_msvc"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.52.4"
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "1515e9a29e5bed743cb4415a9ecf5dfca648ce85ee42e15873c3cd8610ff8e02"
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
[[package]]
name = "windows_x86_64_gnu"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.48.5"
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "53d40abd2583d23e4718fddf1ebec84dbff8381c07cae67ff7768bbf19c6718e"
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
[[package]]
name = "windows_x86_64_gnu"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.52.4"
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "5eee091590e89cc02ad514ffe3ead9eb6b660aedca2183455434b93546371a03"
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
[[package]]
name = "windows_x86_64_gnullvm"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.48.5"
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "0b7b52767868a23d5bab768e390dc5f5c55825b6d30b86c844ff2dc7414044cc"
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
[[package]]
name = "windows_x86_64_gnullvm"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.52.4"
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "77ca79f2451b49fa9e2af39f0747fe999fcda4f5e241b2898624dca97a1f2177"
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
[[package]]
name = "windows_x86_64_msvc"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.48.5"
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "ed94fce61571a4006852b7389a063ab983c02eb1bb37b47f8272ce92d06d9538"
build: Bump terminal_size from 0.2.1 to 0.2.2 Bumps [terminal_size](https://github.com/eminence/terminal-size) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/eminence/terminal-size/releases) - [Commits](https://github.com/eminence/terminal-size/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: terminal_size dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-09 23:02:50 +00:00
build: Bump rustix from 0.36.8 to 0.36.12 Bumps [rustix](https://github.com/bytecodealliance/rustix) from 0.36.8 to 0.36.12. - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.36.8...v0.36.12) --- updated-dependencies: - dependency-name: rustix dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-04-13 23:58:30 +00:00
[[package]]
name = "windows_x86_64_msvc"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.52.4"
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "32b752e52a2da0ddfbdbcc6fceadfeede4c939ed16d13e648833a61dfb611ed8"
build: Bump anstyle-query from 1.0.0 to 1.0.2 Bumps [anstyle-query](https://github.com/rust-cli/anstyle) from 1.0.0 to 1.0.2. - [Commits](https://github.com/rust-cli/anstyle/compare/anstyle-query-v1.0.0...anstyle-query-v1.0.2) --- updated-dependencies: - dependency-name: anstyle-query dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-19 23:09:03 +00:00
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "winnow"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
version = "0.5.40"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
checksum = "f593a95398737aeed53e489c785df13f3618e41dbcd6718c6addbf1395aa6876"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"memchr",
]
[[package]]
name = "xdg-home"
build: Bump xdg-home from 1.0.0 to 1.1.0 Bumps [xdg-home](https://github.com/zeenix/xdg-home) from 1.0.0 to 1.1.0. - [Release notes](https://github.com/zeenix/xdg-home/releases) - [Commits](https://github.com/zeenix/xdg-home/compare/1.0.0...1.1.0) --- updated-dependencies: - dependency-name: xdg-home dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-27 23:50:50 +00:00
version = "1.1.0"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump xdg-home from 1.0.0 to 1.1.0 Bumps [xdg-home](https://github.com/zeenix/xdg-home) from 1.0.0 to 1.1.0. - [Release notes](https://github.com/zeenix/xdg-home/releases) - [Commits](https://github.com/zeenix/xdg-home/compare/1.0.0...1.1.0) --- updated-dependencies: - dependency-name: xdg-home dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-27 23:50:50 +00:00
checksum = "21e5a325c3cb8398ad6cf859c1135b25dd29e186679cf2da7581d9679f63b38e"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
build: Bump xdg-home from 1.0.0 to 1.1.0 Bumps [xdg-home](https://github.com/zeenix/xdg-home) from 1.0.0 to 1.1.0. - [Release notes](https://github.com/zeenix/xdg-home/releases) - [Commits](https://github.com/zeenix/xdg-home/compare/1.0.0...1.1.0) --- updated-dependencies: - dependency-name: xdg-home dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-27 23:50:50 +00:00
"libc",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"winapi",
]
[[package]]
name = "zbus"
build: Bump zbus from 3.14.1 to 3.15.2 Bumps [zbus](https://github.com/dbus2/zbus) from 3.14.1 to 3.15.2. - [Release notes](https://github.com/dbus2/zbus/releases) - [Commits](https://github.com/dbus2/zbus/compare/zbus-3.14.1...zbus-3.15.2) --- updated-dependencies: - dependency-name: zbus dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-04 23:52:32 +00:00
version = "3.15.2"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump zbus from 3.14.1 to 3.15.2 Bumps [zbus](https://github.com/dbus2/zbus) from 3.14.1 to 3.15.2. - [Release notes](https://github.com/dbus2/zbus/releases) - [Commits](https://github.com/dbus2/zbus/compare/zbus-3.14.1...zbus-3.15.2) --- updated-dependencies: - dependency-name: zbus dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-04 23:52:32 +00:00
checksum = "675d170b632a6ad49804c8cf2105d7c31eddd3312555cffd4b740e08e97c25e6"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"async-broadcast",
"async-executor",
"async-fs",
build: Bump async-process from 1.8.0 to 1.8.1 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.8.0 to 1.8.1. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.8.0...v1.8.1) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-12 23:04:01 +00:00
"async-io 1.13.0",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"async-lock 2.8.0",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"async-process",
"async-recursion",
"async-task",
"async-trait",
build: bump zbus related dependencies * zbus v3.13.1 -> v3.14.1 * zbus_macros v3.13.1 -> v3.14.1 * zbus_names v2.5.1 -> v2.6.0 * zvariant v3.14.0 -> v3.15.0 * zvariant_derive v3.14.0 -> v3.15.0 Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-07-31 05:30:30 +00:00
"blocking",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"byteorder",
"derivative",
"enumflags2",
build: Bump async-process from 1.7.0 to 1.8.0 Bumps [async-process](https://github.com/smol-rs/async-process) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/smol-rs/async-process/releases) - [Changelog](https://github.com/smol-rs/async-process/blob/master/CHANGELOG.md) - [Commits](https://github.com/smol-rs/async-process/compare/v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: async-process dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-28 23:47:38 +00:00
"event-listener 2.5.3",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
"futures-core",
"futures-sink",
"futures-util",
"hex",
"nix",
"once_cell",
"ordered-stream",
"rand",
"serde",
"serde_repr",
"sha1",
"static_assertions",
"tracing",
"uds_windows",
"winapi",
"xdg-home",
"zbus_macros",
"zbus_names",
"zvariant",
]
[[package]]
name = "zbus_macros"
build: Bump zbus from 3.14.1 to 3.15.2 Bumps [zbus](https://github.com/dbus2/zbus) from 3.14.1 to 3.15.2. - [Release notes](https://github.com/dbus2/zbus/releases) - [Commits](https://github.com/dbus2/zbus/compare/zbus-3.14.1...zbus-3.15.2) --- updated-dependencies: - dependency-name: zbus dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-04 23:52:32 +00:00
version = "3.15.2"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump zbus from 3.14.1 to 3.15.2 Bumps [zbus](https://github.com/dbus2/zbus) from 3.14.1 to 3.15.2. - [Release notes](https://github.com/dbus2/zbus/releases) - [Commits](https://github.com/dbus2/zbus/compare/zbus-3.14.1...zbus-3.15.2) --- updated-dependencies: - dependency-name: zbus dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-04 23:52:32 +00:00
checksum = "7131497b0f887e8061b430c530240063d33bf9455fa34438f388a245da69e0a5"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"proc-macro-crate",
"proc-macro2",
"quote",
"regex",
"syn 1.0.109",
"zvariant_utils",
]
[[package]]
name = "zbus_names"
build: Bump zbus_names from 2.6.0 to 2.6.1 Bumps [zbus_names](https://github.com/dbus2/zbus) from 2.6.0 to 2.6.1. - [Release notes](https://github.com/dbus2/zbus/releases) - [Commits](https://github.com/dbus2/zbus/compare/zbus_names-2.6.0...zbus_names-2.6.1) --- updated-dependencies: - dependency-name: zbus_names dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-28 23:33:22 +00:00
version = "2.6.1"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump zbus_names from 2.6.0 to 2.6.1 Bumps [zbus_names](https://github.com/dbus2/zbus) from 2.6.0 to 2.6.1. - [Release notes](https://github.com/dbus2/zbus/releases) - [Commits](https://github.com/dbus2/zbus/compare/zbus_names-2.6.0...zbus_names-2.6.1) --- updated-dependencies: - dependency-name: zbus_names dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-28 23:33:22 +00:00
checksum = "437d738d3750bed6ca9b8d423ccc7a8eb284f6b1d6d4e225a0e4e6258d864c8d"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"serde",
"static_assertions",
"zvariant",
]
build: Bump mshv-ioctls from `a45fbeb` to `c5a6050` Bumps [mshv-ioctls](https://github.com/rust-vmm/mshv) from `a45fbeb` to `c5a6050`. - [Commits](https://github.com/rust-vmm/mshv/compare/a45fbeb4a3930a2d17142e5687fe2f667c2df529...c5a60508595dc504da469b89102b8b49e91714a9) --- updated-dependencies: - dependency-name: mshv-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-30 23:43:16 +00:00
[[package]]
name = "zerocopy"
build: Bump zerocopy from 0.7.31 to 0.7.32 Bumps [zerocopy](https://github.com/google/zerocopy) from 0.7.31 to 0.7.32. - [Release notes](https://github.com/google/zerocopy/releases) - [Changelog](https://github.com/google/zerocopy/blob/main/CHANGELOG.md) - [Commits](https://github.com/google/zerocopy/compare/v0.7.31...v0.7.32) --- updated-dependencies: - dependency-name: zerocopy dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-26 23:43:53 +00:00
version = "0.7.32"
build: Bump mshv-ioctls from `a45fbeb` to `c5a6050` Bumps [mshv-ioctls](https://github.com/rust-vmm/mshv) from `a45fbeb` to `c5a6050`. - [Commits](https://github.com/rust-vmm/mshv/compare/a45fbeb4a3930a2d17142e5687fe2f667c2df529...c5a60508595dc504da469b89102b8b49e91714a9) --- updated-dependencies: - dependency-name: mshv-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-30 23:43:16 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump zerocopy from 0.7.31 to 0.7.32 Bumps [zerocopy](https://github.com/google/zerocopy) from 0.7.31 to 0.7.32. - [Release notes](https://github.com/google/zerocopy/releases) - [Changelog](https://github.com/google/zerocopy/blob/main/CHANGELOG.md) - [Commits](https://github.com/google/zerocopy/compare/v0.7.31...v0.7.32) --- updated-dependencies: - dependency-name: zerocopy dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-26 23:43:53 +00:00
checksum = "74d4d3961e53fa4c9a25a8637fc2bfaf2595b3d3ae34875568a5cf64787716be"
build: Bump mshv-ioctls from `a45fbeb` to `c5a6050` Bumps [mshv-ioctls](https://github.com/rust-vmm/mshv) from `a45fbeb` to `c5a6050`. - [Commits](https://github.com/rust-vmm/mshv/compare/a45fbeb4a3930a2d17142e5687fe2f667c2df529...c5a60508595dc504da469b89102b8b49e91714a9) --- updated-dependencies: - dependency-name: mshv-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-30 23:43:16 +00:00
dependencies = [
"byteorder",
build: Bump versions of acpi_tables and zerocopy The 'derive' feature of `zerocopy` crate now is optional and requires to be enabled explicitly [1]. Also, a version bump on `acpi_tables` is needed to reply on a single version of `zerocopy` to avoid compilation errors. [1] https://github.com/google/zerocopy/pull/176 Signed-off-by: Bo Chen <chen.bo@intel.com>
2023-09-25 22:44:06 +00:00
"zerocopy-derive",
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
]
build: Bump mshv-ioctls from `a45fbeb` to `c5a6050` Bumps [mshv-ioctls](https://github.com/rust-vmm/mshv) from `a45fbeb` to `c5a6050`. - [Commits](https://github.com/rust-vmm/mshv/compare/a45fbeb4a3930a2d17142e5687fe2f667c2df529...c5a60508595dc504da469b89102b8b49e91714a9) --- updated-dependencies: - dependency-name: mshv-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-30 23:43:16 +00:00
[[package]]
name = "zerocopy-derive"
build: Bump zerocopy from 0.7.31 to 0.7.32 Bumps [zerocopy](https://github.com/google/zerocopy) from 0.7.31 to 0.7.32. - [Release notes](https://github.com/google/zerocopy/releases) - [Changelog](https://github.com/google/zerocopy/blob/main/CHANGELOG.md) - [Commits](https://github.com/google/zerocopy/compare/v0.7.31...v0.7.32) --- updated-dependencies: - dependency-name: zerocopy dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-26 23:43:53 +00:00
version = "0.7.32"
build: Bump mshv-ioctls from `a45fbeb` to `c5a6050` Bumps [mshv-ioctls](https://github.com/rust-vmm/mshv) from `a45fbeb` to `c5a6050`. - [Commits](https://github.com/rust-vmm/mshv/compare/a45fbeb4a3930a2d17142e5687fe2f667c2df529...c5a60508595dc504da469b89102b8b49e91714a9) --- updated-dependencies: - dependency-name: mshv-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-30 23:43:16 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump zerocopy from 0.7.31 to 0.7.32 Bumps [zerocopy](https://github.com/google/zerocopy) from 0.7.31 to 0.7.32. - [Release notes](https://github.com/google/zerocopy/releases) - [Changelog](https://github.com/google/zerocopy/blob/main/CHANGELOG.md) - [Commits](https://github.com/google/zerocopy/compare/v0.7.31...v0.7.32) --- updated-dependencies: - dependency-name: zerocopy dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-01-26 23:43:53 +00:00
checksum = "9ce1b18ccd8e73a9321186f97e46f9f04b778851177567b1975109d26a08d2a6"
build: Bump mshv-ioctls from `a45fbeb` to `c5a6050` Bumps [mshv-ioctls](https://github.com/rust-vmm/mshv) from `a45fbeb` to `c5a6050`. - [Commits](https://github.com/rust-vmm/mshv/compare/a45fbeb4a3930a2d17142e5687fe2f667c2df529...c5a60508595dc504da469b89102b8b49e91714a9) --- updated-dependencies: - dependency-name: mshv-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-30 23:43:16 +00:00
dependencies = [
"proc-macro2",
"quote",
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
"syn 2.0.58",
build: Bump mshv-ioctls from `a45fbeb` to `c5a6050` Bumps [mshv-ioctls](https://github.com/rust-vmm/mshv) from `a45fbeb` to `c5a6050`. - [Commits](https://github.com/rust-vmm/mshv/compare/a45fbeb4a3930a2d17142e5687fe2f667c2df529...c5a60508595dc504da469b89102b8b49e91714a9) --- updated-dependencies: - dependency-name: mshv-ioctls dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-30 23:43:16 +00:00
]
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
[[package]]
name = "zvariant"
build: Bump zvariant from 3.15.0 to 3.15.2 Bumps [zvariant](https://github.com/dbus2/zbus) from 3.15.0 to 3.15.2. - [Release notes](https://github.com/dbus2/zbus/releases) - [Commits](https://github.com/dbus2/zbus/compare/zvariant-3.15.0...zvariant-3.15.2) --- updated-dependencies: - dependency-name: zvariant dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-15 23:24:03 +00:00
version = "3.15.2"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump zvariant from 3.15.0 to 3.15.2 Bumps [zvariant](https://github.com/dbus2/zbus) from 3.15.0 to 3.15.2. - [Release notes](https://github.com/dbus2/zbus/releases) - [Commits](https://github.com/dbus2/zbus/compare/zvariant-3.15.0...zvariant-3.15.2) --- updated-dependencies: - dependency-name: zvariant dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-15 23:24:03 +00:00
checksum = "4eef2be88ba09b358d3b58aca6e41cd853631d44787f319a1383ca83424fb2db"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"byteorder",
"enumflags2",
"libc",
"serde",
"static_assertions",
"zvariant_derive",
]
[[package]]
name = "zvariant_derive"
build: Bump zvariant from 3.15.0 to 3.15.2 Bumps [zvariant](https://github.com/dbus2/zbus) from 3.15.0 to 3.15.2. - [Release notes](https://github.com/dbus2/zbus/releases) - [Commits](https://github.com/dbus2/zbus/compare/zvariant-3.15.0...zvariant-3.15.2) --- updated-dependencies: - dependency-name: zvariant dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-15 23:24:03 +00:00
version = "3.15.2"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build: Bump zvariant from 3.15.0 to 3.15.2 Bumps [zvariant](https://github.com/dbus2/zbus) from 3.15.0 to 3.15.2. - [Release notes](https://github.com/dbus2/zbus/releases) - [Commits](https://github.com/dbus2/zbus/compare/zvariant-3.15.0...zvariant-3.15.2) --- updated-dependencies: - dependency-name: zvariant dependency-type: indirect update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-15 23:24:03 +00:00
checksum = "37c24dc0bed72f5f90d1f8bb5b07228cbf63b3c6e9f82d82559d4bae666e7ed9"
vmm: dbus: implement the D-Bus API This commit introduces three new dependencies: `zbus`, `futures` and `blocking`. `blocking` is used to call the Internal API in zbus' async context which is driven by `futures::executor`. They are all behind the `dbus_api` feature flag. The D-Bus API implementation is behind the same `dbus_api` feature flag as well. Signed-off-by: Omer Faruk Bayram <omer.faruk@sartura.hr>
2023-03-22 21:03:02 +00:00
dependencies = [
"proc-macro-crate",
"proc-macro2",
"quote",
"syn 1.0.109",
"zvariant_utils",
]
[[package]]
name = "zvariant_utils"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7234f0d811589db492d16893e3f21e8e2fd282e6d01b0cddee310322062cc200"
dependencies = [
"proc-macro2",
"quote",
"syn 1.0.109",
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
]
Reference in New Issue Copy Permalink