The host machine is running Windows 10 Pro Insider Preview (build 10074).
I'm trying to set up a Laravel development environment using Laravel Homestead (github: laravel/homestead) which is a preconfigured vagrant box. However, when doing so, I get the following error:
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'laravel/homestead' 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", "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've attached the VBoxStartup log. Please let me know what other information you may require.
Yes... but it won't be this-week's-edition-of-broken-TP.
Anyway, if people have problems with Windows 10, they need to complain to Microsoft, not to us. Windows 10 is changing too fast to keep up with, and there is no business justification to spend a lot of time on a preview OS that is timebombed and will change in many unpredictable ways before actual release.
michaln wrote:
Anyway, if people have problems with Windows 10, they need to complain to Microsoft, not to us. Windows 10 is changing too fast to keep up with, and there is no business justification to spend a lot of time on a preview OS that is timebombed and will change in many unpredictable ways before actual release.
I couldn't agree more.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
Well actually after long digging in I had found solution for current windows 10 (build 10074).
So to achieve working virtualbox with vagrant you will need follow those steps:
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
3)install vagrant(1.7.2) and install VirtualBox-5.0.0_BETA2-99573-Win.exe to got newest host only driver (v5).
4)install on top of virtualbox v5 VirtualBox-4.3.6-91406-Win.exe
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"
And if you need to create new host only driver do it in your way and not afraid of host-only error just after you receive it repeat 5th step and remember that all this needs to be done in built-in admin.
Hope this helps someone and vitrualbox team can get some clue where problems happens.
I don't think someone understands what it means that we don't support Vagrant. It also means there isn't any point for VirtualBox to figure out what works and doesn't work with Vagrant.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
FWIW, I didn't mean that to sound condescending, it's hard for me to express what I want to say because I hate typing.
I guess what I was trying to say is, if users want to try to employ Vagrant they are certainly free to do so. However, they are on their own to try and get it working. As far as I know, Oracle/VirtualBox has no plans to support Vagrant.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
Its not only for vagrant. If as host is used windoes 10 then to get working host-only functionality its what need to be done, just skip all vagrant stuff and you got working host-only adapter for whatever reason you need. And all what depends on vagrant works the only problem is windows 10 that had changing some protection on network side + I dont ask you to fix anything until windows 10 is finished I just hoped it could be usefull to someone what I had found.
This, as in Windows 10? When Windows 10 gets released in its final form, and Virtualbox developers get that final form to program for, then Windows 10 will work well with Virtualbox.
This, as in the "Laravel development environment....preconfigured vagrant box"? Users of Vagrant guests will have to ask Vagrant or Laravel how to get the guests to run, since Vagrant changes Virtualbox beyond the developers' design, so there's no support for Vagrant in the Virtualbox forum, unless someone who happens to know comes along. Might take a while, though, so it's better to ask Vagrant.
