Windows Server 2008 R2 introduces a new hypervisor feature called “Live Migration.” Live Migration allows administrators to move virtual machines between servers without having to shut down or restart the virtual machines. This new feature is especially useful for organizations that have multiple servers in different locations and want to keep their virtual machines running without having to physically move them. Live Migration works by creating a copy of the virtual machine on the source server, and then moving the copy to the destination server. The source server remains operational while the migration is taking place, so administrators can continue working with their other applications. Once the migration is complete, the original source server is shut down and no data is lost. Live Migration can be used for a variety of purposes, such as moving a virtual machine from one server in your organization to another for maintenance or disaster recovery purposes. Administrators can also use Live Migration to test new software before deploying it on production servers. To use Live Migration, you first need to create a configuration file for your destination server. The configuration file contains information about your destination server, such as its IP address and port number. You then need to create a live migration session on your source server by using Hyper-V Manager or PowerShell cmdlets. After you have created the session, you can start moving virtual machines into it by using Hyper-V Manager or PowerShell cmdlets. Live Migration is an important new feature in Windows Server 2008 R2 and provides administrators with an easy way to move virtual machines between servers without having to shut them down or restart them. ..
Microsoft Windows Server 2008 goes virtual with Hyper-V
Multiple Servers. One Box. Lots of RAM.
Hyper-V is a type-1 (native) hypervisor, meaning it runs at the root level with direct control over the server’s hardware. Virtual operating systems run independently of each other as partitions just above the Hyper-V stack. With server virtualization, you are essentially running multiple servers on one physical box. Previously, the only server virtualization product available from Microsoft was Virtual Server 2005 which ran as a type-2 (hosted) hypervisor over a macro operating system like Windows Server 2003. This meant the Virtual Server 2005 hypervisor did not have direct hardware access. Guest operating systems within Virtual Server 2005 were essentially threaded applications running through a macro-kernel. Hyper-V replaces the operating system layer and runs as a true type 1 micro-kernel hypervisor.
There are two key requirements for running Hyper-V: an x64 edition of Windows Server 2008 and a 64-bit processor with hardware assisted virtualization extensions (like those found in the Intel VT or AMD-V line of processors). Although Hyper-V requires a 64-bit working environment, guest operating systems may be 32 or 64-bit. Supported guest operating systems (the ones you want virtualized) include the following*:
Windows Server 2008 Windows Server 2003 Windows 2000 Server Windows Vista Windows XP Professional SUSE Linux Enterprise Server 10* Other operating systems may work but are not supported in an official capacity
You may have noticed that Hyper-V requires a 64-bit environment. Not surprising given the 4 GB memory limitation found in 32-bit architecture. Four gigabytes divided over multiple instances just doesn’t cut it anymore. Fortunately, Windows Server 2008 Enterprise and Datacenter editions with Hyper-V can support up to 2 terabytes of physical memory and 64 gigabytes of memory per virtual instance. That’s a lot of memory!
Quick Migration and High Availability
Virtualized servers will benefit almost immediately from the ability to quickly migrate from one physical server to another. Microsoft Hyper-V with Quick Migration can save the state of a guest virtual operating system to shared storage, move the storage connection from one server to another, and then restore the image to the new server. Quick Migration works in tandem with the Windows Server 2008 Enterprise and Datacenter Clustering service to provide high availability and rapid disaster-recovery capabilities for your clustered servers. Whether it’s planned (maintenance) or unplanned (disaster recovery), the use of virtualization technology increases server uptime and availability.
Virtual Appliances
The virtual appliance is a promising new development available with virtualization. Vendors can package an operating system and all necessary software to run their product into a virtual “black box” image. This image can then be deployed on different machines even if the configuration is different. Virtual appliances can reduce the installation, configuration, and maintenance costs associated with managing and deploying multiple layers of software. The Microsoft Virtual Hard Disk (VHD) test drive program is a great example. From the VHD website, “The Microsoft Virtual Hard Disk (VHD) format is the common virtualization file format that provides a uniform product support system, and provides more seamless manageability, security, reliability and cost-efficiency for customers. The VHD format captures the entire virtual machine operating system and the application stack in a single file.” As virtualization becomes more prevalent, we’ll begin to see even more innovative and useful virtual appliances.
To V or not to V
Server virtualization represents the next logical step in efficient server-space progression. As servers begin shifting to multi-core architecture and 64-bit platforms, virtualization should become an increasing factor in optimizing server workload performance and reducing costs, especially as server proliferation becomes a growing problem. What was once strictly within the realm of datacenters and development labs is now becoming IT reality. Although there are some performance issues to consider, you might find the advantages of virtualization are well worth the investment.
