NS_ERROR_CALL_FAILED 4.2.14 with vagrant scripting

[ncaustin]

I migrated two machines to 4.2.14 (from 4.2.12) both failed with a NS_ERROR_CALL_FAILED when called via vagrant. Looking through the system logs I saw a crash, Macbook Pro (retina). rolling back to 4.2.12 resolved the issue. Vagrant was using VBoxManage import

9: Hard disk image: source image=box-disk1.vmdk, target path=/Users/<me>/VirtualBox VMs/precise64_1/box-disk1.vmdk, controller=8;channel=0
(change target path with "--vsys 0 --unit 9 --disk path";
disable with "--vsys 0 --unit 9 --ignore")
0%...
Progress object failure: NS_ERROR_CALL_FAILED

Process: VBoxSVC [8857]
Path: /Applications/VirtualBox.app/Contents/MacOS/VBoxSVC
Identifier: VBoxSVC
Version: ???
Code Type: X86-64 (Native)
Parent Process: ??? [1]
User ID: 501

Date/Time: 2013-06-24 17:29:57.396 -0700
OS Version: Mac OS X 10.8.4 (12E55)
Report Version: 10

Crashed Thread: 14 Appliance::Task

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:
-->
__TEXT 0000000100000000-00000001002f2000 [ 3016K] r-x/rwx SM=COW /Applications/VirtualBox.app/Contents/MacOS/VBoxSVC

Thread 14 Crashed:: Appliance::Task
0 VBoxSVC 0x000000010005104c start + 310008
1 VBoxSVC 0x0000000100057fc6 start + 338546
2 VBoxSVC 0x0000000100058733 start + 340447
3 VBoxSVC 0x000000010005ab9a start + 349766
4 VBoxSVC 0x0000000100039de6 start + 215186
5 VBoxRT.dylib 0x00000001003c407f RTThreadCreateF + 271
6 VBoxRT.dylib 0x0000000100416845 RTThreadPoke + 581
7 libsystem_c.dylib 0x00007fff83ea17a2 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff83e8e1e1 thread_start + 13

[frank]

4.2.14 regression, see ticket 11895.

[ncaustin]

Thanks for the report link.