VMware Cloud Community
hihiy
Contributor
Contributor

convert a WinXP vm from ESX3.5U3 to vsphere4 got "encoding UTF-8" error

dear all:

Today I had an error while trying to convert a WinXP VM from an ESX3.5U3 server to vSphere4 ESX server with the VMware converter. But I got an error :

File "/vmfs/volumes/xxxxx/ServerName/ServerName.vmx" line 65: File already has an encoding "UTF-8". Cannot open configuration file /vmfs/volumes/xxxxx/ServerName/ServerName.vmx.

I edited ServerName.vmx file, find the line 65 and delete it. After this has been done, the VM is working fine.

Why? Is this a bug for converter?

Thank you in advanced.

hihiy

Reply
0 Kudos
2 Replies
continuum
Immortal
Immortal

Converter does not understand ALL entries that may appear in a vmx-file - if necessary you may need to "beautify" it a bit so that Converter understands it

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
hihiy
Contributor
Contributor

the vmware support reply me this:

The error, "File already has an encoding "UTF-8"" is caused if the .vmx file has 2 ".encoding" entries.

Deleting one of the entries in the .vmx file helps resolve the issue. This is the resolution for the above error.

and,

The issue of the .encoding parameter being repeated twice in the .vmx file is known to occur if the VM has been converted twice.

For e.g. VMware Converter 3.0.3 will first add a parameter such as .encoding = "windows-1252" and subsequent conversions will add .encoding = "UTF-8"

The above issue has been fixed with the later versions of VMware Converter.

thank you.

Reply
0 Kudos