Win2008 R2, sometimes black screen

[js-hacki]

Hi,

i have installed Windows 2008 R2 x64 Server on an ESXi 3.5 Build 176894.

The installer runs through and my OS boots up, but every second reboot i get a black screen and i have to power off and on the guest.

I got the black screen during the installation reboot, too.

I read several threads where it was recommended to set the guest os to windows 7, but my esxi doesn't have such a template.

Is 2008R2 not supported, yet?

thanks

[Troy_Clavell · Accepted solution]

R2 isn't supported as a guest OS yet

....but you may want to take a look at this blog, it could be useful

http://communities.vmware.com/blogs/PlanetVM/2008/12/01/the-black-screen-of-death

[js-hacki]

thank you, i will decide wether to wait or i install the non-R2 version.

[VMmatty]

I've heard of people having better luck with R2 on ESXi 4.x. Some say to uninstall the VMware Tools (or don't install it in the first place) as it can make the VM unstable. Though as Troy says it isn't supported so I would just wait until official support is available.

I believe the reason you don't have Windows 7 as a guest OS option is because you're using ESXi 3.5. It is available as an "experimental" guest OS on vSphere 4.

[js-hacki]

will there still be updates for ESXi3.5 or do i have to upgrade to 4.0 in the next time?

[VMmatty]

There will more than likely be updates for ESX 3.5 in the future. I'm confident you'll see full 2008 R2 and Windows 7 support in 3.5 at some point in the future, as there is a large install base and not everyone can upgrade to vSphere.

If you have spare hardware lying around you can always download ESXi 4.x and try it to see if your 2008 R2 VM performs better. Either way it probably won't be perfect until official support is released.

[TobiasKracht]

Running WS2k8R2 under ESX 4 - works perfectly with VmWare tools.

StarWind Software R&D

[Phallon]

I'm starting testing of 2008R2 on ESXi 4.0 and have gotten a few random lockups.

The thread seems to have some info, but no obvious solutions yet.

Devin Noel

[Phallon]

http://communities.vmware.com/thread/218244?start=0&tstart=0

Looks like it's a buggy VMware driver.