Version 19 (modified by admin, 14 years ago) (diff)


Frequently Asked Questions (FAQ) for end users (User FAQ)

Here you can find common questions, frequently asked on the VirtualBox mailing lists and IRC channel, along with their answers. Please consult this list every time you run into a problem that is not described in the User Manual.


  • If you have switched a VM to full-screen mode and are wondering how to return to normal operation again, press your host key (usually the right control key) and "F". We'll have an according warning message box in the next release.
  • VirtualBox does not yet support 64-bit hosts. This is actively being worked on. (And no, you can't install the 32-bit version on a 64-bit host.)

Linux hosts

  • If you get a message saying "VirtualBox kernel driver not accessible, permission problem" when starting VirtualBox right after installation, make sure that your user account is listed in the vboxusers group. The installation takes care creating that group, but you will need to manually add all users to it that should be allowed to run VirtualBox. As root, for each such user, run usermod -G vboxusers -a <userid>. If any of the affected users are currently logged in, they need to log out for the changes to take effect. In case any user already attempted to start VirtualBox before logging out (which launches the VBoxSVC service process with incorrect permissions), that user additionally needs to run VirtualBox shutdown from the command line to terminate the service. This solves the permission problems. (Alternatively, a reboot will help as well.)
  • 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.
  • If USB doesn't work, check your usbfs permissions. See section 9.4.6 of the  User Manual.
  • Debian packages: 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 pre-remove (prerm) script of the package (which is executed prior to package removing or upgrading) aborts with an error "(Kernel module not found)!". In that case do the following:
    • Edit /etc/init.d/virtualbox and change line 129 from 'exit 1' to 'exit 0'
    • Reinstall the virtualbox package by 'dpkg -i <the VirtualBox package for your distribution>'. An installation failure of this package is expected.
    • Edit /var/lib/dpkg/info/virtualbox.postinst and change line 39 from 'exit 1' to 'exit 0'
    • Execute 'dpkg --configure --pending'
    • 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, as described in the User Manual (see our  Downloads section).

Windows hosts

  • 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. In the meantime you can install this test build that also fixes the problem.
  • Currently, VirtualBox only works if you have administrator rights. We are working on supporting regular user accounts.
  • Windows Vista hosts might show an error about a COM server not being accessible. This is a problem of our installation routine which we have not figured out yet. To fix the problem, open a command prompt shell and enter:
    cd \Programs\InnoTek VirtualBox
    VBoxSVC.exe /ReRegServer
    regsvr32.exe VBoxC.dll
  • If VirtualBox messes up your USB stack on Windows and you can no longer work with your USB devices, try removing VBoxUSBFlt from LowerFilters of the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}. At this time, we do not know what causes this problem and we have only had very few reports so this is just in case.

Windows Vista guests

  • Unfortunately, with Vista, Microsoft dropped support for the virtual AMD PCnet card that we are providing to virtual machines. As a result, after installation, Vista guests initially have no networking. To fix that, download  the official NDIS5 AMD driver for installation in the guest. -- However, the next problem will be how to get your Vista to access that driver file, as the guest has no networking. One possible solution is to create an ISO CD-ROM that contains it and then mount that ISO in the guest. On Linux, this can be easily done with mkisofs -o name-of-target-iso -R -J /path/to/folder/with/amd/driver/file. Alternatively, put the driver file on a USB stick and enable a corresponding USB filter for the VM.
ContactPrivacy policyTerms of Use