kvm : the Linux Virtual Machine Monitor

By Avi Kivity, Anthony Liguori. 2007

1,813 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/eb20501b8f40704ad6d0ec5cf9dae6d11df77805

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

NOVA: a microhypervisor-based secure virtualization architecture (2010, methodology): “We measured the performance of KVM-L4 on the AMD machine, because KVM-L4 currently does not support Intel CPUs.”
An updated performance comparison of virtual machines and Linux containers (2015, background): “Both VMs and containers are mature technologies that have beneﬁted from a decade of incremental hardware and software optimizations.”
IX: A Protected Dataplane Operating System for High Throughput and Low Latency (2014, background): “, to build type-2 hypervisors [10, 33], run virtual appliances [55], or provide processes with access to privileged instructions [7].”
vCUDA: GPU accelerated high performance computing in virtual machines (2009, methodology): “A variety of VMM platforms [21], [4], [36] provide a complete and consistent view of the underlying hardware to the VM running on top of it.”
Dune: Safe User-level Access to Privileged CPU Features (2012, unknown): “Our implementation is based partially on KVM [30].”
The Turtles Project: Design and Implementation of Nested Virtualization (2010, methodology): “Linux has built-in hypervisor functionality via the KVM [29] hypervisor.”
FLUSH+RELOAD: A High Resolution, Low Noise, L3 Cache Side-Channel Attack (2014, background): “For the cross-VM scenario we used two different hypervisors: VMware ESXi 5.1 on the HP machine and Centos 6.5 with KVM on the Dell machine.”
My VM is Lighter (and Safer) than your Container (2017, background): “A number of works have looked into optimizing hyper-visors such as Xen, KVM and VMWare [3, 20, 47] to reduce their overheads in terms of boot times and other metrics.”
Live virtual machine migration with adaptive, memory compression (2009, methodology): “These include hypervisorbased approaches such as VMware [9], Xen [21], and KVM [22], operating-system level approaches such as OpenVZ system [23], as well as migration over wide-area network [24][25].”
CloudVisor: retrofitting protection of virtual machines in multi-tenant cloud with nested virtualization (2011, background): “A part of our further work includes the evaluation of CloudVisor on other VMMs (such as VMware, KVM and BitVisor [57]) and OSes (such as MAC OS and FreeBSD).”
Post-copy based live virtual machine migration using adaptive pre-paging and dynamic self-ballooning (2009, methodology): “These include hypervisor-based approaches from VMware (18), Xen (3), and KVM (13), OS-level approaches that do not use hypervisors from OpenVZ (20), as well as wide-area migration (2).”
A Holistic Evaluation of Docker Containers for Interfering Microservices (2018, unknown): “Xen [1], VMWare [2], KVM [3], etc.”
RIDL: Rogue In-Flight Data Load (2019, methodology): “Similar solutions have been deployed on other hypervisors such as KVM [8].”
virtio: towards a de-facto standard for virtual I/O devices (2008, background): “This has the subtle e.ect of providing a path of least resistance for any new hypervisors: supporting this e.cient transport mechanism will immediately reduce the amount of work which needs to be done.”
Resource Management in Fog/Edge Computing (2018, background): “late a physical computer. Virtualized resources include CPUs, memory, network, storage devices [99], and even GPUs and FPGAs [100]. Virtualization software called a hypervisor (e.g., Xen [101] or KVM [102]) virtualizes the physical resources and provides the virtualized resources in the form of a VM”