Preface:Corruption for VMware Virtual machine configuration file (. vmx)the cause of the problem may not be the same as mine, but the solution should be the same.However, this method only applies if the. vmx file is damaged and other files are intact.
problem occurs:Recently, I have been studying Hadoop, and today, when I finished with hbase, I felt very slow when I used it, and it stuck when I executed the hbase shell. Then the error message ... Forgot the content ... Then the virtual machine crashes and the virtual machine is no longer open, prompting my. vmx file to be corrupted.
The. vmx file is used in VMware virtual machines to save all hardware and software configurations for the virtual machine, and failure to open the virtual machine normally occurs if it is accidentally damaged.
my situation:The VMware version is 10 and the virtual machine is a Linux system: The CentOS release 6.4.VMX file is named: CENTOS.VMX
To view the log file:Open the Vmware.log file in the virtual machine directory I found the following two words in the last section of the log logs. ......................................................................................................................... ........... 2014-11-01t21:51:09.100+08:00| Vmx| W110:minidump failed:
There is isn't enough space on the disk
2014-11-01t21:51:09.137+08:00| Vmx| I120:coredump error:write, page 0x113 (0xFFFFFFFF)
No space left on device......................................................................................................................... ........... It is obvious that there is not enough disk space to cause errors when writing data. The configuration centos.vmx eventually caused an error.
Solution Ideas:1. Remove the. vmx file (do not delete the wrong!!!) ), and then create a. vmx file of the same name, and mine is centos.vmx;2. Find "DICT---CONFIGURATION" (front is the date and time information); 3. Find "DICT---USER DEFAULTS" (Front is the date and time information) 4. Copy the data between the two lines (the two lines mentioned above do not need to be duplicated); 5. Paste into the. vmx file (mine is CENTOS.VMX); 6. Delete the datetime flag in front of all lines in the Centos.vmx file, leaving only the following information, for example: 2014-11-01t20 : 50:32.963+08:00| Vmx| I120:dict config.version = "8" will "2014-11-01t20:50:32.963+08:00| Vmx| I120:dict "Partial Delete, only keep Config.version =" 8 "; PS: If you do not know the simple way to delete columns, I recommend using notepad++, press the Alt button, you can select the column, and then all the columns representing the time flag are deleted. Then select all, Tab+shift can move all the content left, and finally let the front space all removed, to achieve the left-aligned log information effect. 7. Make all changes in the upper format, and then add double quotation marks to all lines after the equal sign (note Do not use the Chinese input method of double quotation marks) For example: Config.version = 8 to Config.version = "8" If you're like me, you already have double quotes, you don't need to add 8. Save the. vmx file (CENTOS.VMX); 9. Reopen the. vmx file (CENTOS.VMX); 10. OK, start the virtual machine.
At the end of the paper, I enclose some content of the modified Centos.vmx file (first + tail, omitted in the middle): ... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... config.version = "8"
Virtualhw.version = "8"
Scsi0.present = "TRUE"
Scsi0.virtualdev = "Lsilogic"
Memsize = "256"
Scsi0:0.present = "TRUE"
Scsi0:0.filename = "CENTOS-000010.VMDK"
Ide1:0.present = "TRUE"
Ide1:0.filename = "Auto Detect"
Ide1:0.devicetype = "Cdrom-raw"
floppy0.startconnected = "false" ... checkpoint.vmState.readOnly = "false"
Gui.lastpoweredviewmode = "fullscreen"
Ide0:0.present = "FALSE"
Usb:0.present = "TRUE"
Usb:0.devicetype = "HID"
Usb:0.port = "0"
Usb:0.parent = "-1" ...... ..... ................ ....................... ........
VMware Virtual machine configuration file (. vmx) Corruption fix
