From d9fbb6eeafa4c7445dddc0f5392417a7a72d09b6 Mon Sep 17 00:00:00 2001 From: Warren Block Date: Tue, 21 Feb 2012 03:34:51 +0000 Subject: [PATCH] Whitespace-only changes. Wrap long lines and fix indentation. --- .../handbook/virtualization/chapter.sgml | 1324 +++++++++-------- 1 file changed, 679 insertions(+), 645 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml b/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml index f6c32b657b..86e5e007cd 100644 --- a/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml @@ -8,7 +8,7 @@ - Murray + Murray Stokely Contributed by @@ -17,16 +17,16 @@ Virtualization - + Synopsis - + Virtualization software allows multiple operating systems to run simultaneously on the same computer. Such software systems for PCs often involve a host operating system which runs the virtualization software and supports any number of guest operating systems. - + After reading this chapter, you will know: @@ -36,8 +36,8 @@ - How to install &os; on an &intel;-based &apple; &macintosh; - computer. + How to install &os; on an &intel;-based &apple; + &macintosh; computer. @@ -68,214 +69,216 @@ linkend="basics">). - Know how to install &os; (). + + Know how to install &os; (). + - Know how to set up your network connection (). + + Know how to set up your network connection (). + - Know how to install additional third-party - software (). + + Know how to install additional third-party + software (). + - - - &os; as a Guest OS Parallels on MacOS - Parallels Desktop for &mac; is a - commercial software product available for &intel; based &apple; - &mac; computers running &macos; 10.4.6 or higher. &os; is a - fully supported guest operating system. - Once Parallels has been installed on &macos; - X, the user must configure a virtual machine and then install - the desired guest operating system. + Parallels Desktop for &mac; is + a commercial software product available for &intel; based + &apple; &mac; computers running &macos; 10.4.6 or higher. + &os; is a fully supported guest operating system. Once + Parallels has been installed on + &macos; X, the user must configure a virtual machine and then + install the desired guest operating system. - - Installing &os; on Parallels/&macos; X + + Installing &os; on Parallels/&macos; X - The first step in installing &os; on &macos; - X/Parallels is to create a new virtual - machine for installing &os;. Select &os; - as the Guest OS Type when prompted: + The first step in installing &os; on &macos; + X/Parallels is to create a new + virtual machine for installing &os;. Select + &os; as the Guest OS + Type when prompted: - - - - - + + + + + - And 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 Parallels: + And 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 Parallels: - - - - - + + + + + - - - - - + + + + + - - - - - + + + + + - - - - - + + + + + - Select the type of networking and a network - interface: + Select the type of networking and a network + interface: - - - - - + + + + + - - - - - + + + + + - Save and finish the configuration: + Save and finish the configuration: - - - - - + + + + + - - - - - + + + + + - 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 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. - - - - - + + + + + - 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 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. - - - - - + + + + + - 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. + 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. - - - - - + + + + + - When you have finished the installation, reboot - into your newly installed &os; virtual machine. - - - - - - - - - - Configuring &os; on &macos; X/Parallels - - After &os; has been successfully installed on &macos; - X with Parallels, there are a number - of configuration steps that can be taken to optimize the system - for virtualized operation. - - - - Set Boot Loader Variables - - The most important step is to reduce the - tunable to reduce the CPU utilization - of &os; under the Parallels - environment. This is accomplished by adding the following - line to /boot/loader.conf: - - 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%. - - - - 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. - - - - 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 - ifconfig_ed0="DHCP" to - /etc/rc.conf. More advanced - networking setups are described in . - - + When you have finished the installation, reboot into + your newly installed &os; virtual machine. + + + + + + + Configuring &os; on &macos; X/Parallels + + After &os; has been successfully installed on &macos; + X with Parallels, there are a + number of configuration steps that can be taken to + optimize the system for virtualized operation. + + + + Set Boot Loader Variables + + The most important step is to reduce the + tunable to reduce the CPU + utilization of &os; under the Parallels + environment. This is accomplished by + adding the following line to + /boot/loader.conf: + + 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%. + + + + 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. + + + + 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 + ifconfig_ed0="DHCP" to + /etc/rc.conf. More advanced + networking setups are described in + . + + + Virtual PC 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 desired guest operating - system. + µ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 desired guest operating system. - - Installing &os; on Virtual PC/µsoft.windows; + + Installing &os; on Virtual + PC/µsoft.windows; - 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: + 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: - - - - - + + + + + - - - - - + + + + + - And select Other as the - Operating system when prompted: - - - - - - - - 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: + And select Other as the + Operating system when + prompted: - - - - - + + + + + - - - - - + 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: - Save and finish the configuration: + + + + + - - - - - + + + + + - Select your &os; virtual machine and click - Settings, then set the type of networking and a - network interface: + Save and finish the configuration: - - - - - + + + + + - - - - - + Select your &os; virtual machine and click + Settings, then set the type of networking + and a network interface: - 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 - 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. + + + + + - - - - - + + + + + - - - - - + 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 + 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. - Once you have made this association with your CDROM - source, reboot your &os; virtual machine as normal by - clicking the 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. + + + + + - - - - - + + + + + - 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. + Once you have made this association with your CDROM + source, reboot your &os; virtual machine as normal by + clicking the 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. - - - - - + + + + + - When you have finished the installation, remember to eject - CDROM or release ISO image. Finally, reboot into your newly - installed &os; virtual machine. + 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. - - - - - - + + + + + - - Configuring &os; on µsoft.windows;/Virtual PC - - After &os; has been successfully installed on - µsoft.windows; with Virtual PC, - there are a number of configuration steps that can be taken to - optimize the system for virtualized operation. - - - - Set Boot Loader Variables - - 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 /boot/loader.conf: - - kern.hz=100 - - 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%. - - - - 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. - - - - 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 - /etc/rc.conf. More advanced - networking setups are described in . - - + When you have finished the installation, remember to + eject CDROM or release ISO image. Finally, reboot into your + newly installed &os; virtual machine. + + + + + + + Configuring &os; on µsoft.windows;/Virtual + PC + + After &os; has been successfully installed on + µsoft.windows; with Virtual PC + , there are a number of configuration + steps that can be taken to optimize the system for + virtualized operation. + + + + Set Boot Loader Variables + + 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 + /boot/loader.conf: + + kern.hz=100 + + 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%. + + + + 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. + + + + 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 + /etc/rc.conf. More advanced + networking setups are described in + . + + + VMware 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 machine and then - install the desired guest operating system. + 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 + machine and then install the desired guest operating + system. - - Installing &os; on VMware/&macos; X + + Installing &os; on VMware/&macos; X - 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, the Virtual + Machine Library will load. Click "New" to create the + VM: - - - - - + + + + + - 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 to help + you create the VM, click Continue to proceed: - - - - - + + + + + - Select Other as the - Operating System and - &os; or - &os; 64-bit, depending on if - you want 64-bit support, as the Version - when prompted: + Select Other as the + Operating System and + &os; or + &os; 64-bit, depending on if + you want 64-bit support, as the Version + when prompted: - - - - - + + + + + - Choose the Name of the VM Image and the Directory where - you would like it saved: + Choose the Name of the VM Image and the Directory where + you would like it saved: - - - - - + + + + + - Choose the size of the Virtual Hard Disk for the VM: + Choose the size of the Virtual Hard Disk for the + VM: - - - - - + + + + + - Choose the method you would like to install the VM, - either from an ISO image or from a CD: + Choose the method you would like to install the VM, + either from an ISO image or from a CD: - - - - - + + + + + - Once you click Finish, the VM will boot: + Once you click Finish, the VM will boot: - - - - - + + + + + - Install &os; like you normally would, or by following the - directions in : + Install &os; like you normally would, or by following + the directions in : - - - - - + + + + + - Once the install is complete you can modify the settings - of the VM, such as Memory Usage: + Once the install is complete you can modify the settings + of the VM, 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 VM cannot be + modified while the VM is running. + - - - - - + + + + + - The number of CPUs the VM will have access to: + The number of CPUs the VM will have access to: - - - - - + + + + + - 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 CD-Rom Device. Normally you can + disconnect the CD-Rom/ISO from the VM if you will not be + needing it anymore. - - - - - + + + + + - 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 - host's internet connection (NAT) is preferred - so that the VM can have access to the Internet, but the network - cannot access the VM. + 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 + host's internet connection (NAT) is + preferred so that the VM can have access to the Internet, + but the network cannot access the VM. - - - - - + + + + + - After you have finished modifying the settings, boot the - newly installed &os; virtual machine. - + After you have finished modifying the settings, boot the + newly installed &os; virtual machine. + - - Configuring &os; on &macos; X/VMware + + Configuring &os; on &macos; X/VMware - 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. + 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. - - - Set Boot Loader Variables + + + Set Boot Loader Variables - 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 /boot/loader.conf: + 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 + /boot/loader.conf: - kern.hz=100 + 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%. - + 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%. + - - Create a New Kernel Configuration File + + Create a New Kernel Configuration File - You can remove all of the FireWire, and USB device - drivers. VMware 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. - + You can remove all of the FireWire, and USB device + drivers. VMware 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. + - - 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 - ifconfig_em0="DHCP" to - /etc/rc.conf. More advanced - networking setups are described in . - - + + 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 + ifconfig_em0="DHCP" to + /etc/rc.conf. More advanced + networking setups are described in + . + + &virtualbox; Guest Additions on a &os; Guest - The &virtualbox; guest additions - provide support for: + The &virtualbox; guest + additions provide support for: @@ -1008,7 +1029,8 @@ xenbr1 8000.feffffffffff no vif0.1 &prompt.root; cd /usr/ports/emulators/virtualbox-ose-additions && make install clean - Add these lines to /etc/rc.conf: + Add these lines to + /etc/rc.conf: vboxguest_enable="YES" vboxservice_enable="YES" @@ -1018,8 +1040,8 @@ vboxservice_enable="YES" vboxservice_flags="--disable-timesync" - The vboxvideo_drv should be recognized by - Xorg -configure. If not, modify + The vboxvideo_drv should be recognized + by Xorg -configure. If not, modify xorg.conf for the &virtualbox; video card: @@ -1045,13 +1067,14 @@ EndSection HAL users should create this file at /usr/local/etc/hal/fdi/policy/90-vboxguest.fdi - or copy it from /usr/local/share/hal/fdi/policy/10osvendor/90-vboxguest.fdi: + or copy it from + /usr/local/share/hal/fdi/policy/10osvendor/90-vboxguest.fdi: <?xml version="1.0" encoding="UTF-8"?> <!-- # Sun VirtualBox # Hal driver description for the vboxmouse driver -# $Id: chapter.sgml,v 1.30 2012-02-18 05:33:57 eadler Exp $ +# $Id: chapter.sgml,v 1.31 2012-02-21 03:34:51 wblock Exp $ Copyright (C) 2008-2009 Sun Microsystems, Inc. @@ -1085,80 +1108,88 @@ EndSection &os; as a Host OS - 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, the Open Source Edition (OSE) of - Sun's &virtualbox; appeared in the + 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, the Open Source Edition + (OSE) of Sun's + &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 comes in two - flavors, an open source and a proprietary edition. From the user's - point of view, perhaps the most important limitation of the - OSE is the lack of USB support. Other differences - may be found in the Editions page of the - &virtualbox; wiki, at . + &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 comes in two flavors, an open source and a + proprietary edition. From the user's point of view, perhaps the + most important limitation of the OSE is the + lack of USB support. Other differences may be found in the + Editions page of the + &virtualbox; wiki, at + . Currently, only the OSE is 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: + &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: &prompt.root; cd /usr/ports/emulators/virtualbox-ose &prompt.root; make install clean One useful option in the configuration dialog 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 be shared between host - and guest without the need to press a 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. + GuestAdditions suite of programs. These + provide a number of useful features in guest operating + systems, like mouse pointer integration (allowing the mouse to + be shared between host and guest without the need to press a + 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. A few configuration changes are needed before - &virtualbox; is started for the first time. - The port installs a kernel module in /boot/modules which must be loaded - into the running kernel: + &virtualbox; is started for the + first time. The port installs a kernel module in + /boot/modules which + must be loaded into the running kernel: &prompt.root; kldload vboxdrv - To ensure the module always gets loaded after a reboot, add the - following line to /boot/loader.conf: + To ensure the module always gets loaded after a reboot, + add the following line to + /boot/loader.conf: vboxdrv_load="YES" To use the kernel modules that allow bridged or host-only - networking, add the following to /etc/rc.conf - and reboot the computer: + networking, add the following to + /etc/rc.conf and reboot the + computer: vboxnet_enable="YES" - The vboxusers group is created 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: + The vboxusers group is created + 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: &prompt.root; pw groupmod vboxusers -m yourusername - The default permissions for /dev/vboxnetctl are restrictive and - need to be changed for bridged networking. + The default permissions for + /dev/vboxnetctl are + restrictive and need to be changed for bridged + networking. To test it temporarily: @@ -1171,18 +1202,19 @@ EndSection 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 + To launch &virtualbox;, either + select the Sun VirtualBox item from + the graphic environment's menu, or type the following in a terminal: &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 + &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 . @@ -1194,13 +1226,14 @@ perm vboxnetctl 0660 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: + In order to be able to read and write to USB devices, + users need to be members of the operator group: &prompt.root; pw groupmod operator -m jerry - Then, add the following to /etc/devfs.rules - (create it if it does not exist yet): + Then, add the following to + /etc/devfs.rules (create it if it does + not exist yet): [system=10] add path 'usb/*' mode 0660 group operator @@ -1214,32 +1247,33 @@ add path 'usb/*' mode 0660 group operator &prompt.root; /etc/rc.d/devfs restart - USB can now be enabled in the guest operating system. - USB devices should be visible in the &virtualbox; preferences. + USB can now be enabled in the guest operating system. USB + devices should be visible in the &virtualbox; + preferences. &virtualbox; Host DVD/CD Access - The atapicam kernel module needs to be loaded - by adding the following line to + The atapicam kernel module needs to be + loaded by adding the following line to /boot/loader.conf: atapicam_load="YES" 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): + &virtualbox; DVD/CD functions to + work, so enable it in /etc/rc.conf and + start it (if it is not already running): hald_enable="YES" &prompt.root; /usr/local/etc/rc.d/hald start In order for users to be able to use - &virtualbox; DVD/CD functions, they need - access to /dev/xpt0, - &virtualbox; DVD/CD functions, they + need access to + /dev/xpt0, /dev/cdN, and /dev/passN. @@ -1258,15 +1292,15 @@ perm pass0 0660 Other Virtualization Options - There is ongoing work in getting &xen; + There is ongoing work in getting + &xen; to work as a host environment on &os;. --> - -