VBoxManage Error at "Booting VM" stage

96 views
Skip to first unread message

Native New Yorker

unread,
Nov 26, 2019, 3:11:21 PM11/26/19
to Vagrant

Hello,


Getting a horific VBoxManage error while at Booting VM stage.
Wondering where to find help for this situation.
Do not know where to look for help.
Is this a Vagrant or VirtualBox ?
Which forum should this question be sent too?



My goal is to setup Varying Vagrant Vagrants (VVV) Wordpress Local Developmet server.


Meanwhile, successfully installed another random vagrant box and was able to run both vagrant up and vagrant ssh commands on that box,

It seems like vagrant is setup properly.

Any clues appreciated.
Thank you.


Output of VVV listed below.


antho@DESKTOP-LHRUNLM MINGW64 ~/Documents/vagrant/vvv (master)
$ vagrant up
__ __ __ __
\ V\ V\ V / Varying Vagrant Vagrants
 \_/\_/\_/  v3.2.0-git::master

Platform: platform-mingw32 windows vagrant-hostsupdater NoColour shared_db_folder_disabled , VVV Path: "C:/Users/antho/Documents/vagrant/vvv"
Vagrant: v2.2.6, VirtualBox: vN/A

Docs:       https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard:  http://vvv.test

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/bionic64' version '20191125.0.0' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "d8aa572a-8e94-4e0c-80af-8bc51a667875", "--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
 


My computer configuration

  • Operating System: Win10x64
  • Vagrant Version: 2.2.6
  • Virtual Box Version: 6.0.14 r133895 (Qt5.6.2)
###

dragon788

unread,
Nov 27, 2019, 8:37:04 AM11/27/19
to Vagrant
Check out vccw.cc for a good Wordpress Vagrant setup. Flywheel also has an interesting setup though it targets Windows/macOS and not Linux users.

Native New Yorker

unread,
Nov 27, 2019, 10:22:20 AM11/27/19
to Vagrant
Thanks for reply.

The reason I am investigating Vagrant is because I have been using Local by Flywheel for about six months now and it seems to run slowly on my PC.
I am hoping a Vagrant based solution has better performance.
What is your experience?

Already tried the solutions listed below but ironically each of them is failing at exactly the same way, which is "Booting VM" stage.
  1. Seravo
  2. VCCW
  3. VVV
So I wonder if there is something wrong with my PC's VirtualBox network setup.
How can Windows 10 networking for Virtualbox be reset to factory defaults?
I remember changing it while doing Hyper-V testing on a prior project.
Have a good weekend.

dragon788

unread,
Nov 27, 2019, 10:55:08 PM11/27/19
to Vagrant
Some of the trouble maybe because Local by Flywheel also uses Virtualbox under the hood. What you may want to try searching for is a Docker-compose WordPress setup because Docker coexists better with Hyper-V and won't conflict with Virtualbox. I have a feeling if you uninstalled and reinstalled VirtualBox it would reset the network settings.
Reply all
Reply to author
Forward
0 new messages