Vagrant up failure

[IanHeywood]

My VM was subjected to an ungraceful shutdown and now it's refusing to restart. Any advice gratefully received. Thanks!

tachikoma:papino ianh$ vagrant up Bringing machine 'default' up with 'virtualbox' provider... [default] Clearing any previously set forwarded ports... [default] Clearing any previously set network interfaces... [default] Preparing network interfaces based on configuration... [default] Forwarding ports... [default] -- 22 => 2222 (adapter 1) [default] -- 8888 => 8888 (adapter 1) [default] Running 'pre-boot' VM customizations... A customization command failed:

["controlvm", :id, "usbattach", "p=0x7811;v=0x7392;s=0x000087b375caedec;l=0xfd120000"]

The following error was experienced:

<Vagrant::Errors::VBoxManageError: There was an error while executing VBoxManage, a CLI used by Vagrant

for controlling VirtualBox. The command and stderr is shown below.

Command: ["controlvm", "625c147f-43fb-4850-a7f5-16b2ef622a40", "usbattach", "p=0x7811;v=0x7392;s=0x000087b375caedec;l=0xfd120000"]

Stderr: VBoxManage: error: Could not find a USB device with address 'p=0x7811;v=0x7392;s=0x000087b375caedec;l=0xfd120000' VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component Host, interface IHost, callee nsISupports VBoxManage: error: Context: "FindUSBDeviceByAddress(Bstr(a->argv[2]).raw(), dev.asOutParam())" at line 952 of file VBoxManageControlVM.cpp

Please fix this customization and try again.

[gijzelaerr]

this is quite some obscure dropbox voodoo that I don't really know much about.

Did you reboot your machine already? A bit of a Windows XP advice, but it may help.

Is it an option for you to just recreate the virtual machine? vagrant destroy and vagrant up? If not, i'm curious why.

[IanHeywood]

I've got a bunch of recent work on the VM disk that I don't have elsewhere so I was trying to avoid any tear-down-and-rebuild methods in case I lost it. In any case I managed to fix it by removing this line:

vb.customize ["controlvm", :id, "usbattach", "p=0x7811;v=0x7392;s=0x000087b375caedec;l=0xfd120000"]

from the Vagrantfile and then vagrant up behaved normally.

False alarm I guess, thanks Gijs!

[IanHeywood]

For future reference: would vagrant destroy preserve the contents of the disk? I don't keep work on the common /data area due to that earlier bug, so all my stuff is locked up in that .vmdk file...

Cheers.

[gijzelaerr]

as long as you where the one that put that line there.... it is fine with me :)

I advice you to put your data inside /vagrant, this folder is synced with the papino folder on the host. No matter what will happen, you'll still have your data.

Otherwise you probably can mount your virtualbox image, but I didn't try that before. Or create a custom folder mapping and put your data there. I see my VM as hostile and I want to be able to reset the state at any moment.

About vagrant preserving the disk image, I'm not sure, try it :)