Thanks for an answer, indeed I don't need 64 bit OS's on Mini. But this is first time I was told that VMWare actually doesn't use VT for 32-bit. Well make sense if it faster without it, I am going to find out more about it, especially if it is so under Mac OS X.
Well it looks like things are changing slightly...
I found this post:
http://communities.vmware.com/message/1112346;jsessionid=CF38A9C6FB1B7432690D086A4FDC8589
Which states the following:
The following applies only to Fusion 2.0.1.
* VT-x is preferred for all 64-bit guests. (BT is not supported for 64-bit guests.)
* VT-x is preferred for Mac OS X, OS/2, SCO UnixWare and SCO OpenServer guests.
* For CPUs with FlexPriority or EPT, VT-x is preferred for all 32-bit Windows guests except Windows NT and Windows 2000.
* For family 6 model 17H and later CPUs with FlexPriority or CPUs with EPT, VT-x is preferred for all 32-bit Linux and 32-bit FreeBSD guests.
* BT is preferred for all other guests.
So it looks like there are different scenarios where VT will be used. Basically this says VT is required for 64-bit processors as BT (binary translation, VMware's way of running virtual machines before VT existed) isn't supported for 64 bit OS's, as I already knew.
I didn't realize that they're changing the rules with newer CPU's. From what I've just quickly read, the VT in the newer cpu's is starting to catch up or even surpass the speed of their BT method so on newer CPU's they're actually preferring VT over BT in some OS's.
But it really looks like the only thing you lose entirely without VT is 64 bit guest OS support. On a Mac Mini, I don't really see that as being a huge issue. It's not as if you're trying to address more than 4GB in a virtual machine when the physical machine itself can only take 4GB.
I am with you though in one respect. I don't like to limit my options if I don't need to. I would have preferred they had given us a VT capable chip even in the low end Macbook/Mac Mini, but that's where they are saving some costs.