Quantcast
Channel: VMware Communities : Popular Discussions - Open Virtualization Format Tool
Viewing all 34499 articles
Browse latest View live

Issue with ovftool "Error: Failed to open file: .\" when try to export to ovf

$
0
0

Hello

 

I have created a VM in VMware Workstation 15 Player and I am experiencing an issue when trying to export using ovftool.exe.

 

I am running Workstation on a Windows 10 laptop.

 

OS: Windows 10

The host is a Serveur 2012R2

I am using VMware® Workstation 15 Player 15.0.2

 

After having installed ovftool on the laptop, I launched this command from a command prompt (Run as) and get the error message.

 

C:\Program Files\VMware\VMware OVF Tool>ovftool.exe "C:\Users\loulou\Documents\Virtual Machines\Windows Server 2012C\Windows Server 2012.vmx" "D:\Windows Server 2012.ovf"

Error: Failed to open file: C:\Users\loulou\Documents\Virtual Machines\Windows Server 2012C\Windows Server 2012.vmx

Completed with errors

 

I saw this post: https://communities.vmware.com/thread/602858

 

I changed the "sata0:1.deviceType" from "cdrom-image" to "atapi-cdrom" but the command still returns the same error message.

 

Is the command OK?

 

Do I have to run the tool from somewhere else ?

 

In advance, I thank you for your help.

 

Dany


MAC ovftool not working

$
0
0

When I try to fun ovftool from the terminal I get the error message

 

'ovftool: command not found'

 

i.e. m'ovftool Photo_[Work]/VirtualBoxMachines/copyxp\ Base\ V.vmx Photo_[Work]/VBConversions/xpvb.ovf'

 

???

 

Thanks.

 

Pedro

Error exploit ova to vmx

$
0
0

hi,

i'm very newbie on terminal and i get this error when i tried to convert ova file to vmx. It says completed with errors but I can't locate any file, anywhere, and also the whole process is to fast for OVF Tolls to do anything.

What am i missing? Thanks

Miguel

MCR:~ mcr$ /Applications/VMware\ OVF\ Tool/ovftool --lax /Users/mcr/Downloads/untitled\ folder/Ubuntu\ FEUP/Ubuntu\ FEUP.ova exploit.vmx

Opening OVA source: /Users/mcr/Downloads/untitled folder/Ubuntu FEUP/Ubuntu FEUP.ova

Opening VMX target: exploit.vmx

Error: OVF Package is not supported by target:

 - Line 92: Unsupported element 'StorageItem'

 - Line 101: Unsupported element 'StorageItem'

 - Line 110: Unsupported element 'EthernetPortItem'

Completed with errors

What is the EULA character limit?

$
0
0

 

I'm using the OVF 1.0 tool to create a package for deployment to customers.  Included in my command is the --eula@=eulatext.txt  parameter.  When I use this parameter, the tool spends the requisite hour or two to extract and compress the virtual disk drive, but it doesn't create an OVF or MF file.  Without the --eula@= parameter, the OVF and MF files are created as expected.

 

 

Through trial and error, I've determined that the OVF 1.0 tool imposes a character limit in the contents of the text file I'm using.  When I cut about half of the EULA text, use of the --eula@= parameter works as expected.  (An error message from the tool would have saved me quite a bit of time determining this.  Checking this before the virtual disks are processed would also have saved hours.)

 

 

This is a legal concern.  I need to provide documentation of the character limit to my organization as justification for truncating our EULA.  Does anyone know where VMware or DMTF document this character limit?  I've been unable to locate it.

 

 

In search of vmware specific OVF schema (http://www.vmware.com/schema/ovf)

$
0
0

 

Hi,

 

 

I have been trying to work with OVF. I need to be able to read/write in OVF files using xml tools.

 

 

I have exported VM as OVF using the VI CLient and also programmatically. Each time I get and OVF file with the following namespace reference:

 

 

http://www.vmware.com/schema/ovf

 

 

I can't find this schema at the respective URL.

 

 

Does anyone know where I can find this .xsd?

 

 

Thanks in advance,

 

 

Derek

 

 

Properties lost when deployed a VM and exported it to OVF

$
0
0

Hi,

 

I have built a VM, using VMware Studio in OVA format. I defined some custom OVF environment properties in it.

After I built the VM, I opened the .OVF file to see the property values are appeared correctly. They look like the below

 

<ProductSection ovf:required="false">
      <Info>VM ISV branding information</Info>
      <Product>xxxxxxxxx</Product>
      <Vendor> xxxxxxxxx , Inc.</Vendor>
      <Version>x.x.x.x</Version>
      <FullVersion>x.x.x.x alpha</FullVersion>

</ProductSection>

 

I deployed this OVF to a ESXi 4.0 server. Later exported the same VM to OVF format using OVFTool, using the command line

 

ovftool.exe vi://root:xxxxxxxxxxx@IP/vmname  "d:\Virtual Machines\imported-OVF\newVM.ovf"

 

After the export, I opened the newVM.OVF file and found that the properties (like product, vendor, version etc.) are not retained.

 

What could be the issue. Please suggest.

 

--Hemanth

ovftool sanfs://..../linux.iso was not found

$
0
0

Hi,

 

I'm trying to convert VM into ovf. But ovftool fails with the message:

 

./ovftool --powerOffSource vi://administrator:xxxxx@host/?ip=192.168.1.22 myovf.ovf
Opening VI source: vi://administrator@host/
Powering off VM: 0593498732-VM_Name
Error: File sanfs://vmfs_uuid:3c3693e8-f77a642a-1910-5c6bdcb26d3a/packages/4.1.0/vmtools/linux.iso was not found

 

Could you please help me with the issue above?

 

Thanks,

Create OVF/OVA via ovftool

$
0
0

Hi,

 

I have a ESXi 5.0 server running which has a Guest VM running CentOS 5.6.

 

The ESXi server is a standalone server, not included in a datacenter, not managed by vCenter.

 

The server has a HDD of 80G which has both the ESXi host & the Guest OS running on top of it.

 

I installed ovftools on my Windows laptop & tried to create a ovf from the VM but am unsuccessful. I constantly get the following error -

c:\>ovftool vi://root:<rootpassword>@<ESXi Host IP>/datastore1/CentOS c:\testVM.ovf

Error: Cannot parse locater: vi://root:<rootpassword>@<ESXi Host IP>/datastore1/CentOS

Completed with errors

 

The local datastore name is "datastore1"

 

Can someone help me out here with forming the correct the ovftool command to create an ovf & possibly an OVA out of the running VM?

 

 

Thanks

 

Bhushan Pathak


ovftool: unable to upload ovf

$
0
0

Hi,

 

I am trying to upload ovf file to vcloud. But I am getting following error:

 

D:\apps\ovftool>ovftool --acceptAllEulas --diskMode=thin --noSSLVerify

--overwrite --X:connectionReconnectCount=3 --X:forceDnsName --X:disableHostname

Resolve --X:logFile=upload.log --X:logLevel=trivia "D:\VM\VM.ovf" "vcloud://admin:admin123@XYZ.com?org=ORG&vappTemplate

=Test&catalog=CAT"

Opening VMX source: D:\VM\VM.ovf

Opening vCloud target: vcloud://admin@XYZ.com:443/

Deploying to vCloud vApp template: vcloud://admin@XYZ.com:443/

Transfer Failed

Error: Failed to send http data

Completed with errors

 

In log file I can see following log:

 

-->

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: SSL: certificate subject name 'XYZ.com' does not match target host name 'XYZ1.com'

-->

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: => Sending data of size 5

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: header data hidden

2016-01-22T15:40:23.269+05:30 trivia -[04660] [Originator@6876 sub=Default] CURL: Connection #34 to host XYZ1.com left intact

-->

2016-01-22T15:40:23.269+05:30 verbose -[04044] [Originator@6876 sub=Default] vCloud response code: 204

2016-01-22T15:40:23.269+05:30 verbose -[04044] [Originator@6876 sub=Default] vCloud response body:

-->

2016-01-22T15:40:23.269+05:30 verbose -[04044] [Originator@6876 sub=Default] Curl session torn down

 

 

Any help is appreciated.

"Error: Could not lookup host: root" when using passwords with non-alphanumeric characters

$
0
0

I run

 

ovftool vi://root:cFnD_MNi#ba@10.20.30.40

 

and i get

 

Error: Could not lookup host: root

 

However, if i run

 

ovftool vi://anotheruser:abc123@10.20.30.40

 

It does work.

 

So apparently ovftool can't handle special characters in the password. Any way to get around this without changing the root password?

 

Version: OVFTool 4.0.0. for 64 bit windows 7

[BUG] ovftool produces invalid manifest file (.mf)

$
0
0

According to the ovf specification [1] section 5.1:

"The manifest file shall contain SHA digests for all distinct files referenced in the References element of the OVF descriptor and for no other files."

The problem is that ovftool includes SHA digest for the ovf file itself which is of course not referenced in the References element within itself. I think ovftool should behave according to the specification and remove calculation of this digest.

[1] https://www.dmtf.org/sites/default/files/standards/documents/DSP0243_2.1.1.pdf

Converting OVA file to VMX

$
0
0

I downloaded the latest OVF converter tool but it looks like as per documentation, it cannot convert OVA to VMX?

If yes, how?  If no, how do I?  Thanks

Converting OVF file using ovftool from VirtualBox produces error "Line 39: Unsupported element 'Caption'" and many more errors

$
0
0

Hi,

 

I would like to convert VirtualBox 3.2.4 virtual machine to VMWare ESX 4.0.

 

In VirtualBox I have exported appliance to 0.9 format and then follow the following tutorial: http://www.ctrip.ufl.edu/howto-convert-virtualbox-to-vmware

 

 

 

 

 

 

When executing command "ovftool my.ovf my.vmx" I got the following error:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Opening OVF source: e:\VMW\my.ovf

Warning: No manifest file

Opening VMX target: e:\VMW\my.vmx

Error:

 

 

 

 

 

  • Line 39: Unsupported element 'Caption'

  • Line 40: Unsupported element 'Description'

  • Line 41: Unsupported element 'InstanceId'

  • Line 42: Unsupported element 'ResourceType'

  • Line 43: Unsupported element 'VirtualQuantity'

  • Line 37: Missing child element 'InstanceID'.

  • Line 37: Missing child element 'ResourceType'.

  • Line 48: Unsupported element 'Caption'

  • Line 49: Unsupported element 'Description'

  • Line 50: Unsupported element 'InstanceId'

  • Line 51: Unsupported element 'ResourceSubType'

  • Line 52: Unsupported element 'ResourceType'

  • Line 45: Missing child element 'InstanceID'.

  • Line 45: Missing child element 'ResourceType'.

  • Line 57: Unsupported element 'Caption'

  • Line 58: Unsupported element 'Description'

  • Line 59: Unsupported element 'InstanceId'

  • Line 60: Unsupported element 'ResourceSubType'

  • Line 61: Unsupported element 'ResourceType'

  • Line 54: Missing child element 'InstanceID'.

  • Line 54: Missing child element 'ResourceType'.

  • Line 65: Unsupported element 'Caption'

  • Line 66: Unsupported element 'Connection'

  • Line 67: Unsupported element 'InstanceId'

  • Line 68: Unsupported element 'ResourceSubType'

  • Line 69: Unsupported element 'ResourceType'

  • Line 63: Missing child element 'InstanceID'.

  • Line 63: Missing child element 'ResourceType'.

  • Line 74: Unsupported element 'Caption'

  • Line 75: Unsupported element 'Description'

  • Line 76: Unsupported element 'InstanceId'

  • Line 77: Unsupported element 'ResourceType'

  • Line 71: Missing child element 'InstanceID'.

  • Line 71: Missing child element 'ResourceType'.

  • Line 81: Unsupported element 'AutomaticAllocation'

  • Line 82: Unsupported element 'Caption'

  • Line 83: Unsupported element 'Description'

  • Line 84: Unsupported element 'InstanceId'

  • Line 85: Unsupported element 'ResourceSubType'

  • Line 86: Unsupported element 'ResourceType'

  • Line 79: Missing child element 'InstanceID'.

  • Line 79: Missing child element 'ResourceType'.

  • Line 90: Unsupported element 'Caption'

  • Line 91: Unsupported element 'Description'

  • Line 92: Unsupported element 'HostResource'

  • Line 93: Unsupported element 'InstanceId'

  • Line 94: Unsupported element 'Parent'

  • Line 95: Unsupported element 'ResourceType'

  • Line 88: Missing child element 'InstanceID'.

  • Line 88: Missing child element 'ResourceType'.

  • Line 99: Unsupported element 'AutomaticAllocation'

  • Line 100: Unsupported element 'Caption'

  • Line 101: Unsupported element 'Description'

  • Line 102: Unsupported element 'InstanceId'

  • Line 103: Unsupported element 'Parent'

  • Line 104: Unsupported element 'ResourceType'

  • Line 97: Missing child element 'InstanceID'.

  • Line 97: Missing child element 'ResourceType'.

 

 

Please see attached ovf file.

 

 

 

What should I do? 

 

 

 

 

 

 

Thanks

What is the ETA of ovftool 2.1.0?

$
0
0

Hi,

 

We are waiting for the --X:enableHiddenProperties option which will help to silently install and configure an OVF that we built with Studio.

When can we expext that?

 

Thank you!

What is the EULA character limit?

$
0
0

 

I'm using the OVF 1.0 tool to create a package for deployment to customers.  Included in my command is the --eula@=eulatext.txt  parameter.  When I use this parameter, the tool spends the requisite hour or two to extract and compress the virtual disk drive, but it doesn't create an OVF or MF file.  Without the --eula@= parameter, the OVF and MF files are created as expected.

 

 

Through trial and error, I've determined that the OVF 1.0 tool imposes a character limit in the contents of the text file I'm using.  When I cut about half of the EULA text, use of the --eula@= parameter works as expected.  (An error message from the tool would have saved me quite a bit of time determining this.  Checking this before the virtual disks are processed would also have saved hours.)

 

 

This is a legal concern.  I need to provide documentation of the character limit to my organization as justification for truncating our EULA.  Does anyone know where VMware or DMTF document this character limit?  I've been unable to locate it.

 

 


ERROR: Not a supported disk format(Invalid sparse VMDK header)

$
0
0

Hi All,

 

I have just come across ovftool and was giving a try to it. I am fairly new to VMware world.

I have a  .OVF which I exported using vSphere client 4.0. This .OVF comprises of 3 Suse Linux based virtual machines. i.e. I created a vApp on ESX (4.1) host, in this vApp I put my 3 SLES VMs and then exported it as OVF.

It has a total size of around 4.5GB.

 

Now I ran this command to compress this .OVF as well as gave an option to create deltadisks.

C:\> ovftool --compress=9 --makeDeltaDisks --skipManifestCheck  MyVMCluster\MyVMCluster.ovf   E:\

 

output:

{{{

The manifest does not validate
Generating delta disks for 2 disks (capacity 40960 MB)
Reading disks
Disk Transfer Completed

 

Determining optimal configuration for capacity group
Writing configuration to disk
Disk Transfer Completed

 

Completed successfully

}}}

 

Now when I checked my E:\ It had created a folder with the same name and put related files there. I saw a significant reduction in the new vmdk size. ( around 2.3GB now )

 

Now when I manually deploy this new ovf on vSphere client, it goes till certain %age and then flags an error:

{{{

Error uploading file to server ( E:\MyVMCluster\disk3.vmdk.gz ) Not a supported disk format ( Invalid sparse vmdk header )

}}}

and then it stops and everything rolledback.

 

 

Any pointers ?

 

Thanks

Nikunj

Ovftool modify network target ovf

$
0
0

Hello everyone,

 

I'm trying to get "ovftool" to modify the resulting ovf (starting from a vmx) with a few parameters like:

  • --net:'nat=VM Network'
  • --memorySize:vm1=2048
  • etc.

but none of them is working. The resulting ovf is every time exactly the same. Here below the probe of the ova file:

 

Header 1

ovftool ubuntu.ova

OVF version:   1.0

VirtualApp:    false

Name:          ubuntu

 

 

Download Size:  801.99 MB

 

 

Deployment Sizes:

  Flat disks:   16.00 GB

  Sparse disks: 1.86 GB

 

 

Networks:

  Name:        nat

  Description: The nat network

 

 

Virtual Machines:

  Name:               ubuntu

  Operating System:   ubuntu64guest

  Virtual Hardware:

    Families:         vmx-09

    Number of CPUs:   1

    Cores per socket: 1

    Memory:           512.00 MB

 

 

    Disks:

      Index:          0

      Instance ID:    6

      Capacity:       16.00 GB

      Disk Types:     SCSI-lsilogic

 

 

    NICs:

      Adapter Type:   E1000

      Connection:     nat

 

As I said the resulting ovf is always the same. I've tried with different examples from the official "ovftool" doc but nothing seems to work. I've even tried to look in the logs but no errors are displayed and no information about my argument / properties are printed.

 

Could someone please let me know if I'm doing something wrong or is "ovftool" not made for that?

 

Best regards,

 

Vincenzo

Create OVF with flat vmdk

$
0
0

Hey,

 

I'm trying to build a utility that builds an OVF, given a flat.vmdk and a .vmdk with the descriptor. But I've found that only streamOptimized disks will export properly, however they only take embedded descriptors. I'm using VSphere 4 to deploy an ovf.

 

In the ovf, I have the disk format to be ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized". This works perfectly fine until VSphere gets to reading the vmdk file where it gives the error message "Error uploading file C:\path\to\scsi0_0.vmdk to server. I/O exception while reading VMDK header", where the header is,

 

# Disk DescriptorFile
version=1
CID=fffffffe
parentCID=ffffffff
createType=streamOptimized
# Extend description
RW 16777216 FLAT "scsi0_0-flat.vmdk"
# The Disk Data Base
#DDB
ddb.virtualHWVersion = "7"
ddb.adapterType = "lsilogic"
ddb.geometry.heads = "64"
ddb.geometry.sectors = "32"
ddb.geometry.cylinders = "8192"

 

 

I guess my question is, does deploying ovfs support any other format other than streamOptimized where I can use a flat.vmdk and a .vmdk?

 

Thank you,

Kyle

ovftool VM->ova/f fails with SHA1 digest of file . . . disk.iso does not match manifest"

$
0
0

I'm trying to create an OVA file from an installed VM.  If I try creating it with ovftool 3.5, it downloads everything completely then gives me the following error:

SHA1 digest of file https://172.31.68.10:443/ha-nfc/52cca89a-6cde-c7a7-0810-25ff2197d3d6/disk-1.iso does not match manifest
and then deletes the file(s) it generated.

 

I am using compress=0 and --noImageFiles so i don't get the install iso.

 

If I manually go into Edit Settings and remove the cdrom, then 3.5 creates the ova correctly.

 

If I use ovftool 2.0, it succeeds even without manually removing the cdrom iso.

 

I've seen posts where users get the same error I do when they are going ova/f to vm and the answer is to delete the manifest.   Since all of the files are deleted after the error message, I don't have the option to delete the locally created manifest.

 

Is there a way to keep the files around even after a manifest error?

 

Does anyone know why ovftool 3.5 would fail in this case and 2.0 would word?  Has there been some deprecation between the two of them?

 

Thanks,
Mike

Problem with converting vmworkstation vm(.vmx) to ovf by ovftool

$
0
0

Ovftool in VMworkstation·7.0 used to convet .vmx to ovf

 

display error:

 

1.jpg

ovftool version  2.0

2.jpg

 

Any help with this is super appreciated!!

 

Thanks,

Viewing all 34499 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>