Let’s Work Together

Partner with you to deliver responsive and cost-effective IT & Support solutions
Partner with you
Attitude to Serve
These are the reasons why AionSolution is your vendor when you are seeking someone to support your IT in your office.
+852 2636 6177

Starting a virtual machine generates a syntax error

Starting a virtual machine generates a syntax error


  • The virtual machine fails to power on.
  • The .vmx file contains garbled data or is zero bytes long or is corrupted.
  • You see the error:“<VM_Name>.vmx” line <x>: syntax error


This issue occurs if the .vmx file is corrupted. To resolve this issue, either build a new.vmx file or manually repair the existing file.

Creating a new .vmx file

To create a new .vmx file:

  1. Locate the virtual machine files and delete the .VMX file.
  2. Open the VMware product or VMware Infrastructure Client.
  3. Click File > New > Virtual Machine (if listed).
  4. Follow the new virtual machine wizard making sure to select the Custom configuration installation option. When prompted to create a new virtual hard disk file, choose to specify an existing file. Specify the existing .vmdk file.

Note: For related information when using a Fusion virtual machine, see Creating a virtual machine from an existing virtual disk in Fusion (1023555).

Manually rebuilding the .vmx file

It is possible to reconstruct the corrupted .vmx file provided a copy of thevmware.log is available where the virtual machine started correctly.
To manually rebuild the .vmx file:
  1. Locate the virtual machine files. For Fusion, see Locating the virtual machine bundle in VMware Fusion (1007599)
  2. Open the vmware.log file where the virtual machine started successfully with a text editor. In Macs, use Text Edit.
  3. Find the line in the log file that contains: — CONFIGURATIONBeyond this line — until the next line that contains  — are the complete contents of the .vmx file as it was parsed by the vmx process.
  4. Copy the text into a new .vmx file, overwriting the damaged .vmx file.
  5. From the new file, clean the logging output from the text to restore the original configuration.For example, change the line that reads: 

    vmx| DICT svga.vramSize = 134217728


    svga.vramSize = “134217728”