I am trying to convert VMX to OVF format using OVFTool as below, however it gives error:
C:\Program Files\VMware\VMware OVF Tool>ovftool.exe
vi://vcenter.com:port/folder/myfolder/abc.vmx abc.ovf
Error: Failed to open file: https://vcenter.com:port/folder/myfolder/abc.vmx
Completed with errors
Please let me know if you have any solution.
Maybe
ovftool
is unable to recognize the path you are giving.Try with following command:
Once you provide the ESX address, it will list down the folders you have created in your ESX box. Then you can trigger the command above mentioned again with appending folder name.
If no folder hierarchy present in your box, then it will simply list down vm names.
Retry the same command appending
[foldername]/[vmname no vmx file name required]
For me opening the .vmx and deleting the following line worked:
I had a similar problem with OVFTool trying to export to OVF format.
First, I opened .VMX file in editor (it's a text file) and made sure that settings like
mention proper file names. Then I noticed this line:
This is Cyrillic code page, so I modified it to use Western code page
Then, running OVFTool gave a different error
To fix it I had to open .VMDK file in HEX editor (because it's usually a big binary file), found there the string
(it's somewhere in the beginning of the file), and replaced "1251" with "1252".
And it did the trick!
In my case, this works:
I did change
true
tofalse
and works fine, ascdrom-image
not exist, this change permit the format conversion.I had this same exact issue. In my case I opened up the VMX file and dropped the IDE and sound controllers from the file and saved. I was then able to convert everything to an OVA using the tool with the standard syntax.
e.g. I dropped:
and:
This allowed me to convert the file like normal.
I had a similar situation in vmware fusion trying to use a .vmx that was probably created on windows. I could boot the VM, but any attempt to export the machine with ovftool or use vmware-vdiskmanager bombed out with:
the diskname was totally valid, path was valid, permissions were valid, and the only clue was running ovftool with:
as others suggested, i took a peek in the .vmdk. therein i found 3 other clues:
so first i converted the monolithicSparse vmdk to "preallocated virtual disk split in 2GB files":
then i could edit the "foo.vmdk" to change the encoding, which now looks like:
and finally, after fixing up the source.vmx:
profit: