Re: Unity & USB MacBook Pro 2.4 Ghz Santa Rosa

mikechadwick · ‎06-08-2007

I've been using Fusion with absolutely no problems - until now. i've just installed the new unity beta on my new macbook pro (2.4 Ghz, Santa Rosa) and it's not connecting usb devices. it sees the device (e.g. 4gb USB disk) but nothing happens! it doesn't auto connect, it doesn't connect manually. Everything works fine though on my Mac Pro. i've tried it with three different usb devices and same result - nothing happens.

Is this just a minor bug with the new Intel processors or....?

new install, xp pro

thanks

mike

Message was edited by:

mikechadwick

admin · ‎06-08-2007

Is this with the exact same VM on both computers?

admin · ‎06-08-2007

When you click the toolbar buttons for the USB devices, they don't even get the green checkmark now?

Can you look in the VM logfile (named vmware.log, found inside the VM bundle) for anything mentioning USB?

admin · ‎06-08-2007

One way to get the USB information out of the logfile would be: open Terminal, and run:

grep -i usb ~/Documents/Virtual\ Machines/YourVMName.vmwarevm/vmware.log

admin · ‎06-08-2007

When you click the toolbar buttons for the USB devices, they don't even get the green checkmark now?

Beta 4 removes USB devices from the toolbar and places them in the lower right corner. A connected device will be glowing blue, a disconnected device will be black.

mikechadwick · ‎06-09-2007

Dear All

thanks for your replies. i've just done a complete reinstallation of Mac OSX and done a clean install of VMWare Beta 4.0 - and i've still got the same problem: USB devices won't connect. Here's a copy of the log since the reinstall:

Jun 09 14:03:03.533: vmfusion| Log for VMware Fusion pid=304 version=1.0b4 build=build-48339 option=BETA

Jun 09 14:03:03.533: vmfusion| Hostname=mike-chadwicks-computer.local

Jun 09 14:03:03.533: vmfusion| Using log file /Users/mikechadwick/Library/Logs/VMware Fusion/vmware-vmfusion.log

Jun 09 14:03:03.604: vmfusion| Failed to acquire super user privileges.

Jun 09 14:03:03.604: vmfusion| UUID: Unable to open /dev/mem: No such file or directory

Jun 09 14:03:03.613: vmfusion| Msg_Reset:

Jun 09 14:03:03.613: 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 09 14:03:03.613: vmfusion| \----

Jun 09 14:03:03.613: vmfusion| Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/tip_list.vmsg".

Jun 09 14:03:03.617: vmfusion| XXXMACOS: Implement HostDeviceInfo_FindHostSoundDevices

Jun 09 14:03:03.622: vmfusion| Could not open /proc/net/dev

Jun 09 14:03:03.622: vmfusion| SGMAC: XXX: SGHostEnumerate not yet implemented

Jun 09 14:03:03.623: vmfusion| Failed to acquire super user privileges.

Jun 09 14:03:03.623: vmfusion| SMBIOS: can't open /dev/mem: Could not find the file

Jun 09 14:03:03.623: vmfusion| VmhsHostInfoPopulateSystem: Could not get information from smbios to populate VMDB.

Jun 09 14:03:03.623: vmfusion| Failed to acquire super user privileges.

Jun 09 14:03:03.623: vmfusion| UUID: Unable to open /dev/mem: No such file or directory

Jun 09 14:03:03.623: vmfusion| HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.

Jun 09 14:03:03.623: vmfusion| HOSTINFO: This machine has 1 physical CPUS, 2 total cores, and 2 logical CPUs.

Jun 09 14:03:03.717: vmfusion| Foundry Init: setting up global state (0 threads)

Jun 09 14:03:03.718: vmfusion| Foundry Init: version 2, hostType 1, hostName (null), hostPort 0, options 0x203

Jun 09 14:03:16.130: | Failed to acquire super user privileges.

Jun 09 14:03:16.131: | Reloading config state: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:03:16.209: | Failed to acquire super user privileges.

Jun 09 14:03:16.210: | Failed to acquire super user privileges.

Jun 09 14:03:16.321: vmfusion| readlink /var/run/vmware/38a6e68adc183d8c6f9b780759e3d8dd: No such file or directory

Jun 09 14:03:16.321: vmfusion| readlink /var/run/vmware/%2fUsers%2fmikechadwick%2fDocuments%2fVirtual%20Machines%2fWindows%20XP%20Professional%2evmwarevm%2fWindows%20XP%20Professional%2evmx: No such file or directory

Jun 09 14:03:16.392: vmfusion| DUI: Beginning dialog (0x16eacda0) for window (0x16ea9310)

Jun 09 14:03:32.800: vmfusion| Failed to acquire super user privileges.

Jun 09 14:03:50.439: vmfusion| Failed to acquire super user privileges.

Jun 09 14:04:14.323: vmfusion| Failed to acquire super user privileges.

Jun 09 14:04:14.324: vmfusion| Failed to acquire super user privileges.

Jun 09 14:04:17.027: vmfusion| DUI: Got destroyed signal! Destroying dialog 0x16eacda0

Jun 09 14:04:18.641: vmfusion| Failed to acquire super user privileges.

Jun 09 14:04:18.643: vmfusion| Failed to acquire super user privileges.

Jun 09 14:04:18.653: vmfusion| VMHSVMCbPower: Setting state of VM /vm/#8f2bf8c98cf3da92/ to powerOn with option soft

Jun 09 14:04:18.654: vmfusion| VMHS: Exec()'ing /Library/Application Support/VMware Fusion/vmware-vmx, /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:04:18.748: vmfusion| Mounting virtual machine paths on connection: /db/connection/#134/, /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:04:18.769: vmfusion| Mount VM completion for vm: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:04:18.770: vmfusion| Mount VM Complete: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx, Return code: OK

Jun 09 14:04:18.920: vmfusion| Disconnect check in progress: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:04:19.577: vmfusion| VMX status has been set for vm: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:04:19.577: vmfusion| Disconnect check in progress: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:06:47.818: vmfusion| DUI: Beginning dialog (0x18c68a00) for window (0x16ea9310)

Jun 09 14:06:53.718: vmfusion| DUI: Got destroyed signal! Destroying dialog 0x18c68a00

Jun 09 14:09:13.212: vmfusion| Disconnect check in progress: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:09:13.212: vmfusion| Unmounting the vm: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:09:13.212: vmfusion| Unmounting VM complete: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:09:13.293: vmfusion| Mount state values have changed: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:09:13.294: vmfusion| Reloading config state: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:09:13.342: vmfusion| Failed to acquire super user privileges.

Jun 09 14:09:24.760: vmfusion| Failed to acquire super user privileges.

Jun 09 14:09:24.762: vmfusion| Failed to acquire super user privileges.

Jun 09 14:09:24.773: vmfusion| VMHSVMCbPower: Setting state of VM /vm/#8f2bf8c98cf3da92/ to powerOn with option soft

Jun 09 14:09:24.773: vmfusion| VMHS: Exec()'ing /Library/Application Support/VMware Fusion/vmware-vmx-debug, /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:09:25.105: vmfusion| Mounting virtual machine paths on connection: /db/connection/#2d0/, /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:09:25.243: vmfusion| Mount VM completion for vm: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:09:25.243: vmfusion| Mount VM Complete: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx, Return code: OK

Jun 09 14:09:25.449: vmfusion| Disconnect check in progress: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:09:25.546: vmfusion| DUI: Adding new Hint dialog 0x18c844e0

Jun 09 14:09:25.546: vmfusion| DUI: Beginning dialog (0x18c844e4) for window (0x16ea9310)

Jun 09 14:09:26.044: vmfusion| Disconnect check in progress: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:09:31.529: vmfusion| DUI: Replied signal returned 'keep disabled' for dialog 0x18c844fc. Hiding dialog.

Jun 09 14:09:32.146: vmfusion| DUI: Got destroyed signal! Destroying dialog 0x18c844e4

Jun 09 14:09:32.146: vmfusion| Disconnect check in progress: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:09:32.845: vmfusion| VMX status has been set for vm: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:09:32.845: vmfusion| Disconnect check in progress: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:11:09.521: vmfusion| VMHSVMCbPower: Setting state of VM /vm/#8f2bf8c98cf3da92/ to suspend with option soft

Jun 09 14:11:09.522: vmfusion| Disconnect check in progress: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:11:09.611: vmfusion| Disconnect check in progress: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:11:15.624: vmfusion| DUI: Adding new Progress dialog 0x1bde250 with text \[Saving virtual machine state...]

Jun 09 14:11:15.624: vmfusion| DUI: Beginning dialog (0x1bde254) for window (0x16ea9310)

Jun 09 14:11:21.029: vmfusion| DUI: Got destroyed signal! Destroying dialog 0x1bde254

Jun 09 14:11:21.156: vmfusion| Failed to acquire super user privileges.

Jun 09 14:11:21.157: vmfusion| DUMPER: restoring checkpoint version 8

Jun 09 14:11:21.158: vmfusion| Failed to acquire super user privileges.

Jun 09 14:11:21.181: vmfusion| Disconnect check in progress: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:11:21.181: vmfusion| Unmounting the vm: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:11:21.181: vmfusion| Unmounting VM complete: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:11:22.109: vmfusion| Mount state values have changed: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:11:22.110: vmfusion| Reloading config state: /Users/mikechadwick/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx

Jun 09 14:11:22.157: vmfusion| Failed to acquire super user privileges.

Jun 09 14:11:22.158: vmfusion| Failed to acquire super user privileges.

Jun 09 14:11:22.280: vmfusion| Failed to acquire super user privileges.

Jun 09 14:11:22.300: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 09 14:11:22.302: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 09 14:11:22.307: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 09 14:11:22.307: vmfusion| HardwareVersion::GetVMMaxMemory: Invalid HW version: 1.

Jun 09 14:11:22.307: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 09 14:11:22.307: vmfusion| HardwareVersion::GetVMMaxMemory: Invalid HW version: 1.

Jun 09 14:11:22.307: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 09 14:11:22.307: vmfusion| HardwareVersion::GetVMMaxMemory: Invalid HW version: 1.

Jun 09 14:11:22.308: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 09 14:11:22.308: vmfusion| HardwareVersion::GetVMMaxMemory: Invalid HW version: 1.

Jun 09 14:11:22.308: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 09 14:11:22.308: vmfusion| HardwareVersion::GetVMMaxMemory: Invalid HW version: 1.

Jun 09 14:11:22.308: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 09 14:11:22.308: vmfusion| HardwareVersion::GetVMMaxMemory: Invalid HW version: 1.

Jun 09 14:11:22.308: vmfusion| AIOMGR-S : stat o=666 r=1332 w=2 i=0 br=4432896 bw=1024

i'm not an expert in these things so the above doesn't mean much to me - interestingly there's no mention of USB even though there was a memory stick attached. my bluetooth mighty mouse works fine however!

i'm running Beta 4.0 successfully on the Mac Pro - no problems at all.

any help much appreciated or else it's back to parallels i guess!

thanks

mike

Pat_Lee · ‎06-09-2007

Mike,

Please file a service request for this issue so that it can be more easily tracked internally:

http://www.vmware.com/support/home.html

Thanks,

Pat

mikechadwick · ‎06-09-2007

ok Pat - will do

thanks

mike

tobyg · ‎06-10-2007

Having the same problem here with USB on the same system, Santa Rosa MBP 2.4ghz.

Only thing I can see is that this was a fresh install of beta 4, I wonder if beta 4 didn't install something that beta 3 did.

Edit: Nope, doesn't appear that's the issue. Installed Beta 3 and even in Beta 3 I can't attach USB devices.

Here is the output I see in the vmware.log when I try to attach my USB to Serial port adapter.

Jun 11 01:33:59.712: vmx| USB: Found device \[name:Apple\ Built-in\ iSight vid:05ac pid:8502 path:13/15/4 speed:high family:vendor,other,video]

Jun 11 01:33:59.712: vmx| USB: Found device \[name:Apple\ Bluetooth\ USB\ Host\ Controller vid:05ac pid:8205 path:10/1/1 speed:full family:other,wireless,bluetooth]

Jun 11 01:33:59.712: vmx| USB: Found device \[name:Apple\ IR\ Receiver vid:05ac pid:8242 path:13/5/1 speed:low family:hid]

Jun 11 01:33:59.713: vmx| USB: Found device \[name:Future\ Devices\ USB\ HS\ SERIAL\ CONVERTER vid:0403 pid:6001 path:10/1/2 speed:full family:vendor]

Jun 11 01:33:59.713: vmx| VMXVmdbLoadUsbDevices: New set of 4 USB devices

Jun 11 01:34:13.735: vmx| USB: Connecting device 0xe1a2000004036001

Jun 11 01:34:13.991: vmx| USB: Found device \[name:Apple\ Built-in\ iSight vid:05ac pid:8502 path:13/15/4 speed:high family:vendor,other,video]

Jun 11 01:34:13.991: vmx| USB: Found device \[name:Apple\ Bluetooth\ USB\ Host\ Controller vid:05ac pid:8205 path:10/1/1 speed:full family:other,wireless,bluetooth]

Jun 11 01:34:13.991: vmx| USB: Found device \[name:Apple\ IR\ Receiver vid:05ac pid:8242 path:13/5/1 speed:low family:hid]

Jun 11 01:34:13.991: vmx| USB: Found device \[name:Future\ Devices\ USB\ HS\ SERIAL\ CONVERTER vid:0403 pid:6001 path:10/1/2 speed:full family:vendor]

Jun 11 01:34:13.993: vmx| USBG: CONNREQ: Dequeued head request after 258 ms for \[name:Future\ Devices\ USB\ HS\ SERIAL\ CONVERTER vid:0403 pid:6001 path:10/1/2 speed:full family:vendor]

Jun 11 01:34:13.993: vmx| USBGM: Connect failed for e1a2000004036001

Jun 11 01:34:13.994: vmx| USB: Found device \[name:Apple\ Built-in\ iSight vid:05ac pid:8502 path:13/15/4 speed:high family:vendor,other,video]

Jun 11 01:34:13.994: vmx| USB: Found device \[name:Apple\ Bluetooth\ USB\ Host\ Controller vid:05ac pid:8205 path:10/1/1 speed:full family:other,wireless,bluetooth]

Jun 11 01:34:13.994: vmx| USB: Found device \[name:Apple\ IR\ Receiver vid:05ac pid:8242 path:13/5/1 speed:low family:hid]

Jun 11 01:34:13.994: vmx| USB: Found device \[name:Future\ Devices\ USB\ HS\ SERIAL\ CONVERTER vid:0403 pid:6001 path:10/1/2 speed:full family:unknown]

Message was edited by:

tobyg

Message was edited by:

tobyg

mikechadwick · ‎06-11-2007

so it does look like this problem is due to the new santa rosa chip? i've filed as service request - let's see what happens. interesting that you had the same problem when you reinstalled beta 3 - it's answered a question that i had in the back of my mind.

Message was edited by:

mikechadwick

Message was edited by:

mikechadwick

tobyg · ‎06-12-2007

I've also submitted a service request. This is a huge issue now for me on this new Macbook Pro. Hopefully they can come up with a workaround solution prior to the next beta release. I'm not sure I can wait that long!

admin · ‎06-12-2007

I also filed a bug to raise the visibility of this bug. Can anyone who's filed a SR about this PM me with the number?

The developers are aware of the issue and are trying to get their hands on a new MBP to reproduce the bug.

tonynt · ‎06-12-2007

Not that this helps but I am experiencing the same issue on my new 2.4Ghz MacBook Pro.

mikechadwick · ‎06-13-2007

here's my service request number:

189416131

matthewbunce · ‎06-13-2007

This has me really worried. I due to pick up my new 2.4Ghz MacBook Pro on Saturday and the first thing I was going to do was pre-order and install Fusion.

If this is a real issue will I have to wait for a new beta to be released before I can use USB on the new MBP or will there be a patch? Has this sort of thing happened before with a new MBP/MB release?

Andreas_Masur · ‎06-13-2007

If this is a real issue will I have to wait for a new
beta to be released before I can use USB on the new
MBP or will there be a patch? Has this sort of thing
happened before with a new MBP/MB release?

Most likely it will be corrected with the next Beta or Release Candidate I would expect. However, it did not happen with previous Betas as far as I know....mainly because the hardware did not change that much...

Ciao, Andreas

HobbitFootAussi · ‎06-13-2007

I have a feeling that the next VMWare beta will have to come quickly since this is an immediate issue. However as a developer, I also understand that timelines and problems don't always work hand in hand. So hopefully they find the issue and issue a quick-fix for it.

tobyg · ‎06-14-2007

Just another tidbit of information...

It's definitely related to the Santa Rosa notebooks. Just tried it on a 17" version, same problem.

I hope they fix this soon!

admin · ‎06-15-2007

We've reproduced and understood this issue internally and will have a fix in the next version of Fusion. I can't promise whether that will be the next beta or RC or whether we'll issue a patch for the current beta, yet.

Thanks for reporting this and please be patient while we QA the fix and figure out how soon we can get it to y'all.

tobyg · ‎06-15-2007

So theres no hope for a quick fix like "add this line to your configuration file" huh?

Thanks for the update. This may hold me off on moving everything to my new SR MBP.