I should add, this was not a problem in 1.1.2, with several VMs running off Raid0 drives (software, OS X Raid 0 on both - not Raid-card based).

The crash/reboot is reproducable.

Thx,
Dan

Hi,
and thanks for the quick response.
I am not doubting you know your product well - but I can say that we never, ever, had any crashes running 1.x with the VMs (not the app) on Soft-Raid0 partitions; and we are running 3 Mac Pros in that configuration.
I now have 2 Mac Pros I upgraded to the beta, and both will crash / reboot when a 2nd VM is started, so at the very least it seems to be more prevalent with 2.x ?! Maybe the AHCPI driver changed, or it's something about Apple Software Raid implementation?

No promises - but IS this being worked on / one of the milestones that will be fixed for the release version, or is this considered 'acceptable' (my hope is that it's not of course ).

Thx,
Dan

That's the 'difference': We have NO problems running Fusion (1.x or 2.x). on Software Raid 0 Partitions provided by OS X.

The problem occurs when running (or just starting - it's usually immediate! - a 2nd instance of any VM. Say, you are running XP and now starting Vista (or running Solaris and starting Fedora). This is when on both test machines (which were build less than a month ago, so Id' consider the disks clean) crash (reboot spontaneously). There is no problem running just one instance. And - at least for us - there never has been a problem with 1.x. One of the 2 machine in fact is not new, but upgraded from 1.1.2. While we could and have run up to 3 VMs on THE SAME MACHINE, since the upgrade, it reboots upon starting the 2nd.

All our test (and production) machines are Early 2008 Mac Pro 3.2 Ghz 8 Cores, with 16GB RAM.

THe question remains - is this something that VMware is looking into for a 'fix' as it seems to have been reported before? I realize it's tought one if they haven't reproduced it in-house yet.
Of course, the situation lends itself to more or less Mac Pros.

Dan