I've got the same problem and make a note about it here

https://gist.github.com/ratiw/1428d432877d745aa49d

See if it works for you.

The problem still persist. I have tried installing both virtualbox version 4.3.10 and 4.3.6 I have also tried to change the network adapter with 10 ending, still not functioning.

Might be a good idea to make another key and bin the one you posted above :)

t-v-m said:

I had the same problem. For me it was because hardware virtualisation (VT-x) was not enabled on my processor so I could not install ubuntu 64bit in Virtualbox. Use this tool from Microsoft to see if VT-x is enabled - http://www.microsoft.com/en-za/download/details.aspx?id=592

If its not you will need to enable it in your BIOS setting.

Hope this helps.

Worked for me thanks!

Used Intel Processor Identification Utility, it does say that intel virtualization technology is supported.

@shabushabu I have generated quita a few keys. So no worry there

t-v-m said:

I had the same problem. For me it was because hardware virtualisation (VT-x) was not enabled on my processor so I could not install ubuntu 64bit in Virtualbox. Use this tool from Microsoft to see if VT-x is enabled - http://www.microsoft.com/en-za/download/details.aspx?id=592

If its not you will need to enable it in your BIOS setting.

Hope this helps.

+1 - this also solved my issue.

I've submitted a PR to the docs to include this for Windows 7 users to consider: https://github.com/laravel/docs/pull/765

So, as I understand, If my CPU doesn't support (VT-x) Homestead wont work? There is some workaround for this? Thanks in advance.

I'm in the same boat as sveggiani

I keep getting the "default: Warning: Connection timeout. Retrying..." message.

I'm on Windows 8 x64, running latest version of VirtualBox and Vagrant.

Any help?

@daparky I've been doing some tests and not only Laravel Homestead, but any 64bit VM doesn't seem to work along with Vagrant. I've tested a 32bit VM without problems.

So, it seems to be a Virtualbox issue in the end.

Are there any chance of a Homestead version based on 32bit VMs?

Sorry, I forgot to mention that this happens only with non VT-x capable CPU's

sveggiani said:

@daparky I've been doing some tests and not only Laravel Homestead, but any 64bit VM doesn't seem to work along with Vagrant. I've tested a 32bit VM without problems.

So, it seems to be a Virtualbox issue in the end.

Are there any chance of a Homestead version based on 32bit VMs?

@sveggiani It appears that Homestead is 32bit. I've nailed it down - there seems to be an issue within the Homestead box because if i open Homestead/scripts/homestead.rb and change config.vm.box = "laravel/homestead" to config.vm.box = "precise32" it works fine, just no software installed.

@daparky Homestead uses ubuntu/trusty64 which is 64 bit. See https://github.com/laravel/settler/blob/master/Vagrantfile for the vagrant file used to generate the Homestead environment.

@t-v-m You're right but when i open VirtualBox it says Ubuntu 32bit for some reason?

Maybe we need what @sveggiani says, a 32bit version.

daparky said:

@t-v-m You're right but when i open VirtualBox it says Ubuntu 32bit for some reason?

Maybe we need what @sveggiani says, a 32bit version.

Yeah thats weird, mine also says Ubuntu 32 bit but 64 bit is definitely installed.

Are you sure your processor doesn't support VT-x? If you have an intel i3, i5 or i7 it should. See here for a list of supported intel platforms - http://ark.intel.com/Products/VirtualizationTechnology

Had the same problem. It turned out that Virtualization Technology was disabled in BIOS on my notebook (HP Pavilion g6). I enabled it and now homestead is working.

t-v-m said:

daparky said:

@t-v-m You're right but when i open VirtualBox it says Ubuntu 32bit for some reason?

Maybe we need what @sveggiani says, a 32bit version.

Yeah thats weird, mine also says Ubuntu 32 bit but 64 bit is definitely installed.

Are you sure your processor doesn't support VT-x? If you have an intel i3, i5 or i7 it should. See here for a list of supported intel platforms - http://ark.intel.com/Products/VirtualizationTechnology

At home I have an i7 940XM so it supports VT-x. At work (where i'm having trouble) has an Intel Pentium CPU B960 which doesnt support VT-x.

I'm solved that, enabling cpu virtualization on BIOS Setup.

Tnx :)

Fot those of you WITHOUT a VT-x capable cpu, I got things running by changing the box to this one: antoniofrignani/laravel-homestead-settler-32.

Simply open Homestead/scripts/homestead.rb and change config.vm.box = "laravel/homestead" to config.vm.box = "antoniofrignani/laravel-homestead-settler-32".

Worked for me!

Thanks tiagosv! Additionally to what you posted, I had to vagrant destroy and vagrant up again to fix this.

I have an old machine with Pentium Dual-Core E5200, without virtualization capability, running Vista 32 and it worked!

wow! this is my new knowledge.

Thanks man. Finally got it working too with your help. Win 8.1 here, was driving me nuts..

tiagosv said:

Fot those of you WITHOUT a VT-x capable cpu, I got things running by changing the box to this one: antoniofrignani/laravel-homestead-settler-32.

Simply open Homestead/scripts/homestead.rb and change config.vm.box = "laravel/homestead" to config.vm.box = "antoniofrignani/laravel-homestead-settler-32".

Worked for me!

Definitely glad I wasn't the only one and that the solution helped others!

I have tried all of your suggested solutions, but none of them work for me :(. Does anyone has more suggestions/solutions?

MindisWorld said:

I have tried all of your suggested solutions, but none of them work for me :(. Does anyone has more suggestions/solutions?

Launching the VM via Vagrant utilizes the "headless" variant of VirtualBox (there is no graphical representation of the running VM), which can make it difficult to troubleshoot problems during boot.

What happens when you launch the VM from within VirtualBox? Does it boot-up completely (to the login prompt)? Or does it fail/halt somewhere in the process?

Thank you for your time cbj4074.

If I try to run from within VirtualBox, it loads the server without problems and showing "Running" state. But if I try to access it through the browser, it does not show up. If I try to run through CLI the server, it shows that error message. But it also boots the server somehow, because when I type "vagrant status" it shows "already running" or something like that even though those error messages were shown.

Sorry I am really not good at this. What do you mean by "to the login prompt"?

This might help....

https://gist.github.com/gamerwalt/659091e9a2f353a0e762

I use this gist to build my 32 bit box that reflects taylor's box.

https://gist.github.com/noeldiaz/0f9a2583a41579878764

I have faced the same problem. I fixed this by enabling ' Virtualization ' from BIOS setup.

I've tried all possible solutions to run default Lavavel's homestead, but it's impossible run on old 32Bit CPU.

For fix it, I've created a new homestead 32Bit, using the last version of laravel settler and ubuntu 14.04 i386 (32Bit).

Check out on github rmff/laravel-homestead-32bit

I hope this help people starting with Laravel and homestead.