VMware Workstation Frequently Asked questions resolved

This article in the way of FAQ, we can search by keyword.

Issue One: VMware installs 64-bit operating system error "This host supports Intel Vt-x, but Intel Vt-x is disabled"

"Issue One" VMware installs 64-bit operating system error "This host supports Intel Vt-x, but Intel Vt-x is disabled"

Phenomenon

The virtual machine has been 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.

If Intel Vt-x is disabled in the bios/firmware settings, or if the host has never restarted since the setting was changed, the Intel Vt-x may be disabled.

(1) Verify that Intel vt-x is enabled in the Bios/firmware settings and that trusted execution is disabled.

(2) If one of these two bios/firmware settings has changed, restart the host

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

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

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/5A/61/wKiom1T7lKKg3jDRAAGqsmF4k0Q975.jpg "title=" 1.png " alt= "Wkiom1t7lkkg3jdraagqsmf4k0q975.jpg"/>

Solution

Virtual 64-bit systems, virtualization technology must be supported.

If prompted: This host does not support Intel Vt-x, it is not possible to virtual 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, enabling virtualization support requires several conditions : chipset support, BIOS support, processor support, operating system support.

• On the operating system side, the mainstream operating system supports VMM management, so there is no need to consider.

• Chipsets, which have been supported since the era of Intel 945 (except for netbooks), are not considered.

• CPU, can be judged by the Intel official website query.

• Therefore, it is more to see if it is supported from the BIOS. CPU is not enabled by default VT, need to manually modify in the BIOS

1. Intel Virtualization Technology (Intel Vt-x) is turned on in the BIOS's CPU advanced options.

2. Some BIOS also need to go to security in Intel Virtualization technology.

• See if the CPU supports virtualization technology and can use securable to determine if virtualization is supported
  

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/5A/61/wKiom1T7lxmCEG1MAALTaKLyqL4579.jpg "style=" float: none; "title=" 2.png "alt=" Wkiom1t7lxmceg1maaltaklyql4579.jpg "/>

• Or use cpu-z software to view
  

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/5A/5D/wKioL1T7mDPweAWbAAHkokSS_Y0909.jpg "style=" float: none; "title=" 201105250842279783.png "alt=" Wkiol1t7mdpweawbaahkokss_y0909.jpg "/>

• Turn on the BIOS virtualization feature (because the motherboard model is different, so you need to operate according to the actual situation)
  

Note: Adjust the bios of the physical machine (host) Oh, not the virtual machine!

Phoenix BIOS:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/5A/61/wKiom1T7l5aB2KbWAAIeO7uwaN8776.jpg "title=" 2.png " alt= "Wkiom1t7l5ab2kbwaaieo7uwan8776.jpg"/>

Insyde BIOS

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/5A/5E/wKioL1T7meqgTLmIAAJ0QvW-V9w978.jpg "title=" 1.png " alt= "Wkiol1t7meqgtlmiaaj0qvw-v9w978.jpg"/>

ASUS UEFI BIOS

ASUS Motherboard BIOS UEFI BIOS Open VT step

• Press F2 to enter BIOS setup when powering on

• Go to Advanced (Premium menu)

• Enter CPU configuration (processor settings)

• Turn Intel Virtualization Technology (Intel Virtualization Technology), change it to Enabled (enable)

• Press F10 to save the settings

• Press ESC to exit the BIOS Setup
  

• 
  

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/5A/61/wKiom1T7mTuBmKlJAAJv36cxyyg295.jpg "title=" 1.png " alt= "Wkiom1t7mtubmkljaajv36cxyyg295.jpg"/>

Chinese interface

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/5A/61/wKiom1T7mdnweSanAAFi7MDznLI338.jpg "title=" 1.png " alt= "Wkiom1t7mdnwesanaafi7mdznli338.jpg"/>

"Problem Two" This is virtual machine appears.

Phenomenon

This could be a bug with VMware Workstation when virtual machine in VMware Workstation is running and is shut down or restarted unexpectedly. Cause when we restart virtual machine again, it will prompt "The VM appears to is in use", unable to start the VMS.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/5A/5E/wKioL1T7nmXDseDrAACtfDZMG2k161.jpg "title=" 1.png " alt= "Wkiol1t7nmxdsedraactfdzmg2k161.jpg"/>

PS: This lck file is a disk lock file for a virtual machine, and we know that the disk of the virtual machine is co-exist with the host's disk, but only because of the specific virtual mechanism that makes the two non-impact. When using a virtual machine, VMware generates several disk lock files to protect the disks that are currently occupied by the virtual machines from being modified by the host or other virtual machines. VMware automatically removes this lock when the virtual machine is shut down normally. However, in rare cases, such as a sudden crash of the host, abnormal shutdown, and so on, VMware is not able to delete the LCK disk lock file. So the next time you start the virtual machine, VMware will also mistakenly assume that the virtual system that needs to start is already running, and there is an error on the above of this virtual machines appears to is in use. After you delete the file, you can return to normal.

Solution

The repair method is very simple, to the corresponding virtual machine directory to delete the% virtual machine name%.vmx.lck folder or files in it, such as error, you need to restart the host.

• Yes, if you're certain that the guest was truly not running, go to the guest's folder and delete any. lck Files and folder S. Delete the folders with. lck file extension.

• If you can ' t delete the these files, make sure to close the 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 Task Manager, we find Vmware.exe and vmware-vmx.exe two important processes .

• Where Vmware-vmx.exe is the main program, the virtual machine runs under this process;

• VMware.exe is the shell that displays the virtual systems running in the Vmware-vmx.exe and explains the various commands and operations that are used, and is our most common VMware user interface, which can be re-entered to open multiple simultaneously.
  

Because VMware Workstation is reentrant, in order to prevent the same virtual system from being opened by multiple VMware.exe at the same time, this can cause errors, so each VMware opens the appropriate Virtual Machine tab and checks to see if there is * in the virtual machine root directory. Vmx.lck the folder and validates the file, if the file contains a legitimately generated UUID (Universal unique identifier), the virtual machine's tab cannot be opened and the following error message appears:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/5A/61/wKiom1T7oH7T3KZWAADrJUtXnlI353.jpg "style=" float: none; "title=" 1.png "alt=" Wkiom1t7oh7t3kzwaadrjutxnli353.jpg "/>

The following prompt appears after take ownership:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/5A/5E/wKioL1T7oZiB5OBfAACxUzVO7_w872.jpg "style=" float: none; "title=" 2.png "alt=" Wkiol1t7ozib5obfaacxuzvo7_w872.jpg "/>

If there is no corresponding legal file, the *.vmx.lck folder is generated under the root of the virtual machine, and a *.lck file containing the UUID is generated under that folder, the Virtual Machine tab is opened, and the display information is received from the main program.

This *.lck file can be edited with Notepad. It's uuid={. A string of alphanumeric},uuid is a universal unique identification code (universally unique Identifier), which is characterized by uniqueness. So that only one vmware.exe can accept the display of the main program and operate on the virtual machine. LCK is the abbreviation for lock, which is the lock on the requested resource.

When virtual machine was successfully created, there are actually only three main files:. The vmx file is a parameter file for the virtual machine. VMDK files are disk files for virtual machines. Other files are generated after the virtual machine is started, and the virtual machine will automatically delete the files after normal exit, each time the VM starts, it detects if they exist, and if there is a prompt error (that is, a virtual machine is not allowed to be opened two times). This error is usually caused by an abnormal shutdown of the virtual machine!

At runtime, VMware virtual machines generate at least three *.vmx.lck,*.vmdk.lck,*.vmem.lck folders in the corresponding virtual machine directory, containing files named *.lck. The *.VMX.LCK is generated when the Vmware.exe tab is opened, and the other two are about the use of virtual disks and memory, which are accompanied by the operation of the virtual system. If VMware.exe is turned off so that the virtual machine runs in the background, the *.vmx.lck folder disappears and the other two do not.

When you open a virtual Machine tab in VMware.exe, the *.vmsd.lck folder is briefly generated, which is estimated to be generated when the data was originally transmitted (send), preventing multiple shells from simultaneously requesting the virtual machine to open.

Original reference here: http://hi.baidu.com/patriotspy/item/259d515b1ee8e90ae7c4a50b

The "problem three" of the VMware Authorization Service is not running.

Phenomenon

Turning on the virtual machine error (for example), starting the virtual machine fails with the following error:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/5A/61/wKiom1T7pBeiN5AxAABl_Dp-Pys213.jpg "title=" 1.png " alt= "Wkiom1t7pbein5axaabl_dp-pys213.jpg"/>

Solution

Reason:

This problem may occur when the VMware Authorization service is not running or if the service does not have administrator rights.

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

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

2. Log on to the Windows operating system as an administrator.

4. Click Start , and then click Run .

6. Type services.msc, and then click OK

8. Scroll down the list that appears to find the VMware Authorization service

10. Click Start this service unless the status shown by this service is already started.

Note : The VMware Authorization service relies on the Windows Management Instrumentation service. The service must also be in a running state. If the VMware Authorization service fails to start or stops after startup, locate and start the Windows Management Instrumentation service.

If the VMware Authorization service displays a status of started, this service may not have administrator rights. to provide administrator privileges to the VMware Authorization service

Start-run, enter: services.msc, open "services". Locate the VMware Authorization Service, start the service, and modify its properties to change the startup type to Automatic.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/5A/5E/wKioL1T7piaD6IPRAAG34HA_VAM081.jpg "title=" 1.png " alt= "Wkiol1t7piad6ipraag34ha_vam081.jpg"/>

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

This article is from the "Share Your Knowledge" blog, so be sure to keep this source http://skypegnu1.blog.51cto.com/8991766/1618356

VMware Workstation Frequently Asked questions resolved