Gabrie heeft part3 gepost.
In part 3 of this series, I want to shed a light on the difference between the types of Migration in ESX and Hyper-V and the differences in storage between the both of them. Although I think most of the readers know the differences, I will start with a brief summary.
- Hyper-V QuickMigration: When you want to move a running Virtual Machine from one host to another with as little downtime as possible, you can use QuickMigration. On host-A the VM will be suspended to disk, and then host-B will unsuspend the VM and run it.
- Hyper-V & ESX Cold Migration: Moving a VM that is not running, to different host and/or different storage.
- ESX VMotion: Moving of a running VM to a different host, without downtime.
- ESX Storage VMotion: Moving the disks of a VM to different storage without downtime (VM doesn’t move).
Lees de rest hier: http://www.gabesvirtualworld.com/?p=107
Gabrie heeft Part 2 gepost van zijn serie Hyper-v, not in my Datacenter.
After you installed your hypervisor you want to virtualize your physical servers on it. When doing the research for my presentation I was very surprised to find some strange limitations in which guest are supported with Hyper-V. Can you believe that not all Windows Server versions are supported? Well neither could I.
The guest OS support of Hyper-V:
- Windows 2000 Server is only supported with SP4 and 1 CPU.
- Windows 2003 Server is only supported with SP2 and 1 or 2 CPUs.
- Windows 2008 Server is supported with 1, 2 and 4 CPUs.
- and there is Linux support for SUSE Linux Server 10 sp1 / sp2 with only 1 CPU.
This does look quite reasonable at first glance, because these are current versions. True, but when looking at the ESX environment I work in now, we would not be able to virtualize as many servers as we have running on ESX right now
Part 2 vind je hier: http://www.gabesvirtualworld.com/?p=104#more-104
Kenon Owens heeft een blogpost gemaakt over de benchmark tool van Intel, vConsolidate. Met deze tool zijn een aantal tests losgelaten op VMware ESX en Hyper-V.
Lees de bevindingen hier: http://dantedog29.blogspot.com/2008/11/esx-server-beats-hyper-v-in.html
So what exactly is Microsoft Hyper-V Server 2008? Following are some bits I’ve collected that you might not see/read on the Web site or TechNet (or maybe you will).
- Hyper-V Server 2008 was built using the Windows hypervisor and other components, including base kernel and driver technologies. Microsoft Hyper-V Server 2008 shares kernel components with Windows Server 2008.
Microsoft Hyper-V Server 2008 contains a sub-set of components that make up Server Core deployment option of Windows Server 2008, and has a similar interface and look and feel. But as you know, Server Core has roles like DNS, DHCP, file. Hyper-V Server 2008 is just virtualization.
Because Hyper-V Server 2008 shares kernel components with Windows Server 2008, we don’t expect special hardware drivers to be required to run Microsoft Hyper-V Server.
The maximum number of guest instances that can run on Microsoft Hyper-V Server 2008 is 128 (of course this is dependent on the hardware, memory and workloads). Additionally, each guest OS must have a valid license.
Hyper-V Server 2008 runs/supports all the guest OSes supported by its big brother, WS08 Hyper-V. See here for a complete list.
Windows Server licenses are not included with Microsoft Hyper-V Server 2008. Client access licenses (CALs) are only required for Windows Server and all Windows Server images that are virtualized, regardless of virtualization platform (e.g., ESXi). No CALs are required for Hyper-V Server 2008.
Download Hyper-V Server here: http://www.microsoft.com/servers/hyper-v-server/how-to-get.mspx
More info here: http://www.microsoft.com/servers/hyper-v-server/product-information.mspx
VMware heeft een vergelijking gemaakt tussen Hyper-V op Server Core vs ESXi. Hieronder zie je de uitkomst van deze test. Verder vind je twee videos met meer informatie over de installatie van beide Hypervisors en een video over het configureren van iSCSI op beide Hypervisors.
Video 1: http://www.vmware.com/technology/whyvmware/resources/esxi-hyper-v-installation.html
This first video shows every step required to install Hyper-V and ESXi on a fresh machine. We kept count of the elapsed time, reboots, mouse clicks and keystrokes each product needed and it clearly shows the huge advantage the truly thin and OS-free ESXi architecture has in installation speed and simplicity. ESXi goes from bare-metal to fully installed in one-third the time, half the mouse clicks, hundreds fewer keystrokes and just one reboot vs. seven compared to Hyper-V. The simplicity of the ESXi wizard-driven installation is striking compared to the arduous process needed to first get the Server Core OS installed and then configure Hyper-V in a command line environment.
Video 2: http://www.vmware.com/technology/whyvmware/resources/hyper-v-side-by-side-esxi.html
Our second video starts where the first left off and takes Hyper-V and ESXi through the steps needed to configure two iSCSI datastores for VM use. iSCSI setup is a standard task for any virtualization user that wants to take advantage of shared storage for VM migration and high availability. ESXi’s Windows-based Virtual Infrastructure client makes the iSCSI setup quick and easy. For Hyper-V, the "Windows you know" is nowhere to be seen. Instead, working with Server Core requires you to key in a long sequence of obscure commands to configure iSCSI initiators and targets, partitions and file systems. We generously showed the Hyper-V setup executed with no delays, although it took us hours of digging through Microsoft documents and knowledgebase articles to find the right commands to use when configuring iSCSI in Server Core.