Vagrant: Vagrant not starting after upgrade to Windows 10

[halszkaraptor]

I am having this issue after upgrading to Windows 10 yesterday, did not have this issue with windows 7 two days ago.

$ 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

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)
3. Homestead init and/or up
4. Homestead halt
5. In Virtualbox preferences -> network -> host-only networks edit existing Host-Only adapter and add 192.168.10.10 as IP address
6. Select homestead box in Virtualbox and go to settings -> network -> adapter 2 and select Host-only network (the one edited in step above)
7. Homestead up, provision

[draganescu]

hi i have the same issue and did these steps and apparently they work but then i get ssh connection failure. :( any idea if they are related?

[darryldecode]

same problem here :( any updates on this issue?

[arnovr]

confirming the issue, and did not have this issue with windows 8.1

[tidytrax]

Please do not use private network that avoid machive to go up!

[darryldecode]

@arnovr I don't have any issues with windows 8.1, the problem is when I upgraded to windows 10.
@tidytrax It is best if the fix is from vagrant itself :)

[draganescu]

Hi, yes not using the private network allows the machine to start but the boot scripts don't get executed like mounting shared folders etc. because of ssh connection failure.

[bohrshaw]

Confirming this issue...

[npestana]

This is not a problem of Vagrant, it is a VirtualBox bug. Open VirtualBox, go to File -> Preferences -> Network -> Host-only Networks and try to add one. I get this error: "Result Code: E_FAIL (0x80004005)", but VirtualBox creates the interface successfully. We can avoid this for now if we can specify the interface to vagrant to avoid the creation process, but I don't know if it's possible.

EDIT: I can confirm this as a VirtualBox issue, check this ticket: https://www.virtualbox.org/ticket/14040. I tried the VBox-Win10-fix-14040.exe and it worked (Run as Administrator) before you use "vagrant up". I'm using Windows 10 with VirtualBox 5.0.

[YarivGilad]

Confirming the issue - have the same exact behavior. any ideas?

[npestana]

Ajar-Ajar Did you tried the work around I mentioned?

[YarivGilad]

@npestana - thank you for asking! No I didn't. I'm not sure what to do, it is unclear...
I realize that Vbox is actually creating the interface even though it throws the error... ok... what's next?
How can we specify the interface for vagrant to communicate with?

[npestana]

@Ajar-Ajar - I don't know how to specify the interface, but I used the tool in that ticket I mentioned and you just need to execute it as Administrator before the "vagrant up". According to the creator it helps VirtualBox to wait for the creation of the interface before trying to use it (Miscrosoft created the Windows 10 kernel from scratch and probably affected the way VirtualBox detects that the interface was successfully created).

EDIT: Keep the tool running until vagrant configures the interface.

[draganescu]

Yes the tool works just fine :) Thanks!

[YarivGilad]

@draganescu - Which tool is that?
@npestana - Are you referring to the ticket in the link you mentioned - https://www.virtualbox.org/ticket/14040 ??
This is all too obscure... I tried several times going through this thread... I would REALLY appreciate it if someone can sum up the steps to be taken. I'm a JavaScript developer, I don't know much about low-level VBox technicalities... I tried following the steps mentioned in this very thread at the top:
I Installed Vbox 5 and Vagrant 1.7.4
then it says to "Comment line 17: config.vm.network :private_network, ip: settings["ip"] ||= "192.168.10.10" in homestead.rb " - what is that all about?
I have a Vagrantfile, what is a "homestead.rb" ??
Seriously - can someone PLEASE write simple steps without assuming "homestead.rb" or low level knowledge of Vbox?
Thank you.

[phaberest]

The tool in the ticket at https://www.virtualbox.org/ticket/14040 didn't work for me. With the edits in this thread I am able to boot the vm, I can even ssh into it, but I can't ping on its IP from the host. No way.

Can't understand how to properly configure the host only network. Do'h.

[draganescu]

Hi,

The steps to get it up and running are:

0 . vagrant halt, uninstall vagrant and VB, if not latest

1. install latest vagrant and latest virtual box, skip if already latest
2. download https://www.virtualbox.org/attachment/ticket/14040/VBox-Win10-fix-14040.exe
3. Start the exe file as Administrator (right click, run as Administrator)
4. cd to folder where vagrant is and vagrant up
5. after vagrant completes booting close the window from the exe at point 3

With these stept the virtual machine will successfully boot and everything should work.

Yet if you had an old vagrant / VB like I did you will get a permission problem which can be fixed by:

• if it is a regular vagrant machine open the Vagrantfile inside
  or if its puphpet
• open #{dir}/puphpet/vagrant/Vagrantfile-local where #{dir}/ is your home vagrant folder
• replace Vagrant.configure('2') do |config| with config.ssh.insert_key = false

@Ajar-Ajar everything you find with "homestead" they refer to the vagrant machine used for Laravel development. But its the same thing only the naming is different. I use for example puphpet to create my vagrant machine, they use the preconfigured "homestead".

[YarivGilad]

@draganescu - Thank you for your detailed instructions.
I followed them exactly as you described but unfortunately I get the following error when I run vagrant up...

When I click the OK button - it gives me the original error in the command-line window...

Any ideas?
Cheers
Ajar

[luiscastillocr]

Can confirm the steps described by @draganescu did the trick!, now let's wait for the patch from Oracle!

[Kriptonic]

@draganescu helped me too! Thanks!

[YarivGilad]

I ran vagrant halt.
I uninstalled both vagrant & VBox.
I installed the latest versions of both.
I downloaded the patch from here - https://www.virtualbox.org/attachment/ticket/14040/VBox-Win10-fix-14040.exe
I ran the patch as an Administrator
I ran vagrant up
as a result I got the errors I displayed in the screenshots above (2 comments up...)
The error says it cannot find VBoxSVC.exe within the specified folder path. I checked it and it is right there!!
I seriously come to a dead end after trying for 2 days to fight with this bug...
Would really appreciate any help.
Thank you guys
Ajar.

[Mortos]

Also try out the test build
https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-101902-Win.exe

[ztrange]

I am also no expert. Any help would be appreciated :)

I tried the fixer and the test build. With existing vms I get this error.

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/precise64' is up to date...
==> 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", "ipconfig", "VirtualBox Host-Only Ethernet Adapter", "--ip", "192.168.50.1", "--netmask", "255.255.255.0"]

Stderr: VBoxManage.exe: error: The host network interface with the given name could not be found
VBoxManage.exe: error: Details: code E_INVALIDARG (0x80070057), component HostWrap, interface IHost, callee IUnknown
VBoxManage.exe: error: Context: "FindHostNetworkInterfaceByName(Bstr(pszName).raw(), hif.asOutParam())" at line 204 of file VBoxManageHostonly.cpp

I also tried creating a new vm. It starts ok but no networking and no ssh:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/precise64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/precise64' is up to date...
==> default: Setting the name of the VM: test_default_1438698535688_89410
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

[jurosh]

@Ajar-Ajar thanks, https://www.virtualbox.org/attachment/ticket/14040/VBox-Win10-fix-14040.exe helped but hopefully we will see this fix in next build :)

[iJoyCode]

confirming problem. Any solutions?

P.S. Also try out the test build
https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-101902-Win.exe

don't help :(

[frnkly]

Can confirm that @npestana's solution works, where he refers to this ticket: https://www.virtualbox.org/ticket/14040

Thanks a million :)

[YarivGilad]

Thank you all for helping out. Still not able to complete "vagrant up" however...
I uninstalled the current build of VirtualBox and installed the latest test build for Windows 10 64bit
version 5.0.1-101908
I wasn't sure if I should just "vagrant up" - so I did and it threw the following error during...

I then ran "vagrant halt", ran the patch as administrator (VBox-Win10-fix-14040.exe) and tried again to "vagrant up" this time resulting the previous error I reported...

I hope the next build will finally solve this nightmare...
With the new builds - am I suppose to use the patch or just re-install and run "vagrant up"?
Cheers
Ajar

[rohandesai91]

I follwed all the steps given by @draganescu and everthing was going fine. When I enter vagrant up, it starts the process and after a while a prompt appears with the message:-
Error Renaming Connection
Cannot rename this connection. A connection with the name already exists. Specify a different name.
I click ok and then vagrant does other steps and finally vagrant gives this error:-
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run vagrant up while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

Can someone please help with this?

Thanks in advance

[Mortos]

@Ajar-Ajar I got the same error after it was working normally, I ran the test build setup again and selected the repair option, restart the system and it was working again... also I want to point out that I installed the test build after clearing all the host only, bridged, etc interfaces with the VBox GUI manually.

Hope this helps!
Cheers.

EDIT: I'm getting this error each time I shutdown the system, but it works after running the setup again as I mention (I deleted the adapters only the first time, it doesn't seem necessary at this point), btw I'm only running the test build, not the patch program.

[orszaczky]

@Mortos I'm having the same issue as @Ajar-Ajar but reinstall/repair won't change anything. I'm getting the same 'Error Renaming Connection' error regardless of running the fix in the background or not... The only way to get past this is disabling network altogether in vagrantfile.. :(

[Unforgiven-wanda]

Has anyone here managed to make it work so far? And if so, how please?

[Mortos]

@orszaczky Sorry to hear that, sadly I have no idea... that's the only way I got it working, and just for the record, I'm not running the fix program in any way, just the test build.

Cheers.

[IamAdamJowett]

I ended up getting everything working by doing a variation of the age old process of "turning it off and back on again" and using a Test build of Virtual Box.

I did the following:

• Uninstall Vagrant
• Uninstall Virtual Box
• Download latest Vagrant installer http://www.vagrantup.com/downloads.html
• Download the test version of Virtual Box (this is important) https://www.virtualbox.org/wiki/Testbuilds
• Restart
• Install test build of Virtual Box
• Install Vagrant latest
• Restart if prompted during this process
• vagrant up

Everything came back to life for me after that as per normal.

[kenpb]

@IamAdamJowett Hi, do you get a "cannot rename this connection" error after shutting down your computer?

[YarivGilad]

Hey @IamAdamJowett - thank you for the specific instructions!
However - I followed it closely, and did exactly what you wrote, and got the following error:

After which - I clicked the "OK" button, it continued for a while and then stoped with the following error:

I cleaned up my hosts file to look like that -

then I ran "vagrant up" again (using Git Bash CLI as Administrator...) and got the following error:

This is a dead-end from my perspective. its just isn't working. they have a lot to test until official support will finally be out there. till then, I see it as a complete waste of precious time to go through it over and over again just to find out that in my case for whatever reason the current patch or test build didn't work...
Please let me know anyone if you got it to work as well or ran into the same problems of the sort...
Cheers
Ajar

[IamAdamJowett]

@Ajar-Ajar unfortunately (or fortunately for me I guess), I didn't get the error you are showing at all, at least not yet. Sorry I can't help on that one.

[YarivGilad]

Appreciate your help none the less @IamAdamJowett

[orszaczky]

@Ajar-Ajar I managed to fire up vagrant. I found this thread on the VB forums:
https://forums.virtualbox.org/viewtopic.php?f=6&t=67675#p320760

I used the latest build of Vagrant (had it installed, so no need to reinstall) and then I uninstalled the previous version of VirtualBox, restarted, and installed the latest test build (102010), and restarted again.

Then I tried to vagrant up, but got the same error. So I followed these steps, the key was to get the host-only network adapter working:

1) activate build in administrator account with cmd "net user administrator /active:yes" - you will need to run cmd with admin permissions
2) log in to admin
5) go to device manger from where virtualbox host only driver needs to be updated with windows updates. This will create network adapter under "Control Panel\Network and Internet\Network Connections" now you need to assign ip adress to adapter in normal way with virtualbox or just in adapter setting.
6)you are ready to go with "vagrant up"

I skipped step 2) because i'm logged in as admin
In step 5) under network connections I had two adapters, one called 'VirtualBox Host-Only Network Adapter #3' (and had the same description) and once called Ethernet3 (with 'VirtualBox Host-Only Network Adapter #4' in the description).

VB Host-Only Adapter #3 was set to 192.168.56.1
VB Host-Only Adapter #4 was set to 192.168.150.1

I tried to assign manual ip to #3 (192.168.88.1, as my virtualbox is configured to use 192.168.88.88), but I got an error that theip was assigned to VirtualBox Host-Only Network Adapter #2 which was not visible in the list.

At this point I wanted to set my virtualbox to the 192.168.56.xx range but before that I tried to run vagrant up out of curiosity, and magically it fired up without the connection rename popup.

After vagrant up I checked the network adapter settings and VB Host-Only Adapter #3 was automatically set to 192.168.88.1

Hope this helps...

[PaulDinelle]

Just following up to say that @orszaczky solution got me past the "Error Renaming Connection" issue in Windows 10.

To clarify the solution above (as I'm pretty novice), I did the following (assuming you're logged in as this windows administrator):

1) Download latest Vagrant and Dev version of VirtualBox (I used this one: https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-102010-Win.exe )
2) Run Command Prompt (search "cmd" in the windows bar) as Administrator and typed: net user administrator /active:yes
3) Open up the network adapters view (located at this path: Control Panel\Network and Internet\Network Connections)
4) With the network adapters window open, navigate to your vagrant folder and do vagrant up. This will error out at the "Error Renaming Connection" part. If you look at your network adapters window, you'll notice a new network adapter that is active (mine was called Ethernet 3 with the description for VirtualBox Host-Only Ethernet Adapter). Right-click on this new adapter and go to Properties.
5) Click on Internet Protocol Version 4 (TCP/IPv4) in the list that appears and then click the Properties button below the list.
6) Notice that the IP address listed here doesn't match the Vagrant box you're trying to create (if it does, these instructions probably won't work for you). Change the IP here to align with your Vagrant config (my config was set to 192.168.44.44, so I changed my adapter IP to 192.168.44.1 - notice the difference by using 1 at the end instead of 44). Click OK twice after you've made this change to save the settings to the adapter.
7) Go back to your Command Prompt and type vagrant up again. Hopefully it'll work for you!

[philbates35]

FYI VirtualBox 5.0.2 has been officially released, containing some Windows 10 fixes, including a fix for the Host Only Adapter creation.

Changelog: https://www.virtualbox.org/wiki/Changelog
Download link: http://download.virtualbox.org/virtualbox/5.0.2/VirtualBox-5.0.2-102096-Win.exe

Would be good to hear if people are still experiencing issues with Vagrant/VirtualBox 5.0.2 and report back here.

Personally I'm holding off upgrading to Windows 10 purely because of this issue, so I'm interested to know as soon as Vagrant / VirtualBox is compatible with Windows 10 :)

[Unforgiven-wanda]

Hi,
I can confirm that Virtualbox 5.0.2 (and Vagrant 1.7.4) seems to have fixed the problem. My box just now booted without any problems.

Thank you for the heads up @philbates35 and to all contributors to this thread.
Happy programming, people.

[kuya1284]

I'm still having issues with 5.0.2 (with Vagrant 1.7.4). Whenever I reboot my (host) system, I have to run vagrant up FOUR TIMES before everything starts to work normally. Each time before the forth attempt, the machine will choke and instead of running, it'll abort. This will happen after seeing Booting VM... and Waiting for machine to boot. This may take a few minutes..., which will then be followed by the following error:

The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run vagrant up while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

I was able to consistently reproduce this behavior with both VirtualBox 5.0.1 and 5.0.2. Looks like we're just going to have to wait for Oracle to come up with a release that's stable for Windows 10.

EDIT I just created this VirtualBox ticket in case you're interested: https://www.virtualbox.org/ticket/14454

[YarivGilad]

Just downloaded 5.0.3-102166 build
removed previous version of VB, restarted, installed this version, restarted again and got the following error while trying to run vagrant up. somehow I get the feeling this is a minor issue someone here could help me with... would appreciate any help. cheers. Ajar

[kuya1284]

Ajar, did you try running vagrant up four times in a row as I mentioned in my previous comment? That's the only way I was able to get past that error after every single time I reboot my system.

[YarivGilad]

Just tried
even 5 times. restarting my computer after each time.
latest vagrant. latest VB build (5.0.3 revision 102166)
the error is back to the hosts file:

checked out my hosts file... nothing unusual...

here is my VagrantFile...

as you can see - there is absolutely nothing special about it...
any other ideas?
cheers
Ajar

[raysuelzer]

I'm having a different problem. I've followed all of the different instructions in here and am still faced with being unable to connect to my box. It works fine on my non windows 10 machines.

[raysuelzer]

Solved by disabling Hyper V in Windows Features!!!

[YarivGilad]

@raysuelzer - how do you disable Hyper V in Windows Features?

[raysuelzer]

Click the start menu. Search for "Turn Windows Features On/Off" and then uncheck Hyper-V.

[YarivGilad]

I'm still trying every few days... just downloaded the latest VB build (VirtualBox-5.0.3-102322-Win.exe)
restarted twice, opened my git bash commandline as admin, ran vagrant up just to get the following error:

Any of you lucky ones recognize this one?
Cheers
Ajar

[kuya1284]

Ajar, that's the same error you posted before. Is your Vagrantfile pointing to a box that's being hosted remotely (i.e. on Atlas)? If so, have you tried vagrant login yet?

[YarivGilad]

@kuya1284 - thank you for your response. Nope. My box line is - config.vm.box = "ubuntu/trusty32"
You can see the full Vagrantfile on my previous post. it's all very basic setup. no Atlas or anything of the sort. I've also included a screenshot of my hosts file... I'm in a dead end...

[Mortos]

@Ajar-Ajar Trusty 64/32 is indeed from Atlas try using vagrant login or check your local boxes and use one of those instead, also try commenting out the provision script and see if it has any effect.

[orszaczky]

@Ajar-Ajar try checking your windows network connections, and see if the IP range in your host-only adapter matches the one in your vagrant config (look under under TCP/IPv4 properties). if not, set it manually.
(the first 3 chunks should be the same, and the last chunk should be 1 for the host-only adapter. eg. if vagrant is set to 192.168.50.50 -> your network adapter should be on 192.168.50.1)

i had this error when the IP ranges didn't match...

[m-torin]

Try running VirtualBox beta 5.0RC3, this solved my similar problem.

[npestana]

I managed to successfully use Vagrant (1.7.4) with VirtualBox 5.0.2-102096.

[philbates35]

VirtualBox 5.0.4 has been released today with more Windows 10 fixes:

Anyone still having issues, please try this new release and let us know how you get on.

Changelog:
https://www.virtualbox.org/wiki/Changelog

[JeffreyPYL]

I still have the issue with VirtualBox 5.0.4.
I was not able to complete vagrant up while using private_network in vagrant file and not being able to create Host Only Interfaces in the VirtualBox GUI

[ericfrancis]

@philbates35 I am having issues.

Windows 10
Vagrant 1.7.4
Virtualbox 5.0.4.102546

PS> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: Setting the name of the VM: eric-vagrant-vm
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 8180 => 8180 (adapter 1)
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

Opened up virtualbox and tried to manually start the created vm and got this error:

RTR3InitEx failed with rc=-1912 (rc=-1912)
where: supR3HardenedMainInitRuntime
what:  4
VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

[ericfrancis]

My problem was fixed by re-installing Virtualbox and deleting C:\Users\eric\VirtualBox VMs

[kuya1284]

I just upgraded from 5.0.2 to 5.0.4 and can confirm that the latest release solved my problems. I no longer have to run vagrant up four times just to launch my boxes. I also didn't have to do anything special (such as remove and re-add the host-only adapter). Everything just worked for my particular situation.

Good luck to everyone else.

[arnovr]

Updating to 5.0.4 worked for me

[CodeKJ]

5.0.4 didn't fix it for me.

How I fixed:

1. for the first time start your vagrant box in VirtualBox GUI - just press Start;
2. wait till it boots up, then shutdown;
3. now run vagrant up

[philbates35]

VirtualBox 5.0.6 has been released, and there's a few reports on the forum that using 5.0.6 has resolved their Windows 10 VirtualBox issues.

I don't have Windows 10 installed yet so I can't test myself, but it would be good to hear if this resolves anyone else's issues with Vagrant / VirtualBox / Windows 10.

Should be worth noting though that as far as I can see, Windows 10 at this point is still not an officially supported host OS for VirtualBox.

[almasmaris]

Finally i solved the problem after many days. This -> https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-102010-Win.exe, did not solve my problem.

I don't really know how i fixed this but i'm fixed it after doing this:

1. Uninstall/and Download latest Vagrant (1.7.4) and VirtualBox (5.0.6).
2. Run with compatibility: Go to the C:\Program Files\Oracle\VirtualBox folder, right click on VirtualBox.exe, go to compatibility, check the "Run in compatibility mode" checkbox and choose Windows 7. Click OK to close the window. Repeat step 2. for VBoxManage.exe and VBoxHeadless.exe
3. update 'laravel/homestead' box if not up to date.
4. RESTART
5. run homestead in virtualbox GUI, it worked
6. testing in cmd, it worked

if the vagrant already running but cannot connect to the site:

1. In Virtualbox preferences -> network -> host-only networks create new Host-Only adapter and add 192.168.10.1 as IP address, So,there are 2 Host-Only adapter with IP 192.168.56.1 and IP 192.168.10.1.
2. Select homestead box in Virtualbox and go to settings -> network -> adapter 2 and select Host-only network (the one created in step above, 192.168.10.1)
3. So, homestead using adapter 1 (NAT) and adapter 2 (host-only)

:) Good luck to everyone

[nhdinh]

Hi all,
Is there any report that VB 5.0.8 and Windows 10 are working friendly together? I don't have Windows 10 box so I can't tell.
Thanks

[Mortos]

I'm getting a weird glitch with the host-only adapter when creating private networks, it's using the same adapter for every VM and when try to create a new one manually I get the familiar "Cannot rename this connection... blah blah", I'm not sure if this is related, anyone else having this issue?

[btopro]

fought with this ... forever today. So @almasmaris 3 up helped get me in the right direction. Ultimately, my BIOS was locked down when it came to allowing virtualization to run on the computer. This article helped point me in the right direction and the VM is spinning up as we speak (finally) :) http://www.sysprobs.com/disable-enable-virtualization-technology-bios

[Gamezpedia]

Window 10 Virtual Box 5.0.8
homestead up
Bringing machine 'default' up with 'virtualbox' provider...
==> 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", "ipconfig", "VirtualBox Host-Only Ethernet Adapter", "--ip", "192.168.10.1", "--netmask", "255.255.255.0"]

Stderr: VBoxManage.exe: error: The host network interface with the given name could not be found
VBoxManage.exe: error: Details: code E_INVALIDARG (0x80070057), component HostWrap, interface IHost, callee IUnknown
VBoxManage.exe: error: Context: "FindHostNetworkInterfaceByName(Bstr(pszName).raw(), hif.asOutParam())" at line 205 of file VBoxManageHostonly.cpp

[mitchellh]

This is a VirtualBox issue they introduced with VB5. I've heard that installing VBox on Windows and restarting your machine fixes it but I've heard mixed things. Sorry folks! I also hear Google has some results but I'm not sure. Given that the Vagrant Windows userbase is in the millions, I think we'd be hearing a lot more if it was widespread (though this issue is already quite loud).

Unfortunately, I'm not sure there is anything Vagrant can do here. Sorry

[NoiseEee]

I know the issue is closed, but I did want to say that I went through both problems listed here ("host only adapter" and "invalid state") with wild frustration and came out on top:
How to solve:

• latest version of vagrant
• VirtualBox 4.3.32, downloaded from the "Old Builds" page
• no other wackiness (hosts edits, compatibility mode, etc etc)

Frankly, the last comment from @mitchellh about "introduced with VB5" inspired me to use an old (but recent) version of 4.x, and all is good.

MADNESS but THANKS to @mitchellh for having a resource on the interwebs to solve this craziness. Cheers.

[coderdiaz]

Hi all,

I re-install and update my VBox in Windows 10 Version 1511 Build 10586.14 but this machine not boot.

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 80 => 8000 (adapter 1)
    default: 443 => 44300 (adapter 1)
    default: 3306 => 33060 (adapter 1)
    default: 5432 => 54320 (adapter 1)
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

Updates, updates, everywhere. If someone had the same issue, I would if you told me how to fix it.
Thanks guys.

[NoiseEee]

@coderdiaz Did you install Virtual Box 4.3.32 as I happened to note just above your comment?

[coderdiaz]

@NoiseEee Nope, I install it and back here. Thanks. :+1:

[AlennGK]

Confirm: deleting name line with homestead-7 in homestead.rb helped and it has created a new box, so I hope that after reboot it wont create another 2GB box =) Under W10!
# Configure A Few VirtualBox Settings config.vm.provider "virtualbox" do |vb| vb.customize ["modifyvm", :id, "--memory", settings["memory"] ||= "2048"] vb.customize ["modifyvm", :id, "--cpus", settings["cpus"] ||= "1"] vb.customize ["modifyvm", :id, "--natdnsproxy1", "on"] vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"] vb.customize ["modifyvm", :id, "--ostype", "Ubuntu_64"] end

[coderdiaz]

Yeah, in my W10 it's working now with Virtual Box v5.0.10 build 104061.
Thank's Alenn

Best Regards,

2016-01-18 15:10 GMT-06:00 Alenn [email protected]:

Confirm: deleting name line with homestead-7 in homestead.rb helped and it
has created a new box, so I hope that after reboot it wont create another
2GB box =) Under W10!

Configure A Few VirtualBox Settings

config.vm.provider "virtualbox" do |vb|
vb.customize ["modifyvm", :id, "--memory", settings["memory"] ||= "2048"]
vb.customize ["modifyvm", :id, "--cpus", settings["cpus"] ||= "1"]
vb.customize ["modifyvm", :id, "--natdnsproxy1", "on"]
vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
vb.customize ["modifyvm", :id, "--ostype", "Ubuntu_64"]
end

—
Reply to this email directly or view it on GitHub
https://github.com/mitchellh/vagrant/issues/6068#issuecomment-172654484.

[fletchowns]

I'm having problems after upgrading to Windows 10 with VirtualBox 5.0.14:

==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: You are trying to forward to privileged ports (ports <= 1024). Most
==> default: operating systems restrict this to only privileged process (typically
==> default: processes running as an administrative user). This is a warning in case
==> default: the port forwarding doesn't work. If any problems occur, please try a
==> default: port higher than 1024.
==> default: Forwarding ports...
    default: 443 (guest) => 443 (host) (adapter 1)
    default: 8443 (guest) => 8443 (host) (adapter 1)
    default: 5432 (guest) => 5432 (host) (adapter 1)
    default: 8787 (guest) => 8787 (host) (adapter 1)
    default: 9090 (guest) => 9090 (host) (adapter 1)
    default: 9091 (guest) => 9091 (host) (adapter 1)
    default: 8000 (guest) => 8000 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

Downgrade to VirtualBox 4.3.36 seemed to resolve the issue. The two VirtualBox tickets I saw linked from this thread, https://www.virtualbox.org/ticket/14040 & https://www.virtualbox.org/ticket/14454 are closed out. Is there a different ticket on the VirtualBox side I should folllow?

[coderdiaz]

Verify if your computer has activate VT-x or start your virtual machine
from GUI and check the error.

El martes, 9 de febrero de 2016, Greg Barker [email protected]
escribió:

I'm having problems after upgrading to Windows 10 with VirtualBox 5.0.14:

==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: You are trying to forward to privileged ports (ports <= 1024). Most
==> default: operating systems restrict this to only privileged process (typically
==> default: processes running as an administrative user). This is a warning in case
==> default: the port forwarding doesn't work. If any problems occur, please try a
==> default: port higher than 1024.
==> default: Forwarding ports...
default: 443 (guest) => 443 (host) (adapter 1)
default: 8443 (guest) => 8443 (host) (adapter 1)
default: 5432 (guest) => 5432 (host) (adapter 1)
default: 8787 (guest) => 8787 (host) (adapter 1)
default: 9090 (guest) => 9090 (host) (adapter 1)
default: 9091 (guest) => 9091 (host) (adapter 1)
default: 8000 (guest) => 8000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run vagrant up while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

Downgrade to VirtualBox 4.3.36 seemed to resolve the issue. The two
VirtualBox tickets I saw linked from this thread,
https://www.virtualbox.org/ticket/14040 &
https://www.virtualbox.org/ticket/14454 are closed out. Is there a
different ticket on the VirtualBox side I should folllow?

—
Reply to this email directly or view it on GitHub
https://github.com/mitchellh/vagrant/issues/6068#issuecomment-182036366.

From Gmail Mobile in iPhone