禁用cpu重置虚拟机(虚拟机客户机已禁用cpu)

Types of data garbage in virtual infrastructure Abandoned VM images When a virtual machine is deleted from VMware vCenter, Microsoft Systems Center, Red Hat Enterprise Management (RHEM), or other virtual machine management console, it is still Must be deleted from disk. Otherwise, the virtual machine no longer appears in the management console, but its accompanying VM image still exists in storage. If this happens, the result is an obsolete VM image that still resides in storage and takes up storage space, but is no longer used. In theory, the correct course of action would be that every time a system administrator deletes a virtual machine from the management console, the administrator should repeat the same operation on the storage array, but this is not the case.
For a variety of reasons, a virtual machine image may still exist on the storage system even though it has been deleted from the management console. It may be caused by the following reasons:
A certain VMware vMotion storage failed, but the files have not been completely transferred to another data storage. This situation may occur whether the previous VMDK file is migrated or the new VMDK file is copied to a new data storage location. In both cases, vCenter will not know where these files are. If the new host is not of the same configuration or does not have enough disk space, vMotion will fail. Additionally, some users configure vMotion in a completely automated manner, so vMotion storage failures will be difficult to detect unless the error logs are checked.
System administrators migrated by manually copying and pasting VM images, but forgot to delete the old files.
The VM image is copied to replace the template in use. The virtual machine image is unnecessary but has not been deleted.
A third-party backup or storage snapshot tool copies the VM image file, but the management console is unaware that additional VM image files were created in this manner.

Open the directory where the newly created virtual machine is located (if you are on a Windows 7 system! It is really troublesome to search one by one, just use the file search function of Windows 7 to find it), find the file "" and use After opening Notepad, find the line guestOS= and change the content in the double quotation marks "" after it to darwin10. After the change, it becomes:
guestOS="darwin10" Save and exit. Restart the virtual machine and it will be OK. Anyway This is how I solved it! Hope it helps you!