VMware Communities
Darth_Titan
Contributor
Contributor
Jump to solution

No mouse or keyboard on Mac Pro using Leopard and Fusion 1.1rc1

I'm trying to use my Boot Camp partition with Fusion. Fusion installs fine and boots the Boot Camp partition. When VMWare tools installs I get an error, "Mouse drivers could not be installed automatically, must be installed manually." or something along those lines. I can't click OK because the mouse click doesn't register. (mouse will move albeit with much difficulty but no clicks register in the VM) I can't press enter to clear the prompt because the keyboard doesn't respond. I can't shut down the VM due to the open confirm dialog, so I have to force-quit Fusion. After a restart of the VM the mouse driver dialog box goes away, and additional drivers install but the process hangs at a PCI SCSI device driver. Again, I cannot interact with the dialog box because mouse and keyboard are unresponsive.

I've read a few posts here relating similar problems and have tried the fixes I can find. I added the registry edits to the Boot Camp partition mentioned in one post, I disabled the Mac keyboard and mouse shortcuts as mentioned in another post. I've tried three different mice and two keyboards, and I've installed and uninstalled Fusion more times than I care to recount. This is frustrating because Fusion runs beautifully on my Macbook Pro, but I am having no luck getting things working on my Mac Pro.

Is there any chance anyone can let me know how to proceed?

Reply
0 Kudos
1 Solution

Accepted Solutions
Pat_Lee
Virtuoso
Virtuoso
Jump to solution

Did either of you try the recommendation and registry change recommended in this thread?

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

Please give it a shot and let us know.

Pat

View solution in original post

Reply
0 Kudos
16 Replies
rcardona2k
Immortal
Immortal
Jump to solution

I had these kind of issues migrating a virtual machine a long time ago from VirtualPC. The way I solved it was to switch to bridged networking, renew your IP (ipconfig /release, then ipconfig /renew), and once you have your VM's IP address, download the OS X version of the Microsoft Remote Desktop client, then connect to the machine over Remote Desktop. Regardless of VMware's inability to capture the kb/mouse, you should be able to have full control over RDP. Try completing the VMware Tools installation, and/or you may need to delete your keyboard and mouse Windows devices and re-discover them through Plug-n-Play after the VMware Tools have been installed.

Reply
0 Kudos
bflad
Enthusiast
Enthusiast
Jump to solution

I had these kind of issues migrating a virtual machine a long time ago from VirtualPC. The way I solved it was to switch to bridged networking, renew your IP (ipconfig /release, then ipconfig /renew), and once you have your VM's IP address, download the OS X version of the , then connect to the machine over Remote Desktop. Regardless of VMware's inability to capture the kb/mouse, you should be able to have full control over RDP. Try completing the VMware Tools installation, and/or you may need to delete your keyboard and mouse Windows devices and re-discover them through Plug-n-Play after the VMware Tools have been installed.

Following along the same line... couldn't you setup the VM with its built-in VNC server via its VMX preferences file (See: )? You should be able to connect via Screen Sharing.app in Leopard or CotVNC.

~Brian

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

Don't use Screen Sharing.app, there's currently some weirdness with Fusion ().

Reply
0 Kudos
rcardona2k
Immortal
Immortal
Jump to solution

My experience with input grab issues is that if the Fusion console is unable to grab, neither will the Fusion VNC service. VNC is just an alternative way to get to same console keyboard and mouse. Remote Desktop, however is completely indepedent of the VM console, it takes over or creates a new winstation terminal session and always gives you access to a working keyboard and mouse.

Reply
0 Kudos
Darth_Titan
Contributor
Contributor
Jump to solution

Interesting suggestions. But no dice yet. I am unable to make any kind of VNC connection to the VM, and I still have no keyboard or mouse in the VM. I've tried rooting through the log file, but no luck yet. Does anyone have any further suggestions?

I'm attaching a copy of the log file.

Reply
0 Kudos
rcardona2k
Immortal
Immortal
Jump to solution

Can you offer any more details about what happened connecting to the machine via Remote Desktop?

Reply
0 Kudos
Darth_Titan
Contributor
Contributor
Jump to solution

Unfortunately there are no details to offer. No connection could be made.

I enabled the VNC server in the .vmx file, and according to the log the vnc server started. I used Chicken of the VNC to try to connect, but no connection could be made.

I know there's someone besides me running Fusion on a Mac Pro with Leopard, so I must be doing something wrong. It's probably going to end up being something dumb.

Reply
0 Kudos
Darth_Titan
Contributor
Contributor
Jump to solution

So I'm out of luck? My purchase of Fusion was pointless? C'mon Parallels sucks and I know getting this working should be possible.

Why don't my mouse and keyboard work?

Reply
0 Kudos
BooCross
Contributor
Contributor
Jump to solution

I have exactly the same problem! No error messages. When Windows Vista loads in Fusion, I click on the Windows screen in Fusion, but the trackpad and keyboard of my MacBook Pro Dual Core (4 Gb) become inoperable. Fusion Menus do still function as normal. And I can switch back to the the main screen, and everything works again. I'll keep my eyes open for a suggestion that works...

Reply
0 Kudos
Pat_Lee
Virtuoso
Virtuoso
Jump to solution

Did either of you try the recommendation and registry change recommended in this thread?

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

Please give it a shot and let us know.

Pat

Reply
0 Kudos
BooCross
Contributor
Contributor
Jump to solution

Hi Pat!

Thanks so much for the link!

The solution worked perfectly for me.

I was a little uncertain about applying a change to the MAC OS because I am new to MAC - but it was very easy to perform (adding on line of text) and has worked.

THANKS soooo much!

Reply
0 Kudos
rcardona2k
Immortal
Immortal
Jump to solution

The mouse and keyboard could not work for different reasons. Some tips in general are,

1) before importing any VM from other virtualization products, set your Windows VM to auto-login. You don't want to be stuck at login screen troubleshooting without a keyboard and mouse. The easily way is not to use regedit (like in the thread linked above) but use Start > Run > control userpasswords2 > uncheck "User must use a password to login"

2) Uninstall the virtualization tools for the product you're migrating from. You can't do this after you migrate so if you don't want artifacts around, this step helps.

3) Setup Remote Desktop (if you don't already have it) temporarily and run Microsoft SysInternals BgInfo BgInfo provides a wealth of machine knowledge right on your desktop. Every lab/test machine I know everywhere runs this. Remote Desktop in set XP is in Properties of My Computer (I forget exactly where it is in Vista). Having your VM in bridged mode networking mode, knowing the IP from BgInfo you can use, the Microsoft OS X Remote Desktop Client login from your Mac and fix the keyboard and mouse by installing the VMware Tools or deleting the keyboard/mouse in Device Manager and using Plug-n-Play to fix things.

4) When using the keyboard and it is not working, please indicate whether the OS X default beep is beeping. This indicates that there is a input grab problem, e.g. Checkpoint VPN secure input or any other offenders on the secure input list.

Reply
0 Kudos
Darth_Titan
Contributor
Contributor
Jump to solution

Well I searched the forums for days and didn't find this one. Worked like a charm. I feel a bit sheepish, but I can't tell you how much I appreciate the help.

Reply
0 Kudos
Pat_Lee
Virtuoso
Virtuoso
Jump to solution

We are happy to help.

Pat

Reply
0 Kudos
Fusionman1
Contributor
Contributor
Jump to solution

Thanks for all your posts. I had this problem, looked at several posts on this and other forums, and people tended to be talking mostly about BootCamp fixes, and driver issues. Links are being posted to places on the forum that weren't quite relevant, or easy to interpret. I use VM Fusion on my OS 10.5 Leopard, in native mode, not through bootcamp. The fix was rather simple, for me. The support staff had me reinstalling everything, deleting code, checking the logs, etc when the problem was so much easier to fix, and I finally had an epiphany that allowed me to fix it. (Some of the solutions in this thread for example didn't work for me or others).

I was running MS Entourage to log into my server for email access. Whether this a VPN Client, Checkpoint, or not, is really irrelevent, and frankly confusing to some readers. I knew what a VPN was, but wasn't certain that my Entourage mail retrieval was configured in a way that the VM would consider to be a VPN, or security issue. It is best to notify people that anything they are using to connect outside their OS to retrieve messages, could be interfering with the VM and therefore causing the mouse/keyboards to not work properly.

I simply shutoff Entourage, or make sure that I wasn't logged in, and the keyboard functionality returned completely. If I go outside the VM Fusion window, log into Entourage, my keyboard stops working in the Vista Guest OS, and the classic Mac OS beep notifies me of an error. As of right now, I don't have a work around, to allow one to be logged into their email client, while the VM Fusion is operating, so it would be nice to have that option.

Thanks again for everyone's help.

Reply
0 Kudos
Richard_Archamb
Contributor
Contributor
Jump to solution

This also happened occurred after installing the Last.fm client application on my Mac. Restarting Last.fm seemed to do the trick and restore keyboard access to Fusion. Strange. Just thought I would add this tidbit to the thread for posterity.

Reply
0 Kudos