07 October 2009

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.”

ISSUE:

Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx.

"G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file.

image

I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB).

Resolution:

I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps

1. First of all go to the folder where you have your virtual machine and delete all .lck folders.

image

564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck
Windows XP Professional.vmdk.lck
Windows XP Professional-000001.vmdk.lck
Windows XP Professional-000002.vmdk.lck

2. Open the .vmx file. In my case it was empty and 0KB.

image

3. Copy the content from any other .vmx file that you may have. This could be from a backup or from other virtual machine you may have. Let me know if you do not have any so I can send one to you.

image

4. Change following line in the file

scsi0:0.fileName = "Windows XP Professional-000001.vmdk"
displayName = "Apps - Windows XP Professional - QTP"
nvram = "Windows XP Professional.nvram"
extendedConfigFile = "Windows XP Professional.vmxf"

To get this value “scsi0:0.fileName = "Windows XP Professional-000001.vmdk"” you need to open Windows Explorer with detail view. Sort the folders & files by recent date and copy the name of the most recent .vmdk file.  See the picture below and you will notice that in my case it was "Windows XP Professional-000001.vmdk". Other values are self explanatory but if you have any question then post a comment & I will respond back with particular details.

image

Following line should also be changed but I could not find the correct value for it. So I left it like this.

ethernet0.generatedAddress = "00:0c:29:1d:4b:3f"

5. After you done editing, save & close the file.

6. Open VMWare and try to open the virtual machine. It it show you a message (I forgot to take screen shot of that message). The message will say something like this “Did you copy or move this virtual machine.” It will give you two options to chose from. 1. Copy & 2. Move. Select Copy option and Do not select move option. If you select move option then VMWare will not generate new SID & other keys.

7. That it. It should open your VMWare virtual machine and you should be good to go.   

Alternate Methods:

There are many other methods too that you can try to resolve this issue.

1. Create a new virtual machine & attach the existing .vmdk file: Create a new virtual machine with custom (advanced) configuration option and chose “I will install the operating system later”. Later in the new virtual machine wizard chose “Use an existing virtual disk”. This will allow you to browse and select your existing virtual disk. While browsing for file remember to sort the folders & files by recent date and then select the most recent .vmdk file.

2. Recover vmx from log file: Following pages describe this process.

http://communities.vmware.com/message/1029971#1029971
http://www.vi-toolkit.com/wiki/index.php/Recover_vmx_from_log_file 

3. Recreate vmx file: Following pages describe this process.

VMware ESX – How to easily recreate a missing or corrupt VMX file - http://www.techhead.co.uk/vmware-esx-how-to-easily-recreate-a-missing-or-corrupt-vmx-file 

Understanding VMware VMX Configuration Files – Learn How To Create and Edit VMX Files

Tagged: ,

10 comments:

  1. I dont have the Ubuntu-10.10.vmx file can you please send it asap

    ReplyDelete
  2. Thanks a lot for this resolution! Still valid and woking 100% (with vm workstation 11)
    (Lucky me to have a copy of the f***** up vmx file o0)

    I "produced" this issue while restoring a large sql-db in the vm. Unfortunatly my host-disk was nearly full, vm-workstation probably tried to expand the vm-disk consuming the very last byte of the host-disk, *boom*

    learning: always ensure to have at least the configured max capacity disk-size of the virtual disk free on host-disk... -.X

    ReplyDelete
  3. Graciaaaaassss, me salvaste la tesis,
    No podia reparar la máquina virtual por nada, pero con esto funcionó perfectamente

    ReplyDelete
  4. Thanks for sharing the post.. parents are worlds best person in each lives of individual..they need or must succeed to sustain needs of the family. best vpn

    ReplyDelete
  5. I admit, I have not been on this web page in a long time... however it was another joy to see It is such an important topic and ignored by so many, even professionals. professionals. I thank you to help making people more aware of possible issues. China VPN

    ReplyDelete