当前位置：首页 > 虚拟机 > 正文

虚拟机一直让重新启动又启动不了(打开虚拟机时一直卡在启动界面)

虚拟机
2023-12-22 09:46:53
8229

How to solve the problem that the virtual machine cannot start

Solution:

Go to the corresponding virtual machine directory and delete the %virtual machine name%. folder Or just the files in it

When we open the task manager, we will find two important processes: and . Among them, is the main program, and the virtual machine runs under this process; is the shell program, which is responsible for displaying the virtual system running in and explaining and transmitting various commands and operations. It is our most commonly used VMware user interface, the program can be reentrant i.e. multiple can be opened at the same time.

Because VMwareWorkstation is reentrant, in order to avoid errors caused by the same virtual system being opened by multiple at the same time, each VMware will first check this when opening the corresponding virtual machine tab. Check whether there is a *. folder in the root directory of the virtual machine and verify the file in it. If the file contains a legally generated uuid (universal unique identification code), the tab of the virtual machine will not be opened and an error message will appear. The following error message:

The following message will appear after TakeOwnership:

If there is no corresponding legal file, it will Generate the *. folder in the root directory of the virtual machine, generate a *.lck file containing uuid in the folder, open the virtual machine tab, and receive display information from the main program.

This *.lck file can be edited with Notepad. Inside is uuid={a string of letters and numbers}, uuid is a universal unique identifier (UniversallyUniqueIdentifier), and its characteristic is uniqueness. The purpose is that only one can accept the display of the main program and operate the virtual machine at the same time. lck is the abbreviation of lock, which is the lock on the requested resource.

When the VMware virtual machine is running, it will generate three files *., *., and *. folders in the corresponding virtual machine directory, which contain *. File named lck. Among them, *. is generated when the tab in is opened; the other two are about the use of virtual disks and memory, and they are generated when the virtual system is running. If you close and let the virtual machine run in the background, the *. folder will disappear and the other two will not.

When you open a virtual machine tab in , the *. folder will be generated briefly. It is estimated that this is generated when the data (senddata) is initially transferred to prevent multiple The shell also requests to open the virtual machine.

Solution to the vmware virtual machine that cannot be opened

1. Find the working directory of the virtual machine, which is the folder where the virtual machine is stored. You will see a folder with a name ending with "lck". Delete them all, and you can start the virtual machine. If you are not worried about deleting them all at once, cut them elsewhere first; 1. Most of the time, the virtual machine cannot be opened because of firewall interception. The solution is interrupted. Internet, turn off the anti-virus software, and turn off the firewall 2. If the Internet is disconnected and there is still no response when opening the virtual machine after turning off the firewall, it may be that the software does not have enough permissions to run. At this time, you need to right-click to run the VMware solution as an administrator; it is a firewall problem. There are two solutions: 1. Turn off the firewall. 2. Add VMware in "Allow programs to communicate through Windows Firewall". You can try it. If it is as you said, click to open the virtual machine and there is no response at all. An error warning will pop up. Then these two I wish you a solution. The specific solutions are as follows: 1. First open the control panel and find the management tools. 2. Open the management tools and find the service inside. 3. Double-click the service to enter and find the VMware Authorization Service. 4. Click Start on the left. 5. Click again after starting. The virtual machine can be turned on.
2. If possible, you don’t need to do the following steps. 4 Right-click the computer and click Management. 5 Click Services and Application Services. 6 Find the vmware service "VMware Authorization Service, and set it to automatically start and open. 7 Pass The above steps can successfully open and use the VMware virtual machine; 1. Click the "Start" button in the lower left corner and click "Computer Management" 2. Select "Service and Application Management", click the "Service" drop-down menu and select the "VMware Authorization Service" file 3. Double-click to open it. Change the startup type to "automatic" to open the virtual machine normally; 1. Use anti-virus software to kill viruses, recommend NOD32, Kabasi, and Rising. 2. Delete VMware in safe mode, and then reinstall it. 3. Check whether VMware is disabled in the WINDOWS service. Service, if there is one, start it. 4 If the recently installed software conflicts with VMware, uninstall the conflicting software and find similar software to replace the conflicting software V.
3. Select the one that is not the local optical drive and add the ISO file to In this optical drive, click Confirm, then select the VM power BIOS item from the virtual machine menu to boot. Otherwise, it will be difficult to enter the BIOS on the screen. After booting, enter BOOT to boot the optical drive. After the installation is completed, resume booting from the hard disk. ; First check the location of the virtual machine file, open the file location, check the vmware text document, open it and search for the pid text. You can also pull it to the right and you will see it. Generally, the result obtained on the first line is that the virtual machine entered The pid value of the field is displayed in the Task Manager Performance Resource Monitor 5 resource; when installing the VM for the first time, if this prompt appears, you can try the following method. Enter the system preferences, select Security and Privacy under the General tab, and "Allow access from the following locations" If you don’t have any source options, open the terminal and enter the following command again; if your computer is a 64-bit computer system, if not, then you need to download a 32-bit virtual machine. It is a 64-bit operating system, so you may need to re-download a compatible version of the virtual machine software and reinstall it; if you cannot find this service at all, please download the official full version and reinstall it. Summary The virtual machine power cannot be turned on. Question: Open the host control panel management tool service, find the VMware authorization service VMwareAuthorizationservice, and set this service to the automatic startup type; vmwareworkstation10 cannot open the virtual machine. Solution 1: Use anti-virus software to kill the virus. It is recommended that NOD32 Cabasi Rising 2 delete VMware in safe mode. , and then reinstall. 3 Check whether VMware related services are disabled in the WINDOWS service. If so, start 4 the recently installed software and VMwar; Arm cannot be opened, and the virtual machine stops automatically after running half way. It may be that the system has insufficient memory. As a result, reasonable resources cannot be provided and the storage resources he needs cannot be provided.
4. 2 Right-click Start, click Computer Management, PS can also right-click this computer, click Manage 3 Double-click Services and Applications 4 Double-click Services 5 Find and double-click VMware Authorization Service 6 Change the startup type to Automatic, Apply OK 7 Accept After that, you can open the virtual machine normally; I have also encountered this problem. After many attempts and research, I found that the problem lies in the VMs. Just close the VMs to open the virtual machine. To close the VMs, edit=Preferences=ShareVMs and click DisableSharing. After clicking, it will become EnableSharing, and you can open the virtual machine normally; "devvmmon cannot be opened" The solution conflicts with HAXM or docker. Let's talk about the solution to the haxm conflict on mac. 1. Before starting vmwarefushion, uninstall the haxm kernel module sudokextunloadLibraryExtensionsintelhaxmkext, and then you can Start vmwarefushion2 normally.