VirtualBox

Changes between Version 98 and Version 99 of User_FAQ


Ignore:
Timestamp:
Jan 23, 2009 2:00:22 PM (15 years ago)
Author:
Michael Thayer
Comment:

Updated information about USB and added information on dkms

Legend:

Unmodified
Added
Removed
Modified
  • User_FAQ

    v98 v99  
    1010
    1111== General ==
    12 
    13  * ping does not work with !VirtualBox NAT networking
    14 
    15  !VirtualBox's implementation of NAT networking is done entirely in user space.  This means in particular that it has no way of passing on the ICMP IP packets which are used by the ping command from the guest, as these require special privileges to send from the host.  The upshot of this is that you can't ping anything outside the local 10.0.2.x subnet from a NATed guest.
    1612
    1713 * Sometimes !VirtualBox fails to start with a message on the lines of
     
    3228== Linux hosts ==
    3329
     30 * Problems with network interfaces after installing or rebuilding the !VirtualBox drivers: this is likely to be caused by a problem in the dkms tool.  You can work around this by changing the line
     31{{{
     32/sbin/udevadm trigger
     33}}}
     34 in the dkms script (/usr/sbin/dkms on Ubuntu) to
     35{{{
     36true
     37}}}
     38
    3439 * '''dkms status''' fails after !VirtualBox was removed (deb/rpm): The !VirtualBox 1.6.0 and 1.6.2 packages did not properly de-register from dkms during uninstallation. To work around this problem do
    3540{{{
     
    4348}}}
    4449
    45  * '''USB on Ubuntu/Gutsy''': Ubuntu removed support for `/proc/bus/usb/*`. We will address this issue in the future. Until this, edit the script `/etc/init.d/mountdevsubfs.sh and activate the four lines around line 40 (Magic to make /proc/bus/usb work). Then execute
    46 {{{
    47 /etc/init.d/mountdevsubfs.sh start
    48 }}}
    49   From now on, there should be a directory `/proc/bus/usb/` and the device entries below should be accessible by any user.
    50 
    51  * '''USB on Ubuntu/Intrepid''': Finally, the Ubuntu guys completely removed these lines. So you have to manually add them again:
    52 {{{
    53 mkdir -p /dev/bus/usb/.usbfs
    54 domount usbfs "" /dev/bus/usb/.usbfs usbfs -obusmode=0700,devmode=0600,listmode=0644
    55 ln -s .usbfs/devices /dev/bus/usb/devices
    56 mount --rbind /dev/bus/usb /proc/bus/usb
    57 }}}
    58   Add these lines to at the end of the `start()` function of `/etc/init.d/mountdevsubfs.sh`.[[BR]]
    59   Note that the '''udev permissions''' for the USB devices are still used. For instance, to access a USB disk you have to be member of the group `disk`. Execute
    60 {{{
    61 /bin/ls -l /proc/bus/usb/*/*
    62 }}}
    63   and check if you have '''write access''' to all desired USB devices.[[BR]][[BR]]
    64   If you want to make all USB devices available for users member of the vboxusers group, apply the proposed change for '''USB on openSUSE'''.
    65 
    66  * '''USB on openSUSE''': Add the following entry to `/etc/fstab`:
    67 {{{
    68 none  /proc/bus/usb  usbfs  auto,busgid=XXX,busmode=0775,devgid=XXX,devmode=0664  0  0
    69 }}}
    70   Replace `XXX` by the group ID of the group vboxusers. You can determine this value by executing
    71 {{{
    72 grep vboxusers /etc/group
    73 }}}
    74   Of course, the current user should be member of that group. After the next reboot, there should be a directory `/proc/bus/usb/` and the device entries below should be accessible by any user of the `vboxusers` group.
    75 
    76  * If '''USB doesn't work,''' check your usbfs permissions. See "Troubleshooting" -> "Linux hosts" in the [wiki:"Downloads" User Manual] for a solution.
     50 * USB: if you are having trouble accessing USB devices in a guest, make sure that you are a member of the '''vboxusers''' system group.
    7751
    7852 * '''Tickless Linux timer''': !VirtualBox currently does not work well on Linux kernels with tickless timer support (CONFIG_NO_HZ enabled). We are investigating the problem but in the meantime you should disable the tickless timer by disabling that config option or by adding '''nohz=off''' to the Linux kernel command line.[[BR]]

© 2023 Oracle
ContactPrivacy policyTerms of Use