10.5.2 and Fusion conflict.

axewww · ‎02-22-2008

Hi!

I purchased Fusion little before the 10.5.2 Leopard update, and everything was ok with 10.5.1.

After the update to 10.5.2, my Fusion starts, but the VirtualMachine selection window not, also none of the menus really work in Fusion. (when i try to open a VM image, one of the cpu cores goes to 99%, and thats all, nothing more..)

I tried to repair disk permission, delete the pref file, but no change.

I'm using the latest version of Fusion (1.1.1), on Leopard 10.5.2, with MacbookPro.

Any advice? Thanks, axewww

axewww · ‎02-22-2008

Also, here is my log:

Feb 23 00:20:04.207: vmfusion| Log for VMware Fusion pid=452 version=1.1.1 build=build-72241 option=Release

Feb 23 00:20:04.207: vmfusion| Hostname=x0r.local

Feb 23 00:20:04.207: vmfusion| Using log file /Users/ax/Library/Logs/VMware Fusion/vmware-vmfusion.log

Feb 23 00:20:04.213: vmfusion| Msg_Reset:

Feb 23 00:20:04.213: vmfusion| http://msg.dictionary.load.statFailed Unable to get information about file "/Library/Application Support/VMware Fusion/messages/en/vmware.vmsg": No such file or directory.

Feb 23 00:20:04.213: vmfusion| -

Feb 23 00:20:04.213: vmfusion| Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/vmware.vmsg".

Feb 23 00:20:04.288: vmfusion| UUID: Unable to open /dev/mem: No such file or directory

Feb 23 00:20:04.371: vmfusion| Msg_Reset:

Feb 23 00:20:04.371: vmfusion| http://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.

Feb 23 00:20:04.371: vmfusion| -

Feb 23 00:20:04.371: vmfusion| Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/tip_list.vmsg".

Feb 23 00:20:04.376: vmfusion| XXXMACOS: Implement HostDeviceInfo_FindHostSoundDevices

Feb 23 00:20:04.383: vmfusion| Could not open /proc/net/dev

Feb 23 00:20:04.383: vmfusion| SGMAC: XXX: SGHostEnumerate not yet implemented

Feb 23 00:20:04.384: vmfusion| SMBIOS: can't open /dev/mem: Could not find the file

Feb 23 00:20:04.384: vmfusion| VmhsHostInfoPopulateSystem: Could not get information from smbios to populate VMDB.

Feb 23 00:20:04.384: vmfusion| UUID: Unable to open /dev/mem: No such file or directory

Feb 23 00:20:04.385: vmfusion| HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.

Feb 23 00:20:04.385: vmfusion| HOSTINFO: This machine has 1 physical CPUS, 2 total cores, and 2 logical CPUs.

Feb 23 00:20:04.500: vmfusion| Foundry Init: setting up global state (0 threads)

Feb 23 00:20:04.500: vmfusion| Foundry Init: version 2, hostType 1, hostName (null), hostPort 0, options 0x203

admin · ‎02-22-2008

That log looks pretty normal, we just need to clean up some messages that aren't important. Try uninstalling/reinstalling Fusion (this won't affect your installed virtual machines)?

axewww · ‎02-23-2008

I tried reinstall many times with no success..

Today, I am going to reinstall the machine itself, maybe this solve this dirty problem..

(I'm using mobile net, maybe that has something to do with this problem..i have no idea)

Thanks anyway, any help welcome here!

LeeTDavy · ‎02-26-2008

I am having confused success with 10.5.2 on MacBook Pro and Fusion 1.1.1 with three different USB devices.

First is my preferred device - For years, Keyspan USA-19QW on printer cable always works perfect.

Second is FTDI LocoBuffer USB on above printer cable for model trains (JMRI) was reconized when connected but I didn't try installing drivers.

Failed in Fusion 1.1.1 running XP Home Edition Ver 2002 SP2 is the Cheapie - Best Buy Dynex ISB DB9 with working Source Forge OS X drivers

Title OS X Pl2303 USB to Serial driver v0.3.0 OS X 10.4 (universal)

Version

Description PL2303 USB to Serial Driver for Mac OS X. It supports different manufacturers of PL2303 based USB to serial dongles

like ATEN, IOData, Elcom, Itegno, Ma620, Ratoc, Tripp, Radioshack, Dcu10, SiteCom, Alcatel, Samsung, Siemens, Syntech, Nokia, MS3303H

PL2303 one piece molded cable and connectors failed to be reconized but was in the ICON and Settings list as connected.

HERE'S the log...

Feb 26 17:14:33.520: vmx| USB: Found device

Feb 26 17:14:33.521: vmx| USB: Found device

Feb 26 17:14:33.521: vmx| VMXVmdbLoadUsbDevices: New set of 4 USB devices

Feb 26 17:14:34.347: vmx| MachPoll: mach_port_extract_member failed for port 48911 (15)

Feb 26 17:15:13.674: vmx| USB: Disconnecting device 0xe1a2000006cd0119

Feb 26 17:15:13.674: vmx| MachPoll: mach_port_extract_member failed for port 47247 (15)

Feb 26 17:15:13.675: vmx| MachPoll: mach_port_extract_member failed for port 48411 (15)

Feb 26 17:15:14.176: vmx| USB: Found device

Feb 26 17:15:14.176: vmx| VMXVmdbLoadUsbDevices: New set of 3 USB devices

Feb 26 17:15:34.870: vmx| USB: Found device

Feb 26 17:15:34.871: vmx| USB: Found device

Feb 26 17:15:34.871: vmx| VMXVmdbLoadUsbDevices: New set of 4 USB devices

Feb 26 17:15:57.586: vmx| USB: Disconnecting device 0xe1a200000403c7d0

Feb 26 17:15:57.586: vmx| MachPoll: mach_port_extract_member failed for port 49263 (15)

Feb 26 17:15:58.088: vmx| USB: Found device

Feb 26 17:15:58.088: vmx| VMXVmdbLoadUsbDevices: New set of 3 USB devices

Feb 26 17:18:02.141: vmx| USBGM: USBDeviceOpenSeize failed (e00002c5)

Feb 26 17:18:02.142: vmx| USBGM: Connect failed for e1a20000067b2303

Feb 26 17:18:02.143: vmx| USB: Found device

Feb 26 17:18:02.143: vmx| VMXVmdbLoadUsbDevices: New set of 4 USB devices

bxd · ‎03-25-2008

I'm having a similar issue, trying to use a cheapo cel phone cable with a Prolific chip in it:

Mar 25 09:39:43.646: vmx| USB: Found device

Mar 25 09:39:43.649: vmx| USBG: CONNREQ: Dequeued head request after 191 ms for

Mar 25 09:39:43.650: vmx| USBGM: USBDeviceOpenSeize failed (e00002c5)

Mar 25 09:39:43.651: vmx| USBGM: Connect failed for e1a20000067b2303

MandarMS · ‎03-25-2008

please go through the following link and check you can use the Prolific cable in virtual machine

http://communities.vmware.com/message/628912#628912

bxd · ‎03-25-2008

Actually managed to solve it with a little extra debugging. It turns out that I had the open sourced pl2303 driver loaded in OS X (http://sourceforge.net/projects/osx-pl2303/). I switched to the official Prolific driver (http://www.prolific.com.tw/eng/downloads.asp?ID=31) and removed the open source driver, and all is well.

I'm not 100% clear if when VMware unplugged the device from the first driver, the second one snagged it, or if the open source driver just doesn't properly support the methods needed for VMware to take over the device. In either case, kextunload'ing and removing the open source driver solved the issue.

All

10.5.2 and Fusion conflict.