VMWARE W HWHITE I T E PPAPER A P E R Virtualization Overview 1
Table of Contents Introduction... 3 Virtualization in a Nutshell... 3 Virtualization Approaches... 4 Virtualization for Server Consolidation and Containment... 7 How Virtualization Complements New-Generation Hardware... 8 Para-virtualization... 8 VMware s Virtualization Portfolio... 9 Glossary... 10 2
Virtualization Overview Introduction Among the leading business challenges confronting CIOs and IT managers today are: cost-effective utilization of IT infrastructure; responsiveness in supporting new business initiatives; and flexibility in adapting to organizational changes. Driving an additional sense of urgency is the continued climate of IT budget constraints and more stringent regulatory requirements. Virtualization is a fundamental technological innovation that allows skilled IT managers to deploy creative solutions to such business challenges. Virtualization in a Nutshell Simply put, virtualization is an idea whose time has come. The term virtualization broadly describes the separation of a resource or request for a service from the underlying physical delivery of that service. With virtual memory, for example, computer software gains access to more memory than is physically installed, via the background swapping of data to disk storage. Similarly, virtualization techniques can be applied to other IT infrastructure layers - including networks, storage, laptop or server hardware, operating systems and applications. This blend of virtualization technologies - or virtual infrastructure - provides a layer of abstraction between computing, storage and networking hardware, and the applications running on it (see Figure 1). The deployment of virtual infrastructure is non-disruptive, since the user experiences are largely unchanged. However, virtual infrastructure gives administrators the advantage of managing pooled resources across the enterprise, allowing IT managers to be more responsive to dynamic organizational needs and to better leverage infrastructure investments. Before Virtualization: Single OS image per machine Software and hardware tightly coupled Running multiple applications on same machine often creates conflict Underutilized resources Inflexible and costly infrastructure After Virtualization: Hardware-independence of operating system and applications Virtual machines can be provisioned to any system Can manage OS and application as a single unit by encapsulating them into virtual machines Figure 1: Virtualization 3
Using virtual infrastructure solutions such as those from VMware, enterprise IT managers can address challenges that include: Server Consolidation and Containment Eliminating server sprawl via deployment of systems as virtual machines (VMs) that can run safely and move transparently across shared hardware, and increase server utilization rates from 5-15% to 60-80%. Test and Development Optimization Rapidly provisioning test and development servers by reusing pre-configured systems, enhancing developer collaboration and standardizing development environments. Business Continuity Reducing the cost and complexity of business continuity (high availability and disaster recovery solutions) by encapsulating entire systems into single files that can be replicated and restored on any target server, thus minimizing downtime. Enterprise Desktop Securing unmanaged PCs, workstations and laptops without compromising end user autonomy by layering a security policy in software around desktop virtual machines. Virtualization Approaches While virtualization has been a part of the IT landscape for decades, it is only recently (in 1998) that VMware delivered the benefits of virtualization to industry-standard x86-based platforms, which now form the majority of desktop, laptop and server shipments. A key benefit of virtualization is the ability to run multiple operating systems on a single physical system and share the underlying hardware resources known as partitioning. Today, virtualization can apply to a range of system layers, including hardware-level virtualization, operating systemlevel virtualization, and high-level language virtual machines. Hardware-level virtualization was pioneered on IBM mainframes in the 1970s, and then more recently Unix/RISC system vendors began with hardware-based partitioning capabilities before moving on to software-based partitioning. For Unix/RISC and industry-standard x86 systems, the two approaches typically used with software-based partitioning are hosted and hypervisor architectures (See Figure 2). A hosted approach provides partitioning services on top of a standard operating system and supports the broadest range of hardware configurations. In contrast, a hypervisor r architecture is the first layer of software installed on a clean x86-based system (hence it is often referred to as a bare metal approach). Since it has direct access to the hardware resources, a hypervisor is more efficient than hosted architectures, enabling greater scalability, robustness and performance. Hosted Architecture Installs and runs as an application Relies on host OS for device support and physical resource management Bare-Metal (Hypervisor) Architecture Lean virtualization-centric kernel Service Console for agents and helper applications Figure 2: Virtualization Architectures 4
Hypervisors can be designed to be tightly coupled with operating systems or can be agnostic to operating systems. The latter approach provides customers with the capability to implement an OS-neutral management paradigm, thereby providing further rationalization of the data center. Application-level partitioning is another approach, whereby many applications share a single operating system, but this offers less isolation (and higher risk) than hardware or software partitioning, and limited support for legacy applications or heterogeneous environments. However, various partitioning techniques can be combined, albeit with increased complexity. Hence, virtualization is a broad IT initiative, of which partitioning is just one facet. Other benefits include the isolation of virtual machines and the hardware-independence that results from the virtualization process. Virtual machines are highly portable, and can be moved or copied to any industry-standard (x86- based) hardware platform, regardless of the make or model. Thus, virtualization facilitates adaptive IT resource management, and greater responsiveness to changing business conditions (see Figures 3-5). To provide advantages beyond partitioning, several system resources must be virtualized and managed, including CPUs, main memory, and I/O, in addition to having an inter-partition resource management capability. While partitioning is a useful capability for IT organizations, true virtual infrastructure delivers business value well beyond that. Figure 3: Traditional Infrastructure 5
Hardware/Software Separation Figure 4: Virtual Infrastructure Infrastructure is what connects resources to your business. Virtual Infrastructure is a dynamic mapping of your resources to your business. Result: decreased costs and increased efficiencies and responsiveness Figure 5: VMware Virtual Infrastructure Transforms farms of individual x86 servers, storage, and networking into a pool of computing resources 6
Virtualization for Server Consolidation and Containment Virtual infrastructure initiatives often spring from data center server consolidation projects, which focus on reducing existing infrastructure box count, retiring older hardware or life-extending legacy applications. Server consolidation benefits result from a reduction in the overall number of systems and related recurring costs (power, cooling, rack space, etc.) While server consolidation addresses the reduction of existing infrastructure, server containment takes a more strategic view, leading to a goal of infrastructure unification. Server containment uses an incremental approach to workload virtualization, whereby new projects are provisioned with virtual machines rather than physical servers, thus deferring hardware purchases. It is important to note that neither consolidation nor containment should be viewed as standalone exercise. In either case, the most significant benefits result from adopting a total costof-ownership (TCO) perspective, with a focus on the ongoing, recurring support and management costs, in addition to onetime, up-front costs. Data center environments are becoming more complex and heterogeneous, with correspondingly higher management costs. Virtual infrastructure enables more effective optimization of IT resources, through the standardization of data center elements that need to be managed. Partitioning alone does not deliver server consolidation or containment, and in turn consolidation does not equate to full virtual infrastructure management. Beyond partitioning and basic component-level resource management, a core set of systems management capabilities are required to effectively implement realistic data center solutions (see Figure 6). These management capabilities should include comprehensive system resource monitoring (of metrics such as CPU activity, disk access, memory utilization and network bandwidth), automated provisioning, high availability and workload migration support. VM VM VM VM Management and Distributed Virtualization Services VirtualCenter VMotion Provisioning Consolidated Backup DRS DAS Distributed Services VMM VMM VMM VMM Resource Management CPU Virtualization VMFS MPIO MMU Virtualization ESX Server Virtual Networking Other Enterprise Features I/O Virtualization Monitor Enterprise-Class Features Hypervisor CPU Memory NIC Disk Hardware Blade Hardware Other Hardware Hardware Certification Figure 6: Virtual Infrastructure Management 7
How Virtualization Complements New- Generation Hardware Extensive scale-out and multi-tier application architectures are becoming increasingly common, and the adoption of smaller form-factor blade servers is growing dramatically. Since the transition to blade architectures is generally driven by a desire for physical consolidation of IT resources, virtualization is an ideal complement for blade servers, delivering benefits such as resource optimization, operational efficiency and rapid provisioning. The latest generation of x86-based systems feature processors with 64-bit extensions supporting very large memory capacities. This enhances their ability to host large, memory-intensive applications, as well as allowing many more virtual machines to be hosted by a physical server deployed within a virtual infrastructure. The continual decrease in memory costs will further accelerate this trend. Likewise, the forthcoming dual-core processor technology significantly benefits IT organizations by dramatically lowering the costs of increased performance. Compared to traditional single-core systems, systems utilizing dual-core processors will be less expensive, since only half the number of sockets will be required for the same number of CPUs. By significantly lowering the cost of multi-processor systems, dual-core technology will accelerate data center consolidation and virtual infrastructure projects, Beyond these enhancements, VMware is also working closely with both Intel and AMD to ensure that new processor technology features are exploited by virtual infrastructure to the fullest extent. In particular, the new virtualization hardware assist enhancements (Intel s VT and AMD s Pacifica ) will enable robust virtualization of the CPU functionality. Such hardware virtualization support does not replace virtual infrastructure, but allows it to run more efficiently. Para-virtualization Although virtualization is rapidly becoming mainstream technology, the concept has attracted a huge amount of interest, and enhancements continue to be investigated. One of these is para-virtualization, whereby operating system compatibility is traded off against performance for certain CPU-bound applications running on systems without virtualization hardware assist (see Figure 7). The para-virtualized model offers potential performance benefits when a guest operating system or application is aware that it is running within a virtualized environment, and has been modified to exploit this. One potential downside of this approach is that such modified guests cannot ever be migrated back to run on physical hardware. In addition to requiring modified guest operating systems, paravirtualization leverages a hypervisor for the underlying technology. In the case of Linux distributions, this approach requires extensive changes to an operating system kernel so that it can coexist with the hypervisor. Accordingly, mainstream Linux distributions (such as Red Hat or SUSE) cannot be run in a paravirtualized mode without some level of modification. Likewise, Microsoft has suggested that a future version of the Windows operating system will be developed that can coexist with a new hypervisor offering from Microsoft. Yet para-virtualization is not an entirely new concept. For example, VMware has employed it by making available as an option enhanced device drivers (packaged as VMware Tools) that increase the efficiency of guest operating systems. Furthermore, if and when para-virtualization optimizations are eventually built into commercial enterprise Linux distributions, VMware s hypervisor will support those, as it does all mainstream operating systems. Figure 7: Para-virtualization 8
VMware s Virtualization Portfolio VMware pioneered x86-based virtualization in 1998 and continues to be the innovator in that market, providing the fundamental virtualization technology for all leading x86- based hardware suppliers. The company offers a variety of software-based partitioning approaches, utilizing both hosted (Workstation and VMware Server) and hypervisor (ESX Server) architectures. (see Figure 8) VMware s virtual machine (VM) approach creates a uniform hardware image implemented in software on which operating systems and applications run. On top of this platform, VMware s VirtualCenter provides management and provisioning of virtual machines, continuous workload consolidation across physical servers and VMotion technology for virtual machine mobility. VirtualCenter is virtual infrastructure management software that centrally manages an enterprise s virtual machines as a single, logical pool of resources. With VirtualCenter, an administrator can manage thousands of Windows NT, Windows 2000, Windows 2003, Linux and NetWare servers from a single point of control. Unique to VMware is the VMotion technology, whereby live, running virtual machines can be moved from one physical system to another while maintaining continuous service availability. VMotion thus allows fast reconfiguration and optimization of resources across the virtual infrastructure. VMware is the only provider of high-performance virtualization products that give customers a real choice in operating systems. VMware supports: Windows 95/98/NT/2K/2003/XP/3.1/MS-DOS 6; Linux (Red Hat, SUSE, Mandrake, Caldera); FreeBSD (3.x, 4.0-4.9); Novell (NetWare 4,5,6); Sun Solaris 9 and 10 (experimental). VMware is designed from the ground up to ensure compatibility with customers existing software infrastructure investments. This includes not just operating systems, but also software for management, high availability, clustering, replication, multipathing, and so on. VMware s hypervisor-based products and solutions have been running at customer sites since 2001, with more than 75% of customers running ESX Server in production deployments. As the clear x86 virtualization market leader, VMware is uniquely positioned to continue providing robust, supportable, highperformance virtual infrastructure for real-world, enterprise data center applications. App Ap p App App OS O S OS OS CONSISTENT VIRTUAL HARDWARE PLATFORM Open Interfaces VMware Infrastructure ACE Secured Enterprise Desktop Workstation Technical Desktop VMware Server Departmental Computing ESX Server Enterprise Computing System Architecture & Highlights Hosted on Windows Hosted on Windows or Linux Hosted on Windows or Linux Bare Metal V-SMP Option Mgmt Server, Console & APIs VMotion Figure 8: Single Virtual Platform Desktop to Enterprise 9
Glossary Virtual Machine A representation of a real machine using software that provides an operating environment which can run or host a guest operating system. Guest Operating System An operating system running in a virtual machine environment that would otherwise run directly on a separate physical system. Virtual Machine Monitor Software that runs in a layer between a hypervisor or host operating system and one or more virtual machines that provides the virtual machine abstraction to the guest operating systems. With full virtualization, the virtual machine monitor exports a virtual machine abstraction identical to a physical machine, so that standard operating systems (e.g., Windows 2000, Windows Server 2003, Linux, etc.) can run just as they would on physical hardware. Hypervisor A thin layer of software that generally provides virtual partitioning capabilities which runs directly on hardware, but underneath higher-level virtualization services. Sometimes referred to as a bare metal approach. Operating system level virtualization In this case the virtualization layer sits between the operating system and the application programs that run on the operating system. The virtual machine runs applications, or sets of applications, that are written for the particular operating system being virtualized. High-level language virtual machines In high-level language virtual machines, the virtualization layer sits as an application program on top of an operating system. The layer exports an abstraction of the virtual machine that can run programs written and compiled to the particular abstract machine definition. Any program written in the high-level language and compiled for this virtual machine will run in it. For more information: http://www.vmware.com http://www.vmware.com/solutions/ http://www.vmware.com/vinfrastructure/ Hosted Virtualization A virtualization approach where partitioning and virtualization services run on top of a standard operating system (the host). In this approach, the virtualization software relies on the host operating system to provide the services to talk directly to the underlying hardware. Para-virtualization A virtualization approach that exports a modified hardware abstraction which requires operating systems to be explicitly modified and ported to run. Virtualization Hardware Support Industry standard servers will provide improved hardware support for virtualization. Initial hardware support includes processor extensions to address CPU and some memory virtualization. Future support will include I/O virtualization, and eventually more complex memory virtualization management. Hardware-level virtualization Here the virtualization layer sits right on top of the hardware exporting the virtual machine abstraction. Because the virtual machine looks like the hardware, all the software written for it will run in the virtual machine. 10
6/21/2018 Hyper-V Technology Overview Microsoft Docs Hyper-V Technology Overview 11/29/2016 5 minutes to read Contributors In this article Some ways Hyper-V can help you Hyper-V and other virtualization products What features does Hyper-V have? How to get Hyper-V Supported operating systems How Hyper-V works What does Hyper-V consist of? Related technologies Applies To: Windows Server 2016, Microsoft Hyper-V Server 2016 Hyper-V is Microsoft's hardware virtualization product. It lets you create and run a software version of a computer, called a virtual machine. Each virtual machine acts like a complete computer, running an operating system and programs. When you need computing resources, virtual machines give you more flexibility, help save time and money, and are a more efficient way to use hardware than just running one operating system on physical hardware. Hyper-V runs each virtual machine in its own isolated space, which means you can run more than one virtual machine on the same hardware at the same time. You might want to do this to avoid problems such as a crash affecting the other workloads, or to give different people, groups or services access to different systems. Some ways Hyper-V can help you Hyper-V can help you: Establish or expand a private cloud environment. Provide more flexible, on-demand IT services by moving to or expanding your use of shared resources and adjust utilization as demand changes. Use your hardware more effectively. Consolidate servers and workloads onto fewer, more powerful physical computers to use less power and physical space. https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview 1/4
6/21/2018 Hyper-V Technology Overview Microsoft Docs Improve business continuity. Minimize the impact of both scheduled and unscheduled downtime of your workloads. Establish or expand a virtual desktop infrastructure (VDI). Use a centralized desktop strategy with VDI can help you increase business agility and data security, as well as simplify regulatory compliance and manage desktop operating systems and applications. Deploy Hyper-V and Remote Desktop Virtualization Host (RD Virtualization Host) on the same server to make personal virtual desktops or virtual desktop pools available to your users. Make development and test more efficient. Reproduce different computing environments without having to buy or maintain all the hardware you'd need if you only used physical systems. Hyper-V and other virtualization products Hyper-V in Windows and Windows Server replaces older hardware virtualization products, such as Microsoft Virtual PC, Microsoft Virtual Server, and Windows Virtual PC. Hyper-V offers networking, performance, storage and security features not available in these older products. Hyper-V and most third-party virtualization applications that require the same processor features aren't compatible. That's because the processor features, known as hardware virtualization extensions, are designed to not be shared. For details, see Virtualization applications do not work together with Hyper-V, Device Guard, and Credential Guard. What features does Hyper-V have? Hyper-V offers many features. This is an overview, grouped by what the features provide or help you do. Computing environment - A Hyper-V virtual machine includes the same basic parts as a physical computer, such as memory, processor, storage, and networking. All these parts have features and options that you can configure different ways to meet different needs. Storage and networking can each be considered categories of their own, because of the many ways you can configure them. Disaster recovery and backup - For disaster recovery, Hyper-V Replica creates copies of virtual machines, intended to be stored in another physical location, so you can restore the virtual machine from the copy. For backup, Hyper-V offers two types. One uses saved states and the other uses Volume Shadow Copy Service (VSS) so you can make application-consistent backups for programs that support VSS. https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview 2/4
6/21/2018 Hyper-V Technology Overview Microsoft Docs Optimization - Each supported guest operating system has a customized set of services and drivers, called integration services, that make it easier to use the operating system in a Hyper-V virtual machine. Portability - Features such as live migration, storage migration, and import/export make it easier to move or distribute a virtual machine. Remote connectivity - Hyper-V includes Virtual Machine Connection, a remote connection tool for use with both Windows and Linux. Unlike Remote Desktop, this tool gives you console access, so you can see what's happening in the guest even when the operating system isn't booted yet. Security - Secure boot and shielded virtual machines help protect against malware and other unauthorized access to a virtual machine and its data. For a summary of the features introduced in this version, see What's new in Hyper-V on Windows Server 2016. Some features or parts have a limit to how many can be configured. For details, see Plan for Hyper-V scalability in Windows Server 2016. How to get Hyper-V Hyper-V is available in Windows Server and Windows, as a server role available for x64 versions of Windows Server. For server instructions, see Install the Hyper-V role on Windows Server. On Windows, it's available as feature in some 64-bit versions of Windows. It's also available as a downloadable, standalone server product, Microsoft Hyper-V Server. Supported operating systems Many operating systems will run on virtual machines. In general, an operating system that uses an x86 architecture will run on a Hyper-V virtual machine. Not all operating systems that can be run are tested and supported by Microsoft, however. For lists of what's supported, see: Supported Linux and FreeBSD virtual machines for Hyper-V on Windows Supported Windows guest operating systems for Hyper-V on Windows Server How Hyper-V works Hyper-V is a hypervisor-based virtualization technology. Hyper-V uses the Windows hypervisor, which requires a physical processor with specific features. For hardware details, see System requirements for Hyper-V on Windows Server 2016. https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview 3/4
6/21/2018 Hyper-V Technology Overview Microsoft Docs In most cases, the hypervisor manages the interactions between the hardware and the virtual machines. This hypervisor-controlled access to the hardware gives virtual machines the isolated environment in which they run. In some configurations, a virtual machine or the operating system running in the virtual machine has direct access to graphics, networking, or storage hardware. What does Hyper-V consist of? Hyper-V has required parts that work together so you can create and run virtual machines. Together, these parts are called the virtualization platform. They're installed as a set when you install the Hyper- V role. The required parts include Windows hypervisor, Hyper-V Virtual Machine Management Service, the virtualization WMI provider, the virtual machine bus (VMbus), virtualization service provider (VSP) and virtual infrastructure driver (VID). Hyper-V also has tools for management and connectivity. You can install these on the same computer that Hyper-V role is installed on, and on computers without the Hyper-V role installed. These tools are: Hyper-V Manager Hyper-V module for Windows PowerShell Virtual Machine Connection (sometimes called VMConnect) Windows PowerShell Direct Related technologies These are some technologies from Microsoft that are often used with Hyper-V: Failover Clustering Remote Desktop Services Virtual Machine Manager Various storage technologies: cluster shared volumes, SMB 3.0, storage spaces direct Windows containers offer another approach to virtualization. See the Windows Containers library on MSDN. https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview 4/4