cloud-hypervisor/vmm/Cargo.toml

[package]
name = "vmm"
version = "0.1.0"
authors = ["The Cloud Hypervisor Authors"]
edition = "2018"

[dependencies]
arch = { path = "../arch" }
devices = { path = "../devices" }
epoll = "=4.0.1"
kvm-bindings = "0.1"
kvm-ioctls = { git = "https://github.com/rust-vmm/kvm-ioctls", branch = "master" }
libc = ">=0.2.39"
log = "*"
net_util = { path = "../net_util" }
pci = {path = "../pci"}
qcow = { path = "../qcow" }
vfio = { path = "../vfio" }
vm-virtio = { path = "../vm-virtio" }
vm-allocator = { path = "../vm-allocator" }
vmm-sys-util = { git = "https://github.com/rust-vmm/vmm-sys-util" }

[dependencies.linux-loader]
git = "https://github.com/rust-vmm/linux-loader"
features = ["elf", "bzimage"]

[dependencies.vm-memory]
git = "https://github.com/rust-vmm/vm-memory"
features = ["backend-mmap"]
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"`

			`[dependencies]`
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" }`
vmm: Add a basic stdin loop After starting all vCPUs, we loop for STDIN input. We need a more scalable eventfd control loop, obviously. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-03-18 20:59:50 +00:00			`epoll = "=4.0.1"`
cloud-hypervisor: Add a vmm crate Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-02-22 16:04:35 +00:00			`kvm-bindings = "0.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: Basic Vcpu implementation Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-02-28 14:26:30 +00:00			`libc = ">=0.2.39"`
vmm: Simplify the vcpu run switch Use a catchall case for all reasons that we do not handle, and move the vCPU run switch into its own function. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-05-19 02:24:47 +00:00			`log = "*"`
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" }`
vmm: Add PCI root Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-04-18 10:26:09 +00:00			`pci = {path = "../pci"}`
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: Support direct device assignment With the VFIO crate, we can now support directly assigned PCI devices into cloud-hypervisor guests. We support assigning multiple host devices, through the --device command line parameter. This parameter takes the host device sysfs path. Fixes: #60 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-07-15 09:42:40 +00:00			`vfio = { path = "../vfio" }`
vmm: Use virtio-blk to support booting from disk image After the virtio-blk device support has been introduced in the previous commit, the vmm need to rely on this new device to boot from disk images instead of initrd built into the kernel. In order to achieve the proper support of virtio-blk, this commit had to handle a few things: - Register an ioevent fd for each virtqueue. This important to be notified from the virtio driver that something has been written on the queue. - Fix the retrieval of 64bits BAR address. This is needed to provide the right address which need to be registered as the notification address from the virtio driver. - Fix the write_bar and read_bar functions. They were both assuming to be provided with an address, from which they were trying to find the associated offset. But the reality is that the offset is directly provided by the Bus layer. - Register a new virtio-blk device as a virtio-pci device from the vm.rs code. When the VM is started, it expects a block device to be created, using this block device as the VM rootfs. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2019-05-06 17:27:40 +00:00			`vm-virtio = { path = "../vm-virtio" }`
			`vm-allocator = { path = "../vm-allocator" }`
vendor: Move to the rust-vmm vmm-sys-util package Locked to 60fe35be but no longer dependent on liujing2 repo. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-06-04 11:23:52 +00:00			`vmm-sys-util = { git = "https://github.com/rust-vmm/vmm-sys-util" }`
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"]`