VirtualBox

Changes between Version 55 and Version 56 of User_FAQ


Ignore:
Timestamp:
10/20/2007 03:20:25 PM (15 years ago)
Author:
achimha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • User_FAQ

    v55 v56  
    1010 
    1111== General == 
    12  
    13  * Starting with 1.4.0, !VirtualBox now supports '''64-bit Linux hosts'''. 64-bit Windows hosts are not yet supported; this is being worked on. Also, 64-bit guest operating systems are generally not supported. 
    1412 
    1513 * Sometimes VirtualBox fails to start with a message on the lines of  
     
    4240 * If the kernel module refuses to load with a message saying '''"Error inserting vboxdrv: Invalid argument",''' check (as root) the output of the "dmesg" command, and see "Troubleshooting" -> "Linux hosts" in the [wiki:"Downloads" User Manual] for solutions. 
    4341 
    44  * Host interface networking with dynamic TAP interfaces does not work with !VirtualBox versions 1.3.8 and earlier on Linux kernels 2.6.18 and newer. Please update to !VirtualBox version 1.4.0, where this was fixed. 
    45  
    4642 * If '''USB doesn't work,''' check your usbfs permissions. See "Troubleshooting" -> "Linux hosts" in the [wiki:"Downloads" User Manual] for a solution. 
    4743 
    48  * When installing from a Debian/Ubuntu package, the installation script will ask the user to accept the [wiki:"VirtualBox_PUEL" VirtualBox Personal Use and Evaluation License (PUEL)] one time. Accepting this license is necessary to install this package. Some Debian/Ubuntu systems have selected the '''non-interactive debconf frontend'''. The license dialog can not be displayed on these systems and the package will refuse to install itself. The recommended debconf frontend is either '''GNOME''' or '''KDE''' which can be selected using 
    49 {{{ 
    50 dpkg-reconfigure debconf 
    51 }}} 
    52   executed as root. Some systems use the '''dialog''' frontend which is acceptable as well. Note that to accept the license with this frontend, the user has to use the tabulator key to switch to 'Yes'. Clicking with mouse will not work. This is a limitation of this specific debconf frontend. 
    53  
    5444== Windows hosts == 
    55  
    56  * Currently, !VirtualBox only works if you have administrator rights. We are working on supporting regular user accounts. 
    5745 
    5846 * 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: 
     
    6351}}} 
    6452 
    65  * If a !VirtualBox version before 1.4.0 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: 
    66 {{{ 
    67 HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}  
    68 }}} 
    69  The problem was fixed with !VirtualBox 1.4.0. 
    70  
    7153== Windows Vista guests == 
    7254 
    7355 * There is no networking in Windows Vista guests initially because, unfortunately, with Vista, Microsoft dropped driver support for the virtual AMD PCnet card that we are providing. See "Troubleshooting" -> "Windows guests" in the [wiki:"Downloads" User Manual] for a solution. 
    74    The !VirtualBox Guest Additions of version 1.4.0 contain the AMD PCnet driver. 
     56   The !VirtualBox Guest Additions contain the AMD PCnet driver. 
    7557 
    7658== High CPU load while running Windows 98 == 
     
    8062== Linux guests == 
    8163 
    82  * The !VirtualBox 1.4.0 Guest Additions do not work out of the box with Fedora 7 guests.  Before you install the Additions, add the following lines to your Fedora 7 guest's /etc/X11/xorg.conf file: 
    83 {{{ 
    84 Section "ServerFlags" 
    85         Option      "Xinerama" "true" 
    86 EndSection 
    87 }}} 
    88  * Mouse in PCLinuxOS: Look at /etc/X11/xorg.conf for the !ServerLayout section and comment out the following line: 
    89 {{{ 
    90 InputDevice "Mouse2" "SendCoreEvents" 
    91 }}} 
    92 After restarting the X server, the mouse should work fine. 
    93  
    94 This problem was fixed with !VirtualBox 1.5.0. 

www.oracle.com
ContactPrivacy policyTerms of Use