Publication | Closed Access
NoHype
240
Citations
22
References
2010
Year
Unknown Venue
VirtualizationEngineeringInformation SecurityVirtualization SecurityCloud ComputingVirtualized InfrastructureData PrivacyVirtualization SupportVirtualization ToolCloud Computing SecurityComputer ScienceNohype ArchitectureVirtualization LayerData SecurityCryptography
Cloud computing relies on virtualization, but the shared virtualization layer introduces a major security risk by allowing attackers to compromise all virtual machines on a host. This paper proposes eliminating the hypervisor while preserving its essential functions. The NoHype architecture replaces the hypervisor by directly managing CPU, memory, I/O, networking, and guest VM lifecycle through hardware extensions. We demonstrate that the required features are already available as processor and I/O hardware extensions, making NoHype a practical, hype‑free alternative.
Cloud computing is a disruptive trend that is changing the way we use computers. The key underlying technology in cloud infrastructures is virtualization -- so much so that many consider virtualization to be one of the key features rather than simply an implementation detail. Unfortunately, the use of virtualization is the source of a significant security concern. Because multiple virtual machines run on the same server and since the virtualization layer plays a considerable role in the operation of a virtual machine, a malicious party has the opportunity to attack the virtualization layer. A successful attack would give the malicious party control over the all-powerful virtualization layer, potentially compromising the confidentiality and integrity of the software and data of any virtual machine. In this paper we propose removing the virtualization layer, while retaining the key features enabled by virtualization. Our NoHype architecture, named to indicate the removal of the hypervisor, addresses each of the key roles of the virtualization layer: arbitrating access to CPU, memory, and I/O devices, acting as a network device (e.g., Ethernet switch), and managing the starting and stopping of guest virtual machines. Additionally, we show that our NoHype architecture may indeed be "no hype" since nearly all of the needed features to realize the NoHype architecture are currently available as hardware extensions to processors and I/O devices.
| Year | Citations | |
|---|---|---|
Page 1
Page 1