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

37 lines
1.1 KiB
TOML
Raw Normal View History

hypervisor: Introduce hypervisor crate The purpose of this trait is to add support for other hypervisors than KVM, like e.g. Microsoft Hyper-V. Further commits will define additional hypervisor related traits like Vcpu and Vm. Each of the supported hypervisor will need to implement all traits defined from the hypervisor crate. Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-06-08 00:50:38 +00:00
[package]
name = "hypervisor"
version = "0.1.0"
hypervisor: Update Author and license info in the toml file Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-10-19 22:42:43 +00:00
authors = ["Microsoft Authors"]
hypervisor: Introduce hypervisor crate The purpose of this trait is to add support for other hypervisors than KVM, like e.g. Microsoft Hyper-V. Further commits will define additional hypervisor related traits like Vcpu and Vm. Each of the supported hypervisor will need to implement all traits defined from the hypervisor crate. Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-06-08 00:50:38 +00:00
edition = "2018"
hypervisor: Update Author and license info in the toml file Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-10-19 22:42:43 +00:00
license = "Apache-2.0 OR BSD-3-Clause"
hypervisor: Introduce hypervisor crate The purpose of this trait is to add support for other hypervisors than KVM, like e.g. Microsoft Hyper-V. Further commits will define additional hypervisor related traits like Vcpu and Vm. Each of the supported hypervisor will need to implement all traits defined from the hypervisor crate. Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-06-08 00:50:38 +00:00
build: add a default feature KVM It gets bubbled all the way up from hypervsior crate to top-level Cargo.toml. Cloud Hypervisor can't function without KVM at this point, so make it a default feature. Fix all scripts that use --no-default-features. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2020-07-07 11:06:40 +00:00
[features]
kvm = []
hypervisor: Introduce mshv module in the hypervisor This is the initial folder structure of the mshv module inside the hypervisor crate. The aim of this module is to support Microsoft Hyper-V as a supported Hypervisor. Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-03 22:14:04 +00:00
mshv = []
hypervisor: Introduce hypervisor crate The purpose of this trait is to add support for other hypervisors than KVM, like e.g. Microsoft Hyper-V. Further commits will define additional hypervisor related traits like Vcpu and Vm. Each of the supported hypervisor will need to implement all traits defined from the hypervisor crate. Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-06-08 00:50:38 +00:00
hypervisor: Add Vcpu trait This Vcpu trait should be implemented by each underlying hypervisor. Previously created hypervisor object should create the VM based on already selected hypervisor and Vm object should create this vcpu object based on same hyperviosr. Each of this object should be referenced by trait object i.e <dyn Vcpu>. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-03 19:23:56 +00:00
[dependencies]
anyhow = "1.0"
hypervisor: mshv: Emulate IrqFd and IOEventFd for mshv module We don't have IrqFd and IOEventFd support in the kernel for now. So an emulation layer is needed. In the future, we will be adding this support in the kernel. Co-Developed-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Wei Liu <liuwe@microsoft.com> Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-04 18:30:29 +00:00
epoll = ">=4.0.1"
hypervisor: Add Vcpu trait This Vcpu trait should be implemented by each underlying hypervisor. Previously created hypervisor object should create the VM based on already selected hypervisor and Vm object should create this vcpu object based on same hyperviosr. Each of this object should be referenced by trait object i.e <dyn Vcpu>. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-03 19:23:56 +00:00
thiserror = "1.0"
build(deps): bump libc from 0.2.80 to 0.2.81 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.80 to 0.2.81. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.80...0.2.81) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-12-08 05:46:11 +00:00
libc = "0.2.81"
hypervisor: kvm: Make MSRs set/get more flexible Based on the way KVM_GET_MSRS and KVM_SET_MSRS work, both function are very unlikely to fail, as they simply stop looping through the list of MSRs as soon as getting or setting one fails. This is causing some issues with the snapshot/restore feature, as on some platforms, we only save a subset of the list of MSRs, leading to unproper way of saving the VM. The way to address this issue is by checking the number of MSRs get/set matches the expected amount from the list. In case it does not match, we simply ignore the failing MSR and continue getting/setting the rest of the list. By doing this by iterations, we end up getting/setting as many MSRs as the platform can support. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-08-05 10:00:56 +00:00
log = "0.4.11"
build: Fix cargo fuzz build Unfortunately it seems patch entries are ignored when obtaining dependencies from another workspace. Remove the problematic kvm-ioctls and kvm-bindings patch entries and use the forked repository directly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-12-04 10:58:51 +00:00
kvm-ioctls = { git = "https://github.com/cloud-hypervisor/kvm-ioctls", branch = "ch" }
kvm-bindings = { git = "https://github.com/cloud-hypervisor/kvm-bindings", branch = "ch", features = ["with-serde", "fam-wrappers"] }
hypervisor: Modify toml file to add mshv-{bindings, ioctls) crates Signed-off-by: Muminul Islam <muislam@microsoft.com>
2020-12-03 22:43:48 +00:00
mshv-bindings = {git = "https://github.com/cloud-hypervisor/mshv", branch = "master", features = ["with-serde", "fam-wrappers"] }
mshv-ioctls = { git = "https://github.com/cloud-hypervisor/mshv", branch = "master" }
hypervisor: Add Vcpu trait This Vcpu trait should be implemented by each underlying hypervisor. Previously created hypervisor object should create the VM based on already selected hypervisor and Vm object should create this vcpu object based on same hyperviosr. Each of this object should be referenced by trait object i.e <dyn Vcpu>. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-03 19:23:56 +00:00
serde = {version = ">=1.0.27", features = ["rc"] }
serde_derive = ">=1.0.27"
serde_json = ">=1.0.9"
cargo: Move to crates.io vm-memory 0.4.0 vm-memory 0.4.0 now contains all our fixes. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-22 23:13:14 +00:00
vm-memory = { version = "0.4.0", features = ["backend-mmap", "backend-atomic"] }
hypervisor: Add Vcpu trait This Vcpu trait should be implemented by each underlying hypervisor. Previously created hypervisor object should create the VM based on already selected hypervisor and Vm object should create this vcpu object based on same hyperviosr. Each of this object should be referenced by trait object i.e <dyn Vcpu>. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-03 19:23:56 +00:00
vmm-sys-util = { version = ">=0.5.0", features = ["with-serde"] }
build: Only pull in iced-x86 for x86_64 builds Fixes: #2024 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-12-07 17:07:28 +00:00
[target.'cfg(target_arch = "x86_64")'.dependencies.iced-x86]
hypervisor: Bump iced-x86 to 1.10.0 And fix related warnings: op_kind and op_register are being deprecated as they might panic. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-12-14 10:46:40 +00:00
version = "1.10"
hypervisor: x86: Add a CpuStateManager interface For efficiently emulating x86 instructions, we need to build and pass a CPU state copy/reference to instruction emulation handlers. Those handlers will typically modify the CPU state and let the caller commit those changes back through the PlatformEmulator trait set_cpu_state method. Hypervisors typically have internal CPU state structures, that maps back to the correspinding kernel APIs. By implementing the CpuState trait, instruction emulators will be able to directly work on CPU state instances that are directly consumable by the underlying hypervisor and its kernel APIs. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-13 11:30:25 +00:00
default-features = false
hypervisor: emulator: Format instructions on error paths Formatting instructions might be costly, so we only want to do that on the emulation error paths. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-30 23:00:53 +00:00
features = ["std", "decoder", "op_code_info", "instr_info", "fast_fmt"]
hypervisor: x86: Emulate MOV And add a few unit tests based on a Mock platform. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-11-19 19:20:23 +00:00
[dev-dependencies]
env_logger = "0.8.2"
Reference in New Issue Copy Permalink