VMware Workstation FAQ

This article is organized in the form of FAQ, and you can search by keywords.

[Question 1] VMware reports an error "This host supports Intel VT-x, but Intel VT-x is disabled" when installing a 64-bit operating system

【Phenomenon】

The virtual machine is configured to use a 64-bit guest operating system. However, 64-bit operations cannot be performed.

This host supports Intel VT-x, but Intel VT-x is disabled.

Intel VT-x may be disabled if Intel VT-x has been disabled in BIOS/firmware settings, or if the host has never rebooted since changing this setting.

(1) Verify that Intel VT-x is enabled and Trusted Execution is disabled in the BIOS/firmware settings.

(2) If one of these two BIOS/firmware settings has been changed, reboot the host

(3) If you have never rebooted the host after installing VMware Workstation, reboot.

(4) Update the host's BIOS/firmware to the latest version.

【solve】

Virtual 64-bit systems must support virtualization technology.

If the prompt: This host does not support Intel VT-x, it is impossible to virtualize a 64-bit system

If prompted: This host supports Intel VT-x, but when Intel VT-x is disabled, we only need to turn on the VT function in the BIOS.

First, to enable virtualization technology support, several conditions are required: chipset support, BIOS support, processor support, and operating system support.

In terms of operating system, all mainstream operating systems support VMM management, so there is no need to consider it.
As for the chipset, it has been supported since the era of Intel 945 (except for netbooks), so there is no need to consider it.
In terms of CPU, it can be judged by querying Intel's official website.
So, it's more to see if it is supported from the BIOS. The CPU does not turn on VT by default, you need to manually modify it in the BIOS

Enable Intel Virtualization Technology (Intel VT-x) in the cpu advanced options of the bios.
Some bios also require intel virtualization technology in security.

Check whether the CPU supports virtualization technology, you can use Securable to determine whether it supports virtualization

Or use CPU-Z software to view

Turn on the virtualization function of the BIOS (because the motherboard models are different, it needs to be operated according to the actual situation)

Note: The adjustment is the bios of the physical machine (host machine), not the virtual machine!

Phoenix BIOS:

Insyde BIOS

ASUS UEFI BIOS

ASUS motherboard BIOS UEFI BIOS steps to enable VT

Press F2 at boot to enter BIOS setup
Go to Advanced (Advanced menu)
Enter CPU Configuration
Change Intel Virtualization Technology to Enabled
Press F10 to save settings
Press ESC to exit BIOS setup

Chinese interface

Virtualization technology currently mainly depends on the CPU model and BIOS of your computer. Some CPUs or BIOS cannot support virtualization technology for the time being. Those that support virtualization technology can be turned on in the BIOS. The method of turning on is as follows:

1. Enter the BIOS. Press F2 or F12 or DEL or ESC key when booting up (different computers).

2. After entering the BIOS, find the Configuration option, select Intel Virtual Technology and press Enter, move the cursor to Enabled, then press Enter, and finally press F10 to save and exit.

If you can't find the Configuration option, you can try the following methods:

(1) After some HP computers enter the BIOS, you need to select the SystemConfiguration menu, then select Device Configuration, find Virtualization Technology, and set it to Enabled.

(2) After entering the BIOS of some Lenovo Thinkpad computers, you need to select the Security menu, then select Virtualization and set it to Enabled.

(3) After some DELL (Dell) computers enter the BIOS, you need to select the Processor Settings menu, then select Virtualization Technology and set it to Enabled.

【问题二】This virtual machine appears to be in use.

【Phenomenon】

This may be a bug in VMware Workstation, when the virtual machine in VMware Workstation is running but is shut down or restarted abnormally. As a result, when we restart the virtual machine again, "The Virtual Machine Appears to be in use" will be prompted, and the virtual machine cannot be started.

PS: This lck file is the disk lock file of the virtual machine. We know that the disk of the virtual machine and the disk of the host coexist, but due to the use of a specific virtual mechanism, the two do not affect each other. When using a virtual machine, vmware will generate several disk lock files to protect the disk occupied by the current virtual machine from being occupied and modified by the host or other virtual machines. After a graceful shutdown of the virtual machine, vmware will automatically remove this lock. However, in a few cases, such as the sudden crash of the host, abnormal shutdown, etc., vmware cannot delete the lck disk lock file. So the next time you start the virtual machine, vmware will mistakenly think that the virtual system that needs to be started is already running, and the above error of this virtual machine appears to be in use appears. After deleting the file, it will be back to normal.

【solve】

The repair method is very simple. Go to the corresponding virtual machine directory and delete the % virtual machine name%.vmx.lck folder or the files in it. If there is still an error, you need to restart the host machine.

Yes, if you are certain that the guest is truly not running, go to the guest's folder and delete any .lck files and folders. Delete the folders with .lck file extension.
If you can’t delete these files, make sure to close VMware workstation program and then try.
After deleting above .lck folders and files, I could able to successfully start virtual machine on VMware workstation 10.

【More】

When we run the virtual machine and then open the task manager, we will find two important processes, vmware.exe and vmware-vmx.exe.

Among them, vmware-vmx.exe is the main program, and the virtual machine runs under this process;
VMware.exe is a shell program that is responsible for displaying the virtual system running in vmware-vmx.exe and interpreting and transmitting various commands and operations. It is our most commonly used VMware user interface. This program can be reentrant and open multiple at the same time.

Because VMware Workstation is reentrant, in order to avoid the same virtual system being opened by multiple VMware.exe operations at the same time, causing errors, each VMware will first check whether the virtual machine root directory is under the virtual machine's root directory when opening the corresponding virtual machine tab. There is a folder of *.vmx.lck and verify the files in it. If the file contains a legitimately generated uuid (Universal Unique Identifier), the tab of the virtual machine cannot be opened, and the following error message will appear:

After taking Ownership, the following prompt will appear:

If there is no corresponding legal file, a *.vmx.lck folder will be generated in the root directory of the virtual machine, and a *.lck file containing the uuid will be generated in this folder, open the virtual machine tab, and from the main The program receives the display information.

This *.lck file can be edited with Notepad. Inside is uuid={a string of alphanumerics}, uuid is a Universally Unique Identifier, and its characteristic is uniqueness. The purpose is that only one vmware.exe can accept the display of the main program and operate on the virtual machine at the same time. lck is the abbreviation of lock, that is, the lock on the requested resource.

After the virtual machine is successfully created, there are actually only three main files: the .VMX file is the parameter file of the virtual machine, and the .VMDK file is the disk file of the virtual machine. Other files are generated after the virtual machine is started. After the virtual machine exits normally, the virtual machine will automatically delete these files. Every time the virtual machine starts, it will detect whether these files exist. If they exist, an error will be prompted (that is, a virtual machine is not allowed to be opened twice at the same time). This kind of error is generally caused by the abnormal shutdown of the virtual machine!

When a VMware virtual machine is running, it will generate at least three *.vmx.lck, *.vmdk.lck, *.vmem.lck folders in the corresponding virtual machine directory, which contain files named *.lck. Among them, *.vmx.lck is generated with the opening of the tab in vmware.exe; the other two are about the use of virtual disks and memory, which are generated with the running of the virtual system. If you close VMware.exe and let the virtual machine run in the background, the *.vmx.lck folder will disappear and the other two will not.

When opening a virtual machine tab in VMware.exe, a folder of *.vmsd.lck will be temporarily generated. It is estimated that this is generated when the data is initially sent (send data), preventing multiple shells from requesting to open the virtual machine at the same time. machine.

The original text is here: http://hi.baidu.com/patriotspy/item/259d515b1ee8e90ae7c4a50b

【问题三】The VMware Authorization Service is not running.

【Phenomenon】

An error is reported when the virtual machine is opened (as shown in the figure below), and the startup of the virtual machine fails due to the following errors:

【solve】

reason:

This issue can occur when the VMware Authorization service is not running or the service does not have administrator privileges.

To resolve this issue, start the service and make sure it does have administrator rights.

To start the VMware Authorization service or check if it is running, follow these steps:

Log in to the Windows operating system as an administrator.
Click Start, and then click Run.
Type services.msc and click OK
Scroll down the list that appears and find the VMware Authorization service
Click Start this service unless the status shown for this service is already Started.

Note: The VMware Authorization service depends on the Windows Management Instrumentation service. The service must also be running. If the VMware Authorization service fails to start or starts and then stops, locate and start the Windows Management Instrumentation service.

If the VMware Authorization service shows a status of Started, the service may not have administrator privileges. To provide administrator privileges to the VMware Authorization service

Start-Run, enter: services.msc, open "Services". Find the VMware Authorization Service service, start the service, modify its properties, and change the startup type to "automatic".

Original reference: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2040995

[Question 4] Failed to connect Ethernet0 to virtual network "VMnet0" Details can be found in the vmware.log file Failed to connect to virtual machine Ethernet0

【Phenomenon】

Open the virtual machine and report an error (as shown below), failed to connect to the virtual machine Ethernet0:

【solve】

Solution one:

Delete the original network card, add a new network card, and then reconfigure it.

Solution two:

In vmware "Edit->Virtual Network Settings", click "Restore Default" to solve the problem. It should be noted that the virtual network settings cannot be restored after the virtual machine is powered on. Please close all open virtual machines first.

【问题五】VMware Workstation cannot connet to the virtual machine.

【Phenomenon】

Open the virtual machine and report an error (as shown below):

【solve】

solution:

To start the VMware Authorization service or check if it is running, follow these steps:

Log in to the Windows operating system as an administrator.
Click Start, and then click Run.
Type services.msc and click OK
Scroll down the list that appears and find the VMware Authorization service
Click Start this service unless the status shown for this service is already Started.

【问题六】The network bridge on device 'VMnet0' is not running.

【Phenomenon】

Open the virtual machine and report an error (as shown below):

Observe that in the network connection, there is one VMware Bridge Protocol missing in the properties of the VMware virtual network card VMnet1. Normal as shown below:

【solve】

solution:

1. In "VMware Network Adapter VMnet1 Properties", click "Install" -> "Services" -> "Add..." -> "VMware, Inc" in Manufacturers, and "VMware Bridge Protocol Version" in Network Services: 4.0.0.0 [2004-8-5]"->"Install from disk..."->"Browse"->C:\Program Files\VMware\VMware Workstation\netbridge.inf (here choose your own installation directory )->"Open".

2. Restart the computer.

http://blog.csdn.net/eastmingchen/article/details/7372407

This article is from the " Share your knowledge " blog, please be sure to keep this source http://skypegnu1.blog.51cto.com/8991766/1618355

VMware Workstation FAQ

Guess you like