UPDATE This post is actually woefully inaccurate – go read this one instead!
I don’t like making posts like this, really i don’t. As much as I’ll sing the praises of VMware ’til I can’t sing no more, I’ll also point out the shortcomings – I don’t turn a blind eye just because I like the company.
Recently in the course of doing some vSphere testing, we came across some rather strange behaviour. When creating a new Windows Server 2008 VM with Virtual Hardware 7, the LSI SAS Adapter, and 2 virtual disks, we found that the second disk was being offlined during Windows installation. Even more strangely, this only seemed to effect Server 2008 Enterprise, both 32 and 64bit. Standard edition worked fine.
That being the case, and knowing that there was no differentiator between Standard and Enterprise edition from the VMware side (unlike with 2003, which has separate options in the Guest OS dropdown), I presumed this must be some wierd Microsoft problem. So we logged a call with Microsoft, only to have them come back and say the code base is the same so they didn’t think it was them. Microsoft asked if we could log a call with VMware about it, which we duly did.