VirtualBox 4.1 unable install VPS
My intentions is to get vagrant to work in VPS so that i can package images for different development environments and share among developers
I followed
And then i followed the
addgroup: The group `vboxusers' already exists as a system group. Exiting.
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Removing old VirtualBox pci kernel module [ OK ]
Trying to register the VirtualBox kernel modules using DKMS
In the logs /var/logs/vbox-install.log:
Uninstalling modules from DKMS
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxhost/4.1.24/source ->
/usr/src/vboxhost-4.1.24
DKMS: add Completed.
Kernel preparation unnecessary for this kernel. Skipping…
Building module:
cleaning build area….
make KERNELRELEASE=2.6.32-45-generic-pae -C /lib/modules/2.6.32-45-generic-pae/build M=/var/lib/dkms/vboxhost/4.1.24/build………………..
cleaning build area….
DKMS: build Completed.
vboxdrv.ko:
Running module version sanity check.
Original module
No original module exists within this kernel
Installation
Installing to /lib/modules/2.6.32-45-generic-pae/updates/dkms/
vboxnetflt.ko:
Running module version sanity check.
Original module
No original module exists within this kernel
Installation
Installing to /lib/modules/2.6.32-45-generic-pae/updates/dkms/
vboxnetadp.ko:
Running module version sanity check.
Original module
No original module exists within this kernel
Installation
Installing to /lib/modules/2.6.32-45-generic-pae/updates/dkms/
vboxpci.ko:
Running module version sanity check.
Original module
No original module exists within this kernel
Installation
Installing to /lib/modules/2.6.32-45-generic-pae/updates/dkms/
depmod….
DKMS: install Completed.
The log looks okey to me, no error messages, however. I unable to use virtualbox. If i do 'VBoxManage -v' then:
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (2.6.32-45-generic-pae) or it failed to
load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until this problem is fixed.
4.1.24r82872
Then if i run sudo /etc/init.d/vboxdrv setup and it stops with:
- Running VirtualBox in a Xen environment is not supported
How to boot in none Xen environment? ..is that going to effect my current mysql/apache services?
Thank You
6 Replies
That said, it looks like Vagrant's developers are working on making it work with other virtualization systems. Once that's done, it will probably be pretty easy to make Vagrant work with Linode directly via the API.
thanks again
ask them
Or do you mean when VirtualBox will work under Xen? It should be ready to ship by February 30th of next year.
support for other virtualization providers
@hoopycat:
For what it's worth, Vagrant 1.1 now exists, and has
. Time to start working on Linode provider support support for other virtualization providers:-)
I hear a certain other competitor has one already…
@trippeh:
I hear a certain other competitor has one already…
;)
Clarification: one of their users made a provider, nutting official or anything.