James E Keenan
2018-10-19 18:57:28 UTC
My colleague and I have been using Vagrant for several months to run
several VirtualBox VMs on a FreeBSD-11 host. Earlier this month, I ran
'sudo pkg upgrade' on the host. Without specifically intending to
upgrade our VirtualBox installation, I upgraded that package. In the
course of that upgrade, the attached message
(pkg-upgrade-virtual-box-messages.txt) was displayed, but I did not
immediately take any of the suggested actions.
Subsequently, when I next went to enter the VM with 'vagrant up &&
vagrant ssh' -- which I had used many times before -- I got the
following error message:
#####
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "bb3f2c1d-15c1-4020-95ec-9d809211b4ab", "--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 know that the VM itself is still operating as expected, as a cron job
it runs transmits an email once a day. But I will need to go into the
VM in a few days to work with the results of an important monthly cron
job. The regular sysadmin for the host is unavailable, so we have to
figure out how to proceed.
Based on the message I got during 'pkg upgrade' with respect to
virtualbox, and on a reading of the FreeBSD wiki page at
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/virtualization-host-virtualbox.html,
I believe that what we ought to do is the following:
##########
1. Add the following 3 lines to /boot/loader.conf:
#####
vboxdrv_load="YES"
vboxguest_enable="YES"
vboxservice_enable="YES"
#####
2. Reboot the host:
#####
sudo shutdown -r now
#####
3. Run 'vagrant up' for each of the VMs we have installed on the host.
##########
Do those steps sound reasonable?
Thank you very much.
Jim Keenan
--
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+***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/f63c8501-abb8-eb4e-bc1e-8adda259dfa4%40pobox.com.
For more options, visit https://groups.google.com/d/optout.
several VirtualBox VMs on a FreeBSD-11 host. Earlier this month, I ran
'sudo pkg upgrade' on the host. Without specifically intending to
upgrade our VirtualBox installation, I upgraded that package. In the
course of that upgrade, the attached message
(pkg-upgrade-virtual-box-messages.txt) was displayed, but I did not
immediately take any of the suggested actions.
Subsequently, when I next went to enter the VM with 'vagrant up &&
vagrant ssh' -- which I had used many times before -- I got the
following error message:
#####
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "bb3f2c1d-15c1-4020-95ec-9d809211b4ab", "--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 know that the VM itself is still operating as expected, as a cron job
it runs transmits an email once a day. But I will need to go into the
VM in a few days to work with the results of an important monthly cron
job. The regular sysadmin for the host is unavailable, so we have to
figure out how to proceed.
Based on the message I got during 'pkg upgrade' with respect to
virtualbox, and on a reading of the FreeBSD wiki page at
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/virtualization-host-virtualbox.html,
I believe that what we ought to do is the following:
##########
1. Add the following 3 lines to /boot/loader.conf:
#####
vboxdrv_load="YES"
vboxguest_enable="YES"
vboxservice_enable="YES"
#####
2. Reboot the host:
#####
sudo shutdown -r now
#####
3. Run 'vagrant up' for each of the VMs we have installed on the host.
##########
Do those steps sound reasonable?
Thank you very much.
Jim Keenan
--
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+***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/f63c8501-abb8-eb4e-bc1e-8adda259dfa4%40pobox.com.
For more options, visit https://groups.google.com/d/optout.