@pdcmoreira Woot! Just confirming that your solution works with stock install of VirtualBox 5.0.1 test build and Vagrant 1.7.4. Running in compatibility mode solves the problem for me without any file modifications. The test build for VB 5.0.1 also eliminates the need for step #1.
for those whose works, which one is your OS architecture? x86 or x64 ??
Windows 10 Pro x64
Vagrant 1.7.4 VirtualBox 5.0.1 r101939
No compatibility mode. No special file modifications.
@bluesheep , then maybe my windows 10 pro x86 is the problem?
looks like i need to either stay at VB 4.7.2 or install to x64 OS..
Windows 10 Pro x64 Vagrant 1.7.4 VirtualBox 5.0.1 Test Build - Running in Windows 8 compatibility mode
Working well.
Where can we download 5.0.1?
@Eldair Thank you, its working for me on win10 with VB 5.0.0. But when I tried VB 5.0.1 I was getting whole different errors while doing homestead up. So I am using your solution now. But now when I ssh into homestead VM I cannot use the console, linux commands are unknown or displaying some really crazy non-readable stuff. And after a while whole cmd stops responding. Why could this be happening?
After following all Eldair's steps, I'm getting the same error message as Antony:
the guest machine entered an invalid state...
Need help. I'm locked out of my homestead! Thanks.
@DavidEwers This worked for me. VirtualBox 5.0.1 test build (Running in Windows 8 compatibility mode) and Vagrant 1.7.4. .
@fraserk Alright I'm getting somewhere! How do you run it in Windows 8 compatibility mode?
@DavidEwers Open the virtual box GUI then power-off the machine(homestead) from there. Then you can go back to command line do a vagrant up again
Awesome, I can confirm 5.0.1 solves the problem :) No hacks or windows compatibility mode needed. Thanks guys!
@gregorio@latouraineinc.com It works with 5.0.1 with no compatibility options, but when i try to open VirtualBox GUI I get
Failed to open a session for the virtual machine homestead.
Callee RC:
E_FAIL (0x80004005)
And I have to use port :8000, since port :80 is not being forwarded for some reason anymore.
Hello can someone help me with this ? I did -Install Virtualbox 5 and Vagrant 1.7.4 -Comment line 17: config.vm.network :private_network, ip: settings["ip"] ||= "192.168.10.10" in homestead.rb -Comment line 64: b.use ClearNetworkInterfaces in action.rb (path ~\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.7.4\plugins\providers\virtualbox\action.rb)
but when i write homestead up or init i get
$ homestead init
/bin/env: php: No such file or directory
and this is error when i write vagrant up
$ vagrant up
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: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> 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.
@blackpearl : You got the same error messages like mine, perhaps you also use Windows 10 x86 (32 bit) ?
I had those error messages as well, but am on the x64 version. I ended up redoing the whole setup process (deleting all files and traces of previous attempts) and it went away.
I am on the test build of Virtualbox, latest build of vagrant, and used git to clone the homestead directory. Made some changes to the configuration IP in the homestead.yaml and manually created a new adapter for the virtualbox and it all works fine now.
@antonybudianto yes, i upgraded my windows 8.1 to windows 10
Do you know how fix this error ?? It's important for me
I run vagrant up
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> 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...
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: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version of
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If you see
default: shared folder errors, please make sure the guest additions within the
default: virtual machine match the version of VirtualBox you have installed on
default: your host and reload your VM.
default:
default: Guest Additions Version: 4.3.14
default: VirtualBox Version: 5.0
==> default: Setting hostname...
==> default: Mounting shared folders...
default: /vagrant => C:/Users/pajak/Homestead
default: /home/vagrant/Code => C:/Users/pajak/Code
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.
but still homestead.app doesn't work
Can someone help me ?
Install latest Virtualbox test build and that works fine. Link: https://www.virtualbox.org/wiki/Testbuilds
i have lastest version
This solution worked for me, the secondary one in the update did not.
Does anyone know if it works with Mamp, Wamp or Xammp? I find it odd that Windows 10 has been advertised for months yet their is no solution. You should not have to modify anything really.
Now, i have also tested latest test build of Virtualbox and it worked for me out of box (nothing commented out, no manual changes whatsoever).
@Eldair So your saying that you where able to install Laravel on Windows 10 just like installing on any other OS. Im having some issues but hopefully they can be fixed.
The other solutions didn't work for me (not even the test build of VirtualBox) but I saw somewhere else that there's been a new full version of VirtualBox just released yesterday with the Windows 10 fixes and that worked fantastic for me.
There was a couple of UAC's to accept the first time you do the up command, but after that it worked great. I'm running on the latest version of Vagrant and the brand new release of VirtualBox.
Finally I get it worked, as @Rjs37 said, the new Virtualbox 5.0.2 works well, but at first I still encountered the "invalid state" error, and I go to Virtualbox UI preferences and removed all host-only adapters, then I did:
homestead halt
homestead up
and then it worked well (no file modifying, or port hacks) Looks like the new VB don't try to create new adapter anymore when homestead up, if it still creates adapter, then it's because of the old ones and VB think it's the first time, that's why I removed the old, and when homestead up, everything is okay
It would be really really really (yes, really!) great if Homestand would run with the build-in Hyper-v virtualization engine on windows machines as it is much less buggy than VirtualBox (imho).
Unfortunately the Homestead Vagrant image does not provide the Hyper-v integration drivers (and I was not able to get things running). If anybody get this working, I'll buy him a beer (at least one).
Latest version of VirtualBox doesn't give any errors and everything seems to work nicely, but I can't access homestead with its ip address. Any ip I set for homestead (or on the VirtualBox Host-Only Network) goes to localhost/127.0.0.1 instead of homestead.
Hello,
Just a heads up, do not update to windows 10 build 10525 or later, it breaks virtualbox without any fix atm.
Kristijan
Please or to participate in this conversation.