Just took a look at the flash video (Adobe Captive).  Here are the steps for those that aren't able to render the flash video:

-

From the ESX or VC client, highlight the VM and select > Edit virtual machine settings

Select Resources tab

Un-check Unlimited in the right pane and lower Mhz count to 700

Select Advanced CPU in the left pane

Under Scheduling Affinity in the right pane > Select Run on processor(s):

Check "0"

Click OK to close VM edit window

Boot VM

-

I'll say this much - this isn't a great fix.  Although it does allow for additional testing, VM performance is dismal at a minimum.  I'm going to play with MHz and Affinity settings to see if I can get better results.

Thanks for the updates guys.

Thanks Subatomic. The issue is that we cannot start vm's inside 3.5 on WS6.x

(at least not without p1$$-p00r performance)

Cheers,

Note this appears to work with the latest WS6.5 Beta

The feedback on the blog site shows some positive results.

Subatomic -

If you read the blog, it says that VMs still do not start.... not good.

Dave

Thread move to the VMware Workstation forum

Tom Howarth

VMware Communities User Moderator

installing 3.0.2 on WS6 works.  I have this running at home albeit on a Intel Q6600

http://www.intel.com/products/processor_number/chart/core2duo.htm

T7500 does have VT

Intel VT ( or AMD-V) ehancements is normally something you have to enable explicity in the BIOS.

i just tried twice with an ESXi VM. when I start a VM inside the ESXi server, it PSODs and I get a workstation error:

• VMware Workstation internal monitor error ***

vcpu-0:ASSERT vmcore/private/a20_shared.h:67

There is a problem in this version of VMware Workstation.

We rely on your feedback to improve the quality of our product. Please submit a support request that describes the problem at our Web page "http://www.vmware.com/info?id=8". Do not forget to attach the log file (/media/Portable_Drive/VMs/ESXi001/vmware.log) and the core file (/media/Portable_Drive/VMs/ESXi001/vmware-core.gz).

To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.

We appreciate your feedback,

  -- the VMware Workstation team.

This is similar to what is posted on the ntpro.nl blog.

I'm doing a support dump now. I am also going to (re)check the bios.

Wonder why you still try to run ESX 3.5 in WS 6.0.*

As discussed over and over again ...

In WS 6.0.* you can run ESX 3.0.*  - you can start VMs if your host has Intel VT or AMD SVM and you enable that in the vmx-file:

Intel:

monitor_control.restrict_backdoor = "true"

monitor_control.vt32 = "true"

AMD:

monitor_control.restrict_backdoor = "true"

monitor_control.enable_svm= TRUE

In build 91182 you can run ESX 3.5 or ESX 3.5i - you can start VMs if your host has Intel VT or AMD SVM and you enable that in the vmx-file with this new entry:

monitor.virtual_exec = "hardware"

monitor_control.restrict_backdoor = "true"

If VMware sets monitor.virtual_exec = "hardware"

back to "software" then your CPU does NOT qualify

___________________________________

description of vmx-parameters: http://sanbarrow.com/vmx.html

VMware-liveCD: http://sanbarrow.com/moa.html