VirtualBox

Ticket #18343 (new defect)

Opened 3 years ago

Last modified 8 months ago

Unable to import OVA with error NS_ERROR_INVALID_ARG

Reported by: tsenay Owned by:
Component: other Version: VirtualBox 6.0.2
Keywords: import Cc:
Guest type: Linux Host type: Linux

Description

$ vboxmanage import packer_cache/31bc31daafd70a05b35eef0741b96f878b356b4721385a42056d02b946cc22d2.ova

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /var/lib/jenkins/tsenay/packer-core-os-builder/packer_cache/31bc31daafd70a05b35eef0741b96f878b356b4721385a42056d02b946cc22d2.ova...
OK.
Disks:
  vmdisk1       41943040000     -1      http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized       rhel-75-x86_64-core-os-disk001.vmdk     -1      -1

Virtual system 0:
 0: Suggested OS type: "RedHat_64"
    (change with "--vsys 0 --ostype <type>"; use "list ostypes" to list all possible values)
 1: Suggested VM name "rhel-75-x86_64-core-os"
    (change with "--vsys 0 --vmname <name>")
 2: Suggested VM group "/"
    (change with "--vsys 0 --group <group>")
 3: Suggested VM settings file name "/home/ldapccs/tsenay/VirtualBox VMs/rhel-75-x86_64-core-os/rhel-75-x86_64-core-os.vbox"
    (change with "--vsys 0 --settingsfile <filename>")
 4: Suggested VM base folder "/home/ldapccs/tsenay/VirtualBox VMs"
    (change with "--vsys 0 --basefolder <path>")
 5: Description "packer-core-os-image Virtual Machine"
    (change with "--vsys 0 --description <desc>")
 6: Number of CPUs: 2
    (change with "--vsys 0 --cpus <n>")
 7: Guest memory: 2048 MB
    (change with "--vsys 0 --memory <MB>")
 8: Network adapter: orig NAT, config 3, extra slot=0;type=NAT
 9: IDE controller, type PIIX4
    (disable with "--vsys 0 --unit 9 --ignore")
10: IDE controller, type PIIX4
    (disable with "--vsys 0 --unit 10 --ignore")
11: Hard disk image: source image=rhel-75-x86_64-core-os-disk001.vmdk, target path=rhel-75-x86_64-core-os-disk001.vmdk, controller=9;channel=0
    (change target path with "--vsys 0 --unit 11 --disk path";
    disable with "--vsys 0 --unit 11 --ignore")
0%...10%...20%...30%...40%...50%...
Progress state: NS_ERROR_INVALID_ARG
VBoxManage: error: Appliance import failed
VBoxManage: error: Code NS_ERROR_INVALID_ARG (0x80070057) - Invalid argument value (extended info not available)
VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at line 957 of file VBoxManageAppliance.cpp

Attachments

rhel-75-x86_64-core-os.ovf Download (6.1 KB) - added by tsenay 3 years ago.
OVF file

Change History

Changed 3 years ago by tsenay

OVF file

comment:1 follow-up: ↓ 3 Changed 3 years ago by tsenay

After hours of investigations, the problem is basic. There was not enough space on the disk to create the VM files.

So, the real bug is that the out-of-space issue is not handled correctly.

comment:2 Changed 2 years ago by sukhoi191

I've had almost the same error, the only difference was "Progress state: E_INVALIDARGS".

After some trial and error, it turns out it happens when I try to import machine with VMDK disk, with "Import hard drives as VDI" option selected.

comment:3 in reply to: ↑ 1 ; follow-up: ↓ 4 Changed 23 months ago by imtiaz

Replying to tsenay:

After hours of investigations, the problem is basic. There was not enough space on the disk to create the VM files.

So, the real bug is that the out-of-space issue is not handled correctly.

I have VirtualBox 6.0.14 installed on macOS Catalina and I was trying to import a Windows 10 developer virtual machine that I had downloaded from Microsoft. The image was having a size of 17 GB approximately. During installation I receive following error:

Failed to import appliance /Users/demouser/Downloads/WinDev1910Eval.ovf Details: Result Code: NS_ERROR_INVALID_ARG (0x80070057)

After searching couple of hours from editing XML files to changing permission on various directories, I found the solution suggested by tsenay, and my problem was solved. I had only 16 GB available space on my macbook.

Thanks tsenay!

Last edited 23 months ago by imtiaz (previous) (diff)

comment:4 in reply to: ↑ 3 Changed 22 months ago by shiskey

Replying to imtiaz:

Replying to tsenay:

After hours of investigations, the problem is basic. There was not enough space on the disk to create the VM files.

So, the real bug is that the out-of-space issue is not handled correctly.

I have VirtualBox 6.0.14 installed on macOS Catalina and I was trying to import a Windows 10 developer virtual machine that I had downloaded from Microsoft. The image was having a size of 17 GB approximately. During installation I receive following error:

Failed to import appliance /Users/demouser/Downloads/WinDev1910Eval.ovf Details: Result Code: NS_ERROR_INVALID_ARG (0x80070057)

After searching couple of hours from editing XML files to changing permission on various directories, I found the solution suggested by tsenay, and my problem was solved. I had only 16 GB available space on my macbook.

Thanks tsenay!

Just to add, in my case, I had over 800 GB free space but I was still getting the error:

Failed to import appliance <ova file>


Result Code: NS_ERROR_INVALID_ARG (0x80070057)

I later figured out there was already a file of the same name in "$HOME/VirtualBox VMs" folder. This was caused due to a previous unsuccessful import (computer crashed for unrelated reason). I deleted that file and import was successful.

Therefore, it is my hunch that the error NS_ERROR_INVALID_ARG is thrown, at the very least, whenever it is not able to import OVA to disk.

Since it is more of a generic error due to improper error handling, it can also be thrown for other, as yet unknown reasons.

comment:5 Changed 8 months ago by beartooth

Had the same problem, only mine was a parent directory permission problem. For some reason, a parent directory 2 levels up needed to be opened up, once done, the import ran just fine.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use