An Introduction To Server Virtual Is at Ion

An Introduction to
Server Virtualisation
Alan McSweeney
A loose definition
Virtualisation is a framework or methodology of dividing the

resources of a computer into multiple execution environments,
by applying one or more concepts or technologies such as
hardware and software partitioning, time-sharing, partial or
complete machine simulation, emulation, quality of service, and
many others.
November 26, 2009 2

Some history
− An old concept — first virtual machines created

on IBM mainframes in early ’60s
− Typically, IBM's virtual machines were
identical "copies" of the underlying hardware.
Each instance could run its own operating
system.
− Virtualisation formed the basis of “time sharing”
November 26, 2009 3

Some virtual machines you may know…
− NT had Virtual DOS Machine (NTVDM) and Windows on

Win32 (WOW)
− Windows 95 used virtual machines to run older (Windows 3.x

and DOS) applications
November 26, 2009 4

The old model
− A server for every application
− Software and hardware are

tightly coupled
− Underutilised resources
introduce real cost into the
infrastructure
November 26, 2009 5

The new model
− Physical hardware is abstracted by

a virtualisation layer, or
hypervisor
− Manage OS and application as a

single unit by encapsulating them
into virtual machines
− Separate OS and hardware and

break hardware dependancies
− Optimise utilisation levels
November 26, 2009 6

Increased Hardware Utilisation
• Before Virtualisation • After Virtualisation
November 26, 2009 7

Underutilisation of Resources
• Most organisations over-

provision
− Multiple processors in each
server
− Memory requirements over-
estimated
• Aim to drive up CPU

utilisation
Actual DSS customer data – 120
servers monitored
November 26, 2009 8

Virtual Infrastructure
• Virtual infrastructure brings uniformity to

the data centre
• Dynamically map computing resources
to the business
• Lower IT costs through increased
efficiency, flexibility and responsiveness
• Provision new services and change the
amount of resources dedicated to a
software service
• Treat your data centre as a single pool of
processing, storage and networking
power
November 26, 2009 9

How is it implemented?
− Typically, in order to virtualize, you would use a layer of software that

provides the illusion of a "real" machine to multiple instances of "virtual
machines". This layer is traditionally called the Virtual Machine Monitor
(VMM) or “hypervisor”.
− The hypervisor could run directly on the real hardware or it could run as
an application on top of a host operating system.
November 26, 2009 10

Type 1 VMM
Guest Guest Guest

VM VM VM
VMM
Hardware
IBM CP/CMS
VMware ESX
Windows Virtualisation (2008)
Xen
Virtual Iron
Type 2 VMM
Guest Guest Guest

VM VM VM
VMM
Host OS
Hardware
VMware Server

Hybrid VMM
Guest Guest
VM VM
Host
VM
VMM
Hardware
MS Virtual Server
MS Virtual PC

Paravirtualisation
Paravirtualization is a virtualization technique that presents a

software interface to virtual machines that is similar but not
identical to that of the underlying hardware.
This requires operating systems to be explicitly ported to run
on top of the virtual machine monitor (VMM)

Full Virtualisation
• Provides
a complete simulation of the underlying
hardware
• With binary translation, rewrites some x86 instructions
at run time that cannot be trapped and converts them
into a series of instructions that can be trapped and
virtualised
• Capableof running existing legacy operating systems
without modification

Native Virtualisation
− Leverages hardware-assisted capabilities available in the latest

processors from Intel (Intel VT – “Vanderpool”) and Advanced
Micro Devices (AMD-V – “Pacifica”) to provide near-native
performance.
− Virtual Iron is one of the first companies to offer virtualization

software to fully support Intel-VT and AMD-V hardware
assisted virtualization.

Native Virtualisation
− Dell
• Precision 380 Intel Pentium D
• PowerEdge 430 Intel Pentium D
• PowerEdge 440 Intel Xeon 3xxx
• PowerEdge 1435 AMD Opteron 22x
− HP
• ProLiant DL140 G3 Intel Xeon 5xxx
• ProLiant DL365 AMD Opteron 22xx
• ProLiant DL385 G2 AMD Opteron 22xx
• ProLiant DL585 G2 AMD Opteron 82xx
− IBM
• xSeries 100 Intel Pentium-D
• System x3455 AMD Opteron 22xx
• System x3550 Intel Xeon 5xxx
• System x3850 Intel Xeon 7xxx HS21 Intel Xeon 5xxx
• LS21 AMD Opteron 22xx

What’s in a Virtual Machine?

What’s in a Virtual Machine - BIOS
• VM has its own BIOS

• Has everything you would
expect to see in a real BIOS
• Boot options may include
floppy, CD-ROM, disk drive
and PXE.

What’s in a Virtual Machine - Networking
• Each VM has a virtual NIC

• Virtual NICs are connected to
virtual switches implemented
in the virtualisation layer
− VMware — vSwitches
− Microsoft - .vnc-files
• Virtual switches have uplink
connections to physical NICs
on the host

Combining internal and external virtual switches
• Virtual switch with one

outbound adapter acts as a
DMZ
• Backend applications are
secured behind the firewall
using internal-only switches

What’s in a Virtual Machine - Storage
• To the applications and guest operating

systems inside each virtual machine, the
storage subsystem is a simple virtual SCSI
host bus adapter connected to one or
more virtual SCSI disks
• Virtual disks are files kept on physical
storage.
− VMware — VMDK files
− Microsoft — VDF files
• Virtual disk represents a local drive on a
virtual server, such as a C or D drive in
Windows
• Physical storage could be
− Direct attached SCSI
− SAN attached
− iSCSI
− NAS
Licensing Considerations
• On host
− Host OS?
− Virtualisation technology?
• On Guest
− Guest OS?
− Guest Applications

Support Considerations
• Two meanings
− Is it technically possible?
− Will the vendor support a virtual environment?
• The Microsoft position

− “For Microsoft customers who do not have a Premier-level support agreement,
Microsoft will require the issue to be reproduced independently from the non-
Microsoft hardware virtualization software.”
− “Microsoft supports Windows Server System software running within a Microsoft

Virtual Server environment subject to the Microsoft Support Lifecycle policy ... “

Usage Scenarios for Virtualization
Consolidation Business Continuity Management
Workload Mobility Development and Test

Usage Scenario
Production server consolidation
Gartner definition
1. Logical
2. Physical
3. Rational

Usage Scenario
Production server consolidation
• Consolidate workloads
− Infrastructure applications
− Low-utilization workloads
− Branch office and datacenter workloads
− Efficient use of available hardware resources
• Re-host legacy OS and applications
− NT4 guest applications on virtual platform
• Run on current hardware and current OS
• No application updates required
• Partition resources
− Limit CPU resource per VM

Usage Scenario
Business continuity management
• Disaster Recovery
− Maintain DR systems as virtual machines
− Eliminate traditional problems associated
with bare metal restores
• OS and application patching
− Deploy and test patches off-production, and
swap
− Eliminate scheduled downtime
• Isolation / sandboxing
− Isolate OS environments for untrusted
applications
− Prevent malicious code from affecting others

Usage Scenario
Dynamic datacenter
• Workload mobility
− Package up entire OS environment and move to other location
− Flexible deployment of workloads

Usage Scenario
Development and test
• Rapid provisioning of virtual machines

• Create arbitrary test scenarios
• Wider test range for niche scenarios

Application + OS: Now A Data File
Entire server – OS, apps, data, devices, and state – is now

simply a file.
• Server provisioning is similar

to copying a file
• Server migration is now

similar to data migration
• Data management techniques

can be used for server
management
• Server cloning/copying
• Versioning
• Server archival
• Remote mirroring

The Role of Shared Storage
• VirtualMachine files are

centrally located.
• Multiple access.
• VirtualMachines can be moved
for DR purposes, system
repair/upgrade, etc.
• Cantake advantage of advanced
SAN features such as snapshots,
clones and replication.

Live Migration
• Move running virtual machines from one physical

system to another with no downtime
• Zero downtime maintenance
• Balance resource utilisation across infrastructure

Hardware Infrastructure — Scale Up or Scale Out?
• Scaling up means fewer, larger • Scaling out means more,

systems smaller systems
− Advantages − Advantages
• Fewer ESX Server images to manage • Lower hardware costs (servers)
• Lower infrastructure costs • Low H.A. impact in case of failure
(Ethernet/SAN switches) of a node
• More CPUs supported "per rack“
− Disadvantages
• Headroom required for HA is less
• Higher hardware costs (servers) expensive
• Big H.A. impact in case of failure of a • Not locked into obsolete hardware
node
• More flexible
• Fewer CPUs supported "per rack“
• Headroom required for HA is − Disadvantages
expensive • Many hypervisor (ESX) images to
• Servers may go obsolete maintain
• Locked into server architecture • Higher infrastructure costs
(Ethernet/SAN switches)

What should an enterprise ready virtualisation
platform offer?
• Efficient server partitioning
• SMP support in guest VMs
• Scalable memory in guest VMs
• Fault isolation — a crash in one virtual machine should not
impact other virtual machines
• Security isolation — a virtual machine should never access the
memory or I/O operations of another virtual machine
• Resource isolation — runaway applications in one virtual
machine should not “starve” others virtual machines.
• Non-disruptive addition of capacity
• Scalable management tools

VMware Workstation
• Desktop Virtualisation
• Runmultiple operating systems
simultaneously on a single PC
• Supports Windows, Linux, NetWare,
Solaris
• Software development/test
• Training

VMware Server
• Free virtualisation platform

• Type 2 “hosted” VMM
• Runs on any standard x86 hardware
• Runs on a wide variety of Linux and
Windows host and guest operating
systems
• Intended as a “step up” to Type 1
hypervisor products.

VMware Infrastructure 3
• VMware ESX Server 3.0 - Type 1

VMM
• VMware VirtualCenter 2.0
• 4-way vSMP / 16GB Virtual RAM
support
• VMware VMotion
• VMware HA
• VMware Distributed Resource
Scheduling
• VMware Consolidated Backup

Non-disruptive capacity on
demand

Automate resource assurance for critical
applications
Dynamic Balancing
DRS Continuous Optimization

Automatic availability for all
applications
VMWARE HA
X
Backup anytime
VMWARE Decouple backup from production VMs

CONSOLIDATED 20-40% better resource utilization
BACKUP Pre-integrated with 3rd party backup products

Microsoft Virtualisation Products
• Virtual PC
• Microsoft Virtual Server 2005 R2
• Virtual
Machine Manager (in Beta but available for
download)
• Windows Virtualisation (to be released after Longhorn)

Virtual PC
• Suited to use in testing on a desktop environment

• Not recommended for production servers
− Single CPU support only
− No remote management possible
− No SCSI support
− Starts as an application not as a service
• Shares disk format with Virtual Server

Virtual Server 2005 R2 SP1
• Microsoft’s current offering for

virtualisation in production
environments
• Shares underlying technology
with Microsoft Virtual PC
• Web based management portal
• Guests supported include:
− Windows (up to Vista with SP1)
− Linux Virtual Server 2005 R2: Administration Website

Clustering in Virtual Server 2005 R2 SP1
Guest to Guest Host to Host
iSCSI SAN or iSCSI

connection connection
Cluster Cluster
storage storage

Virtual Server 2005 R2 SP1
• VM Additions
− VM additions provide enhanced performance and additional
functionality to the guest OS
− Additions available for XP, Windows 2003, Vista and Linux
− Windows additions provide:
• Allow for direct mode kernel execution (faster processing of some
commands)
− Linux additions provide:
• Time sync
• Shutdown support
• SCSI disk
• Does not allow for direct mode kernel execution
− Important to update for each new release to maximise
performance benefits

Windows Virtualisation
• To be released within 180 days after the Longhorn

release (no Beta available as yet)
• Requires Intel VT or AMD Virtualisation hardware
• Uses Hypervisor (a thin layer of software under the
“Host OS”)
Guest 1
Guest 2
(“Host OS”)
VMM (Hypervisor)
Hardware

Virtual Machine Manager
Virtual Machine Manager: Centralized management view

Centralized Management: Reports
Full set of
reports,
integration with
MOM database
Actions one
click away in
context sensitive
Actions Pane

Self Service Portal
Ability to control
owned virtual
machines
Thumbnails of
all owned virtual
machines
Self-Service Portal
Provisioning
User selects from list

of templates
Administrator has
associated with that
user

Self-Service Portal
Provisioning
New virtual machine

ready for use, Terminal
Services connection
information
automatically emailed
to user.

Virtual Server 2005 vs
Windows Server Virtualization
Virtual Server 2005 R2 Windows Server Virtualization
32-
32-bit VMs?
VMs? Yes Yes
64-
64-bit VMs?
VMs? No Yes
Multi-
Multi-processor VMs?
VMs? No Yes, up to 8 processor VMs
VM memory support? 3.6 GB per VM More than 32 GB per VM
Hot add memory/processors? No Yes
Hot add storage/networking? No Yes
Can be managed by System Center Yes Yes

Virtual Machine Manager?
Microsoft Cluster support? Yes Yes
Scriptable / Extensible? Yes, COM Yes, WMI

More than 64.
Number of running VMs?
VMs? 64
As many as hardware will allow.
User interface Web Interface MMC 3.0 Interface

Xen
• Open source hypervisor

solution
• Installs on bare-metal
• Linux VMs fully supported
− Red Hat
− Debian
− Suse
• Windows VMs require Intel VT
or AMD-V processor
− Microsoft Windows Server 2000
− Microsoft Windows Server 2003
− Microsoft Windows XP SP2

XenSource

XenSource Products
User Profile Enterprise IT, system Windows IT professionals Developers, testers,

integrators support, IT enthusiasts
Windows guest support Windows Server 2003; Windows Server 2003; Windows Server 2003;
Windows XP; Windows Windows XP; Windows Windows XP; Windows
2000 Server 2000 Server 2000 Server
Linux guest support Red Hat EL 3.6, 3.7, 3.8, N/A (Windows guests Red Hat EL 3.6, 3.7, 3.8,
4.1, 4.2, 4.3, 4.4, 5.0; support only) 4.1, 4.2, 4.3, 4.4, 5.0;
SUSE SLES 9.2, 9.3, 10.1; SUSE SLES 9.2, 9.3, 10.1;
Debian Sarge Debian Sarge
Live Migration Mid-2007 N/A N/A
Shared storage Mid-2007 N/A N/A

Virtual Iron
• An enterprise ready native virtualisation platform

• Uses hardware-assisted virtualisation technologies of
Intel VT and AMD-V processors
• Basedon an open source hypervisor derived from the
Xen open source project
• No software need be installed on physical hardware

Virtual Iron Components
Component License Function
Hypervisor GPL First software loaded when physical server boots.

Manages all hardware resources
Service Partition GPL Second software loaded when physical server boots.
Manages virtual server creation and configuration
and all I/O.
Virtualisation Commercial Controls virtual servers through an agent in the service

Manager partition
Guest operating Varies Operating systems that are fully virtualised on a

systems physical server

Virtualization Manager
• Java-based application
• Allows for central
management of
virtualized servers
• A physical server can
have many virtualized
servers, which are run as
unmodified guest
operating systems.

Virtual Manager Policy-based Automation
• LiveMigration — moves a running virtual server from one physical

server without pausing or impacting running applications
• LiveCapacity — monitors virtual server CPU utilisation or other
application needs to determine when a workload needs
additional capacity. When a user-defined threshold is met, the
virtual server is LiveMigrated to a physical server that has the
necessary resources
• LiveRecovery — monitors the status of physical resources and
moves virtual servers to maintain uptime in the event of a
hardware failure
• LiveMaintenance — moves virtual servers to alternative locations
without downtime when a physical server is taken offline for
maintenance

Virtual Iron Architecture

Supported Configurations
Feature Support
Operating systems 32 and 64-bit Red Hat Enterprise Linux 4
32 and 64-bit SUSE Linux Enterprise Server 9
32-bit Windows XP
32-bit Windows 2003
Processors Intel Xeon with Intel VT

AMD Opteron with AMD-V
Virtualised Nodes 100s per virtual data centre
Processors per virtual Server Up to 8
RAM per Physical Server Up to 96GB
Virtual servers per physical server CPU Up to 5
Virtual NIC adapters per virtual server Up to 5

Virtual disks per virtual server Up to 16

Virtuozzo
− Operating System—Level
Virtualisation
− Creates multiple, isolated virtual
environments (VEs)
− Whereas VMs attempt to virtualize
"a complete set of hardware," VEs
represent a "lighter" abstraction,
virtualizing instead "an operating
system instance"

Parallels Workstation
• Test/Development solution
aimed at desktop market
• Uses hypervisor technology
• Wide guest OS support
− Entire Windows family - 3.1,
3.11, 95, 98, Me, 2000, XP and
2003
− Linux distributions Red Hat,
SuSE, Mandriva, Debian and
Fedora Core
− FreeBSD
− “Legacy” operating systems e.g.
OS/2, eComStation and MS-
DOS.

HP Virtual Server Environment
• Implemented on HP Integrity and HP 9000 systems

Physical to Virtual (P2V)
• P2Vis the term used to describe the process of

converting physical servers into virtual machines
• Can be performed while server is live
• Some operating systems require cold migration
• Process:
− Analyse source
− Create a target VM
− Transfer data from physical source to virtual target
− Transform VM

VMware Converter
• Replaces P2V Assistant

• Wizard based conversion
process
• Can convert physical machines,
virtual machines or third party
system images (e.g. Symantec
Ghost, Backup Exec LiveState
Recovery)
• Source physical machines:
− 64-bit Windows XP/2003
− WinNT SP4+
− Windows 2000
− Windows XP
− Windows 2003

Platespin PowerConvert
• “Anywhere to anywhere”
conversion
− Peer-to-Peer
• Physical to Virtual (P2V)
• Virtual to Virtual (V2V)
• Virtual to Physical (V2P)
• Physical to Physical (P2P)
− Image Capture
• Physical to Image (P2I)
• Virtual to Image (V2I)
− Image Deployment
• Image to Virtual (I2V)
• Image to Physical (I2P)
− Disaster Recovery
• Physical to Virtual (P2V)
• Virtual to Virtual (V2V)
• Windows and Linux sources
can be converted

Platespin PowerConvert

Portlock Storage Manager
• Third-party
NetWare data
management product
• Can be used for P2V
conversions of NetWare
servers
• Requiressome manual
reconfiguration of VM

Capacity Planning
• Important first step in any server consolidation project

• Aims:
− Understand server performance and utilization rates of a group
of servers
− Identifying servers that are good candidates to be migrated
into virtual machines
− Size virtual environment accurately
• Statistics are gathered and processed
• What-ifscenarios can be run to examine different
possible approaches

VMware Capacity Planner

Platespin PowerRecon
• Onsite data collection and analysis

• Scenario modelling (what-if)
• Agentless operation
Inventory Workload Analyse Recommend

Data
Collection
Some additional products…

VMware Lab Manager
• Create centralised pools

of VMs, storage and
network components
• Rapid setup and tear
down of test/dev
environments
• Maintain library of
customer and production
system environments

VMware ACE

VMware Virtual Desktop Infrastructure

Dunes VS-0
Dunes VS-O
November 26, 2009 http://www.dunes.ch/content/view/82/157/ 79

Virtual Machine Backup and Replication
− esxRanger Professional
• LAN/WAN backups
• Backup active servers
• Database of backup activity
− esxReplicator
• Replicate changes to remote location
— “chunked” by time or data change
volumes
• Effective business continuity

Virtual Machine Backup and Replication
• esXpress
− Virtual Backup Appliance
runs backup jobs within a
VM
− Offloads CPU and memory
utilisation from VMware ESX
console
• Virtual Solution Box

− Also implemented as a
virtual machine appliance

esxCharter
A Windows based esxtop and more…

esxMigrator
• Assists customers upgrading from

VMware ESX 2.X to VMware ESX
3.0
• Uses data manipulation strategies
that can copy virtual disks much
faster than allowed by the
VMware console
• Enables failback contingency

Best Practice Recommendations
• Explore your options.

• Evaluate your applications for potential consolidation.
• Understand the differences between various
virtualization solutions.
• Look closely at the licensing and support policies of
your software vendors.
• Start small.

Best Practice Recommendations
• Manage expectations.
• Beware of “virtual sprawl.”
• Consider blades as a complementary consolidation
strategy.
• Integrate server consolidation with a broader
consolidation strategy.
• Develop a framework for continuous consolidation.

More Information
Alan McSweeney
alan@alanmcsweeney.com

An Introduction To Server Virtual Is at Ion

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

An Introduction To Server Virtual Is at Ion

Hochgeladen von

Copyright:

Verfügbare Formate

An Introduction to

Virtualisation is a framework or methodology of dividing the

November 26, 2009 2

− An old concept — first virtual machines created

November 26, 2009 3

− NT had Virtual DOS Machine (NTVDM) and Windows on

− Windows 95 used virtual machines to run older (Windows 3.x

November 26, 2009 4

− A server for every application

− Software and hardware are

November 26, 2009 5

− Physical hardware is abstracted by

− Manage OS and application as a

− Separate OS and hardware and

− Optimise utilisation levels

November 26, 2009 6

• Before Virtualisation • After Virtualisation

November 26, 2009 7

• Most organisations over-

• Aim to drive up CPU

November 26, 2009 8

• Virtual infrastructure brings uniformity to

November 26, 2009 9

− Typically, in order to virtualize, you would use a layer of software that

November 26, 2009 10

Guest Guest Guest

Guest Guest Guest

November 26, 2009 12

November 26, 2009 13

Paravirtualization is a virtualization technique that presents a

November 26, 2009 14

November 26, 2009 15

− Leverages hardware-assisted capabilities available in the latest

− Virtual Iron is one of the first companies to offer virtualization

November 26, 2009 16

November 26, 2009 17

November 26, 2009 18

• VM has its own BIOS

November 26, 2009 19

• Each VM has a virtual NIC

November 26, 2009 20

• Virtual switch with one

November 26, 2009 21

• To the applications and guest operating

November 26, 2009 23

• The Microsoft position

− “Microsoft supports Windows Server System software running within a Microsoft

November 26, 2009 24

Consolidation Business Continuity Management

Workload Mobility Development and Test

November 26, 2009 26

November 26, 2009 27

November 26, 2009 28

November 26, 2009 29

• Rapid provisioning of virtual machines

November 26, 2009 30

Entire server – OS, apps, data, devices, and state – is now

• Server provisioning is similar

• Server migration is now

• Data management techniques

November 26, 2009 31

• VirtualMachine files are