lesser-equity

Magazine
Go Back   Computer Juice > Computer Software > Linux & Alternative OS


Register


Reply
 
Thread Tools
  #1  
Old 3rd May 2009, 17:16
Member Group
 
I can't get a VM to run I keep getting an error. When I went to the site to look for info. what I found was this and I don't know what to do. At the end was when I attempted to do gcc -v.


What I Found:
  • status changed from closed to reopened.
  • resolution deleted.
What are main reasons to get the error? VERR_VM_DRIVER_NOT_INSTALLED (rc=-1908)

2009-03-13 15:08:00 changed by frank

The reason for this error message is that the kernel driver is not found. I'm sorry but didn't I tell you in my last comment what your problem is?
Your VM will not start because the VBox kernel driver cannot be loaded. Why is the driver not loaded? Because the vboxdrv module was not correctly compiled. The messages you saw (ignore the CDROM messages, they don't matter here) indicate that the kernel refuses to load the vboxdrv kernel module because the module was compiled with the wrong compiler. The kernel expects that this module will be compiled with the same compiler as the Linux kernel. Your Linux kernel was apparently compiled with gcc-3.4 but you compiled the vboxdrv kernel module with gcc-3.2.
How to resolve this problem? Make sure that
gcc -v
reports 3.4 and that the kernel will find this gcc compiler, that is, enter just gcc without any leading path. For instance, make sure that in one of the directories which is found by the PATH variable, a symlink to /opt/TWWfsw/bin/gcc is found.
Again: gcc -v must report 3.4!
Then, recompile the kernel module with /etc/init.d/vboxdrv setup. Make sure that the output of this command does not show any error message.
After this, make sure that the kernel module is actually loaded:
lsmod|grep vboxdrv
must show the vboxdrv kernel module.
If all this works, then try to start a VM. If something does not work, please attach (there is an Attach button!) the file /var/log/vbox-install.log to this defect as well as the output of dmesg.


What Happened:

Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.3.2-1ubuntu12' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu12)
  #2  
Old 18th May 2009, 18:13
Member Group
 
Fixed
Reply

Register
Thread Tools




Arabic Bulgarian Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Finnish French German Greek Hebrew Hungarian Italian Japanese Korean Latvian Lithuanian Norwegian Polish Portuguese Romanian Russian Serbian Slovak Spanish Swedish Thai Turkish Ukrainian

Copyright ©2006 - 2009 Computer Juice.

Powered by vBulletin® Copyright ©2000 - 2009 Jelsoft Enterprises Ltd. SEO by vBSEO ©2009, Crawlability, Inc.