VMWare Fusion V6.0.2 USB Keyboard and USB Mouse Stop Working on either MacBook OS X 10.9 Sleep/Wake Lid Close/Open or USB Device Unplug/Re-plugin

SOLUTION Workaround Summary: One way I have fixed/workedaround this problem is to Install Fusion v6.0.1 on top of v6.0.2 on my MacBook Retina.

I am sharing this problem Solution Workaround Experience because:

A) I hope is saves others time in their problem determination travels

B) I need YOU TO REPLY if you have experienced this problem

C) I have opened a Support Ticket on this issue and VMWare has been responsive, and I will update this thread when I hear more

>>>  Fusion v6.0.2 vs. v6.0.1 Reproducible Proof of USB Keyboard & MOUSE Problems on suspend/resume and/or USB Device Unplug/Replugin <<<

I tested the following repeatedly with consistent results:

1) Fusion v6.0.2 MacBook Retina OS X 10.9 with USB External Keyboard stops working and

      USB External Mouse stops working on Host and Guest

      when USB devices are unplugged/re-plugged and/or MacBook goes into lid-close/open sleep/wake

      while VMWare Fusion v6.0.2 is running Windows Guests (e.g. tested with Win7 & WinXP)

2) Suspending all VMWare Guest(s) fixes USB Keyboard & Mouse on Host (they start working again) AND

     Keyboard/Mouse start working on Guest when vmware guest is resumed

3) Installing Fusion v6.0.1 on top of MacBook Retina OS X 10.9 with Fusion v6.0.2 fixes problem:

     v6.0.1 system works fine: USB Keyboard and USB Mouse work fine during

     MacBook Sleep/Wake Lid Close/Open as well as when the USB devices are unplugged/replugged

4) I have also tested this on a SECOND completely different MacBook Retina with a DIFFERENT USB Keyboard and Mouse

5) Therefore, this seems to prove to me that v6.0.2 is the problem, as opposed to my MacBook, OS X, Keyboard or Mouse.

I hope these rather extensive problem determination tactics help to isolate the problem more completely to Fusion v6.0.2 and also help VMWare move towards a conclusion and fix to this RATHER CRITICAL problem/Bug.

Thank You.

I have experienced this before.  Keep in mind that there are a couple of ‘port disabled’ messages that could be observed.  For example, if a VM is powered off intentionally by a vSphere admin (i.e. for decom, etc.) the 1000v logs this as ‘port disabled’ which will freak out some network admins that see this via SNMP alerts.  However, there is also a ‘real’ issue in which a powered on VM stops pinging (i.e. after vMotion to a bad VMHost) and displays a “port disabled by admin” message.  The latter issue is what we will discuss below.

With 1000v, typically the first thing to try when faced with VM connectivity quirks is to try the toggle fix:

Quick Toggle Fix:

a) Take note of the VM’s current vNIC port group (from Edit Settings on the VM)

b) Set the VM vNIC to the “Unused / Quarantined” portgroup (from Edit Settings on the VM);

c) Click OK;

d) Set the VM vNIC back to it’s original port group noted in Step A above.

Note:  By using the above fix, often you can get back in business and your VM starts pinging again. However, this may only be a temporary fix.  The problem could come back when the VM vMotions to a bad host again.

Port Channel Review:

If all the hosts in the cluster are configured to use the 1000v and you observe this “port disabled” scenario after vMotion to other hosts, then this is typically indicative of an upstream network configuration problem; specifically I have seen this in scenarios where there were inconsistent port channel configurations across hosts.  If this is the case, generate a CDP report to show the network guys exactly which ports are in scope for review.  Then have them confirm the health of the interfaces and port channel configs.

CDP Report (best served up with PowerCLI):
http://www.virtu-al.net/2008/12/12/detailed-vmware-host-network-information/

Note:  More info about CDP available at VMware KB1007069

Check VSM / VEM Health:

Review the output of the following commands on each host and compare them for consistency (performed via ssh to the ESXi hosts):

vemcmd show version

vemcmd show card

Optional - Gather Logs:

vm-support

vem-support -t /var/tmp/ all

Note:  Use WinSCP in SCP mode to grab the above support bundles from /var/tmp on each host.

Tip:  It’s often beneficial to have ’n’ number of test VMs available, where ’n’ is the total number of physical uplinks participating in the VM Network port group in question.  So for example, if your VM port group uses 4 physical uplinks, create 4 test VMs and configure them with available IP addresses on the VLAN in question.  Next vMotion all 4 VMs to the host in question.  If only one of the 4 ports is misconfigured, this ensures that it’s identified (i.e. one of the VMs stopped pinging).

Hi,

I installed VMware Player 6.0.1 on openSUSE 3.1 using the serial number that I received with Fusion Professional 6.0.2.

Virtual machines run well if they are started via the GUI but I would like to start them via command line.

Question: How can I start virtual machines from command line? I read that vmrun should do the jobs but I can not find that command.

Did a search over my whole system: no file vmrun can be found.

Any idea, where I get vmrun from?

Thanks for your help,

Fred

To set up this configuration, you must create four virtual machines and use the virtual machine settings editor to adjust the settings for their virtual Ethernet adapters. You also need to install the appropriate guest operating systems and application software in each virtual machine and make the appropriate networking settings in each virtual machine.

1. Set up four virtual machines using the New Virtual Machine Wizard.

Create the first virtual machine with bridged networking so it can connect to an external network using the host computer's Ethernet adapter.

Create the other three virtual machines without networking. You will set up their virtual Ethernet adapters in later steps.

2. Start VMware Workstation and open virtual machine 1. Do not power on the virtual machine.

Use the virtual machine settings editor (VM > Settings) to add a second virtual network adapter, as described in Changing the Networking Configuration. Connect the second adapter to Custom (VMnet2).

Click OK to save the configuration and close the virtual machine settings editor.

3. If VMware Workstation is not running, start it. Open virtual machine 2. Do not power on the virtual machine.

Use the virtual machine settings editor (VM > Settings) to add a virtual network adapter. Connect the adapter to Custom (VMnet2).

Click OK to save the configuration and close the virtual machine settings editor.

4. If VMware Workstation is not running, start it. Open virtual machine 3. Do not power on the virtual machine.

Use the virtual machine settings editor (VM > Settings) to add a virtual network adapter. Connect the adapter to Custom (VMnet2).

Use the virtual machine settings editor to add a second virtual network adapter. Connect the adapter to Custom (VMnet3).

Click OK to save the configuration and close the virtual machine settings editor.

5. If VMware Workstation is not running, start it. Open virtual machine 4. Do not power on the virtual machine.

Use the virtual machine settings editor (VM > Settings) to add a virtual network adapter. Connect the adapter to Custom (VMnet3).

Click OK to save the configuration and close the virtual machine settings editor.

6. Determine the network addresses used for VMnet2 and VMnet3.

Note: On a Windows host, you may skip the steps for configuring network addresses manually and, instead, use Workstation's DHCP server. Go to Edit> Virtual Network Settings> DHCP and add VMnet2 and VMnet3 to the list of virtual networks served by the virtual DHCP server. Then skip to step 9.

On a Windows host, open a command prompt on the host computer and run ipconfig /all. Note the network addresses used by each virtual adapter.

On a Linux host, run ifconfig at the console or in a terminal window on the host computer. Note the network addresses used by each virtual switch.

7. Start VMware Workstation, open each virtual machine in turn and install the appropriate guest operating system.

8. Configure the networking in each guest operating system.

For the bridged Ethernet adapter in virtual machine 1, use the networking settings needed for a connection to the external network. If the virtual machine gets its IP address from a DHCP server on the external network, the default settings should work.

For the second Ethernet adapter in virtual machine 1, manually assign an IP address in the range you are using with VMnet2.

In virtual machine 2, assign an IP address in the range you are using with VMnet2.

In virtual machine 3, network adapters are connected to VMnet2 and VMnet3. Assign each adapter an IP address in the range you are using with the virtual network to which it is connected.

In virtual machine 4, assign an IP address in the range you are using with VMnet3.

9. Install the necessary application software in each virtual machine.

I'm using the nvidia card too and when i used the Forceware 285 everything seems okay. but now i'm using the 314.22 and everything seems fine except several issues in virtualized windows 8 and 8.1 metro UI games which i've found so far. I can't roll the video card driver back from 31x series because i changed the old card to gtx 7xx series and the 31x series are the minimum version which can drive that card.

I have posted a thread before and so far it gets zero answer at all:

https://communities.vmware.com/thread/457141

Now it seems that the issue is due to either nvidia or vmware since one of my colleagues tested the evaluation copy of 8.0.6 and 9.0.2 and 10.0.1 in another computer which arms only the intel integrated video card and did as that post described and then found that everything was fine. I would have attemped to post the further report but gave up finally(Because i thought it may not help at all, the vm tech. supporters may ask me to post bug report to the nvidia directly rather than to them, and the nvidia's may do the similiar things either. It's most possible to need them working together to solve such kind of issues, which is however the last thing that gonna happen).

Has anyone had any success with this solution?

I have tried downgrading tools to 6.0.1 with no luck. I still get truncating and bad sync problems.

This post has been marked with a "Correct answer" but I'm not seeing it.

Resolution

Validate that each troubleshooting step below is true for your environment. These steps provide instructions or a link to a document. These steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.

1. Ensure that during step 3 of the conversion (View/Edit Options), you choose the appropriate disk controller for your operating system.
   • For Windows XP, choose Bus Logic.
   • For Windows 2003, choose LSI Logic.
   • For Windows 2008 and Windows 7, choose LSI Logic SAS.
     
     For more information on adjusting the adapter after conversion, see Adjusting the virtual SCSI adapter type in a VMDK file (1006621).
     
     
2. If the source contained more than one hard disk, try changing the virtual hard disk order on the resulting virtual machine by removing both virtual hard disks, then adding them in the reverse order. For information on adding secondary disks, see the Virtual Machine Administration Guide .
   
   
3. Rewrite the master boot record on the virtual hard disk and restore the Windows boot files using the FIXMBR and FIXBOOT commands from the Recovery Console. For more information, see Repairing boot sector problems in Windows NT-based operating systems (1006556).
   
   
4. Verify that no data was corrupted during the conversion process. Corrupted data can affect the virtual machine's ability to boot successfully. For more information, see Checking for disk corruption on the destination after using vCenter Converter (1006559).
   
   
5. Verify that the hardware abstraction layer (HAL) library file is correct and that it is not corrupted for the destination virtual machine type. For more information, see HAL cannot be identified upon conversion of a virtual machine using vCenter Converter and fails to boot (1038576).

Have you tried running VMwareUpdateManagerUtility?  If not, it's placed in Program Files (x86)\VMware\Infrastructure\Update Manager.  Try "Re-register to vCenter Server" and see if that works.

Ather

Resolution

These alarms occur even if the host is working correctly.

To work around this issue, increase the value of handshakeTimeoutMs:

1. Connect to your ESXi/ESX host via a remote Kernel-based Virtual Machine (KVM) or Secure Shell (SSH) session or directly as root.
2. Open the /etc/vmware/hostd/config.xml file in a text editor.
3. Enter <handshakeTimeoutMs> 120000 </handshakeTimeoutMs> between the <ssl> tags in the vmacore section. This parameter is in milliseconds. For example, 120000 millseconds = 2 minutes.
   
   <vmacore>
   <threadPool>
   <MaxFdsPerThread>2048</MaxFdsPerThread>
   </threadPool>
   <ssl>
   <handshakeTimeoutMs> 120000 </handshakeTimeoutMs>
   <useCompression>true</useCompression>
   </ssl>
   <vmdb>
   <maxConnectionCount>8</maxConnectionCount>
   </vmdb>
   <loadPlugins> true </loadPlugins>
   </vmacore>
   
   
4. Save and close the file.
5. Restart the Management agents. For more information, see Restarting the Management agents on an ESXi or ESX host (1003490).
6. To confirm that the tags have taken effect, check the /var/log/vmware/hostd.log file for this message:
   
   [2010-03-15 09:49:32.788 F66D76D0 info 'App'] Vmacore::InitSSL: doVersionCheck = false, handshakeTimeoutUs = 120000000

I have the same problem, in the vmware-ui-xxxx.log:

2013-11-22T17:34:28.798+01:00| vmui| I120: Starting vmx as /opt/vmware/lib/vmware/bin/vmware-vmx

2013-11-22T17:34:28.798+01:00| vmui| I120: Starting vmx as /opt/vmware/lib/vmware/bin/vmware-vmx

2013-11-22T17:34:28.798+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: VMHS: VM /home/herve/vmware.newvms/Windows 7/Windows 7.vmx in directory /home/herve/vmware.newvms/Windows 7

2013-11-22T17:34:28.798+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: VMHS: Exec()'ing /opt/vmware/lib/vmware/bin/vmware-vmx.

2013-11-22T17:34:28.803+01:00| vmui| I120: VmdbAddConnection: cnxPath=/db/connection/#ae/, cnxIx=1

2013-11-22T17:34:28.803+01:00| vmui| I120: Vmdb_AddConnectionAsync_Secure: registered VERSION completion callback, cnx = /db/connection/#ae/

2013-11-22T17:34:28.817+01:00| vmui| I120: OnGuestCanRunUnityChanged: OS is not old Windows, checking Tools status. Version status: 5, running status: 1

2013-11-22T17:34:28.817+01:00| vmui| I120: OnGuestCanRunUnityChanged: Tools status is not INSTALLED

2013-11-22T17:34:28.843+01:00| vmui| I120: OnVMStateChanged: alive = 1

2013-11-22T17:34:28.843+01:00| vmui| I120: SetAttached: detach

2013-11-22T17:34:28.843+01:00| vmui| I120: OnSetAttachedCompleted

2013-11-22T17:34:28.911+01:00| vmui| I120: VmdbPipeStreamsOvlError Couldn't read: OVL_STATUS_EOF, (11) Ressource temporairement non disponible.

2013-11-22T17:34:28.911+01:00| vmui| I120: VmdbCnxDisconnect: Disconnect: closed pipe for sub cnx '/db/connection/#ae/' (-32)

2013-11-22T17:34:28.915+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Mounting VM begun.

2013-11-22T17:34:28.915+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Mounting virtual machine paths on connection: /db/connection/#ae/.

2013-11-22T17:34:28.918+01:00| vmui| I120: VigorClientStartMountCb Failed: Pipe connection has been broken

2013-11-22T17:34:28.918+01:00| vmui| I120: VigorClientDisconnect: disconnect /vm/#44d1d136bdac4d2d/ via /db/connection/#ae/

2013-11-22T17:34:28.918+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Unmounting VM begun.

2013-11-22T17:34:28.918+01:00| vmui| I120: VMDB not mounted for /vm/#44d1d136bdac4d2d/.

2013-11-22T17:34:28.918+01:00| vmui| I120: VigorClientUnmountCb: Mount state values have changed for /vm/#44d1d136bdac4d2d/.

2013-11-22T17:34:28.918+01:00| vmui| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#ae/'

2013-11-22T17:34:28.919+01:00| vmui| I120: VigorClientUnmountCb: Unmount complete for /vm/#44d1d136bdac4d2d/.

2013-11-22T17:34:28.919+01:00| vmui| I120: VigorClientUnmountCb unset Vigor path on vm unmount.

2013-11-22T17:34:28.919+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Unmounting VM complete.

2013-11-22T17:34:28.919+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Pending power op found, completing.

2013-11-22T17:34:28.919+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Clearing execReqPath

2013-11-22T17:34:28.919+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Reloading config state.

2013-11-22T17:34:28.928+01:00| vmui| I120: VMHS: Transitioned vmx/execState/val to poweredOff

2013-11-22T17:34:28.931+01:00| vmui| I120: VmdbCtxCheckOneof: One-of: /db/connection/#ae/type/ sub []

2013-11-22T17:34:28.931+01:00| vmui| I120: Vmdb_Unset failed: /db/connection/#ae/type/sub/mountState/req/#af/ (A one-of constraint has been violated)

2013-11-22T17:34:28.931+01:00| vmui| I120: Vmdb_Unset failed: /db/connection/#ae/type/sub/mountState/req/#af/ (A one-of constraint has been violated)

2013-11-22T17:34:28.931+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: VMHSStartVmxVigorCb: vmPath=/vm/#44d1d136bdac4d2d/ status=error

2013-11-22T17:34:28.931+01:00| vmui| I120: /home/herve/vmware.newvms/Windows 7/Windows 7.vmx: Reloading config state.

2013-11-22T17:34:28.940+01:00| vmui| I120: VMHS: Transitioned vmx/execState/val to poweredOff

2013-11-22T17:34:28.943+01:00| vmui| I120: Internal VMDB error: VMDB failure (-1)

But, I can start the vmware machine with  sudo vmware !

Back in the day of VM-server, I had 2 identical servers - one live, the other for backup.  The backup server powered on at 3am each day and ran a script that shut down a VM on the server PC then copied the entire image directory, then restarted the VM and repeated the process for the remaining live VM's.  The backup server then powered down until the next night.

When I had a m/b failure on the live server I was able to fire up the backup server, activate the VM's and I had only lost a couple of hours transactions.   Because I didn't have to do restores or similar, it also meant the VM's were only offline for about 30 minutes which was the time to realise I had a failure, investigate it, and fire up the backup server.

Since then I bought 2 new identical servers installed ESXi 5.1 on each, then upgraded to the Essentials pack so I have access to the extra features.

I would like to have something similar setup now, but it's getting confusing with information overload.

Simply, I would like to copy/replicate/clone my thin clients from one physical server to another - each just having local datastores.   It's not a major problem if the VM's need to be shut down first.

As I am using SSD's I need to keep the clients thin if possible.

Any help/suggestions much appreciated.

I want a simple solution so that if I am out of the office, I could ask any non tech person to start the 2nd PC and activate the VM's.  I don't have a spare 64bit windows license to use the Veeam 7.

Hello,

We are running a Horizon workspace environment with thinapp set to local mode. I am trying to do the side by side updating such as Firefox.dat.1 or Firefox.1. The issue I am having is that whenever I do this Horizon is not picking up the app as being updated still says 1.0 in Horizon Admin Web portal. I used the "is this a update of another package" and pointed it to the proper package and still no dice. It doesn't matter if I put the new .exe  in the package folder or not. If I change it from .exe to .1 to match the new .dat file still can not get it to work. I have googled and looked at the forums but nothing seems to help. Just wondering if anyone has any advice on this. I also tried to do just straight up updating the package and I still can not get that to work unless I delete the whole package delete the repo and let it rebuild with the new package there and it will just state that it is 1.0 not a 2.0.

Thanks, "Host," so simple, can't believe I didn't see it. That works exactly as I needed.

I believe the issue is that if you do not update the ESXi 5.0 server to Update 3 but instead install all the patches before then it'll show the server as being on build 1311177.  The Nessus scanner thinks 1311177 is the minimum level a host needs to have the patch installed but when you install Update 3 it is installed but the build number shows as 1311175.

Yes, the backing can be set to any of the types at deployment time.  You'll need to modify your add disk operation with the correct backing.

Thanks for the suggestions. I tried disabling Thinprint, both after the install (before 2nd boot) and prior to installation (by removing the printer, which I confirmed set the option you indicated in the vmx file). Still crashes host OS in the same way, though I did get a vmware.log that wasn't full of garbage this time (attached). Unfortunately, nothing meaningful is logged after the interactive prompt about the sata0:1 device (from iso install).

First of all, I am using Windows 7 as a host. Then I install Ubuntu 12.04 Guest under VirtualBox.

Then I get an access to the other four virtual machines (also Ubuntu 12.04 Guest) via ssh by running the following command in my Ubuntu Guest' terminal:

ssh user@ipaddress 

Then I want to connect those four virtual machines in an Internal Network, is there any ways to connect them under my Ubuntu Guest? I'm confused since I can only access those four virtual machines via ssh on my Ubuntu's terminal.

EDIT:

  What I mean by "connect" is to physically connect them using their ethernet. For example, VM1 connect to VM2 by using eth1 on VM1 and eth2 on VM2. I can do this in virtualbox, just add network adapter "Internal Network" for both of them. But as I said, I can only access those VMs via my Ubuntu's t

@Fillips In stead of plagiarizing by copying and pasting content not originally created by you without giving proper credit just provide the link, like... Have a look at: Install Workstation on a Windows Host

BTW What does your reply have to do with the OP's issue?  Nothing really!

Yes, in the HostStorageSystem (of an ESXi host), you can get the status of the adapter....

vSphere 5.5 Documentation Center

$HostStorageSystem->{'storageDeviceInfo'}->{'hostBusAdapter'}->[$i]->{'status'}

The hostBusAdapter is an array of devices, so you'll have to enumerate them.

tried that without luck, still showing same ip.