VirtualBox

Changes between Version 11 and Version 12 of Knowledge Base


Ignore:
Timestamp:
Jan 16, 2007 12:10:51 PM (17 years ago)
Author:
jose
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Knowledge Base

    v11 v12  
    77 * Linux hosts: When the kernel module doesn't load, i.e. you get an '''"Error inserting vboxdrv: Invalid argument",''' check (as root) the output of the "dmesg" command. In 90% of all cases, this is a problem with Linux 2.6.19 and higher, and the message will be: "NMI watchdog active -- refused to load the kernel module! Please disable the NMI watchdog by specifying 'nmi_watchdog=0' at kernel command line." Add this option to your grub configuration, reboot, and the module should load.
    88
     9 * Linux hosts, Debian packets: If the installation of the VirtualBox_*.deb package was not successful because the compilation of the kernel module fails, it might not be possible to remove the package nor to install other packages as the prerm method of the package aborts with an error "(Kernel module not found)...fail!". In that case do the following:
     10   * Edit /etc/init.d/virtualbox and change line 129 from 'exit 1' to 'exit 0'
     11   * Reinstall the virtualbox package by 'dpkg -i <the VirtualBox package for your distribution>'. An installation failure of this package is expected.
     12   * Edit /var/lib/dpkg/info/virtualbox.postinst and change line 39 from 'exit 1' to 'exit 0'
     13   * Execute 'dpkg --configure --pending'
     14   * The package should now be installed successfully. However, the kernel module is still not compiled. Before you will be able to execute VirtualBox you have to create a kernel module for your current kernel.
     15
    916 * '''Windows 2000 hosts:''' Unfortunately a bug slipped into !VirtualBox 1.3.2 that prevents it from executing on Windows 2000 hosts. This will be fixed in the next release. (Windows 2000 guests still work.)

© 2023 Oracle
ContactPrivacy policyTerms of Use