The Network Manager at Westminster School presents solutions to sticky problems...

Monday 25 January 2010

Server 2008 R2 and VMWare vSphere 4

Server 2008 R2 is supported as an experimental product on vSphere 4. As a consequence, there are some gotchas that the boys at VMWare have yet to fix in an official patch. The biggest problem so far is the unexpected and unpredictable lockup on the console. If you want to run Server 2008 R2 on you VMWare box, here is what to look out for:

  • Network Drivers - The E1000 driver is alledged to be responsible for server lock up. Once you have created your initial VM, remove the standard E1000 interface that is added by default, and add a new network interface with a vmxnet 3 driver. Now the OS will not have a driver for this, so you will have to install vmware tools before you start doing any network activity. If you are building from PXE you will need to import the vmxnet drivers into your OS building applciation.

  • Video Drivers - This is the reason the console will lock up, but only after you have installed vmware tools. When installing vmware tools, do a custom installation. Expand the drivers section and change the video driver option to "This option is unavailable." Continuing without this driver will not affect your experience in the slightest.

Other than this, 2008 R2 virtual machines run well in vSphere 4.

No comments:

Post a Comment