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

ovftool installation for Alpine (musl libc instead of glibc)

February 10, 2020, 5:57 pm
$
0
0

Hi,

We are moving from ubuntu to Alpine for our container image and encountered the following error for ovftool installation in an Alpine container. It works fine in an ubuntu container. Please note that Alpine uses musl libc instead of glibc. We also tried installing the glibc using “apk --no-cache --allow-untrusted -X https://apkproxy.herokuapp.com/sgerrand/alpine-pkg-glibc add glibc glibc-bin”, but it did not help.

The https://stackoverflow.com/questions/37818831/is-there-a-best-practice-on-setting-up-glibc-on-docker-alpine-linux-base-image suggests “Instead of installing glibc on Alpine, build and/or package your dependent software packages and libraries for Alpine.”.

Any help or workaround to install the ovftool on Alpine would be greatly appreciated.

bash-5.0# ./VMware-ovftool-4.3.0-7948156-lin.x86_64.bundle

Extracting VMware Installer...done.

musl libc (x86_64)

Version 1.1.24

Dynamic Program Loader

Usage: /lib/ld-musl-x86_64.so.1 [options] [--] pathname

Warning: VMware Installer could not determine this system's glibc version.

User interface initialization failed.  Exiting.  Check the log for details.

bash-5.0#

The log file referred in the above output is attached.

Regards,

Pramod

↧
Search

Powercli Export a specific disk of a VM

March 3, 2020, 8:13 am
$
0
0
Good morning to all, I’ve been trying to find a few posts around, but I haven’t found anything on the subject. I would need to create a script to export a specific disk of a virtual machine. I thought about exporting it as OVF for file compression. Can you help me? thanks
↧
↧

ovftool install fails due to libpython3.7m.so.1.0 missing

April 5, 2020, 8:33 pm
$
0
0

The install of ovftool from VMware-ovftool-4.4.0-15722219-lin.x86_64.bundle on Ubuntu 18.04 LTS fails. Please advise how to proceed.

root@ubuntu-qcore:/tmp# cat /etc/os-release

NAME="Ubuntu"

VERSION="18.04.4 LTS (Bionic Beaver)"

ID=ubuntu

ID_LIKE=debian

PRETTY_NAME="Ubuntu 18.04.4 LTS"

VERSION_ID="18.04"

HOME_URL="https://www.ubuntu.com/"

SUPPORT_URL="https://help.ubuntu.com/"

BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"

PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"

VERSION_CODENAME=bionic

UBUNTU_CODENAME=bionic

root@ubuntu-qcore:/tmp# ls -la VMware-ovftool-4.4.0-15722219-lin.x86_64.bundle

-rw-r--r-- 1 user group 40439098 Apr  2 09:22 VMware-ovftool-4.4.0-15722219-lin.x86_64.bundle

root@ubuntu-qcore:/tmp# sh VMware-ovftool-4.4.0-15722219-lin.x86_64.bundle

Extracting VMware Installer...done.

/usr/lib/vmware-installer/3.0.0/vmis-launcher: error while loading shared libraries: libpython3.7m.so.1.0: cannot open shared object file: No such file or directory

root@ubuntu-qcore:/tmp# /usr/bin/ovftool --version

VMware ovftool 4.3.0 (build-13981069)

root@ubuntu-qcore:/tmp#

 

 

The "missing" library file is present on the system from the previous install of ovftool:

 

root@ubuntu-qcore:/tmp# find / -name libpython3.7m.so.1.0 -ls

  1320180   3096 -rw-r--r--   1 root     root      3167376 Dec 20 15:24 /usr/lib/vmware-installer/3.0.0/python/libpython3.7m.so.1.0

root@ubuntu-qcore:/tmp#

↧

Error: 32 occurring when converting .vmx to .ova file

April 6, 2020, 5:28 pm
$
0
0

I am converting a .vmx for to a .ova file using the ovftool. I have used the ovftool to do this operation in the past,  and would occasionally see the error:

Error: 32
Completed with errors

Whenever this error occurs, the conversion operation fails, and the resultant .ova file is created as an empty file. (Size=0)
I am now seeing this error more consistently and need to determine why it is occurring. 

I am using version 4.3.0 build 12320924.

Any ideas or suggestions on how to avoid this error, or what it means would be very helpful. 

Thanks!

Bill

↧

ovftool install fails on CentOS 8 due to libpython3.8.so.1.0 missing

April 17, 2020, 2:37 pm
$
0
0

Hi all - as this is supported on RHEL, I am using a CentOS 8 machine and am unable to install this new version.  I had v4.3 installed without issues but v4.4 is failing due to libpython3.8.so.1.0 and I cannot figure out how to resolve this.  Can someone advise what packages need to be installed to resolve the dependency?

I've attached a screenshot of the error as well.  Thanks in advance!

↧
↧

automate vapp property creation with api or ovftool?

July 6, 2020, 3:56 am
$
0
0

hi..

i'm creating a vm via packer automation,  i was wondering if there's after creation to use ovftool or even a direct api call to vcenter to add vapps properties

 

i'm talking about version, vendor, vapp ip (static vs dhcp etc..)

↧

How to install OVFTOOL on ESXi 6.7

July 7, 2020, 12:10 pm
$
0
0

I have downloaded and place the Linux file VMware-ovftool-4.4.0-15722219-lin.x86_64.bundle on ESXi but cannot install.

 

I want to run the OVF tool on the ESXi server onto a datastore. It's a 1-2 TB file to package up.

 

The OVFtool on any external machine just cannot do this process.

 

Can someone help?

↧

ovftool deploy to a cluster fails with seg fault

July 15, 2020, 7:41 pm
$
0
0

Using the latest ovftool 4.4.0 (build-15722219) on Linux, having a hard time deploying to a cluster of hosts in vCenter.  What is the current syntax?

$ ovftool win2k16.ova vi://administrator@vsphere.local@my-vc.lab.xyz.com/datacenter-name/host/cluster-name

Opening OVA source: win2k16.ova

The manifest validates

Enter login information for target vi://my-vc.lab.xyz.com/

Username: administrator%40vsphere.local

Password: *****************

Opening VI target: vi://administrator%40vsphere.local@my-vc.lab.xyz.com:443/datacenter-name/host/cluster-name

Segmentation fault

 

↧
Search

OVFTool Import Multiple VMs into vApp or Template

July 20, 2020, 4:54 am
$
0
0

Hi There,

 

Please can someone advise if it is possible, I would like to import multiple VMs into the same vApp or Template in vCloud.

 

When testing i get this error...

 

Opening vCloud target: vcloud://export@derenvvcd.mgsops.net:443/cloud
Error: vApp name already found in the catalog. Either overwrite it or choose a different name.
Completed with errors

Thanks in advanced,

↧
↧

ovf template for including different license agreement text not working as expected

July 23, 2020, 12:09 am
$
0
0

Hi,

 

I am working on one migration where I expected to generate custom ovf template for my product.

I used the earlier version ovf template and it was working in those version perfectly

 

In new ovf template wherever I generated by my own, <Info> tag under Eula section should take content dynamically based on the language selection

 

My ovf template looks like this

 

<EulaSection>

      <Info ovf:msgid="license-info">LicenseAgreement1</Info>

      <License ovf:msgid="license-text">License Agreement1

some content

</License>

</EulaSection>

 

<EulaSection>

      <Info/>

      <License>License Agreement2

some content

</License>

</EulaSection>

 

<Strings xml:lang="ko-KR">

<Msg ovf:msgid="license-info">Korean string for LicenseAgreement1</Msg>

<Msg ovf:msgid="license-text">Korean language License Agreement1</Msg>

</Strings>

 

Note: License Agreement2 looks same for all languages so no message under Strings tag

ovf:msgid="license-text" working fine when switching language

ovf:msgid="license-info" is not working and it is showing default Agreement 1 value

 

Can anyone help me to fix this?

 

Regards,

Gobi S.

↧

ovftool 4.4: Importing OVF template into vCenter 6.7 fails with error "OVF package not supported by target - Unsupported element 'VirtualSystemCollection'"

August 4, 2020, 5:26 am
$
0
0
According to Release Notes of 4.4, the importing of OVF template into vCenter is supported.

" Release 4.4 supports importing OVF into vCenter Server as a template, rather than as a VM. Template import on ESXi is not supported, nor vApp import as template."

 

My goal is to import the OVF as template and do the actual deployment separately, at later stage.

The below error occurs when trying to import in vCenter 6.7, could you please indicate what I'm doing wrong?

Thank you.

 

c:\CAMMS>ovftool --X:logFile=c:\temp\ovftool.log --X:logLevel=verbose --lax --allowExtraConfig --allowAllExtraConfig --exportFlags=extraconfig --vCloudTemplate=truefile://c:\CAMMS\vbgf_man_ip.ovf* *'vi://nrjmisf:nrjmisf@10.44.46.157:443/DC-LAB/vm/vbgf-nrjmisf'

 __ 

Opening OVF source: c:\CAMMS\vbgf_man_ip.ovf

Warning:

- Line -1: Unsupported value 'sched.mem.pin' for attribute 'key' on element 'ExtraConfig'.

- Line -1: Unsupported value 'sched.mem.pin' for attribute 'key' on element 'ExtraConfig'.

- Line -1: Unsupported value 'sched.mem.pin' for attribute 'key' on element 'ExtraConfig'.

Opening VMX target: 'vi://nrjmisf:nrjmisf@10.44.46.157:443/DC-LAB/vm/vbgf-nrjmisf'

Warning:

- Target does not support CPU validation.

- Hardware compatibility check is disabled.

Error: OVF Package is not supported by target:

- Line 41: Unsupported element 'VirtualSystemCollection'

Warning:

- No manifest file found.

Completed with errors

↧

Can't install in Debian 11

September 10, 2020, 12:13 pm
$
0
0

Hello,

I'm trying to install OVF Tool in Debian 11 without luck...

sudo ./VMware-ovftool-4.4.0-16360108-lin.x86_64.bundle
Extracting VMware Installer...done.
Traceback (most recent call last):
  File "/tmp/tmp9tarrq21.vmis.env", line 132, in <module>
    exec(fileObj.read(), mod.__dict__)
  File "<string>", line 243
    except OSError, e:
                  ^
SyntaxError: invalid syntax


[######################################################################] 100%
Installation was unsuccessful.

 

Yesterday I installed without problem VMWare Remote console.

 

How can I solve my problem?

Thanks

↧

Deploy vof template to vSphere

October 11, 2020, 6:46 pm
$
0
0

I want to deploy some vof template to vSphere, but I don't want to deploy them by manually next step and next step.

 

Can I deploy them use PowerCLI or other ways?

 

What should I do?

↧
↧

MACOS OVF tool

October 23, 2020, 2:20 am
$
0
0

# aditya @ Adityas-MacBook-Pro in /Applications/VMware OVF Tool [14:45:05] C:1

$ ./ovftool /Users/aditya/VirtualBox\ VMs/Windows\ 2000/Windows\ 2000\ Professional.vmx /Users/aditya/VirtualBox\ VMs/win2000.ovf

Opening VMX source: /Users/aditya/VirtualBox VMs/Windows 2000/Windows 2000 Professional.vmx

Error: File (/Users/aditya/Downloads/cd2 converted.iso) could not be found.

Completed with errors

(base)

 

I get this error when I try to run the ovf tool, I know the installation ran fine and did not need cd2 converted iso    

↧

Unable to parse xml element 'Envelope'

August 17, 2009, 12:14 pm
$
0
0

 

I used ovftool (1.0 running in a RHEL 5.2 VM) to create an ovf of a powered off RHEL 5.1 VM.  All was successful and I can probe the OVF without issue.  However, when I try to import it as a virtual appliance using Virtual Center 2.5 Update 5 I receive:

 

 

An error occurred while parsing the OVF descriptor:  Unable to parse xml element 'Envelope'

 

I've attached the ovf file.

 

Any ideas?

 

 

↧
Search

ovftool -- mapping multiple nics with same network name to different network names

December 1, 2010, 8:32 am
$
0
0

Is there a way to map network devices that are both associated with "VM Network" in the ova to different networks on the target?  The ova contains only "VM Network", but I would like to put one interface on "NET_A" and one on "NET_B".

↧

Serious problem in ovftool VMDK input

March 9, 2013, 10:23 am
$
0
0

All,

 

First of all, apologies if this is an inappropriate forum. I do not have a support contact for this issue. We are VMware customers, however our licenses are purchased through an academic reseller. Our concern is that this bug has crept into recent releases and perhaps gone unnoticed in QA. It's serious enough for us to consider moving to other hypervisor products.

 

I believe there may be a serious bug in OVFtool's disk read code. We observe that VMs are created OK after upload or import, but disk contents are zero-filled. No error conditions are reported at any time. It is only clear that the bug has been exercised, when an uploaded or imported VM fails to boot.

 

We have several research VMs with multiple LANs, which run FreeBSD 8.2 in VMware Fusion 5.0.2, MacOS X 10.8.2 Mountain Lion. I was also able to reproduce the bug with a fresh installation of vSphere ESXi 5.1 and ovftool 3.0.1. V

 

Using the separately packaged ovftool, I can export the VMs inside Fusion, by giving fully qualified paths to their VMX files. The bug appears to be in VMDK read. I exercised it in two use cases, Fusion OVA import and ESXi OVA upload, as follows:

 

  1. If I import an affected OVA into Fusion from the GUI, Fusion will invoke its own copy of ovftool 3.0.1 to perform the import. VMs are created with a sane VMX file. VMDKs are created. However their contents are zero-filled, and the VMDK contents in the OVA have been ignored.
  2. If I upload an affected OVA to ESXi, using ovftool and a vi:// target URL on the command line, the same bug is observed with ESXi. Again, the VMX is sane - we inspected this by SSHing into ESXi and manually reviewing the VMX on the VMFS data store with vi. The VMDK contents are zeroed on the VMFS datastore, and the VMDK contents in the OVA have been ignored.

 

ovftool seems, in some cases, to ignore the contents of the packaged VMDK files in OVAs, and those associated with VMX files from VMware products.

 

To date I have only been able to reproduce the issue with FreeBSD guests. The bug does not appear in all exported OVAs, however affected VM and OVA combinations will consistently demonstrate it.

 

  • We first noticed this problem in October 2012, and have not been in a position to exercise it thoroughly until now.

 

  • I can make an OVA available which demonstrates the issue. Please contact me privately to arrange. The files are typically 2GB in size.

 

 

Other observations:

 

 

  • There is no problem with OVA generation. I have inspected the OVAs manually using tar, extracted the embedded VMDKs inside, converted them back to 2GB sparse format using vmware-vdiskmanager (or vmkfstools under ESXi), and loaded them into ESXi and Fusion respectively.

 

  • Since ovftool was introduced, VMDKs must be uploaded manually using SFTP to avoid triggering the bug. The functionality in the vmware-vdiskmanager command which allows direct upload to ESXi servers has been removed.

 

  • Casual inspection with DTrace under OS X reveals that ovftool seems to be reading the full OVA file contents. We initially thought there may been a problem with VMDK upload, however other guests have not been affected.

 

  • The serialized format VMDK contents in the OVA are consistent with the original VMDKs. We verified this in one case with MD5 checksums. This requires denying all writes during the test.
  • We also reproduced this bug with out-of-box, unmodified FreeBSD installations, as our research VMs use ZFS in GPT partition containers.

 

  • We also noticed that Fusion's private copy of ovftool will break if ESXi specific options are specified in $HOME/.ovftool - although this is a separate issue from the main bug.
  • No source code is supplied for ovftool, so users are not able to fix this issue themselves.

 

Workarounds:

 

  • We load the OVA into Oracle VirtualBox, and re-export the OVA from there.
  • This is undesirable for many reasons, the main one being that it loses all the network binding information, which is critical to our work.

 

 

thanks,

Bruce

↧
↧

Import OVA Template errors with "Could not convert field 'spec' of structure 'com.vmware.vcenter.vdcs.floppy_model'

November 17, 2017, 2:38 pm
$
0
0

Hopefully this is the right place to ask this.

 

We have a product that's distributed as an OVA and have done so for years. We're finally getting around to supporting vSphere 6.5 but are running into an issue. If we deploy the OVA directly to a 6.5 host, the import works fine. However if we deploy via vCenter, it fails with the following error:

 

Failed to deploy OVF package.

Cause:

A general system error occurred:

An error occurred: Could not convert field 'spec' of structure 'com.vmware.vcenter.vdcs.floppy_model'

 

This only happens on vSphere 6.5. It works fine with vSphere 6.0 and earlier. When we create the template, we do have a floppy device (it's needed as we do our OS install during the build process) so I changed it so right before it creates the OVA using ovftool 4.1, I edit the vmx (while the vm is powered off) and remove all references to the floppy device. However the corresponding ovf file still has references to the floppy.

 

Any ideas what's going on and how to fix? I'm not sure why all of a sudden it stopped working in 6.5. From our end, the build process hasn't changes in years. I can attach the vmx and ovf files if that helps. Thanks!

↧

OVF tool for Windows 64 bit OS VMs

March 13, 2010, 12:45 pm
$
0
0

 

Hi All,

 

 

Do we have an ovf tool

for Windows 64bit OS virtual machines? The ovf tool guide mentions tools

for Windows 32 bit OS and Linux 32 & 64 bit OS but not for Windows

64 bit OS virtual machines.

 

Pleas help.

 

Regards,

Andy

ankit_17@hotmail.com

 

 

↧
Viewing all 34499 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>