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
d5bb0781e4
cloud-hypervisor/vmm/Cargo.toml

44 lines
1.3 KiB
TOML
Raw Normal View History

cloud-hypervisor: Add a vmm crate Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-22 16:04:35 +00:00
[package]
name = "vmm"
version = "0.1.0"
authors = ["The Cloud Hypervisor Authors"]
edition = "2018"
vmm, arch, devices: Put ACPI support behind a default feature Put the ACPI support behind a feature and ensure that the code compiles without that feature by adding an extra build to Travis. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-03 13:54:06 +00:00
[features]
build: Really make the acpi feature disableable The command "cargo build --no-default-features" does not recursively disable the default features across the workspace. Instead add an acpi feature at the top-level, making it default, and then make that feature conditional on all the crate acpi features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-05 15:29:55 +00:00
default = []
arch: vmm: Move ACPI tables creation to vmm crate Remove ACPI table creation from arch crate to the vmm crate simplifying arch::configure_system() GuestAddress(0) is used to mean no RSDP table rather than adding complexity with a conditional argument or an Option type as it will evaluate to a zero value which would be the default anyway. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-11-06 17:20:55 +00:00
acpi = ["acpi_tables","devices/acpi"]
build: make PCI (virtio and vfio) disableable at build time Although included by default it is now possible to build without PCI support. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-11 16:07:33 +00:00
pci_support = ["pci", "vfio", "vm-virtio/pci_support"]
vmm: Add MMIO support Add (non-default) support for using MMIO for virtio devices. This can be tested by: cargo build --no-default-features --features "mmio" All necessary options will be included injected into the kernel commandline. Fixes: #243 Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-11 16:25:07 +00:00
mmio_support = ["vm-virtio/mmio_support"]
devices, vmm: Add legacy CMOS device Based off of crosvm revision b5237bbcf074eb30cf368a138c0835081e747d71 add a CMOS device. This environments that can't use KVM clock to get the current time (e.g. Windows and EFI.) Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-10-02 14:21:54 +00:00
cmos = ["devices/cmos"]
vmm, arch, devices: Put ACPI support behind a default feature Put the ACPI support behind a feature and ensure that the code compiles without that feature by adding an extra build to Travis. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-03 13:54:06 +00:00
cloud-hypervisor: Add a vmm crate Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-22 16:04:35 +00:00
[dependencies]
vmm, arch, devices: Put ACPI support behind a default feature Put the ACPI support behind a feature and ensure that the code compiles without that feature by adding an extra build to Travis. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-03 13:54:06 +00:00
acpi_tables = { path = "../acpi_tables", optional = true }
cloud-hypervisor: Initial kernel booting implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-28 13:16:58 +00:00
arch = { path = "../arch" }
cloud-hypervisor: Add devices crate Based on the Firecracker devices crate from commit 9cdb5b2. It is a trimmed down version compared to the Firecracker one, to remove a bunch of pulled dependencies (logger, metrics, rate limiter, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-03-07 13:56:43 +00:00
devices = { path = "../devices" }
cargo: Update micro_http Update micro_http create to allow set content type. Suggested-by: Samuel Ortiz <sameo@linux.intel.com> Tested-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com> Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
2019-11-08 17:49:51 +00:00
epoll = ">=4.0.1"
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
kvm-bindings = "0.1.1"
dep: Rely on latest kvm-ioctls crate In order to have access to the newly added signal_msi() function from the kvm-ioctls crate, this commit updates the version of the kvm-ioctls to the latest one. Because set_user_memory_region() has been swtiched to "unsafe", we also need to handle this small change in our cloud-hypervisor code directly. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-06-03 21:09:01 +00:00
kvm-ioctls = { git = "https://github.com/rust-vmm/kvm-ioctls", branch = "master" }
vmm: api: Add HTTP server The Cloud Hyper HTTP server runs a synchronous, multi-threaded loop that receives HTTP requests and tries to call the corresponding endpoint handlers for the requests URIs. An endpoint handler will parse the HTTP request and potentially translate it into and IPC request. The handler holds an notifier and an mspc Sender for respectively notifying and sending the IPC payload to the VMM API server. The handler then waits for an API server response and translate it back into an HTTP response. The HTTP server is responsible for sending the reponse back to the caller. The HTTP server uses a static routes hash table that maps URIs to endpoint handlers. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-09-18 09:14:49 +00:00
lazy_static = "1.4.0"
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"
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-08-02 11:02:17 +00:00
log = "0.4.8"
micro_http: Use Firecracker version As of commit 2b94334a, Firecracker includes all the changes we need. We can now switch to using it instead of carrying a copy. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-04 12:24:35 +00:00
micro_http = { git = "https://github.com/firecracker-microvm/firecracker", branch = "master" }
vmm: Leverage virtio-net to provide connectivity This patch expand the device registration to add a new virtio-net device in case the user provide the appropriate flag --net from the command line. If the flag is provided, the code will parse the TAP interface name and the expected MAC address from the command line. The VM will be connected to the provided TAP interface, and it will communicate the MAC address to the virtio-net driver. If the flag is not provided, the VM will not register any virtio-net device, therefore it will not have any connectivity with the host. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-09 15:01:42 +00:00
net_util = { path = "../net_util" }
build: make PCI (virtio and vfio) disableable at build time Although included by default it is now possible to build without PCI support. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-11 16:07:33 +00:00
pci = {path = "../pci", optional = true}
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 = { path = "../qcow" }
vmm: {De}serialize VmConfig We use the serde crate to serialize and deserialize the VmVConfig structure. This structure will be passed from the HTTP API caller as a JSON payload and we need to deserialize it into a VmConfig. For a convenient use of the HTTP API, we also provide Default traits implementations for some of the VmConfig fields (vCPUs, memory, etc...). Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-09-27 09:40:50 +00:00
serde = {version = ">=1.0.27", features = ["rc"] }
serde_derive = ">=1.0.27"
serde_json = ">=1.0.9"
build: make PCI (virtio and vfio) disableable at build time Although included by default it is now possible to build without PCI support. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-11 16:07:33 +00:00
vfio = { path = "../vfio", optional = true }
vmm: Use virtio-blk to support booting from disk image After the virtio-blk device support has been introduced in the previous commit, the vmm need to rely on this new device to boot from disk images instead of initrd built into the kernel. In order to achieve the proper support of virtio-blk, this commit had to handle a few things: - Register an ioevent fd for each virtqueue. This important to be notified from the virtio driver that something has been written on the queue. - Fix the retrieval of 64bits BAR address. This is needed to provide the right address which need to be registered as the notification address from the virtio driver. - Fix the write_bar and read_bar functions. They were both assuming to be provided with an address, from which they were trying to find the associated offset. But the reality is that the offset is directly provided by the Bus layer. - Register a new virtio-blk device as a virtio-pci device from the vm.rs code. When the VM is started, it expects a block device to be created, using this block device as the VM rootfs. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-05-06 17:27:40 +00:00
vm-allocator = { path = "../vm-allocator" }
vfio: Create VFIO implementation of ExternalDmaMapping With this implementation of the trait ExternalDmaMapping, we now have the tool to provide to the virtual IOMMU to trigger the map/unmap on behalf of the guest. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-07 17:48:44 +00:00
vm-virtio = { path = "../vm-virtio" }
cargo: Update to the latest kvm-ioctls version We need to rely on the latest kvm-ioctls version to benefit from the recent addition of unregister_ioevent(), allowing us to detach a previously registered eventfd to a PIO or MMIO guest address. Because of this update, we had to modify the current constraint we had on the vmm-sys-util crate, using ">= 0.1.1" instead of being strictly tied to "0.2.0". Once the dependency conflict resolved, this commit took care of fixing build issues caused by recent modification of kvm-ioctls relying on EventFd reference instead of RawFd. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-30 16:38:38 +00:00
vmm-sys-util = ">=0.1.1"
vm-virtio: Implement console size config feature One of the features of the virtio console device is its size can be configured and updated. Our first iteration of the console device implementation is lack of this feature. As a result, it had a default fixed size which could not be changed. This commit implements the console config feature and lets us change the console size from the vmm side. During the activation of the device, vmm reads the current terminal size, sets the console configuration accordinly, and lets the driver know about this configuration by sending an interrupt. Later, if someone changes the terminal size, the vmm detects the corresponding event, updates the configuration, and sends interrupt as before. As a result, the console device driver, in the guest, updates the console size. Signed-off-by: A K M Fazla Mehrab <fazla.mehrab.akm@intel.com>
2019-07-23 19:18:20 +00:00
signal-hook = "0.1.10"
cloud-hypervisor: Add a vmm crate Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-22 16:04:35 +00:00
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-06 01:51:43 +00:00
[dependencies.linux-loader]
build: Switch over to using rust-vmm linux-loader crate With everything now merged upstream we no longer need to rely on Cathy's fork. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-06-13 10:07:32 +00:00
git = "https://github.com/rust-vmm/linux-loader"
vmm: Add bzimage loader support VMM may load different format kernel image to start guest, we currently only have elf loader support, so add bzimage loader support in case that VMM would like to load bzimage. Signed-off-by: Cathy Zhang <cathy.zhang@intel.com>
2019-06-10 09:14:02 +00:00
features = ["elf", "bzimage"]
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-06 01:51:43 +00:00
cloud-hypervisor: Add a vmm crate Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-22 16:04:35 +00:00
[dependencies.vm-memory]
git = "https://github.com/rust-vmm/vm-memory"
features = ["backend-mmap"]
Reference in New Issue Copy Permalink