VMware Workstation is a professional virtualization solution that allows you to do a lot of things and is able to manage many virtual machines at the same time (if the resources of the host PC allow it).
However, in rare cases (and especially when you edit manually some settings in the vmx files), VMware Workstation can become unstable and arrive in a state where you will not be able to access or close some virtual machines.
Again, this is very rare, but here is how to solve ou avoid these problems.
At some moments, you may not have access to a virtual machine (even if it's down and not password protected).
When you want to access it from VMware Workstation, a "This virtual machine appears to be in use" warning is displayed.
VMware Workstation offers you to obtain the rights on it by clicking on : Take Ownership.
If this virtual machine is not in use, press the "Take Ownership" button to obtain ownership of it. Otherwise, press the "Cancel" button to avoid damaging it.
This warning can occur in 2 cases :
Most of the time, it will fail and this message will appear :
Could not open virtual machine ... .vmx Taking ownership of this virtual machine failed. The virtual machine is in use by an application on your host computer. Configuration file: ... .vmx
Note that in older versions of VMware Workstation, the icon displayed was an error icon and the "Remove" button did not exist.
With these older versions, you had to click OK.
Since VMware Workstation can't open this virtual machine, a red icon appears on it.
To solve this problem, close all open VMware Workstation windows and open VMware Workstation again, but as an administrator.
Now, you will have access to your virtual machine.
From now, you will be able to access it again normally (without having to restart VMware Workstation every time as administrator).
When you run too many virtual machines at the same time or you have mismanaged the amount of RAM allocated to them, your virtual machines may fail.
If it's not too late, try pausing them to prevent the guest OS from being damaged. Then, restore the virtual machines one by one by stopping them correctly before "booting" the next virtual machine.
If it's too late, you may not be able to force the virtual machine to shutdown from VMware Workstation.
Indeed, in this case, we wanted to shut down Windows properly by sending the Windows shutdown ACPI signal from VMware Workstation (via the "Shut Down Guest" option).
The problem is that the virtual machine never stopped, and because the virtual machine was shut down, no more options were available for this virtual machine.
Even when you want to close VMware Workstation to force the virtual machine to shut down, it will not work because VMware Workstation will display this warning : Virtual machine is busy.
In this case, you will only have 2 possibilities :
The only problem is that you can't know which instance of the "vmware-vmx.exe" process corresponds to which virtual machine.
For security, you will have to shut down all possible virtual machines before killing this process or processes. Otherwise, you risk cutting off a virtual machine that was still running correctly.
Confirm the action.
Like magic, the virtual machine will be considered shut down by VMware Workstation.
Nevertheless, don't forget that the sudden shutdown of the "vmware-vmx.exe" process only allows you to recover your hand on the management of the host PC.
Indeed, by killing the "vmware-vmx.exe" process, the host PC will become unstable because of the information left in its RAM.
This may result in a slower shutdown of your host PC when you shut down Windows this time.
Once the host PC is shutdown and then power on again (and not with an automatic restart from Windows), the RAM will be correct again.
This solution therefore only allows you to save what you were doing, rather than losing important changes because of a virtual machine that would have become unstable.
On our InformatiWeb.net website, we talked about the Panda USB Vaccine program that automatically vaccinate USB keys that you connect to your computer to prevent a virus on a USB key infect your physical PC.
The problem is that from the moment you use VMware Workstation, you will not be able to use the automatic vaccination of USB keys with Panda USB Vaccine.
When at least 1 virtual machine is running with VMware Workstation, if you plug an USB key on your physical PC, VMware Workstation and the currently powered virtual machine will be freezers.
Which is very problematic.
To avoid this conflict, we recommend that you no longer use Panda USB Vaccine on your PC where VMware Workstation is installed.
As you probably know, on Windows, you can manage disks (and their partitions) by right-clicking on Computer (or This PC), then clicking on : Disk Management.
The problem is that when virtual machines run on VMware Workstation on your PC, there is a good chance that your PC (including VMware Workstation and the "Computer Management" console) will start blocking (freezing).
It's pretty annoying, but be aware that this bug only occurs if virtual machines are running when you want to manage physical PC disks.
If no virtual machine is currently running, disk management will be possible without any problem.
PS : if you konw other conflicts that occur each time in the same way, don't hesitate to point them out in comments for us to add them in this tutorial.
Depending on the guest OS you are virtualizing, VMware Workstation selects the most suitable version for the USB controller of your virtual machine.
However, this can be problematic in some cases.
For example : you can't plug an USB 3.0 key into an USB 3.0 port on the host PC and pass it to a virtual machine using a USB 2.0 or lower controller.
If VMware Workstation displays the "New USB Device Detected" window, select the virtual machine to which you wish to connect the USB key (or any other USB support).
As mentioned above, you will not be able to plug an USB 3 key into an USB 3 port on the host PC and pass it to a virtual machine using version 2.0 or lower of the USB controller.
In this case, an error will be displayed :
The device '[Name of the USB 3.0 key]' was unable to connect to its ideal host controller. An attempt will be made to connect this device to the best available host controller. This might result in undefined behavior for this device.
Due to the previous error, an error will also be displayed in the guest OS :
USB Device Not Recognized
One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it.
For assistance in solving this problem, click this message.
If you click on this message, you will see a window appear with an "USB Root Hub" and an "Unknown Device" (which corresponds to your USB key).
In the device manager, you will see the same problem.
To solve this problem, simply plug your USB key into a USB 2.0 port on your host PC.
Or change the version of the virtual machine's USB controller to USB 3.0 if you want to connect it to a USB 3.0 port on your host PC.
If you plug an USB 3.0 key or any other USB storage medium (such as an external hard drive) to an USB 2.0 port on your host PC, this message will be displayed on the host PC where VMware Workstation is installed.
This device can perform faster.
This VMware USB Device can perform faster if you connect it to a Hi-Speed USB 3.0 port.
When you pass this USB 3.0 key to your virtual machine, a similar message will appear :
This USB Mass Storage Device can transfer information faster ...
However, the USB key will be accessible from the guest OS.
As you can check in the device manager.
Lorsque vous lancez une de vos machines virtuelles, un de ces messages apparait :
Binary translation is incompatible with long mode on this platform. Disabling long mode. Without long mode support, the virtual machine will not able to run 64-bit code. For more details see http://vmware.com/info?id=152.
This virtual machine is configured for 64-bit guest operating systems.
However, 64-bit operation is not possible. This host supports Intel VT-x, but VT-x is disabled. Intel VT-x might be disabled if it has been disabled in the BIOS/firmware settings or the host has not been power-cycled since changing this setting. (1) Verify that the BIOS/firmware settings enable Intel VT-x and disable 'trusted execution.' (2) Power-cycle the host if either of these BIOS/firmware settings have been changed. (3) Power-cycle the host if you have not done so since installing VMware Workstation. (4) Update the host's BIOS/firmware to the latest version. For more detailed information, see http://vmware.com/info?id=152.
Ces erreurs surviennent lorsque la virtualisation du processeur n'est pas supportée par votre processeur (CPU), le BIOS de votre carte mère ou que celle-ci n'est pas activée par défaut dans le BIOS de votre carte mère.
Si votre processeur supporte la virtualisation du processeur (Intel VT-x ou AMD-V), il vous suffit de l'activer dans le BIOS de votre carte mère.
® InformatiWeb-Pro.net - InformatiWeb.net 2008-2020 - © Lionel Eppe - All rights reserved.
Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L.335-2 and following of the intellectual property Code.