Hello,
I am having issues running homestead via virtualbox on Windows 10 TP 10130 with error code
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: "int __cdecl handleCreate(struct HandlerArg *,int,int *)" at line 66 of file VBoxManageHostonly.cpp
I am aware it is a common issue but was curious if someone has found a workaround?
host-only (and bridged adaptors) do not work. If you remove all networking options (expect port forwarding!) in the VagrantFile (or HomeStead's equivalent) it does seem to boot ok - I've been fighting with this for a couple of days now.
SSH into the box and use 'ifconfig' to locate your IP.
You may also need VirtualBox 5 RC1 to achieve this - install this by running as Admin and in Window's 8 compatibility mode
Link for RC1 http://dlc-cdn.sun.com/virtualbox/5.0.0_RC1/
Hi, thanks a lot, I will try it out today.
Vagrant doesn't support VB5 but I believe it's been merged and awaiting compile for 1.7.3.
Hi, I managed to use Vagrant for VB5 and to install it as suggested. When I start the box from Virtualbox gui it runs until "waiting for network.." message and stops there (via Vagrant - same error as above).
Why don't we back up 25 yards here and wait on the final version of Windows 10 to even be released.
Not pretty but a working solution (tested under Win10 build10130).
Each time after to manage vagrant (start, halt, whatever) switch to Administrator, manage, and switch back to your usual user. Do not sign out of the Administrator account when switching if you have a box up
@jlrdw is 100% correct. From my experience with other windows os previews the final release core code is significantly different. Generally the core code (this case w8) for compatability issues.
Fyi, Vista's preview didn't have the dx sound and core code was nt (XP) and all your old printers and stuff worked. Released and nothing worked.
From what I experienced homestead doesn't play nice with windows. For windows you can try laragon. Just visit http://laragon.org
I've never had any problems with Homestead on Windows 8/8.1
@tradjick Thanks! That actually worked for me :) But, as others noted, win10 is not ready and definitely still not worth doing all that, so back to 8.1 for now.
Another month to go till release @Eldair :) I'll be surprised if every software vendor is going to be on the ball. Every man and his dog not used to OS migrations is going to be jumping on the free license (and getting away from win8/8.1) so it's nice to have a solution in place just in case :D
Hello,
New solution:
P.S. I don't know why, but I had to add :8000 to alias urls in browser to get them to open pages.
Edit: the :8000 can be avoided if you change default port forwarding 80 => 80 instead of 80 => 8000 in homestead.rb or go to settings of your box -> network settings -> adapter 1 (nat) and port forwarding option, and there is port 80 forwarded to port 8000, change 8000 to 80 and that's it.
And it's working (: Cheers
UPDATE Alternative solution by @pdcmoreira:
I found a VERY SIMPLE way to make it work without touching any file in the accepted answer!
Install and run this file: https://www.virtualbox.org/attachment/ticket/14040/VBox-Win10-fix-14040.exe (leave it running in the background) 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 Run cmd and do homestead up. There you go! It should work!
After all is done and working, close the program opened in step 1.
[UPDATED]
You don't need to run cmd as Administrator in step 4.
For now, It's working like a charm @Eldair. Thank you so much.
Hey people, Today I upgraded to W10, and had this problem. @Eldair 's solution worked, though it now takes FOREVER to boot homestead.
In the process, I also had a problem after upgrading to Vagrant 1.7.4. My box was/is called "default", so when I tried running vagrant up, I received an error saying that the box "base" couldn't be find. After trying for some time to fix that without luck, I came up with a handy solution for the time being. I first run a vagrant global-status, get the ID of the box I want to start, and then I do "vagrant up id_of_the_box".
Hope this helps someone. Cheers
Thank you @Eldair works fine. Windows 10 (release)
@Eldair's steps worked great for me as well. Windows 10 Release.
Hi everyone,
I've just upgraded to Windows 10 and while I was trying to implement the recommended fix I thought I ought to remove my old homestead box (bad idea).
As per the steps, I can indeed setup a laravel/homestead box via vagrant up, but the created box is not called homestead and the homestead up command gives a slightly similar error to the initial one:
D:\MyDirectory>homestead up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'laravel/homestead'...
[K==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: Setting the name of the VM: homestead
==> 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
So, considering:
Is there any way that I can setup homestead to work with the regular homestead up command and multiple site mapping? Forgive my ignorance, but I have no clue on how to map several Laravel sites to a single Vagrant box instance and was happy that homestead took care of all of this for me with a simple YAML file :(
Hi @vnobre, to me it seems like you haven't commented out lines in action.rb and homestead.rb. You should do that and manually set networks for existing box after which homestead up should work (with mapping from homestead.yaml file).
@Eldair
You saing this:
"In Virtualbox preferences -> network -> host-only networks edit existing Host-Only adapter and add 192.168.10.10 as IP address"
How you edit host-only network? In my VBox if i go there i dont see any (existing) host-only interface and if i try to create/insert it VBox throws me an error. Resultcode: E_FAIL (0x80004005)
PS: Im running as Admin.
Hi @Eldair , I was following the steps on the accepted answer, sorry! I noticed your answer with new steps after your reply. I followed your steps now, commented the necessary lines and while I'm still able to vagrant up/halt (and it does create the homestead box) I'm still getting the same error when I try to homestead up.
By doing vagrant up, it does fetch my homestead.yaml file and syncs the proper folders/sites. However, my Windows hosts file was referring to 192.168.10.10 and this no longer works. It will work if I refer to 127.0.0.1 and add :8000 to the end of the site address ( http://example.app:8000) but this is less than ideal :(
Thank you for your help either way! I'm a tad disappointed that I've made a mess of my homestead setup, I actually enjoy Windows 10 but I might have to revert to Windows 7...
@bogdanus try to reinstall virtualbox, because it should have created one during installation. If not, try installing as admin. @vnobre the :8000 can be avoided if you change default port forwarding 80 => 80 instead of 80 => 8000 in homestead.rb or go to settings of your box -> network settings -> adapter 1 (nat) and port forwarding option, and there you will see port 80 forwarded to port 8000, change it to 80 and that's it.
@Eldair your tip worked out great and I'm finally up and running again just as I was before! Thank you so much!
Can we mark your steps as the accepted answer? The accepted answer didn't work for me, but your steps did!
@Eldair Any chance you have worked with ssl certificates. I did the port forwarding part 80=>80 but i still have to add :80 on the url. And the page still does not load i get
SSL connection error: ERR_SSL_PROTOCOL_ERROR
Unable to make a secure connection to the server. This may be a problem with the server, or it may be requiring a client authentication certificate that you don't have.
Thank you for this excellent description! I've upgraded to Windows 10 yesterday and got my homestead machine working within a few minutes. The only thing not working for me is the port forwarding. When I change the setting in VirtualBox, there is no effect. When I edit the array in homestead.rb, I'm getting the following error on the "up" command:
To fix this, modify your current projects Vagrantfile to use another port. Example, where '1234' would be replaced by a unique host port:
config.vm.network :forwarded_port, guest: 80, host: 1234
Sometimes, Vagrant will attempt to auto-correct this for you. In this case, Vagrant was unable to. This is usually because the guest machine is in a state which doesn't allow modifying port forwarding.
I tried investigating this and found the command "netstat -a -b" which only shows me the following:
Proto Local Address Remote Address Status
TCP 0.0.0.0:80 My-Username:0 LISTEN
What am I doing wrong?
I suggest living with :8000 for now. For those interested a patched build should hopefully appear soon: https://www.virtualbox.org/ticket/14040
@Mwaa I am working on a project with a self-signed SSL certificate and I had to forward 443 => 443 (by default it'll be 44300 and you'd have to add the port to the end of the address such as http://your.app:44300).
I updated the ports on the homestead.rb file and also on the Box settings as explained by Eldair.
When I perform vagrant up all I get is a warning that these are usually privileged ports, but everything is working fine.
This pretty much ruined my day.
I got this error when trying the solution:
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.
Any ideas? Thank you
Please or to participate in this conversation.