VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
4 Replies Last post: Jun 4, 2009 12:45 AM by chorgeas  

appliance built with studio not working in VMware Workstation posted: Jun 2, 2009 5:47 AM

Click to view mkolcun's profile Enthusiast 37 posts since
Feb 24, 2009
When I try to import a ovf appliance built with vmware studio using vmware workstation I get this error "The OVF descriptor file could not be parsed"

The log proivides a bit more information, but I'm still not sure what is wrong

Workstation version 6.5.2 build 156735 running on windows xp 5.1.2600 sp3

Anyone else had similar issues?

Thanks

        • LOG below ---

3 2009-06-02 08:42:24.864 'App' 2920 info vmImporter,140 Entering UFAD at QuerySourceInfo
3 2009-06-02 08:42:24.864 'App' 2920 verbose vmImporter,141 source:
3 (sysimage.OvfSourceVMSpec) {
3 dynamicType = <unset>,
3 ovfFilePath = "http://10.1.1.119/build/189/exports/ovf/up.time.ovf",
3 }
3 2009-06-02 08:42:24.864 'App' 2920 verbose ufaConnection,94 Creating local adapter...
3 2009-06-02 08:42:24.864 'App' 2920 verbose disposable,69 Registering disposable session object id=VmiQuerySourceInfoTask::task{2}
3 2009-06-02 08:42:24.864 'App' 2920 verbose disposable,80 Associating disposable session object id=VmiQuerySourceInfoTask::task{2} with session id=5B0A9570-E849-4DA3-A349-F870AA4C452A
3 2009-06-02 08:42:24.880 'App' 4772 verbose imageProcessingTaskImpl,504 VmiQuerySourceInfoTask::task{2}: Starting execution of an image processing task
3 2009-06-02 08:42:24.880 'App' 4772 verbose imageProcessingTaskImpl,154 VmiQuerySourceInfoTask::task{2}: SetState to running
3 2009-06-02 08:42:24.880 'App' 4772 info vmiQuerySourceInfoTask,79 VmiQuerySourceInfoTask initialized
3 2009-06-02 08:42:24.880 'App' 4772 verbose ufaConnection,94 Creating local adapter...
3 2009-06-02 08:42:24.896 'App' 4772 info ufaUtils,670 Using temp dir C:\WINDOWS\TEMP\vmware-temp\vmware-mkolcun-1125\ova-dir.0
3 2009-06-02 08:42:25.302 'App' 4772 info [urlStreamWin32,72] Size of the url file is 6804
3 2009-06-02 08:42:25.365 'App' 4772 error ovfImportSource,314 Ovf file could not be parsed
3 2009-06-02 08:42:25.365 'App' 4772 info ufaUtils,697 Cleaning up temp directory C:\WINDOWS\TEMP\vmware-temp\vmware-mkolcun-1125\ova-dir.0 ...
3 2009-06-02 08:42:25.365 'App' 4772 error imageProcessingTaskImpl,552 VmiQuerySourceInfoTask::task{2}: Image processing task has failed with MethodFault::Exception: sysimage.fault.IncompatibilityFault
3 2009-06-02 08:42:25.365 'App' 4772 verbose imageProcessingTaskImpl,154 VmiQuerySourceInfoTask::task{2}: SetState to error
3 2009-06-02 08:42:25.380 'App' 4772 verbose disposable,122 object explicitly disposed: VmiQuerySourceInfoTask::task{2}
3 2009-06-02 08:42:25.380 'App' 4772 verbose imageProcessingTaskImpl,123 VmiQuerySourceInfoTask::task{2} being destroyed

Click to view chorgeas's profile Enthusiast 86 posts since
Jun 16, 2008
OVF is basically meant for Hypervisor class i.e. ESX, ESXi and ZIP is meant for Hosted class i.e. VMware Server, Workstation etc.

So my suggestions are,
1. If you want to boot your VA in Workstation i.e. hosted class then in VMware Studio choose output format as ZIP and rebuild the VA again.
2. Don't edit anything in .OVF file and try to import using Workstation import option.
3. Might be OVF file is corrupt because in your log it is mentioned as "Ovf file could not be parsed". So please download the .OVF file again or rebuild the VA again.
4. Check the md5sum of ovf file on both the end hosted and in VMware Studio.

In my case following procedure is working in Workstation 6.5.0 for importing VA in OVF format. Please check from your end.

File->Import or Export->Next->Next->Select the type of source you want to use: Other->source VM or image: xyz.ovf->prompt for Conversion Wizard which states that "The source you have specified is a virtual appliance in OVF format. You will not be able to make changes to the virtual appliance while importing to a virtual machine."->press OK ->Next->Accept the License->Next->Select the destination type:Other virtual machine->Next->Give the Virtual machine name and the local location to store VA, also select the type of VM to create->Next->Next->Next->Next->Finish.
Click to view chorgeas's profile Enthusiast 86 posts since
Jun 16, 2008
OVF is basically meant for Hypervisor class i.e. ESX, ESXi.

Sorry for this wrong comment. Actually Workspace 6.5.x can also take OVF (via the embeded Converter).

Also I found that Virtual appliances created with VMware Studio 1.0 can run on:
* VMware Server 1.0.4, 1.0.5, 1.0.6, or 2.0.
* VMware ESX 3.0.3 or 3.5 Update 2.
* VMware ESXi Installable Update 2.
* VMware Workstation 6.0.4.
* VMware Player 2.0.4.
* VMware Fusion 1.1.3.

reference: http://www.vmware.com/support/developer/studio/studio10/studio_relnotes10.html

That means Workstation 6.5.x is not officially supported platform for the VA which is created by VMware Studio 1.0

VMware Beta Programs

Want to be Considered for Future Beta Programs?

Learn More

VMware Developer

Download SDKs, APIs, videos,
training, and more in the Developer community.

Learn More

Developer
Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld
Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

Only VMware ... Delivers Nexus 1000V

Ensure consistent, policy-based network capabilities to virtual machines across your data center.

Learn More

Communities