OVf error on line 9

Bug #492608 reported by sgottesman
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
TurnKey Linux
Invalid
Medium
Unassigned

Bug Description

during import of the ovf file for wordpress you receive an error

line9: unsupported value 'http://www.vmware.com/interfaces/specications/vmdk.html#sparse' for attribute 'formate' on element 'disk'.

I am running vcenter 4 sp 1
esx 4.0

Revision history for this message
Liraz (liraz-siri) wrote :

Thanks for reporting this. I'd like you to try a couple of things to help us find a solution for this.

1) try editing the OVF file, and changing the format from:

http://www.vmware.com/interfaces/specifications/vmdk.html#sparse

To:

http://www.vmware.com/specifications/vmdk.html#sparse

If that works great. If it doesn't, we may have to find a workaround such as using ovftool to convert the OVF to a different VMDK format. Instead of the sparse format ESX seems to like the streamOptimized format the best. OVFtool can convert a VMDK to streamOptimized.

2) using ovftool to convert the OVF file:

ovftool path/to/appliance.ovf path/to/appliance2.ovf

If that doesn't work try converting to vmx and back:

ovftool path/to/appliance.ovf path/to/appliance.vmx
ovftool path/to/appliance.vmx path/to/appliance.ovf

Thanks!

Revision history for this message
sgottesman (sgottesman) wrote : RE: [Bug 492608] Re: OVf error on line 9

Ok,

Tried the line change: no dice
Tried the convert to ovf: no dice
Tried the convert to vmx: through an error on line 9

Thanks

Scott G

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of
Liraz
Sent: Saturday, December 05, 2009 11:47 AM
To: Scott Gottesman
Subject: [Bug 492608] Re: OVf error on line 9

Thanks for reporting this. I'd like you to try a couple of things to
help us find a solution for this.

1) try editing the OVF file, and changing the format from:

http://www.vmware.com/interfaces/specifications/vmdk.html#sparse

To:

http://www.vmware.com/specifications/vmdk.html#sparse

If that works great. If it doesn't, we may have to find a workaround
such as using ovftool to convert the OVF to a different VMDK format.
Instead of the sparse format ESX seems to like the streamOptimized
format the best. OVFtool can convert a VMDK to streamOptimized.

2) using ovftool to convert the OVF file:

ovftool path/to/appliance.ovf path/to/appliance2.ovf

If that doesn't work try converting to vmx and back:

ovftool path/to/appliance.ovf path/to/appliance.vmx
ovftool path/to/appliance.vmx path/to/appliance.ovf

Thanks!

--
OVf error on line 9
https://bugs.launchpad.net/bugs/492608
You received this bug notification because you are a direct subscriber
of the bug.

Status in TurnKey Linux: New

Bug description:
during import of the ovf file for wordpress you receive an error

line9: unsupported value
'http://www.vmware.com/interfaces/specications/vmdk.html#sparse' for
attribute 'formate' on element 'disk'.

I am running vcenter 4 sp 1
esx 4.0

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/turnkeylinux/+bug/492608/+subscribe

Revision history for this message
Liraz (liraz-siri) wrote :

OK, I hear vSphere changed a few things. According to the community feedback we're receiving you can use the existing OVF but you'll need to convert it first with OVF tools:

http://www.turnkeylinux.org/forum/support/20090929/vmware-tools#comment-1292

Revision history for this message
2000adm (2000adm) wrote :

I am running VmWare ESXi-4.0.
I have the same bug during importing of the ovf file for DokuWiki and TWiki Appliances.
Appliances have been downloaded from you site today.

Revision history for this message
2000adm (2000adm) wrote :

Solution:

 I've removed OVF file and created new using: ovftool path/to/appliance.vmx path/to/appliance.ovf

Results of: ovftool --schemaValidate path/to/appliance.ovf

For old OVF file:
Deployment Sizes:
  Flat disks: 20.00 GB
  Sparse disks: Unknown

For new OVF file:
Deployment Sizes:
  Flat disks: 20.00 GB
  Sparse disks: 411.50 MB

New OVF file have been imported without error on line 9.

Changed in turnkeylinux:
status: New → Confirmed
status: Confirmed → New
Revision history for this message
Jeremy Davis (jedmeister) wrote :

I think this bug is now resolved? Can anyone confirm that it's no longer a problem?

Changed in turnkeylinux:
importance: Undecided → Medium
Revision history for this message
Jeremy Davis (jedmeister) wrote :

Please reopen if anyone encounters this...

Changed in turnkeylinux:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.