ovftool coredumped

[luger_lee]

I use ovftool to deploy an appliance to a host (esx 3.5i). after disk copy done, I got an error message and the tool core dumped.

What does the message means ?

Thanks in advance.

Opening OVF source: /home/luger_lee/tmpout/VMware-VIPerl-Toolkit-1.6.0-104313-Appliance/VMware-RCLI-3.5-U2-Appliance.ovf

Warning: No manifest file

Opening VI target: vi://root@alaska/

Target: vi://alaska/

Disk progress: 1%

...

Disk progress: 99%

Disk Transfer Failed

Error: Unable to get NFC ticket for target disk

Error: Failed to clean up after failure. Reason: vim.fault.NotAuthenticated

terminate called after throwing an instance of 'Vim::Fault::NotAuthenticated::Exception'

what(): vim.fault.NotAuthenticated

Terminate process signal received - aborting operation/usr/bin/ovftool: line 23: 32361 Aborted (core dumped) $OVFTOOL_BIN "$@"

[admin]

would it be possible for you to post some logs here or PM them to me?

eske

[luger_lee]

Hi. eske

No log I can find out .

I think it's an authentication problem for SOAP to ESXi 3.5 Web service, but I'm not sure.

Here the back trace attached.

(gdb) bt

#0 0x0000003f4fe30155 in raise () from /lib64/libc.so.6

#1 0x0000003f4fe31d98 in abort () from /lib64/libc.so.6

#2 0x00002b7f24a96fe4 in __gnu_cxx::__verbose_terminate_handler () from /opt/vmware/ovftool/libstdc++.so.6

#3 0x00002b7f24a95166 in std::set_unexpected () from /opt/vmware/ovftool/libstdc++.so.6

#4 0x00002b7f24a95193 in std::terminate () from /opt/vmware/ovftool/libstdc++.so.6

#5 0x00002b7f24a9527a in __cxa_throw () from /opt/vmware/ovftool/libstdc++.so.6

#6 0x00002b7f21519649 in Vim::Fault::NotAuthenticated::Throw () from /opt/vmware/ovftool/libtypes.so

#7 0x00002b7f23131f8a in Vmomi::SoapStubAdapterImpl::InvokeCommon () from /opt/vmware/ovftool/libvmomi.so.1.0

#8 0x00002b7f231327a3 in Vmomi::SoapStubAdapterImpl::Invoke_Task () from /opt/vmware/ovftool/libvmomi.so.1.0

#9 0x00002b7f2315b754 in Vmomi::StubImpl::_Invoke_Task () from /opt/vmware/ovftool/libvmomi.so.1.0

#10 0x00002b7f2130de00 in Vim::SessionManagerStub::Logout () from /opt/vmware/ovftool/libtypes.so

#11 0x00000000004c36a6 in Vmacore::NarrowToType<Vim::Vm::ConfigOption> ()

#12 0x00000000004c68cd in Vmacore::NarrowToType<Vim::Vm::ConfigOption> ()

#13 0x00000000004cf582 in Vmacore::NarrowToType<Vmomi::MoRef> ()

#14 0x00000000004edf11 in Vmacore::NarrowToType<Vim::Vm::Device::VirtualController> ()

#15 0x00000000004647a2 in Vmomi::DynamicData::~DynamicData ()

#16 0x0000003f4fe1d8b4 in __libc_start_main () from /lib64/libc.so.6

#17 0x0000000000463cca in Vmomi::DynamicData::~DynamicData ()

#18 0x00007fff8b57e668 in ?? ()

#19 0x0000000000000000 in ?? ()

Best Regards.

[admin]

will with be possible for you to run the same again with these options to ovftool

ovftool --X:logToConsole=true --X:logLevel="verbose" SAME_AS_BEFORE and pipe the log to a file and PM me the log file so I can take a look at it.

eske

[Khal]

I'm getting the same thing using ovftool on the command line. This happened even with the VM in question being powered off.

 [root@thardus ovftool]# /opt/vmware/ovftool/ovftool /nfsroot/VM/auth/Virtual\ Machine.vmx /nfsroot/OVF/auth.ova
Opening VMX source: /nfsroot/VM/auth/Virtual Machine.vmx
Opening OVA target: /nfsroot/OVF/auth.ova
Target: /nfsroot/OVF/auth.ova
Disk progress: 99%
Terminate process signal received - aborting operation
Terminate process signal received - aborting operation/opt/vmware/ovftool/ovftool: line 23:  2050 Aborted                 $OVFTOOL_BIN "$@"
[root@thardus ovftool]# 

I tried both the i386 and x86_64 versions of ovftool. I've done about 10 VMs successfully prior to this. Ovftool versions:

VMware-ovftool-installer-1.0.0-166674-lin.i386.sh

VMware-ovftool-installer-1.0.0-166674-lin.x86_64.sh

[Khal]

I ran the ovftool with verbose logging piped to a file and it looks like some assert failed:

 Exception: Assert Failed: "s.length() < len" @ /build/mts/release/bora-166674/bora/vim/apps/ovfTool/tar.cpp:250
Type: N7Vmacore9ThrowableE
Backtrace:
[00] eip 0x31746db
[01] eip 0x3061e2b
[02] eip 0x3011845
[03] eip 0x30118e9
[04] eip 0x30123bb
[05] eip 0x510ff3
[06] eip 0x511575
[07] eip 0x511f71
[08] eip 0x501c93
[09] eip 0x5078ae
[10] eip 0x4aabb8
[11] eip 0x4ab20e
[12] eip 0x464ec6
[13] eip 0xb8e1d974
[14] eip 0x463cca


Terminate process signal received - aborting operation[2009-11-04 16:17:51.804 2B3B047209A0 error 'ovftool'] Backtrace:
[00] eip 0x31746db
[01] eip 0x3061e2b
[02] eip 0x3174d73
[03] eip 0x300eb1f
[04] eip 0x30118f1
[05] eip 0x30123bb
[06] eip 0x510ff3
[07] eip 0x511575
[08] eip 0x511f71
[09] eip 0x501c93
[10] eip 0x5078ae
[11] eip 0x4aabb8
[12] eip 0x4ab20e
[13] eip 0x464ec6
[14] eip 0xb8e1d974
[15] eip 0x463cca


Terminate process signal received - aborting operation

Command was:

[root@thardus ~]# /opt/vmware/ovftool/ovftool --X:logToConsole=true --X:logLevel="verbose" /nfsroot/VM/auth/Virtual\ Machine.vmx /nfsroot/OVF/auth.ova > ovftool.log

[admin]

Hi Khal,

How big is the VMX you are trying to convert? There is a known limitation in OVF Tool 1.0 which means that none of the files in an OVA can be bigger than 8 GB (actually bigger than 8^11 -1 bytes). This is fixed in the next version of OVF Tool.

- Kristian

[Khal]

The source VMDK is about 36 gb. If I run the same command with ".ovf" instead of ".ova" as the target file, it completes (resulting in 2 small files and a 9.6 GB VMDK).

[admin]

The 9.6 GB VMDK file is the problem. You can create an OVA manually that contain your VM. The way you do it is to create an OVF with chunked file references and then use tar to create an OVA. Here is how to do it:

ovftool --chunkSize=7gb 8 GB).

Please note, that you will only be able to use OVF Tool to deploy this package, since the VI client 4.0 does not support chunking in OVA files. It will in the next version.

- Kristian

[Khal]

Great info, thank you. Do you have any idea when the updated ovftool will be available?

[admin]

I have no idea.

• Kristian