Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#35969 - [virtualbox] Cannot import virtual machines

Attached to Project: Community Packages
Opened by Tom Alexandrowicz (tlalexan) - Friday, 28 June 2013, 19:08 GMT
Last edited by Sébastien Luttringer (seblu) - Friday, 05 July 2013, 12:02 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

- When I use import appliance in the UI to import a machine I just get a dialog box that says an error has occured. Clicking import causes a segmentation fault.

Additional info:
* This broke with the June 23rd version: 4.2.14-1
* I fixed by rolling back to virtualbox-4.2.12-3-x86_64.pkg.tar.xz from the rollback machine

- When using Vagrant from the command line I get an error like this when importing a box:

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "/home/tom/.vagrant.d/boxes/raring-20130622/virtualbox/box.ovf"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/tom/.vagrant.d/boxes/raring-20130622/virtualbox/box.ovf...
OK.
0%...
Progress object failure: NS_ERROR_CALL_FAILED

Steps to reproduce:

- Go to file menu
- Select Import Applicance
- Pick an appliance file .ovf
- click next, click import
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Friday, 05 July 2013, 12:02 GMT
Reason for closing:  Fixed
Comment by Martin Honermeyer (mazzolino) - Tuesday, 02 July 2013, 15:03 GMT
Similar problem over here. "vagrant up" fails immediately. Kernel log says:

Jul 02 16:53:14 archpad kernel: Appliance::Task[2578]: segfault at 0 ip 000000000044e794 sp 00007fc91497a770 error 4 in VBoxSVC[400000+27a000]

Downgrading to 4.2.12 fixed it.
Comment by Sébastien Luttringer (seblu) - Tuesday, 02 July 2013, 18:36 GMT
I'm also not able to export and import VM with .ovf files.
Btw, no issue with .ova files.
Comment by Jesse (techno-geek) - Wednesday, 03 July 2013, 17:31 GMT
"It appears that VirtualBox 4.2.14 import is just broken. Please downgrade and hope that VirtualBox fixes this."

https://github.com/mitchellh/vagrant/issues/981
Comment by Sébastien Luttringer (seblu) - Friday, 05 July 2013, 00:14 GMT
fixed into 4.2.16. Build in progress.

https://www.virtualbox.org/wiki/Changelog
Comment by Tom Alexandrowicz (tlalexan) - Friday, 05 July 2013, 00:15 GMT
Thanks Sébastien! You rock!

Loading...