Hi,
I used to have a working vagrant environment, but I must have done
something stupid because now whenever I run vagrant up for any given VM, I
get this:
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 8000 (guest) => 8000 (host) (adapter 1)
default: 9001 (guest) => 9001 (host) (adapter 1)
default: 22 (guest) => 2200 (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", "20655eb4-a2ba-4572-80d6-62298b22152f", "--type",
"headless"]
Stderr: VBoxManage: error: The VMMR0.r0 module version does not match
VBoxVMM.dll/so/dylib. If you just upgraded VirtualBox, please terminate all
VMs and make sure that neither VBoxNetDHCP nor VBoxNetNAT is running. Then
try again. If this error persists, try re-installing VirtualBox.
(VERR_VMM_R0_VERSION_MISMATCH)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
ConsoleWrap, interface IConsole
I tried installing / reinstalling Virtualbox (5.0.24) and upgraded Vagrant
from 1.8.1 to 1.8.5. Host system is Ubuntu 16.04 and the guest also is some
Ubuntu image.
No idea what changed exactly since it last worked. The only thing that
comes to mind is that I tried to create a new project using the Docker
provider for the first time (which did not succeed), and now when I do
"vagrant global-status" that thing seems to hang around for no reason:
$ vagrant global-status
id name provider state directory
---------------------------------------------------------------------------------------
5f24293 default virtualbox poweroff /home/markus/public_html/project1
8d248ad default virtualbox poweroff /home/markus/public_html/project2
a23d8d2 default virtualbox poweroff /home/markus/public_html/project3
c74ad20 default docker running /home/markus/public_html/project5
9c9ccaf default virtualbox poweroff /home/markus/public_html/project4
9df3fe5 default virtualbox poweroff /home/markus/public_html/project6
Can't destroy that docker container either:
$ vagrant destroy c74ad20
==> default: The container hasn't been created yet.
/home/mwolff/public_html/evercare/siss/trunk/siss/Vagrantfile:5: warning:
already initialized constant VAGRANTFILE_API_VERSION
/home/mwolff/public_html/evercare/siss/trunk/siss/Vagrantfile:5: warning:
previous definition of VAGRANTFILE_API_VERSION was here
So, yeah, that's strange - but no idea if that's even related to my much
more pressing problem above.
Anyone got any ideas? Any hint is appreciated...
Regards,
Markus
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/4ef8f514-e328-4766-8395-a5c6f1eba068%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
