Post on 08-Jun-2015
CITES
May 28| Slide 1
Virtualization: What does it mean and how can I use it!
Clark Roberts
David Gerstenecker
Chris Clausen
John Arends
CITES
May 28| Slide 2
Virtualization
• Virtualization is a logical process– Many processes can be virtualized
1. PC Virtualization – running multiple logical virtual machines on one piece of hardware
2. Desktop Virtualization – providing the end user the entire desktop experience from a central server
3. Server Virtualization – running multiple logical virtual machines on one physical server
CITES
May 28| Slide 3
Virtualizing a PC using Virtual PC 2007(SP1)• New features
– Vista support (guest and host)
– 64bit support
– Hardware assisted virtualization (support of VT technology)
– Run virtual machines on multiple monitors
• Benefits– Great Beta environment
– Easy to run multiple versions of Windows
• Disadvantages– No real Linux support
– “slow” without VT hardware present
CITES
May 28| Slide 4
Have your cake and eat it too…
PC virtualization
CITES
May 28| Slide 5
why?
– Run Outlook on Mac or Linux– Play with ___ OS without dedicated hardware– Evaluate software without leaving footprint– Support Vista without giving up XP– Use x64 host without giving up x32 only apps– Many other reasons that don’t fit on this slide
CITES
May 28| Slide 6
dgersten’s virtual world
• Virtual Machines:– Primary: WinXP, 2
CPUs, 2 GB– Previous: WinXP, 1
CPU, 1 GB– Testing: Vista, 1
CPU, 2 GB
• (Exchange testing)– CAS: Win2003, 1
CPU, 512 MB– Mailbox: Win2003,
1 CPU, 512 MB
CITES
May 28| Slide 7
options for intel mac
– VMware Fusion ($37.50 @ WebStore)– Parallels Desktop ($40 @ WebStore)– Others (audience participation)
CITES
May 28| Slide 8
– VMware Server (free) (version 1 is viable desktop product)
– VMware workstation ($96.99 at programmersparadise.com)
– Parallels Workstation ($49.99 at parallels.com)– Others (audience participation)
options for windows & linux
CITES
May 28| Slide 9
evaluation criteria
– Multiple snapshots– Multiple monitor support– Multiple virtual network support– Interface to guest VM (app vs. Web)– Interface to guest apps (Unity/Coherence)– Interoperability with other programs
CITES
May 28| Slide 10
gotchas
• IP address usage
• SID duplication on copy
• Licensing guest OS
• Performance “hit”
• Getting lost
• Out of date on updates for turned off/suspended machines
CITES
May 28| Slide 11
useful tools
• Fusion scripts to manage virtual networks:– Tokamak (by DaveP on
communities.vmware.com)
• Microsoft’s Sysinternals’ NewSID utility
• VMware’s DiskMount utility (Win & Linux)
CITES
May 28| Slide 12
fine print
The previous segment of this presentation was developed in PowerPoint via Fusion’s Unity mode on a MacPro.
CITES
May 28| Slide 13
Desktop Virtualization
Christopher D. Clausen
CITES
May 28| Slide 14
Desktop Virtualization
• Remote session based
• Microsoft Terminal Services - https://netfiles.uiuc.edu/cclausen/www/TS/
• VNC or (Free)NX for UNIX, Linux, Mac OS
CITES
May 28| Slide 15
clients
• Mstsc – Remote Desktop connection client
• VNC, (Free)NX
• Diskless workstation – PXES.org
• Thin Client dedicated hardware
CITES
May 28| Slide 16
Server Virtualization
CITES
May 28| Slide 17
What is server virtualization?
• A physical server is divided into a number of virtual servers with each running its own operating system
• Each virtual machine has its own virtual processor, memory, storage, networking, etc
CITES
May 28| Slide 18
Pros
• Fewer physical servers which means– Less datacenter space is needed– Less power (and fewer electrical outlets,
power strips, UPSes, etc) (Think Green)– Fewer KVM heads, etc
CITES
May 28| Slide 19
Cons
• Watch for ‘server sprawl’
• You still have to patch every VM
• Adds complexity
• “All your eggs in one basket”
• Cost
CITES
May 28| Slide 20
ACES ITCS implementation
• Started with the free VMware Server product on Linux and Windows hosts
• Used mostly for testing, and for some new low volume services
• Performance was good
CITES
May 28| Slide 21
VMware Server
• Patching the hosts was a problem because a host reboot meant many virtual servers went down
• VMware server 1.0 has some security issues with hosts on the AD and remote console (Addressed in 2.0 beta)
CITES
May 28| Slide 22
VMware Virtual Infrastructure
• Decided to move to the next level
• More complex and substantial cost
• Includes important features such as Vmotion
CITES
May 28| Slide 23
Virtual Infrastructure
• 4 hosts total, 2 in each building– 16 gigs of RAM– Dual, dual core processes
• Hosts run VMware ESX Server as a dedicated OS
• VirtualCenter for management
CITES
May 28| Slide 24
VirtualCenter
• VirtualCenter runs on a Windows machine
• Integrates with AD
• You connect using the VI client on Windows 32 bit
• No client for Linux or Mac OS X
CITES
May 28| Slide 25
CITES
May 28| Slide 26
CITES
May 28| Slide 27
Vmotion
• Probably the greatest thing so far
• Seamlessly move a VM between two ESX hosts with *no* downtime
• Requires the 2 hosts be on the same SAN
CITES
May 28| Slide 28
Results so far
• We have 14 machines virtualized between the 4 hosts and very few resources are being used
• We plan to virtualize many more machines over the next year
CITES
May 28| Slide 29
Important things we learned
• Check the VMware HCL carefully
• Need a lot of NICs – we did 6 per server
• Some instability with older Linux kernels in VMs but easily resolved with updates
CITES
May 28| Slide 30
Server Virtualization with Hyper-V
• Microsoft’s competitor to VMware ESX and Xen Hypervisor• Features (Windows Server 2008 64 bit only)
– 16 virtual CPU’s per VM– 64 GB Ram per VM (2TB per host)– 8 virtual network connections– 16 node clustering (high availability)– VSS support (volume shadow service) for live backup
• Not support by present version of System Center Virtual Machine Manager• MSDN and TechNet are running on Hyper-V RC0 today
CITES
May 28| Slide 31
Questions???