Transcript Virtualization with Windows 2008 Hyper-V

PDI 2009
Lance Baatz and Jason Huitt
ACNS






Introduction
Hyper-V Architecture
Installing Hyper-V and creating Virtual
Machines using Hyper-V Manager
System Center Virtual Machine Manager
Our (ACNS’s) Setup
Questions
To get the most out of this session, please feel free
to jump in with your questions at any time.

Hyper-V is Microsoft’s hypervisor
◦ Type 1 “bare-metal” as opposed to Type 2 “hosted”

Included as a beta in RTM Server 2008
◦ Officially released on June 26, 2008 as an update
◦ Free “Hyper-V Server 2008” released Oct. 1 2008

Hyper-V is a “Role” available for enabling
◦ 64-bit versions of 2008 Enterprise and Datacenter
◦ Requires x64-based Intel VT or AMD-V processors
◦ DEP and Virtualization must be enabled in BIOS
“It provides simple partitioning functionality and is responsible for maintaining strong
isolation between partitions. It has an inherently secure architecture with minimal attack
surface, as it does not contain any third-party device drivers.”
- Microsoft

Windows Server 2008 x64
◦ Datacenter: Unlimited Windows-based Guest VMs
◦ Enterprise: Maximum of four Windows-based Guest
VMs running at any one time
◦ CALs are required regardless of server OS version

Server 2008 Server Core
◦ Hyper-V is supported, however…
 Initial Setup and Configuration
 Troubleshooting
 Lack of a GUI for network configuration is unpleasant
◦ Our recommendation: avoid Server Core for Hyper-V
until you are very familiar with each moving part


Obtain as much horsepower as possible
RAM….lots of it
◦ You cannot commit more memory to VMs than
physically exists in the host machine

2 NICs
◦ Dedicated NIC for host
◦ Dedicated NIC for Hyper-V

Storage
◦ Depends on purpose of the system







Windows NT Architecture
Virtual Server 2005
Server 2008 without Hyper-V
Server 2008 with Hyper-V
VMWare Comparison
Hardware Presented to Guest OS
Hyper-V Networking



Dedicated underlying OS
Requires custom device drivers
Potential advantages:
◦ Provides support for virtualizing USB devices
◦ Supports memory overcommit

Potential disadvantages:
◦ Supports memory overcommit
◦ Much more expensive than Hyper-V for production
system
◦ Moves away from “Microsoft across the board…”










Chipset
◦
Intel 440BX
◦
Based on the host CPU, selections made in System Center Virtual Machine Manager
◦
AMI BIOS
◦
S3 Trio 32/64 with 4MB of video memory
◦
As much as you allocate – cannot allocate more than physically present on host PC
◦
PS/2 Mouse and Keyboard
◦
Up to two 1.44MB 3.5" floppy drives
◦
Two channels, each of which supports up to two devices each (up to four IDE total devices)
◦
Up to four Adaptec 2940 SCSI Controllers (each supports up to 7 devices; 28 devices total)
◦
DEC/Intel 21140 10/100Mb network interface cards
CPU
BIOS
Video
Memory
Input Devices
Floppy Drives
IDE Controllers
SCSI Controllers
Network Interfaces

Easy in practice, can be difficult to
conceptualize
 In other words, take it slow and methodically & document!


Best practice: dedicate a NIC for management
Hyper-V supports 802.11Q – VLAN Tagging
 Allows support for multiple IP subnets on a single wire
 Can eliminate the need for a NIC on every network

Three types of Hyper-V networks
 External – Provides direct access to physical network
 Internal – Isolated within host, between VMs and host
 Private – Isolated within host, no access from host OS

Legacy Network Adapter (Emulated)
◦
◦
◦
◦

Basic NIC presented to an “unenlightened” guest
Supports PXE boot for Remote Installation Services
Support for this NIC in WinPE by default
Basic OS support going back to Windows 95
“Enhanced” Network Adapter
◦
◦
◦
◦
Requires Integration Components for OS to use
No PXE boot
Much faster performance
Driver included in Server 2008 / Vista by default

Create and Manage Virtual Machines
◦ Add disks, networks, etc.
◦ Set automatic start and stop options
◦ Snapshots

Create Virtual Hard Disks
◦ Fixed vs Dynamically Expanding
◦ Fixed disks must be created prior to a virtual
machine being created


Manage Virtual Networks
Connect to Virtual Machines

Install “Integration Components” aka
“Integration Services”
◦ Allows for better user experience when connecting
to VMs and “enlightens” the Guest Virtual Machine
◦ Integration Components are already installed in
Vista and Server 2008
◦ Integration Components exist for XP, Server 2003,
and several flavors of Linux

Build “library” of VHDs
◦ Create Virtual Machine, install software, sysprep,
shutdown, and copy VHD to “library”

Demonstration…





Capable of managing Hyper-V and newer
VMWare deployments
P2V (Physical to Virtual) conversions
Catalogs Virtual Machine deployments across
servers and simplifies the process of moving VMs
from one host to another
Provides a management interface for
virtualization resources - VHDs, hardware
configs, etc…
Integrates nicely with Operations Manager
 Including performance and resource optimization monitoring

Heads Ups:
◦
◦
◦
◦
Install on a dedicated server
Install Hyper-V role on VMM server
Requires SQL Server
Still need to use Hyper-V Manager for some things
 Creating VHDs
 Installing Integration Services

Demonstration…

Three Production Hyper-V Hosts
◦ Two stand alone host servers
◦ One 3-node cluster
 Requires shared storage, currently using iSCSI

Virtualized Servers/Services
◦ Single-purpose servers
◦ Test environments
◦ No plans to virtualize Exchange or production SQL
Server services


Currently being done at the “guest”
Future Options:
◦ Data Protection Manager
◦ EqualLogic tools
Remember to fill out the
evaluations!!
Jason Huitt [email protected]
Lance Baatz [email protected]



"Mark Russinovich: On Working at Microsoft, Windows Server 2008 Kernel, MinWin vs ServerCore, HyperV", MSDN
Channel 9, Dec. 14, 2007: http://channel9.msdn.com/shows/Going+Deep/Mark-Russinovich-On-Working-atMicrosoft-Windows-Server-2008-Kernel-MinWin-vs-ServerCore-HyperV/
"Inside Windows Server 2008 Kernel Changes", Mark Russinovich, TechNet Magazine, March 2008:
http://technet.microsoft.com/en-us/magazine/2008.03.kernel.aspx
"How is Windows Hyper-V different from the old Virtual Server Application", Ido Goldberg, 2008-09-23,
Microsoft: http://blogs.microsoft.co.il/blogs/idogold/archive/2008/09/23/how-is-windows-hyper-v-differentfrom-the-old-virtual-server-application.aspx

"Understanding Networking with Hyper-V", Ben Armstrong, 2008-01-08, MSDN Blogs:
http://blogs.msdn.com/virtual_pc_guy/archive/2008/01/08/understanding-networking-with-hyper-v.aspx

"How does basic networking work in Hyper-V?", John Howard, 2008-06-16, Microsoft Technet:
http://blogs.technet.com/jhoward/archive/2008/06/16/how-does-basic-networking-work-in-hyper-v.aspx

"WinHEC 2006 Presentation slides are available online", John Howard, 2006-06-14, Microsoft TechNet:
http://blogs.technet.com/virtualization/archive/2006/06/14/WinHEC-2006-Slides.aspx

"Hypervisor Top Level Functional Specification v1.0.docx", Microsoft, 2008-12-05:
http://www.microsoft.com/downloads/details.aspx?FamilyID=91e2e518-c62c-4ff2-8e503a37ea4100f5&displaylang=en

"Virtualization with Hyper-V: Technical Resources", Microsoft:
http://www.microsoft.com/windowsserver2008/en/us/hyperv-technical-resources.aspx

"Configuring Virtual Networks", Microsoft TechNet: http://technet.microsoft.com/en-us/library/cc816585.aspx

Download the Hyper-V Management Console for Vista here: http://support.microsoft.com/kb/952627