Safe Hardware Access with the Xen Virtual Machine Monitor

By Keir Fraser, S. Hand, R. Neugebauer, I. Pratt, A. Warfield, Mark Williamson. 2007

413 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/5f5d592b683ae10ad59b237cb1f2f9cf4a836263

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

vTPM: Virtualizing the Trusted Platform Module (2006, methodology): “We use Xen’s existing shared memory mechanism (grant tables[6]) to transfer data between front- and back-end driver.”
High Performance VMM-Bypass I/O in Virtual Machines (2006, methodology): “To address this problem, VMware workstation [37] and Xen [13] carry out I/O operations in a host operating system or a special privileged VM called isolated device domain (IDD), which can run popular operating systems such as Windows and Linux that have a large number of existing device drivers.”
High performance network virtualization with SR-IOV (2010, methodology): “Xen’s PV driver [4] model uses a shared-memory-based data channel and customized interface to reduce data movement overhead, between the guest and domain 0.”
Thorough static analysis of device drivers (2006, background): “…driver’s StartIo function, and then • the driver’s plug-and-play dispatch routine with an IRP MN REMOVE DEVICE I/O request packet (to simulate the device being removed from the computer) , and ﬁnally • the driver’s Unload routine, which the operating sys-tem would call after a device remove event.”
The Turtles Project: Design and Implementation of Nested Virtualization (2010, methodology): “For efficient I/O virtualization, we bypass multiple levels of hypervisor I/O stacks to provide nested guests with direct assignment of I/O devices [11, 16, 28, 33, 49, 50] via multi-level device assignment.”
A protocol for property-based attestation (2006, background): “The recent development in the field of security kernel design (based on e.g., hypervisors or microkernels) shows that these properties can be efficiently provided (see, e.g., [25, 28, 12] and [33, 32, 2, 3 ]).”
Diagnosing performance overheads in the xen virtual machine environment (2005, background): “Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for pro.t or commercial advantage and that copies bear this notice and the full citation on the .rst page.”
Scheduling I/O in virtual machine monitors (2008, background): “Consequently, there has been a resurgence of interest in machine virtualization [2, 3, 4, 7, 9, 12, 13, 18, 19].”
Intel ® Virtualization Technology for Directed I/O (2006, methodology): “The Xen VMM has implemented this architecture as “Isolated Driver Domains” [6], and Microsoft is in the process of developing a version of this architecture in their next generation of VMMs [7].”
Unikernels: library operating systems for the cloud (2013, unknown): “VMs communicate directly by having the local VM grant memory page access rights to the remote VM via the hypervisor [17].”
Improving the reliability of commodity operating systems (2005, background): “Executing extensions in their own virtual machines solves this problem [83, 130, 72], but raises compatibility problems.”
Optimizing Network Virtualization in Xen (awarded best paper) (2006, methodology): “Despite the advances in virtualization technology [15, 4], the overhead of network I/O virtualization can still significantly affect the performance of network-intensive applications.”