From owner-svn-doc-all@FreeBSD.ORG Thu Feb 28 15:40:57 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DEFD9D8D; Thu, 28 Feb 2013 15:40:57 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id CB985CC9; Thu, 28 Feb 2013 15:40:57 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r1SFevBf046211; Thu, 28 Feb 2013 15:40:57 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r1SFevU4046210; Thu, 28 Feb 2013 15:40:57 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201302281540.r1SFevU4046210@svn.freebsd.org> From: Dru Lavigne Date: Thu, 28 Feb 2013 15:40:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r41062 - head/en_US.ISO8859-1/books/handbook/virtualization X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 15:40:57 -0000 Author: dru Date: Thu Feb 28 15:40:57 2013 New Revision: 41062 URL: http://svnweb.freebsd.org/changeset/doc/41062 Log: This is a minor content fixup as much work is needed in this chapter. This patch addresses the following: - minor rewording for "you" - fix xref and guimenuitem tags (need to review ulinks) - enforce consistency in app names - note on vbox 4.0.0 removed as this port hasn't been less than this version for 22 months Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml Thu Feb 28 13:17:34 2013 (r41061) +++ head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml Thu Feb 28 15:40:57 2013 (r41062) @@ -66,23 +66,23 @@ - Understand the basics of &unix; and &os; (). + Understand the basics of &unix; + and &os;. - Know how to install &os; (). + Know how to install + &os;. - Know how to set up your network connection (). + Know how to set up a + network connection. - Know how to install additional third-party - software (). + Know how to install additional + third-party software. @@ -91,7 +91,7 @@ &os; as a Guest OS - Parallels on MacOS + <application>Parallels</application> on &macos; X Parallels Desktop for &mac; is a commercial software product available for &intel; based @@ -104,8 +104,8 @@ Installing &os; on Parallels/&macos; X - The first step in installing &os; on &macos; - X/Parallels is to create a new + The first step in installing &os; on + Parallels is to create a new virtual machine for installing &os;. Select &os; as the Guest OS Type when prompted: @@ -116,8 +116,8 @@ - And choose a reasonable amount of disk and memory - depending on your plans for this virtual &os; instance. + Choose a reasonable amount of disk and memory + depending on the plans for this virtual &os; instance. 4GB of disk space and 512MB of RAM work well for most uses of &os; under Parallels: @@ -174,16 +174,16 @@ - After your &os; virtual machine has been created, you - will need to install &os; on it. This is best done with an - official &os; CDROM or with an ISO image downloaded from an - official FTP site. When you have the appropriate ISO image - on your local &mac; filesystem or a CDROM in your &mac;'s CD - drive, click on the disc icon in the bottom right corner of - your &os; Parallels window. This - will bring up a window that allows you to associate the - CDROM drive in your virtual machine with an ISO file on disk - or with your real CDROM drive. + After the &os; virtual machine has been created, &os; + can be installed on it. This is best done with an + official &os; CD/DVD or with an ISO image downloaded from an + official FTP site. Copy the appropriate ISO image to the + local &mac; filesystem or insert a CD/DVD in the &mac;'s CD + drive. Click on the disc icon in the bottom right corner of + the &os; Parallels window. This + will bring up a window that can be used to associate the + CDROM drive in the virtual machine with the ISO file on disk + or with the real CDROM drive. @@ -191,12 +191,10 @@ - Once you have made this association with your CDROM - source, reboot your &os; virtual machine as normal by - clicking the reboot icon. - Parallels will reboot with a - special BIOS that first checks if you have a CDROM just as a - normal BIOS would do. + Once this association with the CDROM source has been + made, reboot the &os; virtual machine by clicking the reboot + icon. Parallels will reboot with + a special BIOS that first checks if there is a CDROM. @@ -205,10 +203,9 @@ In this case it will find the &os; installation media - and begin a normal sysinstall - based installation as described in . You may install, but do not attempt - to configure X11 at this time. + and begin a normal &os; installation. Perform the + installation, but do not attempt to configure + &xorg; at this time. @@ -216,8 +213,8 @@ - When you have finished the installation, reboot into - your newly installed &os; virtual machine. + When the installation is finished, reboot into the + newly installed &os; virtual machine. @@ -227,7 +224,8 @@ - Configuring &os; on &macos; X/Parallels + Configuring &os; on + <application>Parallels</application> After &os; has been successfully installed on &macos; X with Parallels, there are a @@ -248,35 +246,32 @@ kern.hz=100 Without this setting, an idle &os; - Parallels guest - OS will use roughly 15% of the CPU of a single - processor &imac;. After this change the usage will be - closer to a mere 5%. + Parallels guest will use + roughly 15% of the CPU of a single process &imac;. + After this change the usage will be closer to 5%. Create a New Kernel Configuration File - You can remove all of the SCSI, FireWire, and USB - device drivers. Parallels - provides a virtual network - adapter used by the &man.ed.4; driver, so - all other network devices except for - &man.ed.4; and &man.miibus.4; can be - removed from the kernel. + All of the SCSI, FireWire, and USB device drivers + can be removed from a custom kernel configuration file. + Parallels provides a virtual + network adapter used by the &man.ed.4; driver, so all + network devices except for &man.ed.4; and &man.miibus.4; + can be removed from the kernel. Configure Networking - The most basic networking setup involves simply - using DHCP to connect your virtual machine to the same - local area network as your host &mac;. This can be - accomplished by adding + The most basic networking setup uses DHCP to connect + the virtual machine to the same local area network as + the host &mac;. This can be accomplished by adding ifconfig_ed0="DHCP" to /etc/rc.conf. More advanced - networking setups are described in - . + networking setups are described in . @@ -592,26 +587,27 @@ xenbr1 8000.feffffffffff no --> - Virtual PC on &windows; + <application>Virtual PC</application> on + &windows; Virtual PC for &windows; is a µsoft; software product available for free download. - See system requirements. Once Virtual PC has been installed on µsoft.windows;, - the user must configure a virtual machine and then install + the user can configure a virtual machine and then install the desired guest operating system. - Installing &os; on Virtual - PC/µsoft.windows; + Installing &os; on <application>Virtual + PC</application> The first step in installing &os; on - µsoft.windows; /Virtual PC - is to create a new virtual machine for - installing &os;. Select Create a virtual - machine when prompted: + Virtual PC is to create a new + virtual machine for installing &os;. Select + Create a virtual machine when + prompted: @@ -625,7 +621,7 @@ xenbr1 8000.feffffffffff no - And select Other as the + Select Other as the Operating system when prompted: @@ -636,10 +632,9 @@ xenbr1 8000.feffffffffff no Then, choose a reasonable amount of disk and memory - depending on your plans for this virtual &os; - instance. 4GB of disk space and 512MB of RAM work well - for most uses of &os; under - Virtual PC: + depending on the plans for this virtual &os; instance. + 4GB of disk space and 512MB of RAM work well for most uses + of &os; under Virtual PC: @@ -661,7 +656,7 @@ xenbr1 8000.feffffffffff no - Select your &os; virtual machine and click + Select the &os; virtual machine and click Settings, then set the type of networking and a network interface: @@ -677,18 +672,18 @@ xenbr1 8000.feffffffffff no - After your &os; virtual machine has been created, you - will need to install &os; on it. This is best done with an - official &os; CDROM or with an ISO image downloaded from an - official FTP site. When you have the appropriate ISO image - on your local &windows; filesystem or a CDROM in your CD - drive, double click on your &os; virtual machine to boot. - Then, click CD and choose - Capture ISO Image... on + After the &os; virtual machine has been created, &os; + can be installed on it. This is best done with an + official &os; CD/DVD or with an ISO image downloaded from an + official FTP site. Copy the appropriate ISO image to the + local &windows; filesystem or insert a CD/DVD in the CD + drive, then double click on the &os; virtual machine to + boot. Then, click CD and choose + Capture ISO Image... on the Virtual PC window. This will - bring up a window that allows you to associate the CDROM - drive in your virtual machine with an ISO file on disk or - with your real CDROM drive. + bring up a window where the CDROM drive in the virtual + machine can be associated with an ISO file on disk or + with the real CDROM drive. @@ -702,13 +697,11 @@ xenbr1 8000.feffffffffff no - Once you have made this association with your CDROM - source, reboot your &os; virtual machine as normal by - clicking the Action and - Reset. + Once this association with the CDROM source has been + made, reboot the &os; virtual machine by clicking + Action and Reset. Virtual PC will reboot with a - special BIOS that first checks if you have a CDROM just as a - normal BIOS would do. + special BIOS that first checks for a CDROM. @@ -717,10 +710,9 @@ xenbr1 8000.feffffffffff no In this case it will find the &os; installation media - and begin a normal sysinstall - based installation as described in - . You may install, but do not - attempt to configure X11 at this time. + and begin a normal &os; installation. Continue with the + installation, but do not attempt to configure + &xorg; at this time. @@ -728,9 +720,9 @@ xenbr1 8000.feffffffffff no - When you have finished the installation, remember to - eject CDROM or release ISO image. Finally, reboot into your - newly installed &os; virtual machine. + When the installation is finished, remember to eject + the CD/DVD or release the ISO image. Finally, reboot into + the newly installed &os; virtual machine. @@ -740,8 +732,8 @@ xenbr1 8000.feffffffffff no - Configuring &os; on µsoft.windows;/Virtual - PC + Configuring &os; on <application>Virtual + PC</application> After &os; has been successfully installed on µsoft.windows; with Virtual PC @@ -755,9 +747,9 @@ xenbr1 8000.feffffffffff no The most important step is to reduce the tunable to reduce the CPU - utilization of &os; under the - Virtual PC environment. - This is accomplished by adding the following line to + utilization of &os; under the Virtual + PC environment. This is accomplished + by adding the following line to /boot/loader.conf: kern.hz=100 @@ -765,55 +757,57 @@ xenbr1 8000.feffffffffff no Without this setting, an idle &os; Virtual PC guest OS will use roughly 40% of the CPU of a single processor - computer. After this change the usage will be - closer to a mere 3%. + computer. After this change, the usage will be + closer to 3%. Create a New Kernel Configuration File - You can remove all of the SCSI, FireWire, and USB - device drivers. Virtual PC - provides a virtual network adapter used by the - &man.de.4; driver, so all other network devices except - for &man.de.4; and &man.miibus.4; can be removed from - the kernel. + All of the SCSI, FireWire, and USB device drivers + can be removed from a custom kernel configuration file. + Virtual PC provides a virtual + network adapter used by the &man.de.4; driver, so all + network devices except for &man.de.4; and &man.miibus.4; + can be removed from the kernel. Configure Networking - The most basic networking setup involves simply - using DHCP to connect your virtual machine to the same - local area network as your host µsoft.windows;. - This can be accomplished by adding - ifconfig_de0="DHCP" to + The most basic networking setup uses DHCP to connect + the virtual machine to the same local area network as + the µsoft.windows; host. This can be accomplished + by adding ifconfig_de0="DHCP" to /etc/rc.conf. More advanced - networking setups are described in - . + networking setups are described in . - VMware on MacOS + <application>VMware Fusion</application> on + &macos; VMware Fusion for &mac; is a commercial software product available for &intel; based &apple; &mac; computers running &macos; 10.4.9 or higher. &os; is a fully supported guest operating system. Once VMware Fusion has been - installed on &macos; X, the user must configure a virtual + installed on &macos; X, the user can configure a virtual machine and then install the desired guest operating system. - Installing &os; on VMware/&macos; X + Installing &os; on <application>VMware + Fusion</application> - The first step is to start VMware Fusion, the Virtual - Machine Library will load. Click "New" to create the - VM: + The first step is to start VMware + Fusion which will load the Virtual + Machine Library. Click New to + create the virtual machine: @@ -821,8 +815,8 @@ xenbr1 8000.feffffffffff no - This will load the New Virtual Machine Assistant to help - you create the VM, click Continue to proceed: + This will load the New Virtual Machine Assistant. Click + Continue to proceed: @@ -831,11 +825,10 @@ xenbr1 8000.feffffffffff no Select Other as the - Operating System and + Operating System and either &os; or - &os; 64-bit, depending on if - you want 64-bit support, as the Version - when prompted: + &os; 64-bit, as the + Version when prompted: @@ -843,8 +836,8 @@ xenbr1 8000.feffffffffff no - Choose the Name of the VM Image and the Directory where - you would like it saved: + Choose the name of the virtual machine and the directory + where it should be saved: @@ -852,8 +845,8 @@ xenbr1 8000.feffffffffff no - Choose the size of the Virtual Hard Disk for the - VM: + Choose the size of the Virtual Hard Disk for the virtual + machine: @@ -861,8 +854,8 @@ xenbr1 8000.feffffffffff no - Choose the method you would like to install the VM, - either from an ISO image or from a CD: + Choose the method to install the virtual machine, + either from an ISO image or from a CD/DVD: @@ -870,7 +863,8 @@ xenbr1 8000.feffffffffff no - Once you click Finish, the VM will boot: + Click Finish and the virtual + machine will boot: @@ -878,8 +872,7 @@ xenbr1 8000.feffffffffff no - Install &os; like you normally would, or by following - the directions in : + Install &os; as usual: @@ -887,12 +880,14 @@ xenbr1 8000.feffffffffff no - Once the install is complete you can modify the settings - of the VM, such as Memory Usage: + Once the install is complete, the settings + of the virtual machine can be modified, such as memory + usage: - The System Hardware settings of the VM cannot be - modified while the VM is running. + The System Hardware settings of the virtual machine + cannot be modified while the virtual machine is + running. @@ -901,7 +896,8 @@ xenbr1 8000.feffffffffff no - The number of CPUs the VM will have access to: + The number of CPUs the virtual machine will have access + to: @@ -909,9 +905,9 @@ xenbr1 8000.feffffffffff no - The status of the CD-Rom Device. Normally you can - disconnect the CD-Rom/ISO from the VM if you will not be - needing it anymore. + The status of the CDROM device. Normally the + CD/DVD/ISO is disconnected from the virtual machine when it + is no longer needed. @@ -919,14 +915,15 @@ xenbr1 8000.feffffffffff no - The last thing to change is how the VM will connect to - the Network. If you want to allow connections to the VM - from other machines besides the Host, make sure you choose - the Connect directly to the physical network - (Bridged). Otherwise Share the + The last thing to change is how the virtual machine will + connect to the network. To allow connections to the virtual + machine from other machines besides the host, choose + Connect directly to the physical network + (Bridged). Otherwise, Share the host's internet connection (NAT) is - preferred so that the VM can have access to the Internet, - but the network cannot access the VM. + preferred so that the virtual machine can have access to the + Internet, but the network cannot access the virtual + machine. @@ -934,17 +931,18 @@ xenbr1 8000.feffffffffff no - After you have finished modifying the settings, boot the - newly installed &os; virtual machine. + After modifying the settings, boot the newly installed + &os; virtual machine. - Configuring &os; on &macos; X/VMware + Configuring &os; on <application>VMware + Fusion</application> After &os; has been successfully installed on &macos; X - with VMware, there are a number - of configuration steps that can be taken to optimize the - system for virtualized operation. + with VMware Fusion, there are a + number of configuration steps that can be taken to optimize + the system for virtualized operation. @@ -953,40 +951,40 @@ xenbr1 8000.feffffffffff no The most important step is to reduce the tunable to reduce the CPU utilization of &os; under the - VMware environment. This is - accomplished by adding the following line to + VMware Fusion environment. + This is accomplished by adding the following line to /boot/loader.conf: kern.hz=100 Without this setting, an idle &os; - VMware guest - OS will use roughly 15% of the CPU of a single - processor &imac;. After this change the usage will be - closer to a mere 5%. + VMware Fusion guest will use + roughly 15% of the CPU of a single processor &imac;. + After this change, the usage will be closer to + 5%. Create a New Kernel Configuration File - You can remove all of the FireWire, and USB device - drivers. VMware provides a + All of the FireWire, and USB device drivers can be + removed from a custom kernel configuration file. + VMware Fusion provides a virtual network adapter used by the &man.em.4; driver, - so all other network devices except for &man.em.4; can - be removed from the kernel. + so all network devices except for &man.em.4; can be + removed from the kernel. Configure Networking - The most basic networking setup involves simply - using DHCP to connect your virtual machine to the - same local area network as your host &mac;. This - can be accomplished by adding + The most basic networking setup uses DHCP to connect + the virtual machine to the same local area network as + the host &mac;. This can be accomplished by adding ifconfig_em0="DHCP" to /etc/rc.conf. More advanced - networking setups are described in - . + networking setups are described in . @@ -1000,23 +998,23 @@ xenbr1 8000.feffffffffff no - Clipboard sharing + Clipboard sharing. - Mouse pointer integration + Mouse pointer integration. - Host time synchronization + Host time synchronization. - Window scaling + Window scaling. - Seamless mode + Seamless mode. @@ -1026,7 +1024,8 @@ xenbr1 8000.feffffffffff no First, install the emulators/virtualbox-ose-additions - package in the &os; guest. + package or port in the &os; guest. This will install + the port: &prompt.root; cd /usr/ports/emulators/virtualbox-ose-additions && make install clean @@ -1036,14 +1035,15 @@ xenbr1 8000.feffffffffff no vboxguest_enable="YES" vboxservice_enable="YES" - If &man.ntpd.8; or &man.ntpdate.8; will be used, host time + If &man.ntpd.8; or &man.ntpdate.8; is used, host time synchronization should be disabled: vboxservice_flags="--disable-timesync" - The vboxvideo_drv should be recognized - by Xorg -configure. If not, modify - xorg.conf for the + The vboxvideo driver should be + automatically recognized by Xorg + -configure. If not, modify + /etc/X11/xorg.conf for the &virtualbox; video card: Section "Device" @@ -1058,15 +1058,16 @@ vboxservice_enable="YES" - To use vboxmouse_drv, adjust the mouse - section in your xorg.conf: + To use the vboxmouse driver, adjust the + mouse section in + /etc/X11/xorg.conf: Section "InputDevice" Identifier "Mouse0" Driver "vboxmouse" EndSection - HAL users should create this file at + HAL users should create the following /usr/local/etc/hal/fdi/policy/90-vboxguest.fdi or copy it from /usr/local/share/hal/fdi/policy/10osvendor/90-vboxguest.fdi: @@ -1107,45 +1108,39 @@ EndSection - &os; as a Host OS + &os; as a Host For a number of years, &os; was not officially supported as - a host OS by any of the available virtualization solutions. - Some people were using older and mostly obsolete versions of - VMware (like - emulators/vmware3), which - utilized the &linux; binary compatibility layer. Shortly after - the release of &os; 7.2, Sun's + a host operating system by any of the available virtualization + solutions. Shortly after the release of &os; 7.2, &oracle; &virtualbox; appeared in the Ports Collection as a native &os; program. &virtualbox; is an actively developed, complete virtualization package, that is available for most operating systems including &windows;, &macos;, &linux; - and &os;. It is equally capable at running &windows; or &unix; - like guests. It is released as open source software, but with - closed-source components available in a separate extension pack. - These components include support for USB 2.0 devices, among - others. More information may be found on the - Downloads page of the - &virtualbox; wiki, at . + and &os;. It is equally capable of running &windows; or + &unix;-like guests. It is released as open source software, but + with closed-source components available in a separate extension + pack. These components include support for USB 2.0 devices. + More information may be found on the + Downloads page of the + &virtualbox; wiki. Currently, these extensions are not available for &os;. Installing &virtualbox; &virtualbox; is available as a - &os; port in - emulators/virtualbox-ose. - As &virtualbox; is very actively developed, make sure your - ports tree is up to date before installing. Install using - these commands: + &os; package or port in emulators/virtualbox-ose. The + port can be installed using these commands: &prompt.root; cd /usr/ports/emulators/virtualbox-ose &prompt.root; make install clean - One useful option in the configuration dialog is the + One useful option in the port's configuration menu is the GuestAdditions suite of programs. These provide a number of useful features in guest operating systems, like mouse pointer integration (allowing the mouse to @@ -1153,8 +1148,7 @@ EndSection special keyboard shortcut to switch) and faster video rendering, especially in &windows; guests. The guest additions are available in the Devices - menu, after the installation of the guest OS is - finished. + menu, after the installation of the guest is finished. A few configuration changes are needed before &virtualbox; is started for the @@ -1181,59 +1175,51 @@ EndSection during installation of &virtualbox;. All users that need access to &virtualbox; will have to - be added as members of this group. The pw - command may be used to add new members: + be added as members of this group. pw + can be used to add new members: &prompt.root; pw groupmod vboxusers -m yourusername - The default permissions for - /dev/vboxnetctl are + The default permissions for /dev/vboxnetctl are restrictive and need to be changed for bridged - networking. - - To test it temporarily: + networking: &prompt.root; chown root:vboxusers /dev/vboxnetctl &prompt.root; chmod 0660 /dev/vboxnetctl - To make the permissions change permanent, add these + To make this permissions change permanent, add these lines to /etc/devfs.conf: own vboxnetctl root:vboxusers perm vboxnetctl 0660 - To launch &virtualbox;, either - select the Sun VirtualBox item from - the graphic environment's menu, or type the following in a - terminal: + To launch &virtualbox;, + type from a &xorg; session: &prompt.user; VirtualBox For more information on configuring and using - &virtualbox;, please visit the - official website at - . As the &os; - port is very recent, it is under heavy development. For the - latest information and troubleshooting instructions, please - visit the relevant page in the &os; wiki, at . + &virtualbox;, refer to the + official + website. For &os;-specific information and + troubleshooting instructions, refer to the relevant page in + the &os; wiki. &virtualbox; USB Support - - These steps require VirtualBox 4.0.0 or later. - - In order to be able to read and write to USB devices, - users need to be members of the operator group: + users need to be members of + operator: &prompt.root; pw groupmod operator -m jerry Then, add the following to - /etc/devfs.rules (create it if it does - not exist yet): + /etc/devfs.rules, or create this file if + it does not exist yet: [system=10] add path 'usb/*' mode 0660 group operator @@ -1256,20 +1242,20 @@ add path 'usb/*' mode 0660 group operato &virtualbox; Host DVD/CD Access Access to the host DVD/CD drives from guests is achieved - through the sharing of the physical drives. In GUI this is - set up from the Storage window in the Settings of the virtual - machine. Create an empty IDE CD/DVD device first. - Then choose the Host Drive from the popup menu for the virtual - CD/DVD drive selection. A checkbox labeled - Passthrough check box will appear. - This allows the virtual machine to use the hardware directly. - For example, audio CDs or the burner only function if - this option is selected. + through the sharing of the physical drives. Within + &virtualbox;, this is set up from the Storage window in the + Settings of the virtual machine. If needed, create an empty + IDE CD/DVD device first. Then choose the Host Drive from the + popup menu for the virtual CD/DVD drive selection. A checkbox + labeled Passthrough will appear. This + allows the virtual machine to use the hardware directly. For + example, audio CDs or the burner will only function if this + option is selected. HAL needs to run for &virtualbox; DVD/CD functions to work, so enable it in /etc/rc.conf and - start it (if it is not already running): + start it if it is not already running: hald_enable="YES" @@ -1277,16 +1263,14 @@ add path 'usb/*' mode 0660 group operato In order for users to be able to use &virtualbox; DVD/CD functions, they - need access to - /dev/xpt0, /dev/xpt0, /dev/cdN, and /dev/passN. - This is usually achieved by making the user of - &virtualbox; - a member of the operator group, which is also the default - group of the above mentioned devices. Permissions of these - devices have to be corrected by adding the following lines to + This is usually achieved by making the user a member of + operator. Permissions to these devices + have to be corrected by adding the following lines to /etc/devfs.conf: perm cd* 0600