External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2025-01-12 23:51:49 +00:00
Code Issues Packages Projects Releases Wiki Activity
cloud-hypervisor/Cargo.lock

1288 lines
56 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 11:07:32 +01: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 17:53:37 +01: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 10:54:33 +01: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 17:39:34 +01: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 17:39:34 +01: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 17:39:34 +01: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 12:18:20 -07:00
[[package]]
name = "arc-swap"
build(deps): bump arc-swap from 0.4.2 to 0.4.3 Bumps [arc-swap](https://github.com/vorner/arc-swap) from 0.4.2 to 0.4.3. - [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.2...v0.4.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-21 07:43:25 +00:00
version = "0.4.3"
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 12:18:20 -07: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 14:16:58 +01: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 17:14:34 +01:00
"acpi_tables 0.1.0",
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 14:16:58 +01: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 12:02:17 +01:00
"byteorder 1.3.2 (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 14:16:58 +01:00
"kvm-bindings 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
vm-memory usage: vm-memory latest codes rename MmapError to Error Signed-off-by: Jing Liu <jing2.liu@linux.intel.com>
2019-06-26 17:06:49 +08:00
"kvm-ioctls 0.2.0 (git+https://github.com/rust-vmm/kvm-ioctls)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 11:07:32 +01: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 14:16:58 +01: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 16:45:13 +01: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 16:45:13 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "arrayvec"
build(deps): bump arrayvec from 0.4.11 to 0.4.12 Bumps [arrayvec](https://github.com/bluss/arrayvec) from 0.4.11 to 0.4.12. - [Release notes](https://github.com/bluss/arrayvec/releases) - [Commits](https://github.com/bluss/arrayvec/compare/0.4.11...0.4.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-10 00:35:57 +00:00
version = "0.4.12"
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 16:45:13 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump nodrop from 0.1.13 to 0.1.14 Bumps [nodrop](https://github.com/bluss/arrayvec) from 0.1.13 to 0.1.14. - [Release notes](https://github.com/bluss/arrayvec/releases) - [Commits](https://github.com/bluss/arrayvec/compare/nodrop-0.1.13...nodrop-0.1.14) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-09 14:43:07 +00:00
"nodrop 0.1.14 (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 16:45:13 +01: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 17:39:34 +01: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 12:02:17 +01: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 17:39:34 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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-07 22:28:02 -07: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 17:39:34 +01: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 10:27:40 -07:00
[[package]]
name = "autocfg"
build(deps): bump autocfg from 0.1.5 to 0.1.6 Bumps [autocfg](https://github.com/cuviper/autocfg) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/cuviper/autocfg/releases) - [Commits](https://github.com/cuviper/autocfg/compare/0.1.5...0.1.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-20 06:56:32 +00:00
version = "0.1.6"
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 10:27:40 -07: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 16:45:13 +01:00
[[package]]
name = "backtrace"
build(deps): bump backtrace from 0.3.37 to 0.3.38 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.37 to 0.3.38. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.37...0.3.38) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-23 19:40:37 +00:00
version = "0.3.38"
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 16:45:13 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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 12:02:17 +01:00
"backtrace-sys 0.1.31 (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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 16:45:13 +01:00
]
[[package]]
name = "backtrace-sys"
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 12:02:17 +01:00
version = "0.1.31"
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 16:45:13 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump cc from 1.0.42 to 1.0.45 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.42 to 1.0.45. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.42...1.0.45) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-07 16:53:37 +00:00
"cc 1.0.45 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 16:45:13 +01: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 10:54:33 +01: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 14:56:43 +01:00
[[package]]
name = "bitflags"
vendor: Add vmm-sys-util duplicate Since the top-level Cargo.toml specifies a vmm-sys-util revision but not the sub crates, Cargo.lock points at 2 different crates. cargo vendor copies both of them into the vendor directory but forces the build to use the one coming from the top level driven requirement. Although this is a waste of space, this is a cargo vendor limitation that we have to live with for now. Also, because the dependency onto linux-loader had to be updated, we had to specify a newly introduced feature called "elf". Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-06-05 18:51:43 -07:00
version = "1.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 14:56:43 +01: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 16:45:13 +01: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.7 to 0.5.8 Bumps [blake2b_simd](https://github.com/oconnor663/blake2_simd) from 0.5.7 to 0.5.8. - [Release notes](https://github.com/oconnor663/blake2_simd/releases) - [Commits](https://github.com/oconnor663/blake2_simd/compare/0.5.7...0.5.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-05 18:23:58 +00:00
version = "0.5.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 16:45:13 +01: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 arrayvec from 0.4.11 to 0.4.12 Bumps [arrayvec](https://github.com/bluss/arrayvec) from 0.4.11 to 0.4.12. - [Release notes](https://github.com/bluss/arrayvec/releases) - [Commits](https://github.com/bluss/arrayvec/compare/0.4.11...0.4.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-10 00:35:57 +00:00
"arrayvec 0.4.12 (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 16:45:13 +01:00
]
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 14:16:58 +01: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 12:02:17 +01:00
version = "1.3.2"
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 14:16:58 +01: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 11:50:56 -07:00
[[package]]
name = "c2-chacha"
version = "0.2.2"
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)",
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 11:50:56 -07:00
"ppv-lite86 0.2.5 (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 10:31:50 -07:00
[[package]]
name = "cast"
version = "0.2.2"
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 16:45:13 +01:00
[[package]]
name = "cc"
build(deps): bump cc from 1.0.42 to 1.0.45 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.42 to 1.0.45. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.42...1.0.45) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-07 16:53:37 +00:00
version = "1.0.45"
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 16:45:13 +01: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 12:26:09 +02: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 12:26:09 +02: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 17:39:34 +01: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 17:39:34 +01: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 12:02:17 +01:00
"atty 0.2.13 (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
"bitflags 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"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.5 to 0.1.6 Bumps [unicode-width](https://github.com/unicode-rs/unicode-width) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/unicode-rs/unicode-width/releases) - [Commits](https://github.com/unicode-rs/unicode-width/commits/0.1.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-21 07:20:06 +00:00
"unicode-width 0.1.6 (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 17:39:34 +01: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 17:04:44 +01:00
[[package]]
name = "cloud-hypervisor"
version = "0.1.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 17:39:34 +01: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 16:24:39 +01: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)",
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-21 02:21:54 +08:00
"epoll 4.1.0 (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)",
main: Start the VMM thread We now start the main VMM thread, which will be listening for VM and IPC related events. In order to start the configured VM, we no longer directly call the VM API but we use the IPC instead, to first create and then start a VM. Fixes: #303 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-09-25 15:01:49 +02:00
"libc 0.2.62 (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 12:19:21 +01: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-21 02:21:54 +08:00
"net_gen 0.1.0",
"net_util 0.1.0",
build, tests: Update to ssh2 0.4.0 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-16 12:51:50 +01:00
"ssh2 0.4.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 08:57:01 +01: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-21 02:21:54 +08:00
"vhost_rs 0.1.0",
"vhost_user_backend 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 09:38:42 +02:00
"virtio-bindings 0.1.0 (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-21 02:21:54 +08: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 17:05:02 +01:00
"vmm 0.1.0",
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 13:43:28 +02:00
"vmm-sys-util 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 17:05:02 +01: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 10:27:40 -07:00
[[package]]
name = "cloudabi"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
vendor: Add vmm-sys-util duplicate Since the top-level Cargo.toml specifies a vmm-sys-util revision but not the sub crates, Cargo.lock points at 2 different crates. cargo vendor copies both of them into the vendor directory but forces the build to use the one coming from the top level driven requirement. Although this is a waste of space, this is a cargo vendor limitation that we have to live with for now. Also, because the dependency onto linux-loader had to be updated, we had to specify a newly introduced feature called "elf". Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-06-05 18:51:43 -07:00
"bitflags 1.1.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 10:27:40 -07: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 16:45:13 +01: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 16:45:13 +01: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 16:24:39 +01:00
[[package]]
name = "credibility"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"failure 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"failure_derive 0.1.5 (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
[[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 14:56:43 +01: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 12:02:17 +01:00
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
"epoll 4.1.0 (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 10:31:50 -07:00
"kvm-bindings 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
vm-memory usage: vm-memory latest codes rename MmapError to Error Signed-off-by: Jing Liu <jing2.liu@linux.intel.com>
2019-06-26 17:06:49 +08:00
"kvm-ioctls 0.2.0 (git+https://github.com/rust-vmm/kvm-ioctls)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 12:02:17 +01: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 11:50:56 -07: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 14:56:43 +01:00
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
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 13:43:28 +02:00
"vmm-sys-util 0.1.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 14:56:43 +01: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 16:45:13 +01: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 16:45:13 +01: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 16:45:13 +01: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 16:45:13 +01: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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 16:45:13 +01: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 14:56:43 +01:00
[[package]]
name = "epoll"
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 12:02:17 +01:00
version = "4.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 14:56:43 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
vendor: Add vmm-sys-util duplicate Since the top-level Cargo.toml specifies a vmm-sys-util revision but not the sub crates, Cargo.lock points at 2 different crates. cargo vendor copies both of them into the vendor directory but forces the build to use the one coming from the top level driven requirement. Although this is a waste of space, this is a cargo vendor limitation that we have to live with for now. Also, because the dependency onto linux-loader had to be updated, we had to specify a newly introduced feature called "elf". Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-06-05 18:51:43 -07:00
"bitflags 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 14:56:43 +01: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 16:45:13 +01:00
[[package]]
name = "failure"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump backtrace from 0.3.37 to 0.3.38 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.37 to 0.3.38. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.37...0.3.38) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-23 19:40:37 +00:00
"backtrace 0.3.38 (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 16:45:13 +01:00
"failure_derive 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "failure_derive"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"proc-macro2 0.4.30 (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 12:02:17 +01:00
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump syn from 0.15.43 to 0.15.44 Bumps [syn](https://github.com/dtolnay/syn) from 0.15.43 to 0.15.44. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/0.15.43...0.15.44) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-12 08:12:32 +00:00
"syn 0.15.44 (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 16:45:13 +01:00
"synstructure 0.10.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 10:27:40 -07: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 11:50:56 -07:00
[[package]]
name = "getrandom"
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.1.12"
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 11:50:56 -07: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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 11:50:56 -07: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 10:54:33 +01: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.100 to 1.0.101 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.100 to 1.0.101. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.100...v1.0.101) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-16 10:27:44 +00:00
"serde 1.0.101 (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 10:54:33 +01: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 17:05:02 +01:00
[[package]]
name = "kvm-bindings"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "kvm-ioctls"
vm-memory usage: vm-memory latest codes rename MmapError to Error Signed-off-by: Jing Liu <jing2.liu@linux.intel.com>
2019-06-26 17:06:49 +08:00
version = "0.2.0"
build(deps): bump kvm-ioctls from `37669f6` to `30adb02` Bumps [kvm-ioctls](https://github.com/rust-vmm/kvm-ioctls) from `37669f6` to `30adb02`. - [Release notes](https://github.com/rust-vmm/kvm-ioctls/releases) - [Commits](https://github.com/rust-vmm/kvm-ioctls/compare/37669f60a04a65b9e81cc62ac4a484ea0ed421ca...30adb021584845eed4124bc8ef3b2b96cd9e159f) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-26 07:14:59 +00:00
source = "git+https://github.com/rust-vmm/kvm-ioctls#30adb021584845eed4124bc8ef3b2b96cd9e159f"
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 17:05:02 +01:00
dependencies = [
"kvm-bindings 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 17:39:34 +01: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 10:54:33 +01: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 10:54:33 +01: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 17:39:34 +01:00
[[package]]
name = "libc"
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
version = "0.2.62"
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 17:39:34 +01: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 16:45:13 +01:00
[[package]]
name = "libssh2-sys"
build(deps): bump libssh2-sys from 0.2.11 to 0.2.12 Bumps [libssh2-sys](https://github.com/alexcrichton/ssh2-rs) from 0.2.11 to 0.2.12. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/libssh2-sys-0.2.11...libssh2-sys-0.2.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-16 00:41:43 +00:00
version = "0.2.12"
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 16:45:13 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump cc from 1.0.42 to 1.0.45 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.42 to 1.0.45. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.42...1.0.45) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-07 16:53:37 +00:00
"cc 1.0.45 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 16:45:13 +01:00
"libz-sys 1.0.25 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump openssl-sys from 0.9.50 to 0.9.51 Bumps [openssl-sys](https://github.com/sfackler/rust-openssl) from 0.9.50 to 0.9.51. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-sys-v0.9.50...openssl-sys-v0.9.51) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-10 04:36:11 +00:00
"openssl-sys 0.9.51 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump pkg-config from 0.3.15 to 0.3.16 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.15 to 0.3.16. - [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.15...0.3.16) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-09 12:27:41 +00:00
"pkg-config 0.3.16 (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 11:50:56 -07:00
"vcpkg 0.2.7 (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 16:45:13 +01: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.42 to 1.0.45 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.42 to 1.0.45. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.42...1.0.45) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-07 16:53:37 +00:00
"cc 1.0.45 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump pkg-config from 0.3.15 to 0.3.16 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.15 to 0.3.16. - [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.15...0.3.16) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-09 12:27:41 +00:00
"pkg-config 0.3.16 (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 11:50:56 -07:00
"vcpkg 0.2.7 (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 16:45:13 +01:00
]
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 14:16:58 +01: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 16:40:09 +02: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 10:54:33 +01: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 10:54:33 +01:00
]
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 12:26:09 +02: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 12:26:09 +02: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 12:26:09 +02: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 10:54:33 +01: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 11:14:49 +02:00
[[package]]
name = "micro_http"
version = "0.1.0"
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 14:24:35 +02:00
source = "git+https://github.com/firecracker-microvm/firecracker#2b94334a6a2a5f7dd07ca94f37cc4d9bdbf57ce6"
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 11:14:49 +02: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-07 22:28:02 -07:00
[[package]]
name = "net_gen"
version = "0.1.0"
dependencies = [
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 13:43:28 +02:00
"vmm-sys-util 0.1.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-07 22:28:02 -07: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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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-07 22:28:02 -07: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 10:54:33 +01: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.100 to 1.0.101 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.100 to 1.0.101. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.100...v1.0.101) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-16 10:27:44 +00:00
"serde 1.0.101 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump serde_json from 1.0.40 to 1.0.41 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.40 to 1.0.41. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.40...v1.0.41) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-03 21:38:16 +00:00
"serde_json 1.0.41 (registry+https://github.com/rust-lang/crates.io-index)",
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 13:43:28 +02:00
"vmm-sys-util 0.1.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-07 22:28:02 -07: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 16:45:13 +01:00
[[package]]
name = "nodrop"
build(deps): bump nodrop from 0.1.13 to 0.1.14 Bumps [nodrop](https://github.com/bluss/arrayvec) from 0.1.13 to 0.1.14. - [Release notes](https://github.com/bluss/arrayvec/releases) - [Commits](https://github.com/bluss/arrayvec/compare/nodrop-0.1.13...nodrop-0.1.14) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-09 14:43:07 +00:00
version = "0.1.14"
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 16:45:13 +01:00
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 11:14:49 +02:00
[[package]]
name = "num_cpus"
version = "1.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"libc 0.2.62 (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 16:45:13 +01:00
[[package]]
name = "openssl-sys"
build(deps): bump openssl-sys from 0.9.50 to 0.9.51 Bumps [openssl-sys](https://github.com/sfackler/rust-openssl) from 0.9.50 to 0.9.51. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-sys-v0.9.50...openssl-sys-v0.9.51) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-10 04:36:11 +00:00
version = "0.9.51"
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 16:45:13 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump autocfg from 0.1.5 to 0.1.6 Bumps [autocfg](https://github.com/cuviper/autocfg) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/cuviper/autocfg/releases) - [Commits](https://github.com/cuviper/autocfg/compare/0.1.5...0.1.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-20 06:56:32 +00:00
"autocfg 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump cc from 1.0.42 to 1.0.45 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.42 to 1.0.45. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.42...1.0.45) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-07 16:53:37 +00:00
"cc 1.0.45 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump pkg-config from 0.3.15 to 0.3.16 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.15 to 0.3.16. - [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.15...0.3.16) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-09 12:27:41 +00:00
"pkg-config 0.3.16 (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 11:50:56 -07:00
"vcpkg 0.2.7 (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 16:45:13 +01:00
]
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 12:26:09 +02: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 12:02:17 +01: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 12:26:09 +02:00
"devices 0.1.0",
"kvm-bindings 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
vm-memory usage: vm-memory latest codes rename MmapError to Error Signed-off-by: Jing Liu <jing2.liu@linux.intel.com>
2019-06-26 17:06:49 +08:00
"kvm-ioctls 0.2.0 (git+https://github.com/rust-vmm/kvm-ioctls)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 12:02:17 +01: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 12:26:09 +02:00
"vm-allocator 0.1.0",
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
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 13:43:28 +02:00
"vmm-sys-util 0.1.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 12:26:09 +02: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 16:45:13 +01:00
[[package]]
name = "pkg-config"
build(deps): bump pkg-config from 0.3.15 to 0.3.16 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.15 to 0.3.16. - [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.15...0.3.16) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-09 12:27:41 +00:00
version = "0.3.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 16:45:13 +01: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 10:54:33 +01: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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 10:54:33 +01: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"
version = "0.22.0"
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)",
"pnet_macros 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)",
"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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 10:54:33 +01: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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 10:54:33 +01: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 11:50:56 -07:00
[[package]]
name = "ppv-lite86"
version = "0.2.5"
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 = "proc-macro2"
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-07 22:28:02 -07:00
version = "0.4.30"
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 = [
"unicode-xid 0.1.0 (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"
version = "1.0.1"
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 12:02:17 +01:00
"byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 12:02:17 +01:00
"log 0.4.8 (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
"remain 0.1.4 (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 11:50:56 -07:00
"tempfile 3.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
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 13:43:28 +02:00
"vmm-sys-util 0.1.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
]
[[package]]
name = "quote"
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 12:02:17 +01:00
version = "0.6.13"
qcow: Add qcow support Extracted from crosvm (commit:f82d632), with clippy fixes. Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
2019-04-29 19:32:56 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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-07 22:28:02 -07:00
"proc-macro2 0.4.30 (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 = [
"proc-macro2 1.0.1 (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 08:57:01 +01: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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 08:57:01 +01: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 11:50:56 -07: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.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
"getrandom 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 12:02:17 +01: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 11:50:56 -07: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 12:02:17 +01: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 11:50:56 -07:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"c2-chacha 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
"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 10:27:40 -07: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 12:18:20 -07: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 10:27:40 -07: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 12:18:20 -07: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 10:27:40 -07: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 11:50:56 -07: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.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
"getrandom 0.1.12 (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 11:50:56 -07: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 10:27:40 -07: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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 12:18:20 -07: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 10:27:40 -07: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-07 22:28:02 -07: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 10:27:40 -07: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 17:39:34 +01: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 11:50:56 -07: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 17:39:34 +01: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 16:45:13 +01: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 16:45:13 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"failure 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)",
"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 11:50:56 -07: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 16:45:13 +01: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 10:54:33 +01: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 10:54:33 +01: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 10:54:33 +01: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 10:54:33 +01: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.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
version = "0.1.4"
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 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
"proc-macro2 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 1.0.3 (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 10:27:40 -07: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 10:31:50 -07: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 10:27:40 -07: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-07 22:28:02 -07: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 10:27:40 -07: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.7 to 0.5.8 Bumps [blake2b_simd](https://github.com/oconnor663/blake2_simd) from 0.5.7 to 0.5.8. - [Release notes](https://github.com/oconnor663/blake2_simd/releases) - [Commits](https://github.com/oconnor663/blake2_simd/compare/0.5.7...0.5.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-05 18:23:58 +00:00
"blake2b_simd 0.5.8 (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 16:45:13 +01: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 16:45:13 +01: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 10:54:33 +01:00
[[package]]
name = "rustc-serialize"
version = "0.3.24"
source = "registry+https://github.com/rust-lang/crates.io-index"
[[package]]
name = "ryu"
version = "1.0.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-07 22:28:02 -07:00
[[package]]
name = "serde"
build(deps): bump serde from 1.0.100 to 1.0.101 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.100 to 1.0.101. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.100...v1.0.101) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-16 10:27:44 +00:00
version = "1.0.101"
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-07 22:28:02 -07: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 11:40:50 +02:00
[[package]]
name = "serde_derive"
version = "1.0.101"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"proc-macro2 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
"quote 1.0.2 (registry+https://github.com/rust-lang/crates.io-index)",
"syn 1.0.3 (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 10:54:33 +01:00
[[package]]
name = "serde_json"
build(deps): bump serde_json from 1.0.40 to 1.0.41 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.40 to 1.0.41. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.40...v1.0.41) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-03 21:38:16 +00:00
version = "1.0.41"
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 10:54:33 +01: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)",
"ryu 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump serde from 1.0.100 to 1.0.101 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.100 to 1.0.101. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.100...v1.0.101) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-16 10:27:44 +00:00
"serde 1.0.101 (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 10:54:33 +01: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 12:18:20 -07:00
[[package]]
name = "signal-hook"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 12:18:20 -07:00
"signal-hook-registry 1.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
]
[[package]]
name = "signal-hook-registry"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump arc-swap from 0.4.2 to 0.4.3 Bumps [arc-swap](https://github.com/vorner/arc-swap) from 0.4.2 to 0.4.3. - [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.2...v0.4.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-21 07:43:25 +00:00
"arc-swap 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 12:18:20 -07: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 16:45:13 +01:00
[[package]]
name = "ssh2"
build, tests: Update to ssh2 0.4.0 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-16 12:51:50 +01:00
version = "0.4.0"
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 16:45:13 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build, tests: Update to ssh2 0.4.0 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-16 12:51:50 +01:00
"bitflags 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libssh2-sys from 0.2.11 to 0.2.12 Bumps [libssh2-sys](https://github.com/alexcrichton/ssh2-rs) from 0.2.11 to 0.2.12. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/libssh2-sys-0.2.11...libssh2-sys-0.2.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-16 00:41:43 +00:00
"libssh2-sys 0.2.12 (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 16:45:13 +01: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 17:39:34 +01: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 17:39:34 +01: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 = "syn"
build(deps): bump syn from 0.15.43 to 0.15.44 Bumps [syn](https://github.com/dtolnay/syn) from 0.15.43 to 0.15.44. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/0.15.43...0.15.44) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-12 08:12:32 +00:00
version = "0.15.44"
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 = [
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-07 22:28:02 -07:00
"proc-macro2 0.4.30 (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 12:02:17 +01:00
"quote 0.6.13 (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
"unicode-xid 0.1.0 (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"
version = "1.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"proc-macro2 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)",
"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 16:45:13 +01:00
[[package]]
name = "synstructure"
version = "0.10.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"proc-macro2 0.4.30 (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 12:02:17 +01:00
"quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump syn from 0.15.43 to 0.15.44 Bumps [syn](https://github.com/dtolnay/syn) from 0.15.43 to 0.15.44. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/0.15.43...0.15.44) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-12 08:12:32 +00:00
"syn 0.15.44 (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 16:45:13 +01:00
"unicode-xid 0.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 10:54:33 +01: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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 10:54:33 +01: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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 10:54:33 +01: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 08:57:01 +01: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 10:27:40 -07: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 11:50:56 -07: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 10:27:40 -07: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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 11:50:56 -07: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 10:31:50 -07: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-07 22:28:02 -07: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 10:27:40 -07: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 10:54:33 +01: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 17:39:34 +01: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 17:39:34 +01:00
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
build(deps): bump unicode-width from 0.1.5 to 0.1.6 Bumps [unicode-width](https://github.com/unicode-rs/unicode-width) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/unicode-rs/unicode-width/releases) - [Commits](https://github.com/unicode-rs/unicode-width/commits/0.1.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-21 07:20:06 +00:00
"unicode-width 0.1.6 (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 17:39:34 +01: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 10:54:33 +01: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 10:54:33 +01:00
]
vmm: api: Add HTTP server The Cloud Hyper HTTP server runs a synchronous, multi-threaded loop that receives HTTP requests and tries to call the corresponding endpoint handlers for the requests URIs. An endpoint handler will parse the HTTP request and potentially translate it into and IPC request. The handler holds an notifier and an mspc Sender for respectively notifying and sending the IPC payload to the VMM API server. The handler then waits for an API server response and translate it back into an HTTP response. The HTTP server is responsible for sending the reponse back to the caller. The HTTP server uses a static routes hash table that maps URIs to endpoint handlers. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-09-18 11:14:49 +02:00
[[package]]
name = "threadpool"
version = "1.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"num_cpus 1.10.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 17:39:34 +01:00
[[package]]
name = "unicode-width"
build(deps): bump unicode-width from 0.1.5 to 0.1.6 Bumps [unicode-width](https://github.com/unicode-rs/unicode-width) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/unicode-rs/unicode-width/releases) - [Commits](https://github.com/unicode-rs/unicode-width/commits/0.1.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-21 07:20:06 +00:00
version = "0.1.6"
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 17:39:34 +01: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 10:54:33 +01:00
[[package]]
name = "unicode-xid"
version = "0.0.3"
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 = "unicode-xid"
version = "0.1.0"
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 10:54:33 +01: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 10:54:33 +01: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 16:45:13 +01:00
[[package]]
name = "vcpkg"
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 11:50:56 -07:00
version = "0.2.7"
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 16:45:13 +01: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 17:39:34 +01: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 11:42:40 +02: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 12:02:17 +01: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 11:42:40 +02:00
"devices 0.1.0",
"kvm-bindings 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
"kvm-ioctls 0.2.0 (git+https://github.com/rust-vmm/kvm-ioctls)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 12:02:17 +01: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 11:42:40 +02: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 09:41:13 +02: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 11:42:40 +02:00
"vm-allocator 0.1.0",
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
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 13:43:28 +02:00
"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 11:42:40 +02: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 09:41:13 +02: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 11:42:40 +02: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 11:54:53 -07:00
[[package]]
name = "vhost_rs"
version = "0.1.0"
dependencies = [
"bitflags 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 11:50:56 -07: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 10:54:33 +01:00
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
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 13:43:28 +02:00
"vmm-sys-util 0.1.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 11:54:53 -07: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-21 02:21:54 +08:00
[[package]]
name = "vhost_user_backend"
version = "0.1.0"
dependencies = [
"epoll 4.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
"libc 0.2.62 (registry+https://github.com/rust-lang/crates.io-index)",
"vhost_rs 0.1.0",
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
"vm-virtio 0.1.0",
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 13:43:28 +02:00
"vmm-sys-util 0.1.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-21 02:21:54 +08: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 10:27:40 -07: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 06:42:29 -07: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 10:27:40 -07: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 09:38:42 +02: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 12:26:09 +02:00
[[package]]
name = "vm-allocator"
version = "0.1.0"
dependencies = [
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 12:26:09 +02:00
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
]
cloud-hypervisor: Call into the test_vm() routine test_vm is a dummy VM workload, we use it to test our initial VMM settings. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-22 17:05:02 +01:00
[[package]]
name = "vm-memory"
version = "0.1.0"
build(deps): bump vm-memory from `1635f25` to `8669369` Bumps [vm-memory](https://github.com/rust-vmm/vm-memory) from `1635f25` to `8669369`. - [Release notes](https://github.com/rust-vmm/vm-memory/releases) - [Commits](https://github.com/rust-vmm/vm-memory/compare/1635f25afcd50ad14ed5699399e44394c5430a8d...8669369d17a470d72743fc616a26ee6b95f230f5) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-27 06:33:43 +00:00
source = "git+https://github.com/rust-vmm/vm-memory#8669369d17a470d72743fc616a26ee6b95f230f5"
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 17:05:02 +01:00
dependencies = [
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 10:31:50 -07:00
"cast 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 17:05:02 +01: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 10:27:40 -07: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 12:02:17 +01: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 10:27:40 -07:00
"devices 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 12:02:17 +01:00
"epoll 4.1.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 12:02:17 +01: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-07 22:28:02 -07: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 10:27:40 -07: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 11:50:56 -07: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 11:54:53 -07: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 06:42:29 -07: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 10:27:40 -07:00
"vm-allocator 0.1.0",
"vm-memory 0.1.0 (git+https://github.com/rust-vmm/vm-memory)",
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 13:43:28 +02:00
"vmm-sys-util 0.1.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 10:27:40 -07: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 17:05:02 +01: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 17:53:37 +01:00
"acpi_tables 0.1.0",
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 14:16:58 +01: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 14:56:43 +01:00
"devices 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 12:02:17 +01:00
"epoll 4.1.0 (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 17:05:02 +01:00
"kvm-bindings 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)",
vm-memory usage: vm-memory latest codes rename MmapError to Error Signed-off-by: Jing Liu <jing2.liu@linux.intel.com>
2019-06-26 17:06:49 +08:00
"kvm-ioctls 0.2.0 (git+https://github.com/rust-vmm/kvm-ioctls)",
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 11:14:49 +02:00
"lazy_static 1.4.0 (registry+https://github.com/rust-lang/crates.io-index)",
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 11:07:32 +01: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 14:24:35 +02: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 08:01:42 -07:00
"net_util 0.1.0",
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 12:26:09 +02: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",
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 11:40:50 +02:00
"serde 1.0.101 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_derive 1.0.101 (registry+https://github.com/rust-lang/crates.io-index)",
"serde_json 1.0.41 (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 12:18:20 -07:00
"signal-hook 0.1.10 (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 11:14:49 +02:00
"threadpool 1.7.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 11:42:40 +02: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 10:27:40 -07: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 17:05:02 +01: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 10:27:40 -07:00
"vm-virtio 0.1.0",
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 13:43:28 +02:00
"vmm-sys-util 0.1.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 15:26:30 +01: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 13:43:28 +02: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 15:26:30 +01:00
dependencies = [
build(deps): bump libc from 0.2.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"libc 0.2.62 (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 17:05:02 +01: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 10:54:33 +01: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 17:39:34 +01: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-07 22:28:02 -07: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 17:39:34 +01: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 10:54:33 +01: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 17:39:34 +01: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 17:04:44 +01: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 10:54:33 +01: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 17:39:34 +01: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 10:54:33 +01: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.2 to 0.4.3 Bumps [arc-swap](https://github.com/vorner/arc-swap) from 0.4.2 to 0.4.3. - [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.2...v0.4.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-21 07:43:25 +00:00
"checksum arc-swap 0.4.3 (registry+https://github.com/rust-lang/crates.io-index)" = "f1a1eca3195b729bbd64e292ef2f5fff6b1c28504fed762ce2b1013dde4d8e92"
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 arrayvec from 0.4.11 to 0.4.12 Bumps [arrayvec](https://github.com/bluss/arrayvec) from 0.4.11 to 0.4.12. - [Release notes](https://github.com/bluss/arrayvec/releases) - [Commits](https://github.com/bluss/arrayvec/compare/0.4.11...0.4.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-10 00:35:57 +00:00
"checksum arrayvec 0.4.12 (registry+https://github.com/rust-lang/crates.io-index)" = "cd9fd44efafa8690358b7408d253adf110036b88f55672a933f01d616ad9b1b9"
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 12:02:17 +01:00
"checksum atty 0.2.13 (registry+https://github.com/rust-lang/crates.io-index)" = "1803c647a3ec87095e7ae7acfca019e98de5ec9a7d01343f611cf3152ed71a90"
build(deps): bump autocfg from 0.1.5 to 0.1.6 Bumps [autocfg](https://github.com/cuviper/autocfg) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/cuviper/autocfg/releases) - [Commits](https://github.com/cuviper/autocfg/compare/0.1.5...0.1.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-20 06:56:32 +00:00
"checksum autocfg 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "b671c8fb71b457dd4ae18c4ba1e59aa81793daacc361d82fcd410cef0d491875"
build(deps): bump backtrace from 0.3.37 to 0.3.38 Bumps [backtrace](https://github.com/rust-lang/backtrace-rs) from 0.3.37 to 0.3.38. - [Release notes](https://github.com/rust-lang/backtrace-rs/releases) - [Commits](https://github.com/rust-lang/backtrace-rs/compare/0.3.37...0.3.38) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-23 19:40:37 +00:00
"checksum backtrace 0.3.38 (registry+https://github.com/rust-lang/crates.io-index)" = "690a62be8920ccf773ee00ef0968649b0e724cda8bd5b12286302b4ae955fdf5"
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 12:02:17 +01:00
"checksum backtrace-sys 0.1.31 (registry+https://github.com/rust-lang/crates.io-index)" = "82a830b4ef2d1124a711c71d263c5abdc710ef8e907bd508c88be475cebc422b"
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 10:54:33 +01:00
"checksum bitflags 0.5.0 (registry+https://github.com/rust-lang/crates.io-index)" = "4f67931368edf3a9a51d29886d245f1c3db2f1ef0dcc9e35ff70341b78c10d23"
vendor: Add vmm-sys-util duplicate Since the top-level Cargo.toml specifies a vmm-sys-util revision but not the sub crates, Cargo.lock points at 2 different crates. cargo vendor copies both of them into the vendor directory but forces the build to use the one coming from the top level driven requirement. Although this is a waste of space, this is a cargo vendor limitation that we have to live with for now. Also, because the dependency onto linux-loader had to be updated, we had to specify a newly introduced feature called "elf". Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-06-05 18:51:43 -07:00
"checksum bitflags 1.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "3d155346769a6855b86399e9bc3814ab343cd3d62c7e985113d46a0ec3c281fd"
build(deps): bump blake2b_simd from 0.5.7 to 0.5.8 Bumps [blake2b_simd](https://github.com/oconnor663/blake2_simd) from 0.5.7 to 0.5.8. - [Release notes](https://github.com/oconnor663/blake2_simd/releases) - [Commits](https://github.com/oconnor663/blake2_simd/compare/0.5.7...0.5.8) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-05 18:23:58 +00:00
"checksum blake2b_simd 0.5.8 (registry+https://github.com/rust-lang/crates.io-index)" = "5850aeee1552f495dd0250014cf64b82b7c8879a89d83b33bbdace2cc4f63182"
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 12:02:17 +01:00
"checksum byteorder 1.3.2 (registry+https://github.com/rust-lang/crates.io-index)" = "a7c3dd8985a7111efc5c80b44e23ecdd8c007de8ade3b96595387e812b957cf5"
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 11:50:56 -07:00
"checksum c2-chacha 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "7d64d04786e0f528460fc884753cf8dddcc466be308f6026f8e355c41a0e4101"
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 10:31:50 -07:00
"checksum cast 0.2.2 (registry+https://github.com/rust-lang/crates.io-index)" = "926013f2860c46252efceabb19f4a6b308197505082c609025aa6706c011d427"
build(deps): bump cc from 1.0.42 to 1.0.45 Bumps [cc](https://github.com/alexcrichton/cc-rs) from 1.0.42 to 1.0.45. - [Release notes](https://github.com/alexcrichton/cc-rs/releases) - [Commits](https://github.com/alexcrichton/cc-rs/compare/1.0.42...1.0.45) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-07 16:53:37 +00:00
"checksum cc 1.0.45 (registry+https://github.com/rust-lang/crates.io-index)" = "4fc9a35e1f4290eb9e5fc54ba6cf40671ed2a2514c3eeb2b2a908dda2ea5a1be"
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 10:27:40 -07: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 16:24:39 +01: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"
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 12:02:17 +01:00
"checksum epoll 4.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "990bcfe26bea89669ede68c3f970f61d02568dbc8660317c98d805ea4e710685"
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 16:45:13 +01:00
"checksum failure 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "795bd83d3abeb9220f257e597aa0080a508b27533824adf336529648f6abf7e2"
"checksum failure_derive 0.1.5 (registry+https://github.com/rust-lang/crates.io-index)" = "ea1063915fd7ef4309e222a5a07cf9c319fb9c7836b1f89b85458672dbb127e1"
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 10:27:40 -07:00
"checksum fuchsia-cprng 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "a06f77d526c1a601b7c4cdd98f54b5eaabffc14d5f2f0296febdc7f357c6d3ba"
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 getrandom 0.1.12 (registry+https://github.com/rust-lang/crates.io-index)" = "473a1265acc8ff1e808cd0a1af8cee3c2ee5200916058a2ca113c29f2d903571"
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 10:54:33 +01: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"
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 17:05:02 +01:00
"checksum kvm-bindings 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "c223e8703d2eb76d990c5f58e29c85b0f6f50e24b823babde927948e7c71fc03"
vm-memory usage: vm-memory latest codes rename MmapError to Error Signed-off-by: Jing Liu <jing2.liu@linux.intel.com>
2019-06-26 17:06:49 +08:00
"checksum kvm-ioctls 0.2.0 (git+https://github.com/rust-vmm/kvm-ioctls)" = "<none>"
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.61 to 0.2.62 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.61 to 0.2.62. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.61...0.2.62) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-16 06:56:11 +00:00
"checksum libc 0.2.62 (registry+https://github.com/rust-lang/crates.io-index)" = "34fcd2c08d2f832f376f4173a231990fa5aef4e99fb569867318a227ef4c06ba"
build(deps): bump libssh2-sys from 0.2.11 to 0.2.12 Bumps [libssh2-sys](https://github.com/alexcrichton/ssh2-rs) from 0.2.11 to 0.2.12. - [Release notes](https://github.com/alexcrichton/ssh2-rs/releases) - [Commits](https://github.com/alexcrichton/ssh2-rs/compare/libssh2-sys-0.2.11...libssh2-sys-0.2.12) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-16 00:41:43 +00:00
"checksum libssh2-sys 0.2.12 (registry+https://github.com/rust-lang/crates.io-index)" = "8914d10b159fc288f2b6f253c94bd0c15a777fd5a297691141d89674b87e66fd"
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 16:45:13 +01: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 11:07:32 +01: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 10:54:33 +01: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 10:54:33 +01: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 14:24:35 +02:00
"checksum micro_http 0.1.0 (git+https://github.com/firecracker-microvm/firecracker)" = "<none>"
build(deps): bump nodrop from 0.1.13 to 0.1.14 Bumps [nodrop](https://github.com/bluss/arrayvec) from 0.1.13 to 0.1.14. - [Release notes](https://github.com/bluss/arrayvec/releases) - [Commits](https://github.com/bluss/arrayvec/compare/nodrop-0.1.13...nodrop-0.1.14) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-09 14:43:07 +00:00
"checksum nodrop 0.1.14 (registry+https://github.com/rust-lang/crates.io-index)" = "72ef4a56884ca558e5ddb05a1d1e7e1bfd9a68d9ed024c21704cc98872dae1bb"
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 11:14:49 +02:00
"checksum num_cpus 1.10.1 (registry+https://github.com/rust-lang/crates.io-index)" = "bcef43580c035376c0705c42792c294b66974abbfd2789b511784023f71f3273"
build(deps): bump openssl-sys from 0.9.50 to 0.9.51 Bumps [openssl-sys](https://github.com/sfackler/rust-openssl) from 0.9.50 to 0.9.51. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-sys-v0.9.50...openssl-sys-v0.9.51) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-10 04:36:11 +00:00
"checksum openssl-sys 0.9.51 (registry+https://github.com/rust-lang/crates.io-index)" = "ba24190c8f0805d3bd2ce028f439fe5af1d55882bbe6261bed1dbc93b50dd6b1"
build(deps): bump pkg-config from 0.3.15 to 0.3.16 Bumps [pkg-config](https://github.com/rust-lang/pkg-config-rs) from 0.3.15 to 0.3.16. - [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.15...0.3.16) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-09 12:27:41 +00:00
"checksum pkg-config 0.3.16 (registry+https://github.com/rust-lang/crates.io-index)" = "72d5370d90f49f70bd033c3d75e87fc529fbfff9d6f7cccef07d6170079d91ea"
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 10:54:33 +01: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"
"checksum pnet_macros 0.22.0 (registry+https://github.com/rust-lang/crates.io-index)" = "e2f16d1fa7fd0edebc36055587b8b5af8a109bbc29a55fb484a37e2029b971a7"
"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"
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 11:50:56 -07:00
"checksum ppv-lite86 0.2.5 (registry+https://github.com/rust-lang/crates.io-index)" = "e3cbf9f658cdb5000fcf6f362b8ea2ba154b9f146a61c7a20d647034c6b6561b"
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-07 22:28:02 -07:00
"checksum proc-macro2 0.4.30 (registry+https://github.com/rust-lang/crates.io-index)" = "cf3d2011ab5c909338f7887f4fc896d35932e29146c12c8d01da6b22a80ba759"
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 proc-macro2 1.0.1 (registry+https://github.com/rust-lang/crates.io-index)" = "4c5c2380ae88876faae57698be9e9775e3544decad214599c3a6266cca6ac802"
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 12:02:17 +01:00
"checksum quote 0.6.13 (registry+https://github.com/rust-lang/crates.io-index)" = "6ce23b6b870e8f94f81fb0a363d65d86675884b34a09043c81e5562f11c1f8e1"
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 08:57:01 +01: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 11:50:56 -07: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 12:02:17 +01: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 10:27:40 -07: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 12:18:20 -07: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 11:50:56 -07: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 10:27:40 -07: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 11:50:56 -07: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 10:54:33 +01: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.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 remain 0.1.4 (registry+https://github.com/rust-lang/crates.io-index)" = "ac89e32ec81fb60574791b9ac36aeaf8217dfc5fc5c1b4153b3e51a7814c0e8c"
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 10:31:50 -07: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 10:54:33 +01:00
"checksum rustc-serialize 0.3.24 (registry+https://github.com/rust-lang/crates.io-index)" = "dcf128d1287d2ea9d80910b5f1120d0b8eede3fbf1abe91c40d39ea7d51e6fda"
"checksum ryu 1.0.0 (registry+https://github.com/rust-lang/crates.io-index)" = "c92464b447c0ee8c4fb3824ecc8383b81717b9f1e74ba2e72540aef7b9f82997"
build(deps): bump serde from 1.0.100 to 1.0.101 Bumps [serde](https://github.com/serde-rs/serde) from 1.0.100 to 1.0.101. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.100...v1.0.101) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-09-16 10:27:44 +00:00
"checksum serde 1.0.101 (registry+https://github.com/rust-lang/crates.io-index)" = "9796c9b7ba2ffe7a9ce53c2287dfc48080f4b2b362fcc245a259b3a7201119dd"
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 11:40:50 +02:00
"checksum serde_derive 1.0.101 (registry+https://github.com/rust-lang/crates.io-index)" = "4b133a43a1ecd55d4086bd5b4dc6c1751c68b1bfbeba7a5040442022c7e7c02e"
build(deps): bump serde_json from 1.0.40 to 1.0.41 Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.40 to 1.0.41. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.40...v1.0.41) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-10-03 21:38:16 +00:00
"checksum serde_json 1.0.41 (registry+https://github.com/rust-lang/crates.io-index)" = "2f72eb2a68a7dc3f9a691bfda9305a1c017a6215e5a4545c258500d2099a37c2"
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 12:18:20 -07:00
"checksum signal-hook 0.1.10 (registry+https://github.com/rust-lang/crates.io-index)" = "4f61c4d59f3aaa9f61bba6450a9b80ba48362fd7d651689e7a10c453b1f6dc68"
"checksum signal-hook-registry 1.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "1797d48f38f91643908bb14e35e79928f9f4b3cefb2420a564dde0991b4358dc"
build, tests: Update to ssh2 0.4.0 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-16 12:51:50 +01:00
"checksum ssh2 0.4.0 (registry+https://github.com/rust-lang/crates.io-index)" = "875fc74ffc41049e306a247f4191dd9c2ebfb7c5e0a6e4ddfdccacaba732e8aa"
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 0.15.43 to 0.15.44 Bumps [syn](https://github.com/dtolnay/syn) from 0.15.43 to 0.15.44. - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](https://github.com/dtolnay/syn/compare/0.15.43...0.15.44) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-12 08:12:32 +00:00
"checksum syn 0.15.44 (registry+https://github.com/rust-lang/crates.io-index)" = "9ca4b3b69a77cbe1ffc9e198781b7acb0c7365a883670e8f1c1bc66fba79a5c5"
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 syn 1.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "158521e6f544e7e3dcfc370ac180794aa38cb34a1b1e07609376d4adcf429b93"
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 16:45:13 +01:00
"checksum synstructure 0.10.2 (registry+https://github.com/rust-lang/crates.io-index)" = "02353edf96d6e4dc81aea2d8490a7e9db177bf8acb0e951c24940bf866cb313f"
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 10:54:33 +01: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 08:57:01 +01: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 11:50:56 -07: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 10:54:33 +01: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 10:54:33 +01:00
"checksum thread_local 0.3.6 (registry+https://github.com/rust-lang/crates.io-index)" = "c6b53e329000edc2b34dbe8545fd20e55a333362d0a321909685a19bd28c3f1b"
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 11:14:49 +02:00
"checksum threadpool 1.7.1 (registry+https://github.com/rust-lang/crates.io-index)" = "e2f0c90a5f3459330ac8bc0d2f879c693bb7a2f59689c1083fc4ef83834da865"
build(deps): bump unicode-width from 0.1.5 to 0.1.6 Bumps [unicode-width](https://github.com/unicode-rs/unicode-width) from 0.1.5 to 0.1.6. - [Release notes](https://github.com/unicode-rs/unicode-width/releases) - [Commits](https://github.com/unicode-rs/unicode-width/commits/0.1.6) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2019-08-21 07:20:06 +00:00
"checksum unicode-width 0.1.6 (registry+https://github.com/rust-lang/crates.io-index)" = "7007dbd421b92cc6e28410fe7362e2e0a2503394908f417b68ec8d1c364c4e20"
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 10:54:33 +01:00
"checksum unicode-xid 0.0.3 (registry+https://github.com/rust-lang/crates.io-index)" = "36dff09cafb4ec7c8cf0023eb0b686cb6ce65499116a12201c9e11840ca01beb"
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
"checksum unicode-xid 0.1.0 (registry+https://github.com/rust-lang/crates.io-index)" = "fc72304796d0818e357ead4e000d19c9c174ab23dc11093ac919054d20a6a7fc"
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"
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 11:50:56 -07:00
"checksum vcpkg 0.2.7 (registry+https://github.com/rust-lang/crates.io-index)" = "33dd455d0f96e90a75803cfeb7f948768c08d70a6de9a8d2362461935698bf95"
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 17:39:34 +01: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 09:41:13 +02: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 06:42:29 -07: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 09:38:42 +02: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 17:05:02 +01: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 13:43:28 +02:00
"checksum vmm-sys-util 0.1.1 (registry+https://github.com/rust-lang/crates.io-index)" = "46996f56aeae31fbc0532ae57a944e00089302f03b18c10c76eebfd9249f4a6c"
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 10:54:33 +01: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-07 22:28:02 -07: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 10:54:33 +01: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 17:39:34 +01: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 10:54:33 +01:00
"checksum ws2_32-sys 0.2.1 (registry+https://github.com/rust-lang/crates.io-index)" = "d59cefebd0c892fa2dd6de581e937301d8552cb44489cdff035c6187cb63fa5e"
Reference in New Issue Copy Permalink