It's not just 2008, I have the same problem with 2003.
The issue has something to do with using multiple vCPUs and more than 4 GB of memory, and I'm sure has something to do with the co-scheduling SMP discussed here:
http://communities.vmware.com/docs/DOC-4960
But not sure why the problem only kicks in when we're over 4 GB. Probably related to ESX still being 32bit. Betcha!
Apparently, there's a "solution" here:
http://www.experts-exchange.com/Software/VMWare/Q_24028438.html
But I sort of doubt it. I don't think it can be fixed short of ESX 4.
(EDIT: Side Note* When you find an Experts-Exchange "Solution" in a google search, follow google's cached link, scroll to the bottom of the page and you'll see all the hidden answers. As I suspected, there was nothing useful.)
1 vCPU works great with 32 GB of memory. Make that 2 vCPU and it takes FOREVER to boot.
VM seems OK after booting, but booting takes so damn long.
It's a bit scary with big important services like SQL and Exchange. If you need to restart it, hope you're not in a hurry lol.
I hope they fix this soon. It's anoyning as hell.