Bringing Virtualization to the x86 Architecture with the Original VMware Workstation

Abstract

This article describes the historical context, technical challenges, and main implementation techniques used by VMware Workstation to bring virtualization to the x86 architecture in 1999. Although virtual machine monitors (VMMs) had been around for decades, they were traditionally designed as part of monolithic, single-vendor architectures with explicit support for virtualization. In contrast, the x86 architecture lacked virtualization support, and the industry around it had disaggregated into an ecosystem, with different vendors controlling the computers, CPUs, peripherals, operating systems, and applications, none of them asking for virtualization. We chose to build our solution independently of these vendors.As a result, VMware Workstation had to deal with new challenges associated with (i) the lack of virtualization support in the x86 architecture, (ii) the daunting complexity of the architecture itself, (iii) the need to support a broad combination of peripherals, and (iv) the need to offer a simple user experience within existing environments. These new challenges led us to a novel combination of well-known virtualization techniques, techniques from other domains, and new techniques.VMware Workstation combined a hosted architecture with a VMM. The hosted architecture enabled a simple user experience and offered broad hardware compatibility. Rather than exposing I/O diversity to the virtual machines, VMware Workstation also relied on software emulation of I/O devices. The VMM combined a trap-and-emulate direct execution engine with a system-level dynamic binary translator to efficiently virtualize the x86 architecture and support most commodity operating systems. By relying on x86 hardware segmentation as a protection mechanism, the binary translator could execute translated code at near hardware speeds. The binary translator also relied on partial evaluation and adaptive retranslation to reduce the overall overheads of virtualization.Written with the benefit of hindsight, this article shares the key lessons we learned from building the original system and from its later evolution.

Phoenix: A Framework to Support Transient Overloads on Cloud Computing Environments

“…This system uses controllers based on fuzzy logic to detect the saturation of PMs and proposes algorithms to reciprocate VM automatically, considering VM usage profiles and availability of resources in each PM. VOLTAIC is compatible with most platforms that support the libvirt library, such as: Xen [8], VMWare [9] and KVM [11].…”

Victim Based Statistical Filtering : A New Deterrent Against Spoofed DoS Traffic

“…There are 3 legitimate clients as well who want to access the services of the server machine. The server is running on VMware Player V7 [33], hosted on a Windows 8.1 machine (6.3 build 9600) with Intel® Core™ i5 2.8 GHz, 4 GB RAM. The attacker launches the DoS attack from his machine which is running Kali Linux using a socket-stress testing framework Sockstress.…”

SoK: Introspections on Trust and the Semantic Gap

“…By analogy, although initial hypervisors went through heroic efforts to virtualize unmodified legacy OSes on an ISA very unsuitable for virtualization [26], most modern OSes now implement paravirtualization support [25]. Essentially, paravirtualization makes small modifications to the guest OS that eliminate the most onerous features to emulate.…”