Virtual switching without a hypervisor for a more secure cloud

Xin Jin, Eric Keller, Jennifer Rexford

Research output: Contribution to conferencePaperpeer-review

12 Scopus citations

Abstract

Cloud computing leverages virtualization to offer resources on demand to multiple “tenants”. However, sharing the server and network infrastructure creates new vulnerabilities, where one tenant can attack another by compromising the underlying hypervisor. We design a system that supports virtualized networking using software switches without a hypervisor. In our architecture, the software switch runs in a Switch Domain (DomS) that is separate from the control VM. Both the guest VMs and DomS run directly on the server hardware, with processing and memory resources allocated in advance. Each guest VM interacts with the software switch through a shared memory region using periodic polling to detect network packets. The communication does not involve the hypervisor or the control VM. In addition, any software bugs that crash the software switch do not crash the rest of the system, and a crashed switch can be easily rebooted. Experiments with our initial prototype, built using Xen and Open vSwitch, show that the combination of shared pages and polling offers reasonable performance compared to conventional hypervisor-based solutions.

Original languageEnglish (US)
StatePublished - 2012
Event2nd USENIX Workshop on Hot Topics in Management of Internet, Cloud, and Enterprise Networks and Services, Hot-ICE 2012 - San Jose, United States
Duration: Apr 24 2012 → …

Conference

Conference2nd USENIX Workshop on Hot Topics in Management of Internet, Cloud, and Enterprise Networks and Services, Hot-ICE 2012
Country/TerritoryUnited States
CitySan Jose
Period4/24/12 → …

All Science Journal Classification (ASJC) codes

  • Management Information Systems
  • Computer Networks and Communications

Fingerprint

Dive into the research topics of 'Virtual switching without a hypervisor for a more secure cloud'. Together they form a unique fingerprint.

Cite this