VMware虚拟机打开异常解决方法

版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文链接： https://blog.csdn.net/qq_41248872/article/details/89329339

         <!--一个博主专栏付费入口结束-->
        <link rel="stylesheet" href="https://csdnimg.cn/release/phoenix/template/css/ck_htmledit_views-d284373521.css">
                                    <link rel="stylesheet" href="https://csdnimg.cn/release/phoenix/template/css/ck_htmledit_views-d284373521.css">
            <div class="htmledit_views" id="content_views">
                                        <p>使用虚拟机的朋友想必都或多或少遇到过虚拟机崩溃，无法开启的问题吧。这确实是虚拟机存在的一个严重问题，例如突然断电，或者虚拟机非正常关机等等，很多因素都能造成虚拟机的异常损坏，本文就针对其中的一种常见问题提供相关解决办法，如有不当之处，望不吝指教，谢谢。</p>

问题现象：提示“/xxx/xxx.vmx文件无法打开“

关于VMware虚拟机的几个重要文件说明：        

.vmx文件

文件类型说明：VMware virtual machine configuration

<vmname>.vmx 

该文件为虚拟机的配置文件，储存着根据虚拟机向导或虚拟机编辑器对虚拟机进行的所有配置。

有时需要手动更改配置文件以达到对虚拟机硬件方面的更改。可使用文本编辑器进行编辑。

如果宿主机是Linux，使用VM虚拟机，这个配置文件的扩展名将是.cfg。

.vmdk文件

文件类型说明：VMware virtual disk file

<vmname>.vmdk or <vmname>-s###.vmdk 

这是虚拟机的磁盘文件，它储存了虚拟机硬盘驱动器里的信息。

一台虚拟机可以由一个或多个虚拟磁盘文件组成。

如果在新建虚拟机时指定虚拟机磁盘文件为单独一个文件时，系统将只创建一个<vmname>.vmdk文件

该文件包括了虚拟机磁盘分区信息，以及虚拟机磁盘的所有数据。

随着数据写入虚拟磁盘，虚拟磁盘文件将变大，但始终只有这一个磁盘文件。   

        由上可知，.vmdk文件是虚拟机的所有文件存储的磁盘位置，因此，有一个简单的办法恢复以前的系统，那就是重新创建一个和原来配置相同的虚拟机，然后在其安装目录下找到.vmx文件，拷贝到待恢复的虚拟机的路径下，并且修改.vmx文件中的scsi0:0.fileName = "Ubuntu.vmdk"    （Ubuntu.vmdk文件是待恢复虚拟机路径下的.vmdk文件），另外给出一个我的.vmx文件（VMware 10,ubuntu 64位系统）

.encoding = "GBK"
config.version = "8"
virtualHW.version = "10"
numvcpus = "6"
cpuid.coresPerSocket = "6"
vcpu.hotadd = "TRUE"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
sata0.present = "TRUE"
memsize = "2048"
mem.hotadd = "TRUE"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "Ubuntu.vmdk"
sata0:1.present = "TRUE"
sata0:1.fileName = "C:\usr\Development\Embedded\Source\Linux_ISO\Ubuntu12.04LTS_backup\ubuntu14.04_backup_20190124.iso"
sata0:1.deviceType = "cdrom-image"
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.addressType = "generated"
usb.present = "TRUE"
ehci.present = "TRUE"
ehci.pciSlotNumber = "35"
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
mks.enable3d = "TRUE"
serial0.present = "TRUE"
serial0.fileType = "thinprint"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
usb.vbluetooth.startConnected = "TRUE"
displayName = "Ubuntu"
guestOS = "ubuntu-64"
nvram = "Ubuntu.nvram"
virtualHW.productCompatibility = "hosted"
powerType.powerOff = "soft"
powerType.powerOn = "soft"
powerType.suspend = "soft"
powerType.reset = "soft"
floppy0.present = "FALSE"
uuid.bios = "56 4d 17 3a 8f f2 a1 6e-b0 98 af 9d 2e 34 8a 82"
uuid.location = "56 4d 17 3a 8f f2 a1 6e-b0 98 af 9d 2e 34 8a 82"
replay.supported = "FALSE"
replay.filename = ""
scsi0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "16"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "33"
sound.pciSlotNumber = "34"
vmci0.pciSlotNumber = "36"
sata0.pciSlotNumber = "37"
ethernet0.generatedAddress = "00:0c:29:34:8a:82"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "775195266"
monitor.phys_bits_used = "40"
vmotion.checkpointFBSize = "134217728"
cleanShutdown = "FALSE"
softPowerOff = "FALSE"
usb:1.speed = "2"
usb:1.present = "TRUE"
usb:1.deviceType = "hub"
usb:1.port = "1"
usb:1.parent = "-1"
tools.syncTime = "FALSE"
unity.wasCapable = "FALSE"
usb:0.present = "TRUE"
usb:0.deviceType = "hid"
usb:0.port = "0"
usb:0.parent = "-1"

修改好.vmx文件后保存退出，如无意外，再次打开虚拟机，成功恢复。