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

虚拟机显示已开机但是打开不了(开启虚拟机后无法启动)

What is the reason why the virtual machine cannot be opened?

The reasons why the virtual machine cannot be opened are as follows:

1. Firewall interception. Most of the time, the virtual machine cannot be opened. It's all caused by firewall interception, just turn off the firewall.

2. The permissions for running the software are insufficient.

3. Shut down the virtual machine abnormally.

Hardware requirements for virtual machines in win10 system

Minimum hardware configuration: CPU Celeron 1.7GHz, memory 1GB, available disk space 6GB, 64MB video memory Discrete graphics card.

Recommended hardware configuration: CPU Pentium 42.4GHz, memory 2GB, available disk space 10GB, 128MB video memory independent graphics card.

Explanation: A virtual machine (Virtual Machine) refers to a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment.

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.

The VM virtual machine shows "Powered on", but the system of the virtual machine cannot be started, and the VM options are all gray and cannot be clicked
Is it still like this after trying again? ?