VMware Communities
opjs
Contributor
Contributor
Jump to solution

Error importing OVA/OVF file into Workstation Pro

I am currently running Vmware Workstation Pro 14 on Fedora 28.

Whenever I try to open an ovf/ova file it fails. The GUI does not give any indication as to why this might be, and instead silently fails. I checked the vmware-ui logs and found the below:

log file: /tmp/vmware-user/vmware-ui-4479.log

2018-08-06T12:40:47.635+01:00| vmui| I125: Spawning OVFTool:

2018-08-06T12:40:47.635+01:00| vmui| I125+ '--machineOutput' '--X:logFile=/tmp/vmware-user/ovftool.log' '--X:logLevel=verbose' '--allowExtraConfig' '/run/media/user/NS Linux/VM/kali-linux-2018.2-vm-amd64.ova'

2018-08-06T12:40:47.690+01:00| vmui| I125: OVFTool::OnExit

2018-08-06T12:40:47.690+01:00| vmui| W115: OVFTool::OnUnexpectedExit: Unknown error with output:

2018-08-06T12:40:47.690+01:00| vmui| W115:

2018-08-06T12:40:48.489+01:00| vmui| I125: Spawning OVFTool:

2018-08-06T12:40:48.489+01:00| vmui| I125+ '--machineOutput' '--X:logFile=/tmp/vmware-user/ovftool.log' '--X:logLevel=verbose' '--allowExtraConfig' '/run/media/user/NS Linux/VM/kali-linux-2018.2-vm-amd64.ova'

2018-08-06T12:40:48.539+01:00| vmui| I125: OVFTool::OnExit

2018-08-06T12:40:48.539+01:00| vmui| W115: OVFTool::OnUnexpectedExit: Unknown error with output:

2018-08-06T12:40:48.539+01:00| vmui| W115:

The referenced log file 'tmp/vmware-user/ovftool.log' does not exist on my machine though.

Has anybody else experienced this issue or have any suggestions that might help me fix it?

Many thanks in advance.

Tags (1)
1 Solution

Accepted Solutions
opjs
Contributor
Contributor
Jump to solution

It turns out that VMware logs didn't give any feedback because OVFtool was not executing correctly. This was discovered when running OVFtool from CLI where it became apparent that a dependency libnsl was missing. After installing it and running OVFtool, it started working properly.

Solution:

Checked whether OVFTool runs from CLI.

Installed libnsl

View solution in original post

6 Replies
opjs
Contributor
Contributor
Jump to solution

It turns out that VMware logs didn't give any feedback because OVFtool was not executing correctly. This was discovered when running OVFtool from CLI where it became apparent that a dependency libnsl was missing. After installing it and running OVFtool, it started working properly.

Solution:

Checked whether OVFTool runs from CLI.

Installed libnsl

FTNT_AJH
Contributor
Contributor
Jump to solution

This issue exists in Fedora 29 as well.  Installing libnsl resolved the issue.

cosmic665
Contributor
Contributor
Jump to solution

This issue exists in Fedora 30 as well.  libnsl was already installed.  So here is the command I used instead:

ln -s /usr/lib64/libnsl.so.2 /usr/lib64/libnsl.so.1

dump
Contributor
Contributor
Jump to solution

It happened in fedora 32

* libnsl2 is installed by default

Install it libnsl solved the problem

Regards.,

Reply
0 Kudos
Felipe198520111
Contributor
Contributor
Jump to solution

This cmd line solved my problem, thank you very much!

Reply
0 Kudos
rexfordnyrk
Contributor
Contributor
Jump to solution

The same problem exists for Workstation Pro 17.0.1  on Fedora 38. You can fix it using the solution from the link below.

https://communities.vmware.com/t5/VMware-Workstation-Pro/cannot-import-an-OVF-file-into-Workstation-...

Reply
0 Kudos