freeze AGAIN

[manfredell]

Installed beta4. Loaded my beta3 XP VM. Installed tools.

NOT impressed by the speed again (MBP CD, 2GB), the disk with lots of activity.

Nevertheless:

Created a snapshot, OK. Then I closed the VM window, it started to suspend and after a few seconds my whole system froze again, like on my last test with beta3 (see my thread). I had to hold the power button to force a power down to get hold of the system again.

That’s it again for me with Fusion, not impressed!

P.S. I’d sure would like it to be stable as our ESX servers....

[bgertzfield]

Hi Manfredell,



I apologize for the sporadic issues you've encountered with suspending VMs. I know how frustrating it must be. We've unfortunately never been able to reproduce this in our labs, so we need help from customers like you to make VMware Fusion a top-notch product.

Can you please post the contents of your /Library/Logs/panic.log so we can see what the crash is?

Please note that your Beta 3 XP VM will still have an IDE disk, which will greatly reduce disk performance. If you use Fusion's Easy Install to create a new XP VM, you'll see the performance is much better with a new SCSI disk.

[rpdillon]

I can second this. I have a new MacBook 2.0GHz 13.3" (about 1 month old). I've used VMWare player/Server quite a bit under various Linux distros, and I thought I'd give fusion a try on my new Mac.

My VM os is Kubuntu 7.04. I have installed, installed the tools, and feaures work (resolution switching, USB, network).

Both times I have tried to suspend, it brings down the system. Oddly, the mouse (trackpad) still responds, but the keyboard input does nothing and it appears that OS X has hung (brightness, sound keys do nothing, dock no longer resppnds to clicks, menu at top of screen unresponsive).

Just thought I'd give you another data point. I allocated 512 RAM on a 1GB system, which is heavy. I've toned it down to 256 and will provide more info as I continue to experiment.

Rick

[manfredell]

Hi Manfredell,



I apologize for the sporadic issues you've

encountered with suspending VMs. I know how

frustrating it must be. We've unfortunately never

been able to reproduce this in our labs, so we need

help from customers like you to make VMware Fusion a

top-notch product.

It’s beta after all I know but this has happened to me on both betas and Fusion is told to be so stable....

Can you please post the contents of your

/Library/Logs/panic.log so we can see what the crash

is?

Fri Jun 8 23:41:07 2007

panic(cpu 1 caller 0x3DCE70BB): vmmon: ASSERT bora/modules/vmmon/macos/pageNoMap.cpp:784

Backtrace, Format - Frame : Return Address (4 potential args on stack)

0x258c39c8 : 0x128d08 (0x3cb134 0x258c39ec 0x131de5 0x0)

0x258c3a08 : 0x3dce70bb (0x3dcf3124 0x3dcf3104 0x258c3a30 0x258c3a30)

0x258c3b48 : 0x3dce70dc (0x0 0x0 0x0 0x70c3738)

0x258c3b68 : 0x3dceb00d (0x3dcf3164 0x3dcf3ad8 0x310 0xfff)

0x258c3be8 : 0x3dceb373 (0x635d220 0x2ffff 0x258c3c38 0x3dcf04cf)

0x258c3c08 : 0x3dce9bf1 (0x2ddca 0x2ddca 0x5 0x3042201c)

0x258c3c38 : 0x3dce9cec (0x467e004 0x2ddca 0x0 0x3dce7433)

0x258c3c88 : 0x3dcec10f (0x467e004 0x0 0x6397380 0x558f348)

0x258c3ca8 : 0x3dcecdaf (0x6397380 0x1 0x300 0x6)

0x258c3cf8 : 0x3dce724b (0x467e004 0x0 0x48 0x1)

0x258c3d18 : 0x3dce7a35 (0x15 0x14 0x4395e10 0x0)

0x258c3d68 : 0x1f05d7 (0x10000001 0x20005602 0x258c3eb8 0x3)

0x258c3da8 : 0x1e7411 (0x258c3dd0 0x297 0x258c3e08 0x55debb8)

0x258c3e08 : 0x1df212 (0x45b4ef4 0x20005602 0x258c3eb8 0x3)

0x258c3e58 : 0x331c4c (0x53aa340 0x20005602 0x258c3eb8 0x55debb8)

0x258c3e88 : 0x34ffa8 (0x53aa340 0x20005602 0x258c3eb8 0x55debb8) Backtrace continues...

Kernel loadable modules in backtrace (with dependencies):

com.vmware.kext.vmmon(1.0b4)@0x3dce6000

Kernel version:

Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386

*********

Please note that your Beta 3 XP VM will still have an

IDE disk, which will greatly reduce disk performance.

If you use Fusion's Easy Install to create a new XP

VM, you'll see the performance is much better with a

new SCSI disk.

That’s was has been mentioned BUT I spent so much time tuning my VM ans installinfg software that I just don’t have the time neither mood to do it all again...

[manfredell]

After converting my DIE to SCSI (see another thread) I found out the following:

my system freezes when I suspend the VM immediately after creating a snapshot!!!

When I reboot the VM then it suspends OK.

[mattssi]

I just upgraded to the latest release and this problem now occurs every time I hit suspend in my XP VM. It never occurred with any of the previous versions.

Every time I run the VM, I hit suspend, and bam, the entire Mac freezes.

[bgertzfield]

We've had just no luck reproducing this problem in-house.

manfredell and the others who've run into this: Can you run System Profiler (in /Applications/Utilities), select File -> Save As..., and either email the .xml file to fusion-feedback at vmware.com, or send it to me in a private message?

Sorry for the inconvenience -- this bug has been there since day one, but we've never been able to reproduce it. I'm guessing it's some conflicting software (we initially thought it might be File Vault), so anything that's common between your machines would be helpful in reproducing and fixing the issue.

[mattssi]

sent! (email)

[manfredell]

done, PM

[c_jones]

I to have also experienced this with a Red Hat Enterprise 5 VM. When I go to suspend the VM it completely freezes OS X and I have the power cycle my laptop (MacBook Pro 2.33Ghz, 3GB RAM). If there is some debug information that I can send you please let me know.

Thanks,

-Chris

[c_jones]

I just sent an email and attached my system profiler .xml file. Let me know if there is anything else I can do to help out.

[haroon1]

Strangely enough i was blisfully happy, till i upgraded from 43733.

Since then, i have the horrible "entire machine freezes on pause" or "entire machine freezes when fusion is shutdown".

I have tried going back from 50460 to 48339 and both versions still crash (taking the OS down with it) Im back to 43733 now (but i guess its going to expire in about 3 days despite having a paid for release)

Rapidly losing the faith... (i saw an alternate post in the forum claiming this bug on encrypted partitions.. ill give storing the images in a non file vault directory and re upgrade, but at this point theres been a ton of lost productivity in general )

Any news on this one?

[bgertzfield]

Hi haroon,

So you are storing your VMs in a FileVault partition? (Sorry, it wasn't clear from your post.)

Can you try the following?

0) Make sure the VM isn't running.

1) Right-click on the VM (should be in ~/Documents/Virtual Machines) and choose Show Package Contents.

2) Open the .vmx file inside in TextEdit.

3) Add the line:

mainMem.useNamedFile = "FALSE"

This tells Fusion to store the virtual machine's memory file (.vmem) outside of the encrypted directory it's stored in. Please let us know if this solves the problem for you.

[mattssi]

That worked for me!

Bad ass!

Good job VMware...now accept me for a job there!

[haroon1]

Back to (50460) with the vms running in a non-file-vaulted directory and all looks good..

mainMem.useNamedFile = "FALSE" also seems to work (with a slower pause / resume) but this seems reasonable..

Thanks for the quick response..

[bgertzfield]

Hi mattssi,

So you're also running off a FileVault partition? I'm glad that worked for you.

[mattssi]

Yes, I am. I didn't even think of it until that last post (of course).

[tommythorn2]

FYI, I posted my case in SR 190701064 - it does seem like I had the same problem and the mainMem.useNamedFile=false works for me too.

Hah, so Apple has bugs with mmap'ped files from FileVault? Lame, but VMware should still have caught this in internal testing (you are testing, right?).

Regards,

Tommy

[bgertzfield]

Hah, so Apple has bugs with mmap'ped files from

FileVault? Lame, but VMware should still have caught

this in internal testing (you are testing, right?).

Yeah, it wouldn't be the first mmap bug we've found with Mac OS X...

And yes, we do testing. We've done some testing with FileVault, but clearly not enough.

[rpdillon]

As I posted earlier, this continued to be a problem on my 1GB RAM machine even when I took the VM memory down to 256MB.

I installed Beta 4, and got the same results. I DO use FileVault for my home directory, so I will re-install Fusion again and set the namedFile variable and see if that fixes it.