Vagrant Up fails with "Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only"

[Krishana Pal Chouhan]

Hi,

I have installed Vagrant 1.8.7 and VirtualBox 5.1.8-1.

I am getting following error while bringing up the VM. My setup was working previously with older versions of Virtual Box and Vagrant but it broke after that. I tried multiple uninstall and install of both Virtual Box and Vagrant but I am still getting the following error. I also deleted .vagrant.d .VirtualBox directories from Windows home directory.

----

There was an error while executing `VBoxManage`, a CLI used by Vagrant

for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "e79bfe69-b924-4940-9eaa-69a000e690db", "--type", "headless"]

Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only

Ethernet Adapter #2' (VERR_INTNET_FLT_IF_NOT_FOUND).

VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)

VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

----

Could someone please help me with this error?

[Alvaro Miranda Aguilera]

Hello

Is always good test a default box

mkdir precise64

cd precise64

vagrant init -m hashicorp/precise64

vagrant up

if this works, then could be an issue on the Vagrantifle you are using.

Can you test and share your Vagrantfile ?

It seems be an error on networks. If you can comment out the network part and test, you should be able to find whats causing this problem.

Alvaro.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/8d4ae6e4-7557-4fb6-927f-8cfb2f3ad235%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Krishana Pal Chouhan]

Hi,

Thanks for your reply.

I tested as you suggested and I still got the error. I have attached the vagrant file here for reference. Below is the error message I got.

====

There was an error while executing `VBoxManage`, a CLI used by Vagrant

for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "7764e5a8-cb60-4f6a-8120-70777f7fc559", "--type", "headless"]

Stderr: VBoxManage.exe: error: VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)

VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

====

[Alvaro Miranda Aguilera]

On Mon, Nov 7, 2016 at 8:49 AM, Krishana Pal Chouhan <kpsingh...@gmail.com> wrote:

Stderr: VBoxManage.exe: error: VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)

Hello.

This happened to be too in Dell XPS 15.

Stderr: VBoxManage.exe: error: VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)

Check if there is a BIOS update. If you feel confortable, you should apply it.

Update Virtualbox or Rollback. In my computer I had to skip one.

Basically I had Virtualization enabled on BIOS, did VirtualBox update and had the sane issue. Had to skip one version since couldnt find a better fix.

Hope this helps.

Alvaro.

--

Alvaro