Bummer. The title says it all.
With the new quad-core, 8GB ram with 1.5TB space Dell monster Inspiron 518 I put together -- I wanted to use it to test out both Microsoft's Hyper-V and VMWare's latest server version 2.0 -- at least their release candidate 2 (RC2). The main reason I picked up the machine (overkill, I know) was so I could test out a number softwares and technologies that I had not had the opportunity to.
I went ahead and setup my 60-day trial of the Microsoft Windows Server 2008 operating system, created the server role for Hyper-V and then brought over a couple of Virtual Server / Virtual PC machines that I had setup. The transition went smooth, so I was feel pretty good about it.
At the same time, I have a number of VMWare images because of the hard drive capacity issues that previous versions of Virtual Server and Virtual PC (127GB) had. After having some problems getting VMWare 1.0.7 to install on Windows 2008 server, I focused my attention on VMWare Server 2.0 RC2.
After downloading the 571MB installation file, VMware-server-2.0.0-110949.exe -- I tried to install VMware server. Bad news immediately:
"Setup cannot continue because Microsoft's Hyper-V is being used. Please disable it, reboot and start the VMWare Server installation again."
Not really what I was expecting our hoping for. The best case in my opinion was that I could run both simultaneously on my machine, the worst case is that I could turn one off and run the other. All I needed to do was "disable" the Microsoft Hyper-V software.
If only it was that simple. I figured that to "disable" that meant I could just go into Server Manager, and stop the three main services that run the Microsoft Hyper-V software: Hyper-V Image Management Service, Hyper-V Networking Management Service, and Hyper-V Virtual Machine Management. I went in, stopped the Windows services and then set them to disabled, hoping that would unlock the installation process.
No luck however.
Now I was forced to remove the Hyper-V role from the Windows 2008 server altogether to install the VMWare Server 2.0 RC2 software. After rebooting and completion of the role removal from Windows 2000, the VMWare Server 2.0 RC2 installation went off without a hitch. The only issue I had was with the VMWare Remote Console plugging not working on Windows 2008. Other than that, I copied over my VMWare 1.0.7 images and VMWare Server 2.0 RC2 was off and running.
Then I got a "brilliant" idea. Maybe this was an installation order issue. Perhaps if I installed VMWare Server 2.0 first and then enabled the Hyper-V role on the Windows 2008 server -- everything would work fine. I went ahead and added the Hyper-V role and rebooted.
After the reboot completed, no services failed and both the VMWare and the Hyper-V services started up. I then went into the web consolue (MUI) for VMWare to see if I could access my Virtual Machines. I tried to start up my old "Windows XP" image and the dreaded error came back.
"Power On Virtual Machine" failed to complete. If these problems persist, please contact your system administrator. VMWare server and Hyper-V are not compatible. You must remove the Hyper-V role from your system before running VMWare Server.
I did dink around with some settings once again to see if I could "trick" the VMWare software, but no luck. At this point, I have to conclude that even having both Hyper-V and VMWare installed at the same time on a Windows 2008 server is incompatible, very disappointing. Whether it is simply that VMWare has not addressed the Hyper-V incompatibility in the RC2 software or if there is specific tinkering by Microsoft, I have no idea. Unfortunately, it puts me in a position of having to choose one over the other.
I did do some quick Google search and could not find much on the topic. If you have any additional information or possible work arounds, please let me know. Otherwise it looks like Hyper-V will have to be disabled on this machine. Bummer.
Sunday, September 14, 2008
Bummer. The title says it all.