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

1285 lines
55 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.
acpi_tables: Add initial ACPI tables support Add a revision 2 RSDP table only supporting an XSDT along with support for creating generic SDT based tables. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-07 16:53:37 +00:00
[[package]]
name = "acpi_tables"
version = "0.1.0"
dependencies = [
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
]
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"
version = "0.6.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"memchr 2.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "ansi_term"
build(deps): bump clap from 2.27.1 to 2.33.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.27.1 to 2.33.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/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:22:53 +00:00
version = "0.11.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(deps): bump clap from 2.27.1 to 2.33.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.27.1 to 2.33.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/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:22:53 +00:00
dependencies = [
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
]
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
vm-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(deps): bump arc-swap from 0.4.3 to 0.4.4 Bumps [arc-swap](https://github.com/vorner/arc-swap) from 0.4.3 to 0.4.4. - [Release notes](https://github.com/vorner/arc-swap/releases) - [Changelog](https://github.com/vorner/arc-swap/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/arc-swap/compare/v0.4.3...v0.4.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-17 11:34:27 +00:00
version = "0.4.4"
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"
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: x86_64: Generate basic ACPI tables Generate very basic ACPI tables for HW reduced ACPI. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-14 16:14:34 +00:00
"acpi_tables 0.1.0",
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 13:16:58 +00:00
"arch_gen 0.1.0",
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"kvm-bindings 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
"kvm-ioctls 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"linux-loader 0.1.0 (git+https://github.com/rust-vmm/linux-loader)",
build(deps): bump dirs from 2.0.1 to 2.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 2.0.1 to 2.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>
2019-08-02 07:51:51 +00:00
"rand 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 13:16:58 +00:00
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
]
[[package]]
name = "arch_gen"
version = "0.1.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
[[package]]
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
name = "arrayref"
version = "0.3.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"
[[package]]
name = "arrayvec"
build(deps): bump blake2b_simd from 0.5.8 to 0.5.9 Bumps [blake2b_simd](https://github.com/oconnor663/blake2_simd) from 0.5.8 to 0.5.9. - [Release notes](https://github.com/oconnor663/blake2_simd/releases) - [Commits](https://github.com/oconnor663/blake2_simd/compare/0.5.8...0.5.9) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-07 00:07:00 +00:00
version = "0.5.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"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
[[package]]
name = "atty"
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
version = "0.2.13"
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"
dependencies = [
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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 = "autocfg"
build(deps): bump autocfg from 0.1.6 to 0.1.7 Bumps [autocfg](https://github.com/cuviper/autocfg) from 0.1.6 to 0.1.7. - [Release notes](https://github.com/cuviper/autocfg/releases) - [Commits](https://github.com/cuviper/autocfg/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-20 18:05:52 +00:00
version = "0.1.7"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "backtrace"
build(deps): bump backtrace from 0.3.39 to 0.3.40 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.39 to 0.3.40. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.39...0.3.40) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-17 22:23:06 +00:00
version = "0.3.40"
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"
dependencies = [
build(deps): bump backtrace-sys from 0.1.31 to 0.1.32 Bumps [backtrace-sys](https://github.com/alexcrichton/backtrace-rs) from 0.1.31 to 0.1.32. - [Release notes](https://github.com/alexcrichton/backtrace-rs/releases) - [Commits](https://github.com/alexcrichton/backtrace-rs/compare/backtrace-sys-0.1.31...backtrace-sys-0.1.32) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-17 17:35:28 +00:00
"backtrace-sys 0.1.32 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump cfg-if from 0.1.9 to 0.1.10 Bumps [cfg-if](https://github.com/alexcrichton/cfg-if) from 0.1.9 to 0.1.10. - [Release notes](https://github.com/alexcrichton/cfg-if/releases) - [Commits](https://github.com/alexcrichton/cfg-if/compare/0.1.9...0.1.10) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-24 19:45:47 +00:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump rustc-demangle from 0.1.15 to 0.1.16 Bumps [rustc-demangle](https://github.com/alexcrichton/rustc-demangle) from 0.1.15 to 0.1.16. - [Release notes](https://github.com/alexcrichton/rustc-demangle/releases) - [Commits](https://github.com/alexcrichton/rustc-demangle/compare/0.1.15...0.1.16) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-14 07:18:12 +00:00
"rustc-demangle 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "backtrace-sys"
build(deps): bump backtrace-sys from 0.1.31 to 0.1.32 Bumps [backtrace-sys](https://github.com/alexcrichton/backtrace-rs) from 0.1.31 to 0.1.32. - [Release notes](https://github.com/alexcrichton/backtrace-rs/releases) - [Commits](https://github.com/alexcrichton/backtrace-rs/compare/backtrace-sys-0.1.31...backtrace-sys-0.1.32) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-17 17:35:28 +00:00
version = "0.1.32"
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"
dependencies = [
build(deps): bump cc from 1.0.47 to 1.0.48 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.47 to 1.0.48. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.47...1.0.48) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-04 16:34:10 +00:00
"cc 1.0.48 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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 redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
[[package]]
name = "base64"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "bitflags"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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(deps): bump ssh2 from 0.5.0 to 0.6.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.5.0 to 0.6.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.5.0...0.6.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-08 18:43:54 +00:00
version = "1.2.1"
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-03-07 13:56:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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]]
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
name = "blake2b_simd"
build(deps): bump blake2b_simd from 0.5.8 to 0.5.9 Bumps [blake2b_simd](https://github.com/oconnor663/blake2_simd) from 0.5.8 to 0.5.9. - [Release notes](https://github.com/oconnor663/blake2_simd/releases) - [Commits](https://github.com/oconnor663/blake2_simd/compare/0.5.8...0.5.9) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-07 00:07:00 +00:00
version = "0.5.9"
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"
dependencies = [
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
"arrayref 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump blake2b_simd from 0.5.8 to 0.5.9 Bumps [blake2b_simd](https://github.com/oconnor663/blake2_simd) from 0.5.8 to 0.5.9. - [Release notes](https://github.com/oconnor663/blake2_simd/releases) - [Commits](https://github.com/oconnor663/blake2_simd/compare/0.5.8...0.5.9) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-07 00:07:00 +00:00
"arrayvec 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump constant_time_eq from 0.1.3 to 0.1.4 Bumps [constant_time_eq](https://github.com/cesarb/constant_time_eq) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/cesarb/constant_time_eq/releases) - [Commits](https://github.com/cesarb/constant_time_eq/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-21 08:25:16 +00:00
"constant_time_eq 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "byteorder"
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
version = "1.3.2"
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"
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 = "c2-chacha"
build(deps): bump c2-chacha from 0.2.2 to 0.2.3 Bumps [c2-chacha](https://github.com/cryptocorrosion/cryptocorrosion) from 0.2.2 to 0.2.3. - [Release notes](https://github.com/cryptocorrosion/cryptocorrosion/releases) - [Commits](https://github.com/cryptocorrosion/cryptocorrosion/compare/c2-chacha-0.2.2...c2-chacha-0.2.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-21 17:12:07 +00:00
version = "0.2.3"
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"
dependencies = [
build(deps): bump ppv-lite86 from 0.2.5 to 0.2.6 Bumps [ppv-lite86](https://github.com/cryptocorrosion/cryptocorrosion) from 0.2.5 to 0.2.6. - [Release notes](https://github.com/cryptocorrosion/cryptocorrosion/releases) - [Commits](https://github.com/cryptocorrosion/cryptocorrosion/compare/ppv-lite86-0.2.5...ppv-lite86-0.2.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-21 16:44:04 +00:00
"ppv-lite86 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
vmm: Integrate userspace IOAPIC The previous commit introduced a userspace implementation of an IOAPIC and this commits aims to plumb it into the cloud-hypervisor VMM. Here is the list of new things brought by this patch: - Update the rust-vmm/kvm-ioctls dependency to benefit from latest patches including the support for split irqchip, and the vector being returned when a VM exit is caused by an EOI. - Enable the split irqchip (which means no IOAPIC or PIC is emulated in kernel). This is done conditionally based on the support of the TSC_DEADLINE_TIMER from both KVM and the underlying CPU. The dependency on TSC_DEADLINE_TIMER is related to KVM which does not support creating the in kernel PIT if it has a split irqchip. - Rely on callbacks to handle the following use cases: - in kernel IOAPIC + serial IRQ (pin based) - in kernel IOAPIC + virtio-pci MSI-X - in kernel IOAPIC + virtio-pci IRQ (pin based) - userspace IOAPIC + serial IRQ (pin based) - userspace IOAPIC + virtio-pci MSI-X - userspace IOAPIC + virtio-pci IRQ (pin based) Fixes #13 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-06-18 17:31:50 +00:00
[[package]]
name = "cast"
build(deps): bump cast from 0.2.2 to 0.2.3 Bumps [cast](https://github.com/japaric/cast.rs) from 0.2.2 to 0.2.3. - [Release notes](https://github.com/japaric/cast.rs/releases) - [Changelog](https://github.com/japaric/cast.rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/japaric/cast.rs/compare/v0.2.2...v0.2.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-16 23:53:59 +00:00
version = "0.2.3"
vmm: Integrate userspace IOAPIC The previous commit introduced a userspace implementation of an IOAPIC and this commits aims to plumb it into the cloud-hypervisor VMM. Here is the list of new things brought by this patch: - Update the rust-vmm/kvm-ioctls dependency to benefit from latest patches including the support for split irqchip, and the vector being returned when a VM exit is caused by an EOI. - Enable the split irqchip (which means no IOAPIC or PIC is emulated in kernel). This is done conditionally based on the support of the TSC_DEADLINE_TIMER from both KVM and the underlying CPU. The dependency on TSC_DEADLINE_TIMER is related to KVM which does not support creating the in kernel PIT if it has a split irqchip. - Rely on callbacks to handle the following use cases: - in kernel IOAPIC + serial IRQ (pin based) - in kernel IOAPIC + virtio-pci MSI-X - in kernel IOAPIC + virtio-pci IRQ (pin based) - userspace IOAPIC + serial IRQ (pin based) - userspace IOAPIC + virtio-pci MSI-X - userspace IOAPIC + virtio-pci IRQ (pin based) Fixes #13 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-06-18 17:31:50 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump cast from 0.2.2 to 0.2.3 Bumps [cast](https://github.com/japaric/cast.rs) from 0.2.2 to 0.2.3. - [Release notes](https://github.com/japaric/cast.rs/releases) - [Changelog](https://github.com/japaric/cast.rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/japaric/cast.rs/compare/v0.2.2...v0.2.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-16 23:53:59 +00:00
dependencies = [
"rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
vmm: Integrate userspace IOAPIC The previous commit introduced a userspace implementation of an IOAPIC and this commits aims to plumb it into the cloud-hypervisor VMM. Here is the list of new things brought by this patch: - Update the rust-vmm/kvm-ioctls dependency to benefit from latest patches including the support for split irqchip, and the vector being returned when a VM exit is caused by an EOI. - Enable the split irqchip (which means no IOAPIC or PIC is emulated in kernel). This is done conditionally based on the support of the TSC_DEADLINE_TIMER from both KVM and the underlying CPU. The dependency on TSC_DEADLINE_TIMER is related to KVM which does not support creating the in kernel PIT if it has a split irqchip. - Rely on callbacks to handle the following use cases: - in kernel IOAPIC + serial IRQ (pin based) - in kernel IOAPIC + virtio-pci MSI-X - in kernel IOAPIC + virtio-pci IRQ (pin based) - userspace IOAPIC + serial IRQ (pin based) - userspace IOAPIC + virtio-pci MSI-X - userspace IOAPIC + virtio-pci IRQ (pin based) Fixes #13 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-06-18 17:31:50 +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(deps): bump cc from 1.0.47 to 1.0.48 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.47 to 1.0.48. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.47...1.0.48) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-04 16:34:10 +00:00
version = "1.0.48"
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: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
[[package]]
name = "cfg-if"
build(deps): bump cfg-if from 0.1.9 to 0.1.10 Bumps [cfg-if](https://github.com/alexcrichton/cfg-if) from 0.1.9 to 0.1.10. - [Release notes](https://github.com/alexcrichton/cfg-if/releases) - [Commits](https://github.com/alexcrichton/cfg-if/compare/0.1.9...0.1.10) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-24 19:45:47 +00:00
version = "0.1.10"
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"
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
[[package]]
name = "clap"
build(deps): bump clap from 2.27.1 to 2.33.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.27.1 to 2.33.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/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:22:53 +00:00
version = "2.33.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"
dependencies = [
build(deps): bump clap from 2.27.1 to 2.33.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.27.1 to 2.33.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/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:22:53 +00:00
"ansi_term 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)",
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"atty 0.2.13 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump ssh2 from 0.5.0 to 0.6.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.5.0 to 0.6.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.5.0...0.6.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-08 18:43:54 +00:00
"bitflags 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump clap from 2.27.1 to 2.33.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.27.1 to 2.33.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/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:22:53 +00:00
"strsim 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)",
"textwrap 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump unicode-width from 0.1.6 to 0.1.7 Bumps [unicode-width](https://github.com/unicode-rs/unicode-width) from 0.1.6 to 0.1.7. - [Release notes](https://github.com/unicode-rs/unicode-width/releases) - [Commits](https://github.com/unicode-rs/unicode-width/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-05 18:24:09 +00:00
"unicode-width 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
"vec_map 0.8.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
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"
Fix Cargo.lock Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-28 22:04:07 +00:00
version = "0.3.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 = [
build(deps): bump clap from 2.27.1 to 2.33.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.27.1 to 2.33.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/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:22:53 +00:00
"clap 2.33.0 (registry+https://github.com/rust-lang/crates.io-index)",
tests: Switch to launching by command Launch the test binary by command rather than using using the vmm layer. This makes it easier to manage the running VM as you can explicitly kill it. Also switch to using credibility for the tests which catches assertions and continues with subsequent commands and reports the issues at the end. This means it is possible to cleanup even on failed test runs. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-06-04 15:24:39 +00:00
"credibility 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump dirs from 2.0.1 to 2.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 2.0.1 to 2.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>
2019-08-02 07:51:51 +00:00
"dirs 2.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"epoll 4.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
main: Add logging support controlled by command line This makes the log macros (error!, warn!, info!, etc) in the code work. It currently defaults to showing only error! messages, but by passing an increasing number of "-v"s on the command line the verbosity can be increased. By default log output goes onto stderr but it can also be sent to a file. Fixes: #121 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-07 11:19:21 +00:00
"log 0.4.8 (registry+https://github.com/rust-lang/crates.io-index)",
src: Add vhost-user-net backend Create vhost-user-net backend with Tap interface, to offload network transaction from cloud-hypervisor. The goal is to provide flexibility about the backend being in use, but also more security as it will allow users to isolate the backend with different security profiles since it will run as a dedicated process on the host. Signed-off-by: Cathy Zhang <cathy.zhang@intel.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-09-20 18:21:54 +00:00
"net_gen 0.1.0",
"net_util 0.1.0",
src: add vhost-user-blk backend Create a vhost-user-blk backend using vhost-user-backend and following the conventions established by the existing vhost-user-net implementation. This backend is based on https://github.com/slp/vhost-user-backend, but a bit simplified, making it closer to the original implementation in Firecracker. The main features missing are EVENT_IDX, support for asynchronous I/O and multiqueue, but it's still fully functional and provides a good starting point for evolving it into a more complete implementation. Signed-off-by: Sergio Lopez <slp@redhat.com>
2019-10-23 14:36:01 +00:00
"qcow 0.1.0",
build(deps): bump ssh2 from 0.5.0 to 0.6.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.5.0 to 0.6.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.5.0...0.6.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-08 18:43:54 +00:00
"ssh2 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)",
tests: Use a temporary directory for the temporary test files Use the tempdir crate to create a temporary directory that is deleted when the structure goes out of scope. Use this temporary directory for all temporary test files created by the tests. The cloud init file is still in /tmp as that is created by the test wrapper code. This is the first stage towards being able to run the integration tests in parallel. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-18 07:57:01 +00:00
"tempdir 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
src: Add vhost-user-net backend Create vhost-user-net backend with Tap interface, to offload network transaction from cloud-hypervisor. The goal is to provide flexibility about the backend being in use, but also more security as it will allow users to isolate the backend with different security profiles since it will run as a dedicated process on the host. Signed-off-by: Cathy Zhang <cathy.zhang@intel.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-09-20 18:21:54 +00:00
"vhost_rs 0.1.0",
"vhost_user_backend 0.1.0",
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
"vhost_user_fs 0.1.0",
Cargo: Move virtio-bindings to crates.io v0.1.0 was just published. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-10 07:38:42 +00:00
"virtio-bindings 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"vm-device 0.1.0",
src: Add vhost-user-net backend Create vhost-user-net backend with Tap interface, to offload network transaction from cloud-hypervisor. The goal is to provide flexibility about the backend being in use, but also more security as it will allow users to isolate the backend with different security profiles since it will run as a dedicated process on the host. Signed-off-by: Cathy Zhang <cathy.zhang@intel.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-09-20 18:21:54 +00:00
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
"vm-virtio 0.1.0",
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 0.1.0",
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "cloudabi"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump ssh2 from 0.5.0 to 0.6.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.5.0 to 0.6.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.5.0...0.6.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-08 18:43:54 +00:00
"bitflags 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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 = "constant_time_eq"
build(deps): bump constant_time_eq from 0.1.3 to 0.1.4 Bumps [constant_time_eq](https://github.com/cesarb/constant_time_eq) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/cesarb/constant_time_eq/releases) - [Commits](https://github.com/cesarb/constant_time_eq/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-21 08:25:16 +00:00
version = "0.1.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"
tests: Switch to launching by command Launch the test binary by command rather than using using the vmm layer. This makes it easier to manage the running VM as you can explicitly kill it. Also switch to using credibility for the tests which catches assertions and continues with subsequent commands and reports the issues at the end. This means it is possible to cleanup even on failed test runs. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-06-04 15:24:39 +00:00
[[package]]
name = "credibility"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump failure from 0.1.5 to 0.1.6 Bumps [failure](https://github.com/rust-lang-nursery/failure) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/rust-lang-nursery/failure/releases) - [Changelog](https://github.com/rust-lang-nursery/failure/blob/master/RELEASES.md) - [Commits](https://github.com/rust-lang-nursery/failure/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-12 03:31:31 +00:00
"failure 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
"failure_derive 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
tests: Switch to launching by command Launch the test binary by command rather than using using the vmm layer. This makes it easier to manage the running VM as you can explicitly kill it. Also switch to using credibility for the tests which catches assertions and continues with subsequent commands and reports the issues at the end. This means it is possible to cleanup even on failed test runs. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-06-04 15:24:39 +00:00
]
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
[[package]]
name = "crossbeam-utils"
version = "0.6.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump cfg-if from 0.1.9 to 0.1.10 Bumps [cfg-if](https://github.com/alexcrichton/cfg-if) from 0.1.9 to 0.1.10. - [Release notes](https://github.com/alexcrichton/cfg-if/releases) - [Commits](https://github.com/alexcrichton/cfg-if/compare/0.1.9...0.1.10) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-24 19:45:47 +00:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
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
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +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 = [
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"epoll 4.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"kvm-bindings 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
"kvm-ioctls 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"log 0.4.8 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tempfile 3.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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"
build(deps): bump dirs from 2.0.1 to 2.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 2.0.1 to 2.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>
2019-08-02 07:51:51 +00:00
version = "2.0.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
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump cfg-if from 0.1.9 to 0.1.10 Bumps [cfg-if](https://github.com/alexcrichton/cfg-if) from 0.1.9 to 0.1.10. - [Release notes](https://github.com/alexcrichton/cfg-if/releases) - [Commits](https://github.com/alexcrichton/cfg-if/compare/0.1.9...0.1.10) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-24 19:45:47 +00:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump dirs from 2.0.1 to 2.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 2.0.1 to 2.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>
2019-08-02 07:51:51 +00:00
"dirs-sys 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)",
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
]
[[package]]
name = "dirs-sys"
build(deps): bump dirs from 2.0.1 to 2.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 2.0.1 to 2.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>
2019-08-02 07:51:51 +00:00
version = "0.3.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"
dependencies = [
build(deps): bump cfg-if from 0.1.9 to 0.1.10 Bumps [cfg-if](https://github.com/alexcrichton/cfg-if) from 0.1.9 to 0.1.10. - [Release notes](https://github.com/alexcrichton/cfg-if/releases) - [Commits](https://github.com/alexcrichton/cfg-if/compare/0.1.9...0.1.10) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-24 19:45:47 +00:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
"redox_users 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
]
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"
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
version = "4.0.1"
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-03-07 13:56:43 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump ssh2 from 0.5.0 to 0.6.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.5.0 to 0.6.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.5.0...0.6.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-08 18:43:54 +00:00
"bitflags 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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 = "failure"
build(deps): bump failure from 0.1.5 to 0.1.6 Bumps [failure](https://github.com/rust-lang-nursery/failure) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/rust-lang-nursery/failure/releases) - [Changelog](https://github.com/rust-lang-nursery/failure/blob/master/RELEASES.md) - [Commits](https://github.com/rust-lang-nursery/failure/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-12 03:31:31 +00:00
version = "0.1.6"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump backtrace from 0.3.39 to 0.3.40 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.39 to 0.3.40. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.39...0.3.40) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-17 22:23:06 +00:00
"backtrace 0.3.40 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump failure from 0.1.5 to 0.1.6 Bumps [failure](https://github.com/rust-lang-nursery/failure) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/rust-lang-nursery/failure/releases) - [Changelog](https://github.com/rust-lang-nursery/failure/blob/master/RELEASES.md) - [Commits](https://github.com/rust-lang-nursery/failure/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-12 03:31:31 +00:00
"failure_derive 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "failure_derive"
build(deps): bump failure from 0.1.5 to 0.1.6 Bumps [failure](https://github.com/rust-lang-nursery/failure) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/rust-lang-nursery/failure/releases) - [Changelog](https://github.com/rust-lang-nursery/failure/blob/master/RELEASES.md) - [Commits](https://github.com/rust-lang-nursery/failure/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-12 03:31:31 +00:00
version = "0.1.6"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump proc-macro2 from 1.0.5 to 1.0.6 Bumps [proc-macro2](https://github.com/alexcrichton/proc-macro2) from 1.0.5 to 1.0.6. - [Release notes](https://github.com/alexcrichton/proc-macro2/releases) - [Commits](https://github.com/alexcrichton/proc-macro2/compare/1.0.5...1.0.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-19 22:04:29 +00:00
"proc-macro2 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump failure from 0.1.5 to 0.1.6 Bumps [failure](https://github.com/rust-lang-nursery/failure) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/rust-lang-nursery/failure/releases) - [Changelog](https://github.com/rust-lang-nursery/failure/blob/master/RELEASES.md) - [Commits](https://github.com/rust-lang-nursery/failure/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-12 03:31:31 +00:00
"quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump syn from 1.0.9 to 1.0.11 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.9 to 1.0.11. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.9...1.0.11) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-01 01:16:15 +00:00
"syn 1.0.11 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump synstructure from 0.12.2 to 0.12.3 Bumps [synstructure](https://github.com/mystor/synstructure) from 0.12.2 to 0.12.3. - [Release notes](https://github.com/mystor/synstructure/releases) - [Commits](https://github.com/mystor/synstructure/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-11 18:52:53 +00:00
"synstructure 0.12.3 (registry+https://github.com/rust-lang/crates.io-index)",
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: 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 = "fuchsia-cprng"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
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(deps): bump getrandom from 0.1.12 to 0.1.13 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.1.12 to 0.1.13. - [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.12...v0.1.13) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-25 12:33:16 +00:00
version = "0.1.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"
dependencies = [
build(deps): bump cfg-if from 0.1.9 to 0.1.10 Bumps [cfg-if](https://github.com/alexcrichton/cfg-if) from 0.1.9 to 0.1.10. - [Release notes](https://github.com/alexcrichton/cfg-if/releases) - [Commits](https://github.com/alexcrichton/cfg-if/compare/0.1.9...0.1.10) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-24 19:45:47 +00:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump getrandom from 0.1.11 to 0.1.12 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.1.11 to 0.1.12. - [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.11...v0.1.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-06 13:33:36 +00:00
"wasi 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
vm-virtio: Add virtio console device for single port operation The virtio console device is a console for the communication between the host and guest userspace. It has two parts: the device and the driver. The console device is implemented here as a virtio-pci device to the guest. On the other side, the guest OS expected to have a character device driver which provides an interface to the userspace applications. The console device can have multiple ports where each port has one transmit queue and one receive queue. The current implementation only supports one port. For data IO communication, one or more empty buffers are placed in the receive queue for incoming data, and outgoing characters are placed in the transmit queue. Details spec can be found from the following link. https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.pdf#e7 Apart from the console, for the communication between guest and host, the Cloud Hypervisor has a legacy serial device implemented. However, the implementation of a console device lets us be independent of legacy pin-based interrupts without losing the logs and access to the VM. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-22 18:50:56 +00:00
]
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
[[package]]
name = "glob"
version = "0.2.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "ipnetwork"
version = "0.14.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump serde from 1.0.102 to 1.0.103 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.102 to 1.0.103. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.102...v1.0.103) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 17:16:41 +00:00
"serde 1.0.103 (registry+https://github.com/rust-lang/crates.io-index)",
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"
version = "0.4.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "kernel32-sys"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
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"
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
version = "0.2.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
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: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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"
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
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = [
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
"kvm-bindings 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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"
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(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
version = "0.2.66"
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"
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(deps): bump ssh2 from 0.4.0 to 0.5.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.4.0...0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-20 10:43:20 +00:00
version = "0.2.13"
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"
dependencies = [
build(deps): bump cc from 1.0.47 to 1.0.48 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.47 to 1.0.48. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.47...1.0.48) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-04 16:34:10 +00:00
"cc 1.0.48 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"libz-sys 1.0.25 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump openssl-sys from 0.9.52 to 0.9.53 Bumps [openssl-sys](https://github.com/sfackler/rust-openssl) from 0.9.52 to 0.9.53. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-sys-v0.9.52...openssl-sys-v0.9.53) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 16:35:38 +00:00
"openssl-sys 0.9.53 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump pkg-config from 0.3.16 to 0.3.17 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.16 to 0.3.17. - [Release notes](https://github.com/rust-lang/pkg-config-rs/releases) - [Changelog](https://github.com/rust-lang/pkg-config-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/pkg-config-rs/compare/0.3.16...0.3.17) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-02 09:47:40 +00:00
"pkg-config 0.3.17 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump vcpkg from 0.2.7 to 0.2.8 Bumps [vcpkg](https://github.com/mcgoo/vcpkg-rs) from 0.2.7 to 0.2.8. - [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.7...vcpkg-rs-0.2.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-02 03:45:15 +00:00
"vcpkg 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
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"
version = "1.0.25"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump cc from 1.0.47 to 1.0.48 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.47 to 1.0.48. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.47...1.0.48) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-04 16:34:10 +00:00
"cc 1.0.48 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump pkg-config from 0.3.16 to 0.3.17 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.16 to 0.3.17. - [Release notes](https://github.com/rust-lang/pkg-config-rs/releases) - [Changelog](https://github.com/rust-lang/pkg-config-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/pkg-config-rs/compare/0.3.16...0.3.17) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-02 09:47:40 +00:00
"pkg-config 0.3.17 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump vcpkg from 0.2.7 to 0.2.8 Bumps [vcpkg](https://github.com/mcgoo/vcpkg-rs) from 0.2.7 to 0.2.8. - [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.7...vcpkg-rs-0.2.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-02 03:45:15 +00:00
"vcpkg 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
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"
version = "0.1.0"
build(deps): bump linux-loader from `b270081` to `6cf23a8` Bumps [linux-loader](https://github.com/rust-vmm/linux-loader) from `b270081` to `6cf23a8`. - [Release notes](https://github.com/rust-vmm/linux-loader/releases) - [Commits](https://github.com/rust-vmm/linux-loader/compare/b2700818add982aa361842a0b8da776b3d1b5cb3...6cf23a8bca79b5517fa11f90f7f9d828a8290e9d) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-17 06:15:50 +00:00
source = "git+https://github.com/rust-vmm/linux-loader#6cf23a8bca79b5517fa11f90f7f9d828a8290e9d"
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 = [
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
]
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 = "log"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump log from 0.4.6 to 0.4.8 Bumps [log](https://github.com/rust-lang/log) from 0.4.6 to 0.4.8. - [Release notes](https://github.com/rust-lang/log/releases) - [Changelog](https://github.com/rust-lang-nursery/log/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/log/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 07:52:14 +00:00
"log 0.4.8 (registry+https://github.com/rust-lang/crates.io-index)",
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: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
[[package]]
name = "log"
build(deps): bump log from 0.4.6 to 0.4.8 Bumps [log](https://github.com/rust-lang/log) from 0.4.6 to 0.4.8. - [Release notes](https://github.com/rust-lang/log/releases) - [Changelog](https://github.com/rust-lang-nursery/log/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/log/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 07:52:14 +00:00
version = "0.4.8"
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"
dependencies = [
build(deps): bump cfg-if from 0.1.9 to 0.1.10 Bumps [cfg-if](https://github.com/alexcrichton/cfg-if) from 0.1.9 to 0.1.10. - [Release notes](https://github.com/alexcrichton/cfg-if/releases) - [Commits](https://github.com/alexcrichton/cfg-if/compare/0.1.9...0.1.10) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-24 19:45:47 +00:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +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 = "memchr"
version = "2.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
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
source = "git+https://github.com/firecracker-microvm/firecracker#be978312eaf5f53abc61a130ec0ca4ab344ffacd"
dependencies = [
"epoll 4.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
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
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 = [
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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 = [
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
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"net_gen 0.1.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
"pnet 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump dirs from 2.0.1 to 2.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 2.0.1 to 2.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>
2019-08-02 07:51:51 +00:00
"rand 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump serde from 1.0.102 to 1.0.103 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.102 to 1.0.103. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.102...v1.0.103) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 17:16:41 +00:00
"serde 1.0.103 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump serde_json from 1.0.43 to 1.0.44 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.43 to 1.0.44. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.43...v1.0.44) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-04 20:38:28 +00:00
"serde_json 1.0.44 (registry+https://github.com/rust-lang/crates.io-index)",
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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(deps): bump openssl-sys from 0.9.52 to 0.9.53 Bumps [openssl-sys](https://github.com/sfackler/rust-openssl) from 0.9.52 to 0.9.53. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-sys-v0.9.52...openssl-sys-v0.9.53) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 16:35:38 +00:00
version = "0.9.53"
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"
dependencies = [
build(deps): bump autocfg from 0.1.6 to 0.1.7 Bumps [autocfg](https://github.com/cuviper/autocfg) from 0.1.6 to 0.1.7. - [Release notes](https://github.com/cuviper/autocfg/releases) - [Commits](https://github.com/cuviper/autocfg/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-20 18:05:52 +00:00
"autocfg 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump cc from 1.0.47 to 1.0.48 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.47 to 1.0.48. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.47...1.0.48) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-04 16:34:10 +00:00
"cc 1.0.48 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump pkg-config from 0.3.16 to 0.3.17 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.16 to 0.3.17. - [Release notes](https://github.com/rust-lang/pkg-config-rs/releases) - [Changelog](https://github.com/rust-lang/pkg-config-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/pkg-config-rs/compare/0.3.16...0.3.17) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-02 09:47:40 +00:00
"pkg-config 0.3.17 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump vcpkg from 0.2.7 to 0.2.8 Bumps [vcpkg](https://github.com/mcgoo/vcpkg-rs) from 0.2.7 to 0.2.8. - [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.7...vcpkg-rs-0.2.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-02 03:45:15 +00:00
"vcpkg 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
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: 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 = [
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
"devices 0.1.0",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"log 0.4.8 (registry+https://github.com/rust-lang/crates.io-index)",
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
"vm-allocator 0.1.0",
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +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 = "pkg-config"
build(deps): bump pkg-config from 0.3.16 to 0.3.17 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.16 to 0.3.17. - [Release notes](https://github.com/rust-lang/pkg-config-rs/releases) - [Changelog](https://github.com/rust-lang/pkg-config-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/pkg-config-rs/compare/0.3.16...0.3.17) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-02 09:47:40 +00:00
version = "0.3.17"
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: 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"
version = "0.22.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"ipnetwork 0.14.0 (registry+https://github.com/rust-lang/crates.io-index)",
"pnet_base 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
"pnet_datalink 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
"pnet_packet 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
"pnet_sys 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
"pnet_transport 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "pnet_base"
version = "0.22.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "pnet_datalink"
version = "0.22.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"ipnetwork 0.14.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"pnet_base 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
"pnet_sys 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "pnet_macros"
build(deps): bump pnet_macros from 0.22.0 to 0.23.0 Bumps [pnet_macros](https://github.com/libpnet/libpnet) from 0.22.0 to 0.23.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-06 12:53:15 +00:00
version = "0.23.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"
dependencies = [
"regex 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
"syntex 0.42.2 (registry+https://github.com/rust-lang/crates.io-index)",
"syntex_syntax 0.42.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "pnet_macros_support"
version = "0.22.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"pnet_base 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "pnet_packet"
version = "0.22.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"glob 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)",
"pnet_base 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump pnet_macros from 0.22.0 to 0.23.0 Bumps [pnet_macros](https://github.com/libpnet/libpnet) from 0.22.0 to 0.23.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-06 12:53:15 +00:00
"pnet_macros 0.23.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"pnet_macros_support 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
"syntex 0.42.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "pnet_sys"
version = "0.22.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
"ws2_32-sys 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "pnet_transport"
version = "0.22.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"pnet_base 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
"pnet_packet 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
"pnet_sys 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "ppv-lite86"
build(deps): bump ppv-lite86 from 0.2.5 to 0.2.6 Bumps [ppv-lite86](https://github.com/cryptocorrosion/cryptocorrosion) from 0.2.5 to 0.2.6. - [Release notes](https://github.com/cryptocorrosion/cryptocorrosion/releases) - [Commits](https://github.com/cryptocorrosion/cryptocorrosion/compare/ppv-lite86-0.2.5...ppv-lite86-0.2.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-21 16:44:04 +00:00
version = "0.2.6"
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(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(deps): bump proc-macro2 from 1.0.5 to 1.0.6 Bumps [proc-macro2](https://github.com/alexcrichton/proc-macro2) from 1.0.5 to 1.0.6. - [Release notes](https://github.com/alexcrichton/proc-macro2/releases) - [Commits](https://github.com/alexcrichton/proc-macro2/compare/1.0.5...1.0.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-19 22:04:29 +00:00
version = "1.0.6"
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"
dependencies = [
"unicode-xid 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
qcow: Add qcow support Extracted from crosvm (commit:f82d632), with clippy fixes. Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
2019-04-29 19:32:56 +00:00
[[package]]
name = "qcow"
version = "0.1.0"
dependencies = [
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"log 0.4.8 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump remain from 0.1.4 to 0.1.5 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.4 to 0.1.5. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.4...0.1.5) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 16:36:03 +00:00
"remain 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tempfile 3.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
qcow: Add qcow support Extracted from crosvm (commit:f82d632), with clippy fixes. Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
2019-04-29 19:32:56 +00:00
]
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
[[package]]
name = "quote"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump proc-macro2 from 1.0.5 to 1.0.6 Bumps [proc-macro2](https://github.com/alexcrichton/proc-macro2) from 1.0.5 to 1.0.6. - [Release notes](https://github.com/alexcrichton/proc-macro2/releases) - [Commits](https://github.com/alexcrichton/proc-macro2/compare/1.0.5...1.0.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-19 22:04:29 +00:00
"proc-macro2 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
]
tests: Use a temporary directory for the temporary test files Use the tempdir crate to create a temporary directory that is deleted when the structure goes out of scope. Use this temporary directory for all temporary test files created by the tests. The cloud init file is still in /tmp as that is created by the test wrapper code. This is the first stage towards being able to run the integration tests in parallel. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-18 07:57:01 +00:00
[[package]]
name = "rand"
version = "0.4.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"fuchsia-cprng 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
tests: Use a temporary directory for the temporary test files Use the tempdir crate to create a temporary directory that is deleted when the structure goes out of scope. Use this temporary directory for all temporary test files created by the tests. The cloud init file is still in /tmp as that is created by the test wrapper code. This is the first stage towards being able to run the integration tests in parallel. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-18 07:57:01 +00:00
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
"rdrand 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "rand"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump getrandom from 0.1.12 to 0.1.13 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.1.12 to 0.1.13. - [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.12...v0.1.13) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-25 12:33:16 +00:00
"getrandom 0.1.13 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"rand_chacha 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"rand_core 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
"rand_hc 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "rand_chacha"
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
version = "0.2.1"
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"
dependencies = [
build(deps): bump c2-chacha from 0.2.2 to 0.2.3 Bumps [c2-chacha](https://github.com/cryptocorrosion/cryptocorrosion) from 0.2.2 to 0.2.3. - [Release notes](https://github.com/cryptocorrosion/cryptocorrosion/releases) - [Commits](https://github.com/cryptocorrosion/cryptocorrosion/compare/c2-chacha-0.2.2...c2-chacha-0.2.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-21 17:12:07 +00:00
"c2-chacha 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
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
"rand_core 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "rand_core"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"rand_core 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "rand_core"
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
version = "0.4.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "rand_core"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump getrandom from 0.1.12 to 0.1.13 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.1.12 to 0.1.13. - [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.12...v0.1.13) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-25 12:33:16 +00:00
"getrandom 0.1.13 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "rand_hc"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"rand_core 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "rand_os"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"cloudabi 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
"fuchsia-cprng 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"rand_core 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"rdrand 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "rdrand"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "redox_syscall"
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
version = "0.1.56"
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"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
[[package]]
name = "redox_users"
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
version = "0.3.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"
dependencies = [
build(deps): bump failure from 0.1.5 to 0.1.6 Bumps [failure](https://github.com/rust-lang-nursery/failure) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/rust-lang-nursery/failure/releases) - [Changelog](https://github.com/rust-lang-nursery/failure/blob/master/RELEASES.md) - [Commits](https://github.com/rust-lang-nursery/failure/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-12 03:31:31 +00:00
"failure 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"rand_os 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)",
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
"redox_syscall 0.1.56 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump rust-argon2 from 0.5.0 to 0.5.1 Bumps [rust-argon2](https://github.com/sru-systems/rust-argon2) from 0.5.0 to 0.5.1. - [Release notes](https://github.com/sru-systems/rust-argon2/releases) - [Changelog](https://github.com/sru-systems/rust-argon2/blob/master/CHANGELOG.md) - [Commits](https://github.com/sru-systems/rust-argon2/compare/0.5.0...0.5.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 07:24:31 +00:00
"rust-argon2 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)",
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"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"aho-corasick 0.6.10 (registry+https://github.com/rust-lang/crates.io-index)",
"memchr 2.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump regex-syntax from 0.6.11 to 0.6.12 Bumps [regex-syntax](https://github.com/rust-lang/regex) from 0.6.11 to 0.6.12. - [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/regex-syntax-0.6.11...regex-syntax-0.6.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-03 17:05:22 +00:00
"regex-syntax 0.6.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"thread_local 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump utf8-ranges from 1.0.3 to 1.0.4 Bumps [utf8-ranges](https://github.com/BurntSushi/utf8-ranges) from 1.0.3 to 1.0.4. - [Release notes](https://github.com/BurntSushi/utf8-ranges/releases) - [Commits](https://github.com/BurntSushi/utf8-ranges/compare/1.0.3...1.0.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-05 10:34:09 +00:00
"utf8-ranges 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)",
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(deps): bump regex-syntax from 0.6.11 to 0.6.12 Bumps [regex-syntax](https://github.com/rust-lang/regex) from 0.6.11 to 0.6.12. - [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/regex-syntax-0.6.11...regex-syntax-0.6.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-03 17:05:22 +00:00
version = "0.6.12"
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"
qcow: Add qcow support Extracted from crosvm (commit:f82d632), with clippy fixes. Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
2019-04-29 19:32:56 +00:00
[[package]]
name = "remain"
build(deps): bump remain from 0.1.4 to 0.1.5 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.4 to 0.1.5. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.4...0.1.5) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 16:36:03 +00:00
version = "0.1.5"
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"
dependencies = [
build(deps): bump proc-macro2 from 1.0.5 to 1.0.6 Bumps [proc-macro2](https://github.com/alexcrichton/proc-macro2) from 1.0.5 to 1.0.6. - [Release notes](https://github.com/alexcrichton/proc-macro2/releases) - [Commits](https://github.com/alexcrichton/proc-macro2/compare/1.0.5...1.0.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-19 22:04:29 +00:00
"proc-macro2 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump syn from 1.0.9 to 1.0.11 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.9 to 1.0.11. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.9...1.0.11) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-01 01:16:15 +00:00
"syn 1.0.11 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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 = "remove_dir_all"
vmm: Integrate userspace IOAPIC The previous commit introduced a userspace implementation of an IOAPIC and this commits aims to plumb it into the cloud-hypervisor VMM. Here is the list of new things brought by this patch: - Update the rust-vmm/kvm-ioctls dependency to benefit from latest patches including the support for split irqchip, and the vector being returned when a VM exit is caused by an EOI. - Enable the split irqchip (which means no IOAPIC or PIC is emulated in kernel). This is done conditionally based on the support of the TSC_DEADLINE_TIMER from both KVM and the underlying CPU. The dependency on TSC_DEADLINE_TIMER is related to KVM which does not support creating the in kernel PIT if it has a split irqchip. - Rely on callbacks to handle the following use cases: - in kernel IOAPIC + serial IRQ (pin based) - in kernel IOAPIC + virtio-pci MSI-X - in kernel IOAPIC + virtio-pci IRQ (pin based) - userspace IOAPIC + serial IRQ (pin based) - userspace IOAPIC + virtio-pci MSI-X - userspace IOAPIC + virtio-pci IRQ (pin based) Fixes #13 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-06-18 17:31:50 +00:00
version = "0.5.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
[[package]]
name = "rust-argon2"
build(deps): bump rust-argon2 from 0.5.0 to 0.5.1 Bumps [rust-argon2](https://github.com/sru-systems/rust-argon2) from 0.5.0 to 0.5.1. - [Release notes](https://github.com/sru-systems/rust-argon2/releases) - [Changelog](https://github.com/sru-systems/rust-argon2/blob/master/CHANGELOG.md) - [Commits](https://github.com/sru-systems/rust-argon2/compare/0.5.0...0.5.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 07:24:31 +00:00
version = "0.5.1"
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"base64 0.10.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump blake2b_simd from 0.5.8 to 0.5.9 Bumps [blake2b_simd](https://github.com/oconnor663/blake2_simd) from 0.5.8 to 0.5.9. - [Release notes](https://github.com/oconnor663/blake2_simd/releases) - [Commits](https://github.com/oconnor663/blake2_simd/compare/0.5.8...0.5.9) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-07 00:07:00 +00:00
"blake2b_simd 0.5.9 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump rust-argon2 from 0.5.0 to 0.5.1 Bumps [rust-argon2](https://github.com/sru-systems/rust-argon2) from 0.5.0 to 0.5.1. - [Release notes](https://github.com/sru-systems/rust-argon2/releases) - [Changelog](https://github.com/sru-systems/rust-argon2/blob/master/CHANGELOG.md) - [Commits](https://github.com/sru-systems/rust-argon2/compare/0.5.0...0.5.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 07:24:31 +00:00
"crossbeam-utils 0.6.6 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +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 = "rustc-demangle"
build(deps): bump rustc-demangle from 0.1.15 to 0.1.16 Bumps [rustc-demangle](https://github.com/alexcrichton/rustc-demangle) from 0.1.15 to 0.1.16. - [Release notes](https://github.com/alexcrichton/rustc-demangle/releases) - [Commits](https://github.com/alexcrichton/rustc-demangle/compare/0.1.15...0.1.16) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-14 07:18:12 +00:00
version = "0.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: 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 = "rustc-serialize"
version = "0.3.24"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump cast from 0.2.2 to 0.2.3 Bumps [cast](https://github.com/japaric/cast.rs) from 0.2.2 to 0.2.3. - [Release notes](https://github.com/japaric/cast.rs/releases) - [Changelog](https://github.com/japaric/cast.rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/japaric/cast.rs/compare/v0.2.2...v0.2.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-16 23:53:59 +00:00
[[package]]
name = "rustc_version"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"semver 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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(deps): bump ryu from 1.0.1 to 1.0.2 Bumps [ryu](https://github.com/dtolnay/ryu) from 1.0.1 to 1.0.2. - [Release notes](https://github.com/dtolnay/ryu/releases) - [Commits](https://github.com/dtolnay/ryu/compare/1.0.1...1.0.2) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-15 04:31:53 +00:00
version = "1.0.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(deps): bump cast from 0.2.2 to 0.2.3 Bumps [cast](https://github.com/japaric/cast.rs) from 0.2.2 to 0.2.3. - [Release notes](https://github.com/japaric/cast.rs/releases) - [Changelog](https://github.com/japaric/cast.rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/japaric/cast.rs/compare/v0.2.2...v0.2.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-16 23:53:59 +00:00
[[package]]
name = "semver"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"semver-parser 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "semver-parser"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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(deps): bump serde from 1.0.102 to 1.0.103 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.102 to 1.0.103. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.102...v1.0.103) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 17:16:41 +00:00
version = "1.0.103"
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"
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(deps): bump serde_derive from 1.0.102 to 1.0.103 Bumps [serde_derive](https://github.com/serde-rs/serde) from 1.0.102 to 1.0.103. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.102...v1.0.103) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 19:55:42 +00:00
version = "1.0.103"
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"
dependencies = [
build(deps): bump proc-macro2 from 1.0.5 to 1.0.6 Bumps [proc-macro2](https://github.com/alexcrichton/proc-macro2) from 1.0.5 to 1.0.6. - [Release notes](https://github.com/alexcrichton/proc-macro2/releases) - [Commits](https://github.com/alexcrichton/proc-macro2/compare/1.0.5...1.0.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-19 22:04:29 +00:00
"proc-macro2 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump syn from 1.0.9 to 1.0.11 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.9 to 1.0.11. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.9...1.0.11) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-01 01:16:15 +00:00
"syn 1.0.11 (registry+https://github.com/rust-lang/crates.io-index)",
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(deps): bump serde_json from 1.0.43 to 1.0.44 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.43 to 1.0.44. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.43...v1.0.44) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-04 20:38:28 +00:00
version = "1.0.44"
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"
dependencies = [
"itoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump ryu from 1.0.1 to 1.0.2 Bumps [ryu](https://github.com/dtolnay/ryu) from 1.0.1 to 1.0.2. - [Release notes](https://github.com/dtolnay/ryu/releases) - [Commits](https://github.com/dtolnay/ryu/compare/1.0.1...1.0.2) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-15 04:31:53 +00:00
"ryu 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump serde from 1.0.102 to 1.0.103 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.102 to 1.0.103. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.102...v1.0.103) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 17:16:41 +00:00
"serde 1.0.103 (registry+https://github.com/rust-lang/crates.io-index)",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
]
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
[[package]]
name = "signal-hook"
build(deps): bump signal-hook from 0.1.11 to 0.1.12 Bumps [signal-hook](https://github.com/vorner/signal-hook) from 0.1.11 to 0.1.12. - [Release notes](https://github.com/vorner/signal-hook/releases) - [Changelog](https://github.com/vorner/signal-hook/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/signal-hook/compare/v0.1.11...v0.1.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 20:34:19 +00:00
version = "0.1.12"
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"
dependencies = [
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump signal-hook-registry from 1.1.1 to 1.2.0 Bumps [signal-hook-registry](https://github.com/vorner/signal-hook) from 1.1.1 to 1.2.0. - [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.1.1...registry-v1.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 16:36:38 +00:00
"signal-hook-registry 1.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
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(deps): bump signal-hook-registry from 1.1.1 to 1.2.0 Bumps [signal-hook-registry](https://github.com/vorner/signal-hook) from 1.1.1 to 1.2.0. - [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.1.1...registry-v1.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 16:36:38 +00:00
version = "1.2.0"
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump arc-swap from 0.4.3 to 0.4.4 Bumps [arc-swap](https://github.com/vorner/arc-swap) from 0.4.3 to 0.4.4. - [Release notes](https://github.com/vorner/arc-swap/releases) - [Changelog](https://github.com/vorner/arc-swap/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/arc-swap/compare/v0.4.3...v0.4.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-17 11:34:27 +00:00
"arc-swap 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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(deps): bump ssh2 from 0.5.0 to 0.6.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.5.0 to 0.6.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.5.0...0.6.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-08 18:43:54 +00:00
version = "0.6.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"
dependencies = [
build(deps): bump ssh2 from 0.5.0 to 0.6.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.5.0 to 0.6.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.5.0...0.6.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-08 18:43:54 +00:00
"bitflags 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump ssh2 from 0.4.0 to 0.5.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.4.0...0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-20 10:43:20 +00:00
"libssh2-sys 0.2.13 (registry+https://github.com/rust-lang/crates.io-index)",
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: 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(deps): bump clap from 2.27.1 to 2.33.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.27.1 to 2.33.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/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:22:53 +00:00
version = "0.8.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(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
[[package]]
name = "syn"
build(deps): bump syn from 1.0.9 to 1.0.11 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.9 to 1.0.11. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.9...1.0.11) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-01 01:16:15 +00:00
version = "1.0.11"
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"
dependencies = [
build(deps): bump proc-macro2 from 1.0.5 to 1.0.6 Bumps [proc-macro2](https://github.com/alexcrichton/proc-macro2) from 1.0.5 to 1.0.6. - [Release notes](https://github.com/alexcrichton/proc-macro2/releases) - [Commits](https://github.com/alexcrichton/proc-macro2/compare/1.0.5...1.0.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-19 22:04:29 +00:00
"proc-macro2 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
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
"quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
"unicode-xid 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
[[package]]
name = "synstructure"
build(deps): bump synstructure from 0.12.2 to 0.12.3 Bumps [synstructure](https://github.com/mystor/synstructure) from 0.12.2 to 0.12.3. - [Release notes](https://github.com/mystor/synstructure/releases) - [Commits](https://github.com/mystor/synstructure/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-11 18:52:53 +00:00
version = "0.12.3"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump proc-macro2 from 1.0.5 to 1.0.6 Bumps [proc-macro2](https://github.com/alexcrichton/proc-macro2) from 1.0.5 to 1.0.6. - [Release notes](https://github.com/alexcrichton/proc-macro2/releases) - [Commits](https://github.com/alexcrichton/proc-macro2/compare/1.0.5...1.0.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-19 22:04:29 +00:00
"proc-macro2 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump failure from 0.1.5 to 0.1.6 Bumps [failure](https://github.com/rust-lang-nursery/failure) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/rust-lang-nursery/failure/releases) - [Changelog](https://github.com/rust-lang-nursery/failure/blob/master/RELEASES.md) - [Commits](https://github.com/rust-lang-nursery/failure/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-12 03:31:31 +00:00
"quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump syn from 1.0.9 to 1.0.11 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.9 to 1.0.11. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.9...1.0.11) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-01 01:16:15 +00:00
"syn 1.0.11 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump failure from 0.1.5 to 0.1.6 Bumps [failure](https://github.com/rust-lang-nursery/failure) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/rust-lang-nursery/failure/releases) - [Changelog](https://github.com/rust-lang-nursery/failure/blob/master/RELEASES.md) - [Commits](https://github.com/rust-lang-nursery/failure/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-12 03:31:31 +00:00
"unicode-xid 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "syntex"
version = "0.42.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"syntex_errors 0.42.0 (registry+https://github.com/rust-lang/crates.io-index)",
"syntex_syntax 0.42.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "syntex_errors"
version = "0.42.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"log 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)",
"rustc-serialize 0.3.24 (registry+https://github.com/rust-lang/crates.io-index)",
"syntex_pos 0.42.0 (registry+https://github.com/rust-lang/crates.io-index)",
"term 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
"unicode-xid 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "syntex_pos"
version = "0.42.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"rustc-serialize 0.3.24 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "syntex_syntax"
version = "0.42.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"bitflags 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"log 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)",
"rustc-serialize 0.3.24 (registry+https://github.com/rust-lang/crates.io-index)",
"syntex_errors 0.42.0 (registry+https://github.com/rust-lang/crates.io-index)",
"syntex_pos 0.42.0 (registry+https://github.com/rust-lang/crates.io-index)",
"term 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
"unicode-xid 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)",
]
tests: Use a temporary directory for the temporary test files Use the tempdir crate to create a temporary directory that is deleted when the structure goes out of scope. Use this temporary directory for all temporary test files created by the tests. The cloud init file is still in /tmp as that is created by the test wrapper code. This is the first stage towards being able to run the integration tests in parallel. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-18 07:57:01 +00:00
[[package]]
name = "tempdir"
version = "0.3.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"rand 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)",
"remove_dir_all 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "tempfile"
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
version = "3.1.0"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump cfg-if from 0.1.9 to 0.1.10 Bumps [cfg-if](https://github.com/alexcrichton/cfg-if) from 0.1.9 to 0.1.10. - [Release notes](https://github.com/alexcrichton/cfg-if/releases) - [Commits](https://github.com/alexcrichton/cfg-if/compare/0.1.9...0.1.10) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-24 19:45:47 +00:00
"cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"rand 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)",
"redox_syscall 0.1.56 (registry+https://github.com/rust-lang/crates.io-index)",
vmm: Integrate userspace IOAPIC The previous commit introduced a userspace implementation of an IOAPIC and this commits aims to plumb it into the cloud-hypervisor VMM. Here is the list of new things brought by this patch: - Update the rust-vmm/kvm-ioctls dependency to benefit from latest patches including the support for split irqchip, and the vector being returned when a VM exit is caused by an EOI. - Enable the split irqchip (which means no IOAPIC or PIC is emulated in kernel). This is done conditionally based on the support of the TSC_DEADLINE_TIMER from both KVM and the underlying CPU. The dependency on TSC_DEADLINE_TIMER is related to KVM which does not support creating the in kernel PIT if it has a split irqchip. - Rely on callbacks to handle the following use cases: - in kernel IOAPIC + serial IRQ (pin based) - in kernel IOAPIC + virtio-pci MSI-X - in kernel IOAPIC + virtio-pci IRQ (pin based) - userspace IOAPIC + serial IRQ (pin based) - userspace IOAPIC + virtio-pci MSI-X - userspace IOAPIC + virtio-pci IRQ (pin based) Fixes #13 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-06-18 17:31:50 +00:00
"remove_dir_all 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
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 = "term"
version = "0.4.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"kernel32-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
]
cloud-hypervisor: Application handling We will only support a --kernel option for now. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:39:34 +00:00
[[package]]
name = "textwrap"
build(deps): bump clap from 2.27.1 to 2.33.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.27.1 to 2.33.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/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:22:53 +00:00
version = "0.11.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"
dependencies = [
build(deps): bump unicode-width from 0.1.6 to 0.1.7 Bumps [unicode-width](https://github.com/unicode-rs/unicode-width) from 0.1.6 to 0.1.7. - [Release notes](https://github.com/unicode-rs/unicode-width/releases) - [Commits](https://github.com/unicode-rs/unicode-width/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-05 18:24:09 +00:00
"unicode-width 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "thread_local"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
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
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
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 = "unicode-width"
build(deps): bump unicode-width from 0.1.6 to 0.1.7 Bumps [unicode-width](https://github.com/unicode-rs/unicode-width) from 0.1.6 to 0.1.7. - [Release notes](https://github.com/unicode-rs/unicode-width/releases) - [Commits](https://github.com/unicode-rs/unicode-width/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-05 18:24:09 +00:00
version = "0.1.7"
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: 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 = "unicode-xid"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump remain from 0.1.3 to 0.1.4 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-19 09:50:43 +00:00
[[package]]
name = "unicode-xid"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "utf8-ranges"
build(deps): bump utf8-ranges from 1.0.3 to 1.0.4 Bumps [utf8-ranges](https://github.com/BurntSushi/utf8-ranges) from 1.0.3 to 1.0.4. - [Release notes](https://github.com/BurntSushi/utf8-ranges/releases) - [Commits](https://github.com/BurntSushi/utf8-ranges/compare/1.0.3...1.0.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-05 10:34:09 +00:00
version = "1.0.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"
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(deps): bump vcpkg from 0.2.7 to 0.2.8 Bumps [vcpkg](https://github.com/mcgoo/vcpkg-rs) from 0.2.7 to 0.2.8. - [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.7...vcpkg-rs-0.2.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-02 03:45:15 +00:00
version = "0.2.8"
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"
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 = "vec_map"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
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]]
name = "vfio"
version = "0.0.1"
dependencies = [
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"devices 0.1.0",
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
"kvm-bindings 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
"kvm-ioctls 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"log 0.4.8 (registry+https://github.com/rust-lang/crates.io-index)",
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
"pci 0.1.0",
vfio: Move vfio-bindings to crates.io And remove our local vfio-bindings code. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-10 07:41:13 +00:00
"vfio-bindings 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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-allocator 0.1.0",
vfio: Create VFIO implementation of ExternalDmaMapping With this implementation of the trait ExternalDmaMapping, we now have the tool to provide to the virtual IOMMU to trigger the map/unmap on behalf of the guest. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-07 17:48:44 +00:00
"vm-device 0.1.0",
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-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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]]
name = "vfio-bindings"
vfio: Move vfio-bindings to crates.io And remove our local vfio-bindings code. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-10 07:41:13 +00:00
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"vmm-sys-util 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
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]]
name = "vhost_rs"
version = "0.1.0"
dependencies = [
build(deps): bump ssh2 from 0.5.0 to 0.6.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.5.0 to 0.6.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.5.0...0.6.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-08 18:43:54 +00:00
"bitflags 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"tempfile 3.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
build: Run unit tests on the Jenkins server The addition of [workspace] to the top level Cargo.toml is necessary to have the binaries colocated together. The Cargo.lock files have also been refreshed by the change to the Cargo.toml. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-16 09:54:33 +00:00
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
src: Add vhost-user-net backend Create vhost-user-net backend with Tap interface, to offload network transaction from cloud-hypervisor. The goal is to provide flexibility about the backend being in use, but also more security as it will allow users to isolate the backend with different security profiles since it will run as a dedicated process on the host. Signed-off-by: Cathy Zhang <cathy.zhang@intel.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-09-20 18:21:54 +00:00
[[package]]
name = "vhost_user_backend"
version = "0.1.0"
dependencies = [
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
"epoll 4.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
src: Add vhost-user-net backend Create vhost-user-net backend with Tap interface, to offload network transaction from cloud-hypervisor. The goal is to provide flexibility about the backend being in use, but also more security as it will allow users to isolate the backend with different security profiles since it will run as a dedicated process on the host. Signed-off-by: Cathy Zhang <cathy.zhang@intel.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-09-20 18:21:54 +00:00
"vhost_rs 0.1.0",
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
"vm-virtio 0.1.0",
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
src: Add vhost-user-net backend Create vhost-user-net backend with Tap interface, to offload network transaction from cloud-hypervisor. The goal is to provide flexibility about the backend being in use, but also more security as it will allow users to isolate the backend with different security profiles since it will run as a dedicated process on the host. Signed-off-by: Cathy Zhang <cathy.zhang@intel.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-09-20 18:21:54 +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]]
name = "vhost_user_fs"
version = "0.1.0"
vhost_user_fs: Add FUSE definitions To be able to deal with FUSE requests, this commit introduces FUSE definitions, copied over from the crosvm commit 961461350c0b6824e5f20655031bf6c6bf6b7c30. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-31 17:26:24 +00:00
dependencies = [
build(deps): bump ssh2 from 0.5.0 to 0.6.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.5.0 to 0.6.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.5.0...0.6.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-08 18:43:54 +00:00
"bitflags 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
vhost_user_fs: Implement FileSystem trait for Passthrough Add a "passthrough" file system implementation that just forwards its requests to the appropriate system call. This code has been ported over from crosvm commit 961461350c0b6824e5f20655031bf6c6bf6b7c30. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-31 20:09:20 +00:00
"log 0.4.8 (registry+https://github.com/rust-lang/crates.io-index)",
vhost_user_fs: Add FUSE definitions To be able to deal with FUSE requests, this commit introduces FUSE definitions, copied over from the crosvm commit 961461350c0b6824e5f20655031bf6c6bf6b7c30. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-31 17:26:24 +00:00
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
vhost_user_fs: Add virtio descriptor helper traits Introduce helpers to split a virtio descriptor into its readable part on one side, and into its writable part on the other side. This is useful to separate the request from the reply. This code has been ported over from crosvm commit 961461350c0b6824e5f20655031bf6c6bf6b7c30. Two important modifications have been applied to the original code: - GuestMemory is replaced by GuestMemoryMmap from the vm-memory crate, which comes with different ways of accessing the memory regions. - VolatileSlice has different methods, which means the code has been updated accordingly. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-31 21:55:06 +00:00
"vm-virtio 0.1.0",
vhost_user_fs: Add FUSE definitions To be able to deal with FUSE requests, this commit introduces FUSE definitions, copied over from the crosvm commit 961461350c0b6824e5f20655031bf6c6bf6b7c30. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-31 17:26:24 +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
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 = "virtio-bindings"
version = "0.1.0"
virtio-bindings: Rely on the upstream crate from rust-vmm Now that virtio-bindings is a crate part of the rust-vmm project, we want to rely on this one instead of the local one we had so far. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-09-19 13:42:29 +00:00
source = "git+https://github.com/rust-vmm/virtio-bindings#c5676476f1048d212f53ca80711d2b132dcebe23"
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
Cargo: Move virtio-bindings to crates.io v0.1.0 was just published. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-10 07:38:42 +00:00
[[package]]
name = "virtio-bindings"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
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(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
]
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"
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 = "vm-memory"
version = "0.1.0"
build(deps): bump vm-memory from `8d6ca35` to `bb29ec8` Bumps [vm-memory](https://github.com/rust-vmm/vm-memory) from `8d6ca35` to `bb29ec8`. - [Release notes](https://github.com/rust-vmm/vm-memory/releases) - [Commits](https://github.com/rust-vmm/vm-memory/compare/8d6ca3553c773a00bdbb29eeb92d49f9aadb89d4...bb29ec8713f9a798557abdd7e1449ec065cfc095) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-15 06:09:54 +00:00
source = "git+https://github.com/rust-vmm/vm-memory#bb29ec8713f9a798557abdd7e1449ec065cfc095"
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(deps): bump cast from 0.2.2 to 0.2.3 Bumps [cast](https://github.com/japaric/cast.rs) from 0.2.2 to 0.2.3. - [Release notes](https://github.com/japaric/cast.rs/releases) - [Changelog](https://github.com/japaric/cast.rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/japaric/cast.rs/compare/v0.2.2...v0.2.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-16 23:53:59 +00:00
"cast 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump vm-memory from `4c329f4` to `1635f25` Bumps [vm-memory](https://github.com/rust-vmm/vm-memory) from `4c329f4` to `1635f25`. - [Release notes](https://github.com/rust-vmm/vm-memory/releases) - [Commits](https://github.com/rust-vmm/vm-memory/compare/4c329f4e769801d4597672190dba548c5093bbbc...1635f25afcd50ad14ed5699399e44394c5430a8d) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:23:06 +00:00
"winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)",
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: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
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
"devices 0.1.0",
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
"epoll 4.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"log 0.4.8 (registry+https://github.com/rust-lang/crates.io-index)",
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
"net_gen 0.1.0",
"net_util 0.1.0",
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
"pci 0.1.0",
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
"tempfile 3.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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_rs 0.1.0",
virtio-bindings: Rely on the upstream crate from rust-vmm Now that virtio-bindings is a crate part of the rust-vmm project, we want to rely on this one instead of the local one we had so far. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-09-19 13:42:29 +00:00
"virtio-bindings 0.1.0 (git+https://github.com/rust-vmm/virtio-bindings)",
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
"vm-allocator 0.1.0",
vm-virtio: Trigger external map/unmap from virtio-iommu This patch relies on the trait implementation provided for each device which requires some sort of external update based on a map or unmap. Whenever a MAP or UNMAP request comes through the virtqueues, it triggers a call to the external mapping trait with map()/unmap() functions being invoked. Those external mappings are meant to be used from VFIO and vhost-user devices as they need to update their own mappings. In case of VFIO, the goal is to update the DMAR table in the physical IOMMU, while vhost-user devices needs to update their internal representation of the virtqueues. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-08 00:12:11 +00:00
"vm-device 0.1.0",
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
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
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 = [
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
"acpi_tables 0.1.0",
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 13:16:58 +00:00
"arch 0.1.0",
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
"devices 0.1.0",
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
"epoll 4.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
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
"kvm-bindings 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)",
"kvm-ioctls 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
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
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
"linux-loader 0.1.0 (git+https://github.com/rust-vmm/linux-loader)",
build(deps): bump log from 0.4.6 to 0.4.8 Bumps [log](https://github.com/rust-lang/log) from 0.4.6 to 0.4.8. - [Release notes](https://github.com/rust-lang/log/releases) - [Changelog](https://github.com/rust-lang-nursery/log/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/log/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 07:52:14 +00:00
"log 0.4.8 (registry+https://github.com/rust-lang/crates.io-index)",
micro_http: Use Firecracker version As of commit 2b94334a, Firecracker includes all the changes we need. We can now switch to using it instead of carrying a copy. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-04 12:24:35 +00:00
"micro_http 0.1.0 (git+https://github.com/firecracker-microvm/firecracker)",
vmm: Leverage virtio-net to provide connectivity This patch expand the device registration to add a new virtio-net device in case the user provide the appropriate flag --net from the command line. If the flag is provided, the code will parse the TAP interface name and the expected MAC address from the command line. The VM will be connected to the provided TAP interface, and it will communicate the MAC address to the virtio-net driver. If the flag is not provided, the VM will not register any virtio-net device, therefore it will not have any connectivity with the host. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-09 15:01:42 +00:00
"net_util 0.1.0",
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 10:26:09 +00:00
"pci 0.1.0",
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
"qcow 0.1.0",
build(deps): bump serde from 1.0.102 to 1.0.103 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.102 to 1.0.103. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.102...v1.0.103) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 17:16:41 +00:00
"serde 1.0.103 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump serde_derive from 1.0.102 to 1.0.103 Bumps [serde_derive](https://github.com/serde-rs/serde) from 1.0.102 to 1.0.103. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.102...v1.0.103) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 19:55:42 +00:00
"serde_derive 1.0.103 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump serde_json from 1.0.43 to 1.0.44 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.43 to 1.0.44. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.43...v1.0.44) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-04 20:38:28 +00:00
"serde_json 1.0.44 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump signal-hook from 0.1.11 to 0.1.12 Bumps [signal-hook](https://github.com/vorner/signal-hook) from 0.1.11 to 0.1.12. - [Release notes](https://github.com/vorner/signal-hook/releases) - [Changelog](https://github.com/vorner/signal-hook/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/signal-hook/compare/v0.1.11...v0.1.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 20:34:19 +00:00
"signal-hook 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
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
"vfio 0.0.1",
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
"vm-allocator 0.1.0",
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
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/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
"vm-virtio 0.1.0",
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)",
vmm: Basic Vcpu implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 14:26:30 +00:00
]
[[package]]
name = "vmm-sys-util"
Cargo: Move to crates.io vmm-sys-util Use the newly published 0.1.1 version. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-08 11:43:28 +00:00
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
vmm: Basic Vcpu implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 14:26:30 +00:00
dependencies = [
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
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
]
Bump vmm-sys-utils to 0.2.0 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-23 07:44:42 +00:00
[[package]]
name = "vmm-sys-util"
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
version = "0.3.1"
Bump vmm-sys-utils to 0.2.0 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-23 07:44:42 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)",
Bump vmm-sys-utils to 0.2.0 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-23 07:44:42 +00:00
]
build(deps): bump getrandom from 0.1.8 to 0.1.9 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.1.8 to 0.1.9. - [Release notes](https://github.com/rust-random/getrandom/releases) - [Changelog](https://github.com/rust-random/getrandom/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-random/getrandom/compare/v0.1.8...v0.1.9) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-14 16:19:06 +00:00
[[package]]
name = "wasi"
build(deps): bump getrandom from 0.1.11 to 0.1.12 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.1.11 to 0.1.12. - [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.11...v0.1.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-06 13:33:36 +00:00
version = "0.7.0"
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: 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 = "winapi"
version = "0.2.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
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
version = "0.3.7"
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"
dependencies = [
"winapi-i686-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi-x86_64-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
]
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 = "winapi-build"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
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"
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cloud-hypervisor: Initial commit Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-21 16:04: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 = "ws2_32-sys"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)",
"winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
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
[metadata]
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
"checksum aho-corasick 0.6.10 (registry+https://github.com/rust-lang/crates.io-index)" = "81ce3d38065e618af2d7b77e10c5ad9a069859b4be3c2250f674af3840d9c8a5"
build(deps): bump clap from 2.27.1 to 2.33.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.27.1 to 2.33.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/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:22:53 +00:00
"checksum ansi_term 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ee49baf6cb617b853aa8d93bf420db2383fab46d314482ca2803b40d5fde979b"
build(deps): bump arc-swap from 0.4.3 to 0.4.4 Bumps [arc-swap](https://github.com/vorner/arc-swap) from 0.4.3 to 0.4.4. - [Release notes](https://github.com/vorner/arc-swap/releases) - [Changelog](https://github.com/vorner/arc-swap/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/arc-swap/compare/v0.4.3...v0.4.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-17 11:34:27 +00:00
"checksum arc-swap 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)" = "d7b8a9123b8027467bce0099fe556c628a53c8d83df0507084c31e9ba2e39aff"
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
"checksum arrayref 0.3.5 (registry+https://github.com/rust-lang/crates.io-index)" = "0d382e583f07208808f6b1249e60848879ba3543f57c32277bf52d69c2f0f0ee"
build(deps): bump blake2b_simd from 0.5.8 to 0.5.9 Bumps [blake2b_simd](https://github.com/oconnor663/blake2_simd) from 0.5.8 to 0.5.9. - [Release notes](https://github.com/oconnor663/blake2_simd/releases) - [Commits](https://github.com/oconnor663/blake2_simd/compare/0.5.8...0.5.9) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-07 00:07:00 +00:00
"checksum arrayvec 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "cff77d8686867eceff3105329d4698d96c2391c176d5d03adc90c7389162b5b8"
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"checksum atty 0.2.13 (registry+https://github.com/rust-lang/crates.io-index)" = "1803c647a3ec87095e7ae7acfca019e98de5ec9a7d01343f611cf3152ed71a90"
build(deps): bump autocfg from 0.1.6 to 0.1.7 Bumps [autocfg](https://github.com/cuviper/autocfg) from 0.1.6 to 0.1.7. - [Release notes](https://github.com/cuviper/autocfg/releases) - [Commits](https://github.com/cuviper/autocfg/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-20 18:05:52 +00:00
"checksum autocfg 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)" = "1d49d90015b3c36167a20fe2810c5cd875ad504b39cff3d4eae7977e6b7c1cb2"
build(deps): bump backtrace from 0.3.39 to 0.3.40 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.39 to 0.3.40. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.39...0.3.40) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-17 22:23:06 +00:00
"checksum backtrace 0.3.40 (registry+https://github.com/rust-lang/crates.io-index)" = "924c76597f0d9ca25d762c25a4d369d51267536465dc5064bdf0eb073ed477ea"
build(deps): bump backtrace-sys from 0.1.31 to 0.1.32 Bumps [backtrace-sys](https://github.com/alexcrichton/backtrace-rs) from 0.1.31 to 0.1.32. - [Release notes](https://github.com/alexcrichton/backtrace-rs/releases) - [Commits](https://github.com/alexcrichton/backtrace-rs/compare/backtrace-sys-0.1.31...backtrace-sys-0.1.32) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-17 17:35:28 +00:00
"checksum backtrace-sys 0.1.32 (registry+https://github.com/rust-lang/crates.io-index)" = "5d6575f128516de27e3ce99689419835fce9643a9b215a14d2b5b685be018491"
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
"checksum base64 0.10.1 (registry+https://github.com/rust-lang/crates.io-index)" = "0b25d992356d2eb0ed82172f5248873db5560c4721f564b13cb5193bda5e668e"
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
"checksum bitflags 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)" = "4f67931368edf3a9a51d29886d245f1c3db2f1ef0dcc9e35ff70341b78c10d23"
build(deps): bump ssh2 from 0.5.0 to 0.6.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.5.0 to 0.6.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.5.0...0.6.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-08 18:43:54 +00:00
"checksum bitflags 1.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "cf1de2fe8c75bc145a2f577add951f8134889b4795d47466a54a5c846d691693"
build(deps): bump blake2b_simd from 0.5.8 to 0.5.9 Bumps [blake2b_simd](https://github.com/oconnor663/blake2_simd) from 0.5.8 to 0.5.9. - [Release notes](https://github.com/oconnor663/blake2_simd/releases) - [Commits](https://github.com/oconnor663/blake2_simd/compare/0.5.8...0.5.9) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-07 00:07:00 +00:00
"checksum blake2b_simd 0.5.9 (registry+https://github.com/rust-lang/crates.io-index)" = "b83b7baab1e671718d78204225800d6b170e648188ac7dc992e9d6bddf87d0c0"
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"checksum byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)" = "a7c3dd8985a7111efc5c80b44e23ecdd8c007de8ade3b96595387e812b957cf5"
build(deps): bump c2-chacha from 0.2.2 to 0.2.3 Bumps [c2-chacha](https://github.com/cryptocorrosion/cryptocorrosion) from 0.2.2 to 0.2.3. - [Release notes](https://github.com/cryptocorrosion/cryptocorrosion/releases) - [Commits](https://github.com/cryptocorrosion/cryptocorrosion/compare/c2-chacha-0.2.2...c2-chacha-0.2.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-21 17:12:07 +00:00
"checksum c2-chacha 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "214238caa1bf3a496ec3392968969cab8549f96ff30652c9e56885329315f6bb"
build(deps): bump cast from 0.2.2 to 0.2.3 Bumps [cast](https://github.com/japaric/cast.rs) from 0.2.2 to 0.2.3. - [Release notes](https://github.com/japaric/cast.rs/releases) - [Changelog](https://github.com/japaric/cast.rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/japaric/cast.rs/compare/v0.2.2...v0.2.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-16 23:53:59 +00:00
"checksum cast 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "4b9434b9a5aa1450faa3f9cb14ea0e8c53bb5d2b3c1bfd1ab4fc03e9f33fbfb0"
build(deps): bump cc from 1.0.47 to 1.0.48 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.47 to 1.0.48. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.47...1.0.48) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-04 16:34:10 +00:00
"checksum cc 1.0.48 (registry+https://github.com/rust-lang/crates.io-index)" = "f52a465a666ca3d838ebbf08b241383421412fe7ebb463527bba275526d89f76"
build(deps): bump cfg-if from 0.1.9 to 0.1.10 Bumps [cfg-if](https://github.com/alexcrichton/cfg-if) from 0.1.9 to 0.1.10. - [Release notes](https://github.com/alexcrichton/cfg-if/releases) - [Commits](https://github.com/alexcrichton/cfg-if/compare/0.1.9...0.1.10) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-24 19:45:47 +00:00
"checksum cfg-if 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)" = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
build(deps): bump clap from 2.27.1 to 2.33.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.27.1 to 2.33.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/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:22:53 +00:00
"checksum clap 2.33.0 (registry+https://github.com/rust-lang/crates.io-index)" = "5067f5bb2d80ef5d68b4c87db81601f0b75bca627bc2ef76b141d7b846a3c6d9"
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
"checksum cloudabi 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "ddfc5b9aa5d4507acaf872de71051dfd0e309860e88966e1051e462a077aac4f"
build(deps): bump constant_time_eq from 0.1.3 to 0.1.4 Bumps [constant_time_eq](https://github.com/cesarb/constant_time_eq) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/cesarb/constant_time_eq/releases) - [Commits](https://github.com/cesarb/constant_time_eq/compare/0.1.3...0.1.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-21 08:25:16 +00:00
"checksum constant_time_eq 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "995a44c877f9212528ccc74b21a232f66ad69001e40ede5bcee2ac9ef2657120"
tests: Switch to launching by command Launch the test binary by command rather than using using the vmm layer. This makes it easier to manage the running VM as you can explicitly kill it. Also switch to using credibility for the tests which catches assertions and continues with subsequent commands and reports the issues at the end. This means it is possible to cleanup even on failed test runs. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-06-04 15:24:39 +00:00
"checksum credibility 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "fae7a162fd5b462bc49704873a89950a655d44161add4be07e00e64c4c83a5bf"
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
"checksum crossbeam-utils 0.6.6 (registry+https://github.com/rust-lang/crates.io-index)" = "04973fa96e96579258a5091af6003abde64af786b860f18622b82e026cca60e6"
build(deps): bump dirs from 2.0.1 to 2.0.2 Bumps [dirs](https://github.com/soc/dirs-rs) from 2.0.1 to 2.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>
2019-08-02 07:51:51 +00:00
"checksum dirs 2.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "13aea89a5c93364a98e9b37b2fa237effbb694d5cfe01c5b70941f7eb087d5e3"
"checksum dirs-sys 0.3.4 (registry+https://github.com/rust-lang/crates.io-index)" = "afa0b23de8fd801745c471deffa6e12d248f962c9fd4b4c33787b055599bde7b"
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
"checksum epoll 4.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "f3f0680f2a6f2a17fa7a8668a27c54e45e1ad1cf8a632f56a7c19b9e4e3bbe8a"
build(deps): bump failure from 0.1.5 to 0.1.6 Bumps [failure](https://github.com/rust-lang-nursery/failure) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/rust-lang-nursery/failure/releases) - [Changelog](https://github.com/rust-lang-nursery/failure/blob/master/RELEASES.md) - [Commits](https://github.com/rust-lang-nursery/failure/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-12 03:31:31 +00:00
"checksum failure 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "f8273f13c977665c5db7eb2b99ae520952fe5ac831ae4cd09d80c4c7042b5ed9"
"checksum failure_derive 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "0bc225b78e0391e4b8683440bf2e63c2deeeb2ce5189eab46e2b68c6d3725d08"
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
"checksum fuchsia-cprng 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "a06f77d526c1a601b7c4cdd98f54b5eaabffc14d5f2f0296febdc7f357c6d3ba"
build(deps): bump getrandom from 0.1.12 to 0.1.13 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.1.12 to 0.1.13. - [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.12...v0.1.13) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-25 12:33:16 +00:00
"checksum getrandom 0.1.13 (registry+https://github.com/rust-lang/crates.io-index)" = "e7db7ca94ed4cd01190ceee0d8a8052f08a247aa1b469a7f68c6a3b71afcf407"
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
"checksum glob 0.2.11 (registry+https://github.com/rust-lang/crates.io-index)" = "8be18de09a56b60ed0edf84bc9df007e30040691af7acd1c41874faac5895bfb"
"checksum ipnetwork 0.14.0 (registry+https://github.com/rust-lang/crates.io-index)" = "b3d862c86f7867f19b693ec86765e0252d82e53d4240b9b629815675a0714ad1"
"checksum itoa 0.4.4 (registry+https://github.com/rust-lang/crates.io-index)" = "501266b7edd0174f8530248f87f99c88fbe60ca4ef3dd486835b8d8d53136f7f"
"checksum kernel32-sys 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7507624b29483431c0ba2d82aece8ca6cdba9382bff4ddd0f7490560c056098d"
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
"checksum kvm-bindings 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "d381156ad52005b4655a9421401f02b80f9f049e653496e3ea6639a83fc12453"
"checksum kvm-ioctls 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ac8a59db3c7098cc87f140eb7a4317decda01dd42e7979b1d4d789bd6f6c599a"
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
"checksum lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
build(deps): bump libc from 0.2.65 to 0.2.66 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.65 to 0.2.66. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.65...0.2.66) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-29 12:24:04 +00:00
"checksum libc 0.2.66 (registry+https://github.com/rust-lang/crates.io-index)" = "d515b1f41455adea1313a4a2ac8a8a477634fbae63cc6100e3aebb207ce61558"
build(deps): bump ssh2 from 0.4.0 to 0.5.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.4.0...0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-20 10:43:20 +00:00
"checksum libssh2-sys 0.2.13 (registry+https://github.com/rust-lang/crates.io-index)" = "5fcd5a428a31cbbfe059812d74f4b6cd3b9b7426c2bdaec56993c5365da1c328"
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
"checksum libz-sys 1.0.25 (registry+https://github.com/rust-lang/crates.io-index)" = "2eb5e43362e38e2bca2fd5f5134c4d4564a23a5c28e9b95411652021a8675ebe"
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
"checksum linux-loader 0.1.0 (git+https://github.com/rust-vmm/linux-loader)" = "<none>"
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
"checksum log 0.3.9 (registry+https://github.com/rust-lang/crates.io-index)" = "e19e8d5c34a3e0e2223db8e060f9e8264aeeb5c5fc64a4ee9965c062211c024b"
build(deps): bump log from 0.4.6 to 0.4.8 Bumps [log](https://github.com/rust-lang/log) from 0.4.6 to 0.4.8. - [Release notes](https://github.com/rust-lang/log/releases) - [Changelog](https://github.com/rust-lang-nursery/log/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/log/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 07:52:14 +00:00
"checksum log 0.4.8 (registry+https://github.com/rust-lang/crates.io-index)" = "14b6052be84e6b71ab17edffc2eeabf5c2c3ae1fdb464aae35ac50c67a44e1f7"
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
"checksum memchr 2.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "88579771288728879b57485cc7d6b07d648c9f0141eb955f8ab7f9d45394468e"
micro_http: Use Firecracker version As of commit 2b94334a, Firecracker includes all the changes we need. We can now switch to using it instead of carrying a copy. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-04 12:24:35 +00:00
"checksum micro_http 0.1.0 (git+https://github.com/firecracker-microvm/firecracker)" = "<none>"
build(deps): bump openssl-sys from 0.9.52 to 0.9.53 Bumps [openssl-sys](https://github.com/sfackler/rust-openssl) from 0.9.52 to 0.9.53. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-sys-v0.9.52...openssl-sys-v0.9.53) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 16:35:38 +00:00
"checksum openssl-sys 0.9.53 (registry+https://github.com/rust-lang/crates.io-index)" = "465d16ae7fc0e313318f7de5cecf57b2fbe7511fd213978b457e1c96ff46736f"
build(deps): bump pkg-config from 0.3.16 to 0.3.17 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.16 to 0.3.17. - [Release notes](https://github.com/rust-lang/pkg-config-rs/releases) - [Changelog](https://github.com/rust-lang/pkg-config-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/pkg-config-rs/compare/0.3.16...0.3.17) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-02 09:47:40 +00:00
"checksum pkg-config 0.3.17 (registry+https://github.com/rust-lang/crates.io-index)" = "05da548ad6865900e60eaba7f589cc0783590a92e940c26953ff81ddbab2d677"
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
"checksum pnet 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)" = "63d693c84430248366146e3181ff9d330243464fa9e6146c372b2f3eb2e2d8e7"
"checksum pnet_base 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)" = "4df28acf2fcc77436dd2b91a9a0c2bb617f9ca5f2acefee1a4135058b9f9801f"
"checksum pnet_datalink 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7b34f8ca857599d05b6b082e9baff8d27c54cb9c26568cf3c0993a5755816966"
build(deps): bump pnet_macros from 0.22.0 to 0.23.0 Bumps [pnet_macros](https://github.com/libpnet/libpnet) from 0.22.0 to 0.23.0. - [Release notes](https://github.com/libpnet/libpnet/releases) - [Commits](https://github.com/libpnet/libpnet/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-06 12:53:15 +00:00
"checksum pnet_macros 0.23.0 (registry+https://github.com/rust-lang/crates.io-index)" = "a1635e02f6f098c62682e77b49ae7f3a8f1d0661df5efef679a10f162d29db27"
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
"checksum pnet_macros_support 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)" = "84684f2cddefc37a06f2fe2ca4dcc3457fc3b282734b5246507d8ee75d2780ae"
"checksum pnet_packet 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)" = "08a6cdcdaddc5174f18286298842a4e31cd3cc018933d42af51434b1fa07dcbe"
"checksum pnet_sys 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)" = "682b2eca84cc440bce8336813f78eb6d3cb0fed89fe0e87ae22acfca8363f176"
"checksum pnet_transport 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)" = "5faa55dcf725487a699adcff88dfea8f17ea34fa2640528866d9acbb4e3a104f"
build(deps): bump ppv-lite86 from 0.2.5 to 0.2.6 Bumps [ppv-lite86](https://github.com/cryptocorrosion/cryptocorrosion) from 0.2.5 to 0.2.6. - [Release notes](https://github.com/cryptocorrosion/cryptocorrosion/releases) - [Commits](https://github.com/cryptocorrosion/cryptocorrosion/compare/ppv-lite86-0.2.5...ppv-lite86-0.2.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-21 16:44:04 +00:00
"checksum ppv-lite86 0.2.6 (registry+https://github.com/rust-lang/crates.io-index)" = "74490b50b9fbe561ac330df47c08f3f33073d2d00c150f719147d7c54522fa1b"
build(deps): bump proc-macro2 from 1.0.5 to 1.0.6 Bumps [proc-macro2](https://github.com/alexcrichton/proc-macro2) from 1.0.5 to 1.0.6. - [Release notes](https://github.com/alexcrichton/proc-macro2/releases) - [Commits](https://github.com/alexcrichton/proc-macro2/compare/1.0.5...1.0.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-19 22:04:29 +00:00
"checksum proc-macro2 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)" = "9c9e470a8dc4aeae2dee2f335e8f533e2d4b347e1434e5671afc49b054592f27"
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
"checksum quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "053a8c8bcc71fcce321828dc897a98ab9760bef03a4fc36693c231e5b3216cfe"
tests: Use a temporary directory for the temporary test files Use the tempdir crate to create a temporary directory that is deleted when the structure goes out of scope. Use this temporary directory for all temporary test files created by the tests. The cloud init file is still in /tmp as that is created by the test wrapper code. This is the first stage towards being able to run the integration tests in parallel. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-18 07:57:01 +00:00
"checksum rand 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)" = "552840b97013b1a26992c11eac34bdd778e464601a4c2054b5f0bff7c6761293"
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
"checksum rand 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "d47eab0e83d9693d40f825f86948aa16eff6750ead4bdffc4ab95b8b3a7f052c"
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
"checksum rand_chacha 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "03a2a90da8c7523f554344f921aa97283eadf6ac484a6d2a7d0212fa7f8d6853"
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
"checksum rand_core 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "7a6fdeb83b075e8266dcc8762c22776f6877a63111121f5f8c7411e5be7eed4b"
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
"checksum rand_core 0.4.2 (registry+https://github.com/rust-lang/crates.io-index)" = "9c33a3c44ca05fa6f1807d8e6743f3824e8509beca625669633be0acbdf509dc"
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
"checksum rand_core 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)" = "615e683324e75af5d43d8f7a39ffe3ee4a9dc42c5c701167a71dc59c3a493aca"
"checksum rand_hc 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
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
"checksum rand_os 0.1.3 (registry+https://github.com/rust-lang/crates.io-index)" = "7b75f676a1e053fc562eafbb47838d67c84801e38fc1ba459e8f180deabd5071"
"checksum rdrand 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "678054eb77286b51581ba43620cc911abf02758c91f93f479767aed0f90458b2"
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
"checksum redox_syscall 0.1.56 (registry+https://github.com/rust-lang/crates.io-index)" = "2439c63f3f6139d1b57529d16bc3b8bb855230c8efcc5d3a896c8bea7c3b1e84"
build(deps): bump redox_users from 0.3.0 to 0.3.1 Bumps redox_users from 0.3.0 to 0.3.1. Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-08 06:53:19 +00:00
"checksum redox_users 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "4ecedbca3bf205f8d8f5c2b44d83cd0690e39ee84b951ed649e9f1841132b66d"
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
"checksum regex 1.0.6 (registry+https://github.com/rust-lang/crates.io-index)" = "ee84f70c8c08744ea9641a731c7fadb475bf2ecc52d7f627feb833e0b3990467"
build(deps): bump regex-syntax from 0.6.11 to 0.6.12 Bumps [regex-syntax](https://github.com/rust-lang/regex) from 0.6.11 to 0.6.12. - [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/regex-syntax-0.6.11...regex-syntax-0.6.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-03 17:05:22 +00:00
"checksum regex-syntax 0.6.12 (registry+https://github.com/rust-lang/crates.io-index)" = "11a7e20d1cce64ef2fed88b66d347f88bd9babb82845b2b858f3edbf59a4f716"
build(deps): bump remain from 0.1.4 to 0.1.5 Bumps [remain](https://github.com/dtolnay/remain) from 0.1.4 to 0.1.5. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.1.4...0.1.5) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 16:36:03 +00:00
"checksum remain 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "820b3db16198637c20a1e8a1532b28298820d5dfd7ec3d468fc85bc148035537"
vmm: Integrate userspace IOAPIC The previous commit introduced a userspace implementation of an IOAPIC and this commits aims to plumb it into the cloud-hypervisor VMM. Here is the list of new things brought by this patch: - Update the rust-vmm/kvm-ioctls dependency to benefit from latest patches including the support for split irqchip, and the vector being returned when a VM exit is caused by an EOI. - Enable the split irqchip (which means no IOAPIC or PIC is emulated in kernel). This is done conditionally based on the support of the TSC_DEADLINE_TIMER from both KVM and the underlying CPU. The dependency on TSC_DEADLINE_TIMER is related to KVM which does not support creating the in kernel PIT if it has a split irqchip. - Rely on callbacks to handle the following use cases: - in kernel IOAPIC + serial IRQ (pin based) - in kernel IOAPIC + virtio-pci MSI-X - in kernel IOAPIC + virtio-pci IRQ (pin based) - userspace IOAPIC + serial IRQ (pin based) - userspace IOAPIC + virtio-pci MSI-X - userspace IOAPIC + virtio-pci IRQ (pin based) Fixes #13 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-06-18 17:31:50 +00:00
"checksum remove_dir_all 0.5.2 (registry+https://github.com/rust-lang/crates.io-index)" = "4a83fa3702a688b9359eccba92d153ac33fd2e8462f9e0e3fdf155239ea7792e"
build(deps): bump rust-argon2 from 0.5.0 to 0.5.1 Bumps [rust-argon2](https://github.com/sru-systems/rust-argon2) from 0.5.0 to 0.5.1. - [Release notes](https://github.com/sru-systems/rust-argon2/releases) - [Changelog](https://github.com/sru-systems/rust-argon2/blob/master/CHANGELOG.md) - [Commits](https://github.com/sru-systems/rust-argon2/compare/0.5.0...0.5.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 07:24:31 +00:00
"checksum rust-argon2 0.5.1 (registry+https://github.com/rust-lang/crates.io-index)" = "4ca4eaef519b494d1f2848fc602d18816fed808a981aedf4f1f00ceb7c9d32cf"
build(deps): bump rustc-demangle from 0.1.15 to 0.1.16 Bumps [rustc-demangle](https://github.com/alexcrichton/rustc-demangle) from 0.1.15 to 0.1.16. - [Release notes](https://github.com/alexcrichton/rustc-demangle/releases) - [Commits](https://github.com/alexcrichton/rustc-demangle/compare/0.1.15...0.1.16) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-14 07:18:12 +00:00
"checksum rustc-demangle 0.1.16 (registry+https://github.com/rust-lang/crates.io-index)" = "4c691c0e608126e00913e33f0ccf3727d5fc84573623b8d65b2df340b5201783"
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
"checksum rustc-serialize 0.3.24 (registry+https://github.com/rust-lang/crates.io-index)" = "dcf128d1287d2ea9d80910b5f1120d0b8eede3fbf1abe91c40d39ea7d51e6fda"
build(deps): bump cast from 0.2.2 to 0.2.3 Bumps [cast](https://github.com/japaric/cast.rs) from 0.2.2 to 0.2.3. - [Release notes](https://github.com/japaric/cast.rs/releases) - [Changelog](https://github.com/japaric/cast.rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/japaric/cast.rs/compare/v0.2.2...v0.2.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-16 23:53:59 +00:00
"checksum rustc_version 0.2.3 (registry+https://github.com/rust-lang/crates.io-index)" = "138e3e0acb6c9fb258b19b67cb8abd63c00679d2851805ea151465464fe9030a"
build(deps): bump ryu from 1.0.1 to 1.0.2 Bumps [ryu](https://github.com/dtolnay/ryu) from 1.0.1 to 1.0.2. - [Release notes](https://github.com/dtolnay/ryu/releases) - [Commits](https://github.com/dtolnay/ryu/compare/1.0.1...1.0.2) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-15 04:31:53 +00:00
"checksum ryu 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)" = "bfa8506c1de11c9c4e4c38863ccbe02a305c8188e85a05a784c9e11e1c3910c8"
build(deps): bump cast from 0.2.2 to 0.2.3 Bumps [cast](https://github.com/japaric/cast.rs) from 0.2.2 to 0.2.3. - [Release notes](https://github.com/japaric/cast.rs/releases) - [Changelog](https://github.com/japaric/cast.rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/japaric/cast.rs/compare/v0.2.2...v0.2.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-16 23:53:59 +00:00
"checksum semver 0.9.0 (registry+https://github.com/rust-lang/crates.io-index)" = "1d7eb9ef2c18661902cc47e535f9bc51b78acd254da71d375c2f6720d9a40403"
"checksum semver-parser 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "388a1df253eca08550bef6c72392cfe7c30914bf41df5269b68cbd6ff8f570a3"
build(deps): bump serde from 1.0.102 to 1.0.103 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.102 to 1.0.103. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.102...v1.0.103) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 17:16:41 +00:00
"checksum serde 1.0.103 (registry+https://github.com/rust-lang/crates.io-index)" = "1217f97ab8e8904b57dd22eb61cde455fa7446a9c1cf43966066da047c1f3702"
build(deps): bump serde_derive from 1.0.102 to 1.0.103 Bumps [serde_derive](https://github.com/serde-rs/serde) from 1.0.102 to 1.0.103. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.102...v1.0.103) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 19:55:42 +00:00
"checksum serde_derive 1.0.103 (registry+https://github.com/rust-lang/crates.io-index)" = "a8c6faef9a2e64b0064f48570289b4bf8823b7581f1d6157c1b52152306651d0"
build(deps): bump serde_json from 1.0.43 to 1.0.44 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.43 to 1.0.44. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.43...v1.0.44) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-04 20:38:28 +00:00
"checksum serde_json 1.0.44 (registry+https://github.com/rust-lang/crates.io-index)" = "48c575e0cc52bdd09b47f330f646cf59afc586e9c4e3ccd6fc1f625b8ea1dad7"
build(deps): bump signal-hook from 0.1.11 to 0.1.12 Bumps [signal-hook](https://github.com/vorner/signal-hook) from 0.1.11 to 0.1.12. - [Release notes](https://github.com/vorner/signal-hook/releases) - [Changelog](https://github.com/vorner/signal-hook/blob/master/CHANGELOG.md) - [Commits](https://github.com/vorner/signal-hook/compare/v0.1.11...v0.1.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 20:34:19 +00:00
"checksum signal-hook 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)" = "7a9c17dd3ba2d36023a5c9472ecddeda07e27fd0b05436e8c1e0c8f178185652"
build(deps): bump signal-hook-registry from 1.1.1 to 1.2.0 Bumps [signal-hook-registry](https://github.com/vorner/signal-hook) from 1.1.1 to 1.2.0. - [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.1.1...registry-v1.2.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-25 16:36:38 +00:00
"checksum signal-hook-registry 1.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "94f478ede9f64724c5d173d7bb56099ec3e2d9fc2774aac65d34b8b890405f41"
build(deps): bump ssh2 from 0.5.0 to 0.6.0 Bumps [ssh2](https://github.com/alexcrichton/ssh2-rs) from 0.5.0 to 0.6.0. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/0.5.0...0.6.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-08 18:43:54 +00:00
"checksum ssh2 0.6.0 (registry+https://github.com/rust-lang/crates.io-index)" = "a5e35e594526c7cf14891247d5af64c44328f5dd67df6beff66e21f8e150222b"
build(deps): bump clap from 2.27.1 to 2.33.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.27.1 to 2.33.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/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:22:53 +00:00
"checksum strsim 0.8.0 (registry+https://github.com/rust-lang/crates.io-index)" = "8ea5119cdb4c55b55d432abb513a0429384878c15dde60cc77b1c99de1a95a6a"
build(deps): bump syn from 1.0.9 to 1.0.11 Bumps [syn](https://github.com/dtolnay/syn) from 1.0.9 to 1.0.11. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/1.0.9...1.0.11) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-01 01:16:15 +00:00
"checksum syn 1.0.11 (registry+https://github.com/rust-lang/crates.io-index)" = "dff0acdb207ae2fe6d5976617f887eb1e35a2ba52c13c7234c790960cdad9238"
build(deps): bump synstructure from 0.12.2 to 0.12.3 Bumps [synstructure](https://github.com/mystor/synstructure) from 0.12.2 to 0.12.3. - [Release notes](https://github.com/mystor/synstructure/releases) - [Commits](https://github.com/mystor/synstructure/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-11-11 18:52:53 +00:00
"checksum synstructure 0.12.3 (registry+https://github.com/rust-lang/crates.io-index)" = "67656ea1dc1b41b1451851562ea232ec2e5a80242139f7e679ceccfb5d61f545"
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
"checksum syntex 0.42.2 (registry+https://github.com/rust-lang/crates.io-index)" = "0a30b08a6b383a22e5f6edc127d169670d48f905bb00ca79a00ea3e442ebe317"
"checksum syntex_errors 0.42.0 (registry+https://github.com/rust-lang/crates.io-index)" = "04c48f32867b6114449155b2a82114b86d4b09e1bddb21c47ff104ab9172b646"
"checksum syntex_pos 0.42.0 (registry+https://github.com/rust-lang/crates.io-index)" = "3fd49988e52451813c61fecbe9abb5cfd4e1b7bb6cdbb980a6fbcbab859171a6"
"checksum syntex_syntax 0.42.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7628a0506e8f9666fdabb5f265d0059b059edac9a3f810bda077abb5d826bd8d"
tests: Use a temporary directory for the temporary test files Use the tempdir crate to create a temporary directory that is deleted when the structure goes out of scope. Use this temporary directory for all temporary test files created by the tests. The cloud init file is still in /tmp as that is created by the test wrapper code. This is the first stage towards being able to run the integration tests in parallel. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-18 07:57:01 +00:00
"checksum tempdir 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)" = "15f2b5fb00ccdf689e0149d1b1b3c03fead81c2b37735d812fa8bddbbf41b6d8"
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
"checksum tempfile 3.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "7a6e24d9338a0a5be79593e2fa15a648add6138caa803e2d5bc782c371732ca9"
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
"checksum term 0.4.6 (registry+https://github.com/rust-lang/crates.io-index)" = "fa63644f74ce96fbeb9b794f66aff2a52d601cbd5e80f4b97123e3899f4570f1"
build(deps): bump clap from 2.27.1 to 2.33.0 Bumps [clap](https://github.com/clap-rs/clap) from 2.27.1 to 2.33.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/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-02 08:22:53 +00:00
"checksum textwrap 0.11.0 (registry+https://github.com/rust-lang/crates.io-index)" = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
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
"checksum thread_local 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)" = "c6b53e329000edc2b34dbe8545fd20e55a333362d0a321909685a19bd28c3f1b"
build(deps): bump unicode-width from 0.1.6 to 0.1.7 Bumps [unicode-width](https://github.com/unicode-rs/unicode-width) from 0.1.6 to 0.1.7. - [Release notes](https://github.com/unicode-rs/unicode-width/releases) - [Commits](https://github.com/unicode-rs/unicode-width/commits) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-05 18:24:09 +00:00
"checksum unicode-width 0.1.7 (registry+https://github.com/rust-lang/crates.io-index)" = "caaa9d531767d1ff2150b9332433f32a24622147e5ebb1f26409d5da67afd479"
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
"checksum unicode-xid 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "36dff09cafb4ec7c8cf0023eb0b686cb6ce65499116a12201c9e11840ca01beb"
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
"checksum unicode-xid 0.2.0 (registry+https://github.com/rust-lang/crates.io-index)" = "826e7639553986605ec5979c7dd957c7895e93eabed50ab2ffa7f6128a75097c"
build(deps): bump utf8-ranges from 1.0.3 to 1.0.4 Bumps [utf8-ranges](https://github.com/BurntSushi/utf8-ranges) from 1.0.3 to 1.0.4. - [Release notes](https://github.com/BurntSushi/utf8-ranges/releases) - [Commits](https://github.com/BurntSushi/utf8-ranges/compare/1.0.3...1.0.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-05 10:34:09 +00:00
"checksum utf8-ranges 1.0.4 (registry+https://github.com/rust-lang/crates.io-index)" = "b4ae116fef2b7fea257ed6440d3cfcff7f190865f170cdad00bb6465bf18ecba"
build(deps): bump vcpkg from 0.2.7 to 0.2.8 Bumps [vcpkg](https://github.com/mcgoo/vcpkg-rs) from 0.2.7 to 0.2.8. - [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.7...vcpkg-rs-0.2.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-12-02 03:45:15 +00:00
"checksum vcpkg 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)" = "3fc439f2794e98976c88a2a2dafce96b930fe8010b0a256b3c2199a773933168"
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
"checksum vec_map 0.8.1 (registry+https://github.com/rust-lang/crates.io-index)" = "05c78687fb1a80548ae3250346c3db86a80a7cdd77bda190189f2d0a0987c81a"
vfio: Move vfio-bindings to crates.io And remove our local vfio-bindings code. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-10 07:41:13 +00:00
"checksum vfio-bindings 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "df0379abaedb35cac2636dd2ee75496ab921430fa5775b90f13bbda3e2abaf66"
virtio-bindings: Rely on the upstream crate from rust-vmm Now that virtio-bindings is a crate part of the rust-vmm project, we want to rely on this one instead of the local one we had so far. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-09-19 13:42:29 +00:00
"checksum virtio-bindings 0.1.0 (git+https://github.com/rust-vmm/virtio-bindings)" = "<none>"
Cargo: Move virtio-bindings to crates.io v0.1.0 was just published. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-10 07:38:42 +00:00
"checksum virtio-bindings 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "3ff512178285488516ed85f15b5d0113a7cdb89e9e8a760b269ae4f02b84bd6b"
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
"checksum vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)" = "<none>"
Cargo: Move to crates.io vmm-sys-util Use the newly published 0.1.1 version. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-08 11:43:28 +00:00
"checksum vmm-sys-util 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "46996f56aeae31fbc0532ae57a944e00089302f03b18c10c76eebfd9249f4a6c"
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
"checksum vmm-sys-util 0.3.1 (registry+https://github.com/rust-lang/crates.io-index)" = "f4588e216e77682850f4ae35ec855c2517f93d671a2578d2a32d20bf8a73de38"
build(deps): bump getrandom from 0.1.11 to 0.1.12 Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.1.11 to 0.1.12. - [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.11...v0.1.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-06 13:33:36 +00:00
"checksum wasi 0.7.0 (registry+https://github.com/rust-lang/crates.io-index)" = "b89c3ce4ce14bdc6fb6beaf9ec7928ca331de5df7e5ea278375642a2f478570d"
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
"checksum winapi 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)" = "167dc9d6949a9b857f3451275e911c3f44255842c1f7a76f33c55103a909087a"
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
"checksum winapi 0.3.7 (registry+https://github.com/rust-lang/crates.io-index)" = "f10e386af2b13e47c89e7236a7a14a086791a2b88ebad6df9bf42040195cf770"
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
"checksum winapi-build 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "2d315eee3b34aca4797b2da6b13ed88266e6d612562a0c46390af8299fc699bc"
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
"checksum winapi-i686-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
"checksum winapi-x86_64-pc-windows-gnu 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
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
"checksum ws2_32-sys 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "d59cefebd0c892fa2dd6de581e937301d8552cb44489cdff035c6187cb63fa5e"
Reference in New Issue Copy Permalink