I too am having this issue after upgrading to Windows 10 yesterday, did not 
have this issue with windows 7. (I'm also unable to create Host Only 
Interfaces in the VirtualBox GUI now). I was able to fix it, but it is 
definitely not permanent and does not feel like an appropriate fix. If 
anybody can suggest a more definitive fix or route of investigation for 
this issue, that would be greatly appreciated. The fix I found is from the 
following location (Steps 2 and 3 appear to be the most important as the 
error seems to caused by VirtualBox's inability to clear host only 
interfaces): 
https://laracasts.com/discuss/channels/general-discussion/windows-10-vagrant-virtualbox-homestead/?page=1

   1. Install Virtualbox 5 and Vagrant 1.7.4
   2. Comment line 17: config.vm.network :private_network, ip: 
   settings["ip"] ||= "192.168.10.10" in homestead.rb
   3. Comment line 64: b.use ClearNetworkInterfaces in action.rb (path 
   
~\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.7.4\plugins\providers\virtualbox\action.rb)
   4. Homestead init and/or up
   5. Homestead halt
   6. In Virtualbox preferences -> network -> host-only networks edit 
   existing Host-Only adapter and add 192.168.10.10 as IP address
   7. Select homestead box in Virtualbox and go to settings -> network -> 
   adapter 2 and select Host-only network (the one edited in step above)
   8. Homestead up, provision

 

On Thursday, July 30, 2015 at 2:47:10 PM UTC-4, Laurentiu Nicolae wrote:
>
> I made the upgrade to Windows 10 but after the update the machine does not 
> start. I get this error:
>
> $ vagrant up
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'puphpet/ubuntu1404-x64'...
> ==> default: Matching MAC address for NAT networking...
> ==> default: Checking if box 'puphpet/ubuntu1404-x64' is up to date...
> ==> default: Setting the name of the VM: 
> vagrant5_default_1438281430392_96097
> ==> default: Clearing any previously set network interfaces...
> There was an error while executing `VBoxManage`, a CLI used by Vagrant
> for controlling VirtualBox. The command and stderr is shown below.
>
> Command: ["hostonlyif", "create"]
>
> Stderr: 0%...
> Progress state: E_FAIL
> VBoxManage.exe: error: Failed to create the host-only adapter
> VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error 
> (extended info not available)
> VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl 
> handleCreate(struct HandlerArg *)" at line 70 of file VBoxManageHostonly.cpp
>
>
> Can anyone help me to fix this? 
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/e5f0b1d4-96b3-4a5b-8572-26f4be09ff58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to