This is a message in Mime Format. If you see this, your mail reader does not support this
format.
--=_c0b46d9f4b4a2a557ef0dbb186775a75
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
After reinstallation of engine from build #369 to #440 (clean install),=
I attached NFS export domain to new DC (compatibility 3.0), but on page=
"VM Import" there were only VMs that I saved with 3.1 engine. =0A=0AMes=
sages in webadmin event : =0A=0AFailed to read VM 'VM01' OVF, it may be=
corrupted =0AFailed to read VM 'VM02' OVF, it may be corrupted =0AFaile=
d to read VM 'VM03' OVF, it may be corrupted =0A=0AThere are no error's=
messages in engine.log=0AWhen I tried to edit OVF for VM01 by xml edito=
r, I've got=0A=0AFailed to read VM '[Unknown name]' OVF, it may be corru=
pted=0AFailed to read VM 'VM02' OVF, it may be corrupted =0A=0D=0AFailed=
to read VM 'VM03' OVF, it may be corrupted=0A=0AHow is it possible to c=
onvert from ovf:version "0.9", to ovf:version "3.1.0.0" or correct OVF
f=
iles ?=0A=0A--
--=_c0b46d9f4b4a2a557ef0dbb186775a75
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
After reinstallation of engine from build #369 to #440 (clean install),=
I attached NFS export domain to new DC (compatibility 3.0), but on page=
"VM Import" there were only VMs that I saved with 3.1 engine.
<br><br>M=
essages in webadmin event : <br><br>Failed to read VM 'VM01' OVF, it
may=
be corrupted <br>Failed to read VM 'VM02' OVF, it may be corrupted
<br>=
Failed to read VM 'VM03' OVF, it may be corrupted <br><br>There are no
e=
rror's messages in engine.log<br>When I tried to edit OVF for VM01 by xm=
l editor, I've got<br><br>Failed to read VM '[Unknown name]' OVF,
it may=
be corrupted<br>Failed to read VM 'VM02' OVF, it may be corrupted
<br>=
=0D=0AFailed to read VM 'VM03' OVF, it may be corrupted
<br><br><br>How=
is it possible to convert from ovf:version "0.9", to ovf:version "3.1.0=
.0" or correct OVF files
?<br><br><br><br><br><br><br><br>--<br><br>
--=_c0b46d9f4b4a2a557ef0dbb186775a75--
Show replies by date