Anybody else get this message after installing B4.1?
iMac Core Duo, 2GB Ram. Stopped the guest before install, ran the install program and no problems. Tried several USB devices - no problem. Forgot to re-install tools. Went to "Suspend" and encountered a kernel panic and was forced to restart. Upon restart - received the noted error message.
Anyway around this other than a new install?
First off, what was the kernel panic (contents of /Library/Logs/panic.log)?
What's giving you the Insufficient Permissions error? What are you trying to do at that point? Screenshot?
etung - thanks for the feedback - Here is the information, hope it helps:
Thu Jun 21 17:52:38 2007
panic(cpu 1 caller 0x3ED4C0BB): vmmon: ASSERT bora/modules/vmmon/macos/pageNoMap.cpp:784
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x253bb9c8 : 0x128d08 (0x3cc0a4 0x253bb9ec 0x131de5 0x0)
0x253bba08 : 0x3ed4c0bb (0x3ed58124 0x3ed58104 0x253bba30 0x253bba30)
0x253bbb48 : 0x3ed4c0dc (0x0 0x0 0x0 0x6028ad4)
0x253bbb68 : 0x3ed5000d (0x3ed58164 0x3ed58ad8 0x310 0xfff)
0x253bbbe8 : 0x3ed50373 (0x3bb7ea0 0xffff 0x253bbc38 0x3ed554cf)
0x253bbc08 : 0x3ed4ebf1 (0x9d55 0x9d55 0x1 0x2f9da00c)
0x253bbc38 : 0x3ed4ecec (0x5775004 0x9d55 0x0 0x3ed4c433)
0x253bbc88 : 0x3ed5110f (0x5775004 0x0 0x3fc8750 0x5795c64)
0x253bbca8 : 0x3ed51daf (0x3fc8750 0x1 0x300 0x6)
0x253bbcf8 : 0x3ed4c24b (0x5775004 0x0 0x48 0x1)
0x253bbd18 : 0x3ed4ca35 (0x15 0x14 0x3c64c10 0x0)
0x253bbd68 : 0x1f1668 (0xa000000 0x20005602 0x253bbeb8 0x3)
0x253bbda8 : 0x1e84a2 (0x253bbdd0 0x297 0x253bbe08 0x56019c4)
0x253bbe08 : 0x1e02a3 (0x54b2294 0x20005602 0x253bbeb8 0x3)
0x253bbe58 : 0x332ac8 (0x5f04f90 0x20005602 0x253bbeb8 0x56019c4)
0x253bbe88 : 0x350e24 (0x5f04f90 0x20005602 0x253bbeb8 0x56019c4) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.vmware.kext.vmmon(1.0b4)@0x3ed4b000
Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386
Wow, that's not a helpful error message. You didn't say what you were doing at the time - just launching Fusion, trying to run the VM, etc.
If it was trying to run the VM in the picture, as a random guess, please go to a terminal and post the output of the following:
cd ~/Documents/Virtual\ Machines/
ls -lAF
ls -lAF Windows\ XP\ Professional.vmwarevm
etung - very true about the error message, I could not see anything really relevant either. Yes you were correct, all I was trying to do was run the VM. Here is the additional information you are requesting. Are you suggesting a permissions issue based on your request?
Last login: Thu Jun 21 17:53:36 on console
Welcome to Darwin!
Rons-Office:~ REB$ cd ~/Documents/Virtual\ Machines/
Rons-Office:~/Documents/Virtual Machines REB$ ls -lAF
total 0
drwxr-xr-x 14 REB REB 476 Jun 21 19:52 Windows XP Professional.vmwarevm/
Rons-Office:~/Documents/Virtual Machines REB$ ls -lAF Windows\ XP\ Professional.vmwarevm
total 15557568
drwxr-xr-x 15 REB REB 510 Jun 13 18:03 Applications/
-rw------- 1 REB REB 8684 Jun 21 17:36 Windows XP Professional.nvram
-rw------- 1 REB REB 7216627712 Jun 21 17:51 Windows XP Professional.vmdk
-rw------- 1 REB REB 0 Jun 21 17:36 Windows XP Professional.vmem
-rw------- 1 REB REB 0 Jun 8 12:56 Windows XP Professional.vmsd
drwxrwxrwx 3 REB REB 102 Jun 21 19:52 Windows XP Professional.vmsd.lck/
-rw------- 1 REB REB 136253601 Jun 21 17:51 Windows XP Professional.vmss
-rwxr-xr-x 1 REB REB 1880 Jun 21 17:36 Windows XP Professional.vmx*
-rw-rr 1 REB wheel 50195 Jun 21 17:27 vmware-0.log
-rw-rr 1 REB wheel 47013 Jun 15 13:43 vmware-1.log
-rw-rr 1 REB wheel 53240 Jun 13 18:16 vmware-2.log
-rw-rr 1 REB wheel 45010 Jun 21 17:51 vmware.log
Rons-Office:~/Documents/Virtual Machines REB$
etung - very true about the error message, I could
not see anything really relevant either. Yes you were
correct, all I was trying to do was run the VM. Here
is the additional information you are requesting. Are
you suggesting a permissions issue based on your
request?
Yeah, based on what little info there is in the message 😕
Anything interesting in vmware.log or vmware-vmfusion.log (in ~/Library/Logs/VMware Fusion/)?
Are you able to create a new VM and run it?
etung: Here is the vmware-fusion log. It appears I was not allowed super privileges and I am not certain why. Hopefully, you or someone else looking at this can make more since out of this than me. If nothing else, I will try a re-install first then see if I can create a new VM if that fails. Thank you for your assistance.
________________________________________________________________________
Jun 22 09:56:23.388: vmfusion| Log for VMware Fusion pid=518 version=1.0b4 build=build-49528 option=BETA
Jun 22 09:56:23.388: vmfusion| Hostname=Rons-Office.local
Jun 22 09:56:23.388: vmfusion| Using log file /Users/REB/Library/Logs/VMware Fusion/vmware-vmfusion.log
Jun 22 09:56:23.494: vmfusion| Failed to acquire super user privileges.
Jun 22 09:56:23.494: vmfusion| UUID: Unable to open /dev/mem: No such file or directory
Jun 22 09:56:23.510: vmfusion| Msg_Reset:
Jun 22 09:56:23.510: vmfusion| \[msg.dictionary.load.statFailed] Unable to get information about file "/Library/Application Support/VMware Fusion/messages/en/tip_list.vmsg": No such file or directory.
Jun 22 09:56:23.510: vmfusion| \----
Jun 22 09:56:23.510: vmfusion| Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/tip_list.vmsg".
Jun 22 09:56:23.516: vmfusion| XXXMACOS: Implement HostDeviceInfo_FindHostSoundDevices
Jun 22 09:56:23.523: vmfusion| Could not open /proc/net/dev
Jun 22 09:56:23.523: vmfusion| SGMAC: XXX: SGHostEnumerate not yet implemented
Jun 22 09:56:23.526: vmfusion| Failed to acquire super user privileges.
Jun 22 09:56:23.526: vmfusion| SMBIOS: can't open /dev/mem: Could not find the file
Jun 22 09:56:23.526: vmfusion| VmhsHostInfoPopulateSystem: Could not get information from smbios to populate VMDB.
Jun 22 09:56:23.526: vmfusion| Failed to acquire super user privileges.
Jun 22 09:56:23.526: vmfusion| UUID: Unable to open /dev/mem: No such file or directory
Jun 22 09:56:23.526: vmfusion| HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.
Jun 22 09:56:23.526: vmfusion| HOSTINFO: This machine has 1 physical CPUS, 2 total cores, and 2 logical CPUs.
Jun 22 09:56:23.679: vmfusion| Foundry Init: setting up global state (0 threads)
Jun 22 09:56:23.679: vmfusion| Foundry Init: version 2, hostType 1, hostName (null), hostPort 0, options 0x203
Jun 22 09:56:28.166: | Failed to acquire super user privileges.
Jun 22 09:56:28.166: | Reloading config state: /Users/REB/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx
Jun 22 09:56:28.265: | FILE: ExtractMemberValues mandatory argument 0 is missing!
Jun 22 09:56:28.266: | FILE: FileIO_Lock on '/Users/REB/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmsd' failed: Invalid argument
Jun 22 09:56:28.266: | SNAPSHOT: Unable to open and lock file '/Users/REB/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmsd'.
Jun 22 09:56:28.266: | SNAPSHOT: SnapshotConfigInfoRead: Error 10
Jun 22 09:56:28.266: | SNAPSHOT: GetTree failed 10
Jun 22 09:56:28.266: | Snapshot_GetTree(/Users/REB/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx) failed: Insufficient permissions.
Jun 22 09:56:28.266: | VMHSSnapshotPublishTree failed: ret = Message
Jun 22 09:56:28.266: | VMHSVMLoadSnapshot failed: Message
Jun 22 09:56:28.266: | VMHSVMLoadConfig failed: Insufficient permissions
Jun 22 09:56:28.267: | Failed to acquire super user privileges.
Jun 22 09:56:28.267: | Cmd /host2/#_client/util/vm/cmd/##4f/op/manageVM/ failed: Insufficient permissions
Jun 22 09:56:28.267: | VMHSCmd Command error: Insufficient permissions
Jun 22 09:56:28.329: vmfusion| DUI: Beginning dialog (0x1be5420) for window (0x0)
Jun 22 09:56:29.780: vmfusion| DUI: Got destroyed signal! Destroying dialog 0x1be5420
etung: Here is the vmware-fusion log. It appears I
was not allowed super privileges and I am not certain
why.
That's actually a misleading message, it appears even under normal circumstances. It looks like the problems actually start around the message about ExtractMemberValues.
Hopefully, you or someone else looking at this
can make more since out of this than me. If nothing
else, I will try a re-install first then see if I can
create a new VM if that fails. Thank you for your
assistance.
Those sound like good ideas. Please remember to file a bug report[/url] about the kernel panic, and include the panic.log.
Edit: The 0-byte vmsd and vmem files look suspicious, you could try deleting them (when Fusion is not running). -etung 2007.06.22 12:19
etung: Well I can not figure out what is going on. I did send in a bug report. At this time I will save the VM until I hear something. On the other hand, I did try a re-install and that failed. Last hope was to set up a new VM and this worked. Really have no clue as to why the other VM can not be accessed. Hopefully, VMware will have a clue. Oh - I did see if I had a lock on the previous VM - nope all was okay.
Again thanks for your suggestions.
Can anyone who has one of these problem please email all of the files from within all of the lock directories?
mbellon@vmware.com
I beleive that the panic and file system recovery is damaging the lock files.
I also am having this problem and can no longer use VM Fusion. I have reinstalled and still get the same error/
HELP!?!?!?
Today I have encountered the same Problem.
did you get it solved somehow?
would appreciate if you could help
:)cheers
phil
If you navigate to (Your Home Flder)/Library/Application Support find the folder "VMware Fusion" and delete it. Relaunch the program. This worked for me.
I have the same error message. I tried this solution, but it made no difference for me.
Has anyone found a solution to this problem yet? I would like to get my existing Windows XP VM working again rather than ripping everything out and starting from scratch (again).
Thanks,
DannyS
Hey,
We have successfully worked around this issue by creating a new VM and attaching it to the broken VM's hard drive (.vmdk file). The broken VM can then be removed from inventory but don't delete it's hard drive.