OVF descriptor file could not be parsed

[Lobna]

Hi all,

I am trying to import an OVF package from XenServer into vmware workstation 7.

the conversion of the virtual appliance from xenserver successfull, but when i try to import the ovf package into workstation it says: "failed to query source for information". and if i try to convert the OVF package to .vmx using OVF Tool 1.0 an error message says: "OVF descriptor file could not be parsed"

The host operating system is Windows xp 32-bit,

the virtual appliance I am converting is Windows 7 32-bit,

OVF Tool 1.0, Vmware Workstation 7

What could be the problem?....

PS. I dnt mind changing the operating system as I am only testing the transferability of virtual machines between different vendors using OVF for my bachelor project,

Plz helpppppppppppppppppppppp!!! 

[WoodyZ]

OVF Tool 1.0, Vmware Workstation 7

The OVF Tool that ships with VMware Workstation is old and I'd install the latest Open Virtualization Format Tool and try with that and see if it makes any difference.

[continuum]

can you extract the package with 7zip ?

when you have the vmdk-file separately you can create a VM around it from scratch

[Lobna]

first thanx for the fast reply...

I will try converting with OVF Tool that is not shipped with workstation

second,

u mean i should extract the ovf package with 7zip??
i dnt understand what you mean with "when you have the vmdk-file separately you can create a VM around it from scratch"

[continuum]

OVF packages are tar archives of a VM including a descriptor file plus a vmdk
If you can extract it you get a xml file plus a vmdk.
The ovf-tool translates the xml-file to a vmx-file which is needed by Workstation

If the xml file can not be read by the tool you try you can still create a new VM and assign the vmdk you have

in my experience OVF-importing from XEN is hit or miss - it may work and it may fail

[Lobna]

ahaaaaaaa...now i understant

Okay will try that and will post back the result

Thnx anyways

[Lobna]

hi again,

i have extracted the ovf package and it got me a .pvp file and a .vhd file

and i have created a new vm in vmware, what file should i put where.

thnx . sorry for asking again

[WoodyZ]

Did you try using OVF Tools 2.0.1?

Neither of those files are directly usable by VMware Workstation under normal conditions.

You can try converting the .vhd to a .vmdk with StarWind V2V Converter and then create a new VMware Workstation Virtual Machine pointing it to use and existing virtual hard disk, the one created by converting the .vhd file.

[Lobna]

I downloaded OVF tool 2.0.1 but when i try the setup it says that it is not supported on this operating systems ..windows xp 32-bit :S

anyways, i downlaoded the starwind converter, and converted the .vhd file into .vmdk, started a new created vm pointed it to use the newly created vmdk

and YET IT IS STILL NOT WORKING :S:S

Its very wierd, i dnt get it, it should work now??....the OS starts but it tells me that there are problems and Windows is looking for the cause of the problem, searches for a while and then nothing,,,no solution found and the vm shuts down ...

[WoodyZ]

Are you sure you downloaded the right file "VMware-ovftool-2.0.1-260188-win-i386.exe"?  Did you validate the MD5 and or SHA1 checksums?

From the README file:

             VMware OVF Tool 2.0.1

System Requirements
-----------------------
VMware OVF Tool is supported on the following operating systems:

Windows 32-bit (x86) and 64-bit (x86_x64)
   Windows XP
   Windows 2003
   Windows Vista
   Windows 2008
   Windows 7
  
Linux 32-bit (x86) and 64-bit (x86_x64)
   CentOS 5.x
   Fedora Core 12.x
   RedHat Enterprise Linux (RHEL) 5.x
   SUSE Enterprise Server 10.x
   Ubuntu Desktop 9.x

Mac OS X (64 bit)
   Mac OS X 10.5
   Mac OS X 10.6

I just installed it under Windows XP 32-bit without any problem.

[Lobna]

i downloaded one from the website that didnt work...but i will look for the i386,,,coz that wa not the one i downloaded,,,

THNX

[WoodyZ]

It's the first one in the list.

[Lobna]

Hi Agaaaaaaain

First, thnx for ur timely replies and for the trials to make it work, el7 now it DOES WORK!

I found that the drivers used in the machine were IDE in one and SCSI in the other so I converted the SCSI to IDE and BOOOM IT WORKS...

though I had to change in the xml file, delete the IDE item element :smileygrin::smileygrin:

Thankssss again, now i can begin writing my thesis with PEACE!