os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

This is a minor content fixup as much work is needed in this chapter.

Browse source 
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)
This commit is contained in:
Dru Lavigne 2013-02-28 15:40:57 +00:00
parent f0da12bdad
commit 5c7559f8ae
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=41062
1 changed files with 233 additions and 249 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

482
en_US.ISO8859-1/books/handbook/virtualization/chapter.xml
View file

@ -66,23 +66,23 @@
<itemizedlist>
<listitem>
<para>Understand the basics of &unix; and &os; (<xref
linkend="basics"/>).</para>
<para>Understand the <link linkend="basics">basics of &unix;
and &os;</link>.</para>
</listitem>
<listitem>
<para>Know how to install &os; (<xref
linkend="install"/>).</para>
<para>Know how to <link linkend="install">install
&os;</link>.</para>
</listitem>
<listitem>
<para>Know how to set up your network connection (<xref
linkend="advanced-networking"/>).</para>
<para>Know how to <link linkend="advanced-networking">set up a
network connection</link>.</para>
</listitem>
<listitem>
<para>Know how to install additional third-party
software (<xref linkend="ports"/>).</para>
<para>Know how to <link linkend="ports">install additional
third-party software</link>.</para>
</listitem>
</itemizedlist>
</sect1>
@ -91,7 +91,7 @@
<title>&os; as a Guest OS</title>
<sect2 id="virtualization-guest-parallels">
<title>Parallels on MacOS</title>
<title><application>Parallels</application> on &macos; X</title>
<para><application>Parallels Desktop</application> for &mac; is
a commercial software product available for &intel; based
@ -104,8 +104,8 @@
<sect3 id="virtualization-guest-parallels-install">
<title>Installing &os; on Parallels/&macos; X</title>
<para>The first step in installing &os; on &macos;
X/<application>Parallels</application> is to create a new
<para>The first step in installing &os; on
<application>Parallels</application> is to create a new
virtual machine for installing &os;. Select
<guimenuitem>&os;</guimenuitem> as the <guimenu>Guest OS
Type</guimenu> when prompted:</para>
@ -116,8 +116,8 @@
</imageobject>
</mediaobject>
<para>And choose a reasonable amount of disk and memory
depending on your plans for this virtual &os; instance.
<para>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 <application>Parallels</application>:</para>
@ -174,16 +174,16 @@
</imageobject>
</mediaobject>
<para>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; <application>Parallels</application> 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.</para>
<para>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; <application>Parallels</application> 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.</para>
<mediaobject>
<imageobject>
@ -191,12 +191,10 @@
</imageobject>
</mediaobject>
<para>Once you have made this association with your CDROM
source, reboot your &os; virtual machine as normal by
clicking the reboot icon.
<application>Parallels</application> will reboot with a
special BIOS that first checks if you have a CDROM just as a
normal BIOS would do.</para>
<para>Once this association with the CDROM source has been
made, reboot the &os; virtual machine by clicking the reboot
icon. <application>Parallels</application> will reboot with
a special BIOS that first checks if there is a CDROM.</para>
<mediaobject>
<imageobject>
@ -205,10 +203,9 @@
</mediaobject>
<para>In this case it will find the &os; installation media
and begin a normal <application>sysinstall</application>
based installation as described in <xref
linkend="install"/>. You may install, but do not attempt
to configure X11 at this time.</para>
and begin a normal &os; installation. Perform the
installation, but do not attempt to configure
<application>&xorg;</application> at this time.</para>
<mediaobject>
<imageobject>
@ -216,8 +213,8 @@
</imageobject>
</mediaobject>
<para>When you have finished the installation, reboot into
your newly installed &os; virtual machine.</para>
<para>When the installation is finished, reboot into the
newly installed &os; virtual machine.</para>
<mediaobject>
<imageobject>
@ -227,7 +224,8 @@
</sect3>
<sect3 id="virtualization-guest-parallels-configure">
<title>Configuring &os; on &macos; X/Parallels</title>
<title>Configuring &os; on
<application>Parallels</application> </title>
<para>After &os; has been successfully installed on &macos;
X with <application>Parallels</application>, there are a
@ -248,35 +246,32 @@
<programlisting>kern.hz=100</programlisting>
<para>Without this setting, an idle &os;
<application>Parallels</application> 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%.</para>
<application>Parallels</application> guest will use
roughly 15% of the CPU of a single process &imac;.
After this change the usage will be closer to 5%.</para>
</step>
<step>
<title>Create a New Kernel Configuration File</title>
<para>You can remove all of the SCSI, FireWire, and USB
device drivers. <application>Parallels</application>
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.</para>
<para>All of the SCSI, FireWire, and USB device drivers
can be removed from a custom kernel configuration file.
<application>Parallels</application> 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.</para>
</step>
<step>
<title>Configure Networking</title>
<para>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
<para>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
<literal>ifconfig_ed0="DHCP"</literal> to
<filename>/etc/rc.conf</filename>. More advanced
networking setups are described in
<xref linkend="advanced-networking"/>.</para>
networking setups are described in <link
linkend="advanced-networking"></link>.</para>
</step>
</procedure>
</sect3>
@ -592,26 +587,27 @@ xenbr1 8000.feffffffffff no vif0.1
</sect2>
-->
<sect2 id="virtualization-guest-virtualpc">
<title>Virtual PC on &windows;</title>
<title><application>Virtual PC</application> on
&windows;</title>
<para><application>Virtual PC</application> for &windows; is a
&microsoft; software product available for free download.
See <ulink
See this website for the <ulink
url="http://www.microsoft.com/windows/downloads/virtualpc/sysreq.mspx">
system requirements</ulink>. Once <application> Virtual PC
</application> has been installed on &microsoft.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.</para>
<sect3 id="virtualization-guest-virtualpc-install">
<title>Installing &os; on Virtual
PC/&microsoft.windows;</title>
<title>Installing &os; on <application>Virtual
PC</application></title>
<para>The first step in installing &os; on
&microsoft.windows; /<application>Virtual PC
</application> is to create a new virtual machine for
installing &os;. Select <guimenuitem>Create a virtual
machine</guimenuitem> when prompted:</para>
<application>Virtual PC </application> is to create a new
virtual machine for installing &os;. Select
<guimenuitem>Create a virtual machine</guimenuitem> when
prompted:</para>
<mediaobject>
<imageobject>
@ -625,7 +621,7 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>And select <guimenuitem>Other</guimenuitem> as the
<para>Select <guimenuitem>Other</guimenuitem> as the
<guimenuitem>Operating system</guimenuitem> when
prompted:</para>
@ -636,10 +632,9 @@ xenbr1 8000.feffffffffff no vif0.1
</mediaobject>
<para>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
<application>Virtual PC</application>:</para>
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 <application>Virtual PC</application>:</para>
<mediaobject>
<imageobject>
@ -661,7 +656,7 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Select your &os; virtual machine and click
<para>Select the &os; virtual machine and click
<guimenu>Settings</guimenu>, then set the type of networking
and a network interface:</para>
@ -677,18 +672,18 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>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 <guimenu>CD</guimenu> and choose
<guimenu>Capture ISO Image...</guimenu> on
<para>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 <guimenu>CD</guimenu> and choose
<guimenu>Capture ISO Image...</guimenu> on the
<application>Virtual PC</application> 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.</para>
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.</para>
<mediaobject>
<imageobject>
@ -702,13 +697,11 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Once you have made this association with your CDROM
source, reboot your &os; virtual machine as normal by
clicking the <guimenu>Action</guimenu> and
<guimenu>Reset</guimenu>.
<para>Once this association with the CDROM source has been
made, reboot the &os; virtual machine by clicking
<guimenu>Action</guimenu> and <guimenu>Reset</guimenu>.
<application>Virtual PC</application> will reboot with a
special BIOS that first checks if you have a CDROM just as a
normal BIOS would do.</para>
special BIOS that first checks for a CDROM.</para>
<mediaobject>
<imageobject>
@ -717,10 +710,9 @@ xenbr1 8000.feffffffffff no vif0.1
</mediaobject>
<para>In this case it will find the &os; installation media
and begin a normal <application>sysinstall</application>
based installation as described in
<xref linkend="install"/>. You may install, but do not
attempt to configure X11 at this time.</para>
and begin a normal &os; installation. Continue with the
installation, but do not attempt to configure
<application>&xorg;</application> at this time.</para>
<mediaobject>
<imageobject>
@ -728,9 +720,9 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>When you have finished the installation, remember to
eject CDROM or release ISO image. Finally, reboot into your
newly installed &os; virtual machine.</para>
<para>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.</para>
<mediaobject>
<imageobject>
@ -740,8 +732,8 @@ xenbr1 8000.feffffffffff no vif0.1
</sect3>
<sect3 id="virtualization-guest-virtualpc-configure">
<title>Configuring &os; on &microsoft.windows;/Virtual
PC</title>
<title>Configuring &os; on <application>Virtual
PC</application></title>
<para>After &os; has been successfully installed on
&microsoft.windows; with <application>Virtual PC
@ -755,9 +747,9 @@ xenbr1 8000.feffffffffff no vif0.1
<para>The most important step is to reduce the
<option>kern.hz</option> tunable to reduce the CPU
utilization of &os; under the
<application>Virtual PC</application> environment.
This is accomplished by adding the following line to
utilization of &os; under the <application>Virtual
PC</application> environment. This is accomplished
by adding the following line to
<filename> /boot/loader.conf</filename>:</para>
<programlisting>kern.hz=100</programlisting>
@ -765,55 +757,57 @@ xenbr1 8000.feffffffffff no vif0.1
<para>Without this setting, an idle &os;
<application>Virtual PC</application> 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%.</para>
computer. After this change, the usage will be
closer to 3%.</para>
</step>
<step>
<title>Create a New Kernel Configuration File</title>
<para>You can remove all of the SCSI, FireWire, and USB
device drivers. <application>Virtual PC</application>
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.</para>
<para>All of the SCSI, FireWire, and USB device drivers
can be removed from a custom kernel configuration file.
<application>Virtual PC</application> 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.</para>
</step>
<step>
<title>Configure Networking</title>
<para>The most basic networking setup involves simply
using DHCP to connect your virtual machine to the same
local area network as your host &microsoft.windows;.
This can be accomplished by adding
<literal>ifconfig_de0="DHCP"</literal> to
<para>The most basic networking setup uses DHCP to connect
the virtual machine to the same local area network as
the &microsoft.windows; host. This can be accomplished
by adding <literal>ifconfig_de0="DHCP"</literal> to
<filename>/etc/rc.conf</filename>. More advanced
networking setups are described in
<xref linkend="advanced-networking"/>.</para>
networking setups are described in <link
linkend="advanced-networking"></link>.</para>
</step>
</procedure>
</sect3>
</sect2>
<sect2 id="virtualization-guest-vmware">
<title>VMware on MacOS</title>
<title><application>VMware Fusion</application> on
&macos;</title>
<para><application>VMware Fusion</application> 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
<application>VMware Fusion</application> 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.</para>
<sect3 id="virtualization-guest-vmware-install">
<title>Installing &os; on VMware/&macos; X</title>
<title>Installing &os; on <application>VMware
Fusion</application></title>
<para>The first step is to start VMware Fusion, the Virtual
Machine Library will load. Click "New" to create the
VM:</para>
<para>The first step is to start <application>VMware
Fusion</application> which will load the Virtual
Machine Library. Click <guimenuitem>New</guimenuitem> to
create the virtual machine:</para>
<mediaobject>
<imageobject>
@ -821,8 +815,8 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>This will load the New Virtual Machine Assistant to help
you create the VM, click Continue to proceed:</para>
<para>This will load the New Virtual Machine Assistant. Click
<guimenuitem>Continue</guimenuitem> to proceed:</para>
<mediaobject>
<imageobject>
@ -831,11 +825,10 @@ xenbr1 8000.feffffffffff no vif0.1
</mediaobject>
<para>Select <guimenuitem>Other</guimenuitem> as the
<guimenuitem>Operating System</guimenuitem> and
<guimenuitem>Operating System</guimenuitem> and either
<guimenuitem>&os;</guimenuitem> or
<guimenuitem>&os; 64-bit</guimenuitem>, depending on if
you want 64-bit support, as the <guimenu>Version</guimenu>
when prompted:</para>
<guimenuitem>&os; 64-bit</guimenuitem>, as the
<guimenu>Version</guimenu> when prompted:</para>
<mediaobject>
<imageobject>
@ -843,8 +836,8 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Choose the Name of the VM Image and the Directory where
you would like it saved:</para>
<para>Choose the name of the virtual machine and the directory
where it should be saved:</para>
<mediaobject>
<imageobject>
@ -852,8 +845,8 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Choose the size of the Virtual Hard Disk for the
VM:</para>
<para>Choose the size of the Virtual Hard Disk for the virtual
machine:</para>
<mediaobject>
<imageobject>
@ -861,8 +854,8 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Choose the method you would like to install the VM,
either from an ISO image or from a CD:</para>
<para>Choose the method to install the virtual machine,
either from an ISO image or from a CD/DVD:</para>
<mediaobject>
<imageobject>
@ -870,7 +863,8 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Once you click Finish, the VM will boot:</para>
<para>Click <guimenuitem>Finish</guimenuitem> and the virtual
machine will boot:</para>
<mediaobject>
<imageobject>
@ -878,8 +872,7 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Install &os; like you normally would, or by following
the directions in <xref linkend="install"/>:</para>
<para>Install &os; as usual:</para>
<mediaobject>
<imageobject>
@ -887,12 +880,14 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Once the install is complete you can modify the settings
of the VM, such as Memory Usage:</para>
<para>Once the install is complete, the settings
of the virtual machine can be modified, such as memory
usage:</para>
<note>
<para>The System Hardware settings of the VM cannot be
modified while the VM is running.</para>
<para>The System Hardware settings of the virtual machine
cannot be modified while the virtual machine is
running.</para>
</note>
<mediaobject>
@ -901,7 +896,8 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>The number of CPUs the VM will have access to:</para>
<para>The number of CPUs the virtual machine will have access
to:</para>
<mediaobject>
<imageobject>
@ -909,9 +905,9 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>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.</para>
<para>The status of the CDROM device. Normally the
CD/DVD/ISO is disconnected from the virtual machine when it
is no longer needed.</para>
<mediaobject>
<imageobject>
@ -919,14 +915,15 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>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 <guimenuitem>Connect directly to the physical network
(Bridged)</guimenuitem>. Otherwise <guimenuitem>Share the
<para>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
<guimenuitem>Connect directly to the physical network
(Bridged)</guimenuitem>. Otherwise, <guimenuitem>Share the
host's internet connection (NAT)</guimenuitem> is
preferred so that the VM can have access to the Internet,
but the network cannot access the VM.</para>
preferred so that the virtual machine can have access to the
Internet, but the network cannot access the virtual
machine.</para>
<mediaobject>
<imageobject>
@ -934,17 +931,18 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>After you have finished modifying the settings, boot the
newly installed &os; virtual machine.</para>
<para>After modifying the settings, boot the newly installed
&os; virtual machine.</para>
</sect3>
<sect3 id="virtualization-guest-vmware-configure">
<title>Configuring &os; on &macos; X/VMware</title>
<title>Configuring &os; on <application>VMware
Fusion</application></title>
<para>After &os; has been successfully installed on &macos; X
with <application>VMware</application>, there are a number
of configuration steps that can be taken to optimize the
system for virtualized operation.</para>
with <application>VMware Fusion</application>, there are a
number of configuration steps that can be taken to optimize
the system for virtualized operation.</para>
<procedure>
<step>
@ -953,40 +951,40 @@ xenbr1 8000.feffffffffff no vif0.1
<para>The most important step is to reduce the
<option>kern.hz</option> tunable to reduce the CPU
utilization of &os; under the
<application>VMware</application> environment. This is
accomplished by adding the following line to
<application>VMware Fusion</application> environment.
This is accomplished by adding the following line to
<filename>/boot/loader.conf</filename>:</para>
<programlisting>kern.hz=100</programlisting>
<para>Without this setting, an idle &os;
<application>VMware</application> 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%.</para>
<application>VMware Fusion</application> guest will use
roughly 15% of the CPU of a single processor &imac;.
After this change, the usage will be closer to
5%.</para>
</step>
<step>
<title>Create a New Kernel Configuration File</title>
<para>You can remove all of the FireWire, and USB device
drivers. <application>VMware</application> provides a
<para>All of the FireWire, and USB device drivers can be
removed from a custom kernel configuration file.
<application>VMware Fusion</application> 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.</para>
so all network devices except for &man.em.4; can be
removed from the kernel.</para>
</step>
<step>
<title>Configure Networking</title>
<para>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
<para>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
<literal>ifconfig_em0="DHCP"</literal> to
<filename>/etc/rc.conf</filename>. More advanced
networking setups are described in
<xref linkend="advanced-networking"/>.</para>
networking setups are described in <link
linkend="advanced-networking"></link>.</para>
</step>
</procedure>
</sect3>
@ -1000,23 +998,23 @@ xenbr1 8000.feffffffffff no vif0.1
<itemizedlist>
<listitem>
<para>Clipboard sharing</para>
<para>Clipboard sharing.</para>
</listitem>
<listitem>
<para>Mouse pointer integration</para>
<para>Mouse pointer integration.</para>
</listitem>
<listitem>
<para>Host time synchronization</para>
<para>Host time synchronization.</para>
</listitem>
<listitem>
<para>Window scaling</para>
<para>Window scaling.</para>
</listitem>
<listitem>
<para>Seamless mode</para>
<para>Seamless mode.</para>
</listitem>
</itemizedlist>
@ -1026,7 +1024,8 @@ xenbr1 8000.feffffffffff no vif0.1
<para>First, install the <filename
role="package">emulators/virtualbox-ose-additions</filename>
package in the &os; guest.</para>
package or port in the &os; guest. This will install
the port:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/emulators/virtualbox-ose-additions && make install clean</userinput></screen>
@ -1036,14 +1035,15 @@ xenbr1 8000.feffffffffff no vif0.1
<programlisting>vboxguest_enable="YES"
vboxservice_enable="YES"</programlisting>
<para>If &man.ntpd.8; or &man.ntpdate.8; will be used, host time
<para>If &man.ntpd.8; or &man.ntpdate.8; is used, host time
synchronization should be disabled:</para>
<programlisting>vboxservice_flags="--disable-timesync"</programlisting>
<para>The <literal>vboxvideo_drv</literal> should be recognized
by <command>Xorg -configure</command>. If not, modify
<filename>xorg.conf</filename> for the
<para>The <literal>vboxvideo</literal> driver should be
automatically recognized by <command>Xorg
-configure</command>. If not, modify
<filename>/etc/X11/xorg.conf</filename> for the
<application>&virtualbox;</application> video card:</para>
<programlisting>Section "Device"
@ -1058,15 +1058,16 @@ vboxservice_enable="YES"</programlisting>
BusID "PCI:0:2:0"
EndSection</programlisting>
<para>To use <literal>vboxmouse_drv</literal>, adjust the mouse
section in your <filename>xorg.conf</filename>:</para>
<para>To use the <literal>vboxmouse</literal> driver, adjust the
mouse section in
<filename>/etc/X11/xorg.conf</filename>:</para>
<programlisting>Section "InputDevice"
Identifier "Mouse0"
Driver "vboxmouse"
EndSection</programlisting>
<para><acronym>HAL</acronym> users should create this file at
<para><acronym>HAL</acronym> users should create the following
<filename>/usr/local/etc/hal/fdi/policy/90-vboxguest.fdi</filename>
or copy it from
<filename>/usr/local/share/hal/fdi/policy/10osvendor/90-vboxguest.fdi</filename>:</para>
@ -1107,45 +1108,39 @@ EndSection</programlisting>
</sect1>
<sect1 id="virtualization-host">
<title>&os; as a Host OS</title>
<title>&os; as a Host</title>
<para>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
<application>VMware</application> (like
<filename role="package">emulators/vmware3</filename>), which
utilized the &linux; binary compatibility layer. Shortly after
the release of &os;&nbsp;7.2, Sun's
a host operating system by any of the available virtualization
solutions. Shortly after the release of &os;&nbsp;7.2, &oracle;
<application>&virtualbox;</application> appeared in the
Ports&nbsp;Collection as a native &os; program.</para>
<para><application>&virtualbox;</application> 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
<quote>Downloads</quote> page of the
<application>&virtualbox;</application> wiki, at <ulink
url="http://www.virtualbox.org/wiki/Downloads"></ulink>.
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 <ulink
url="http://www.virtualbox.org/wiki/Downloads">
<quote>Downloads</quote> page of the
<application>&virtualbox;</application> wiki</ulink>.
Currently, these extensions are not available for &os;.</para>
<sect2 id="virtualization-virtualbox-install">
<title>Installing &virtualbox;</title>
<para><application>&virtualbox;</application> is available as a
&os; port in
<filename role="package">emulators/virtualbox-ose</filename>.
As &virtualbox; is very actively developed, make sure your
ports tree is up to date before installing. Install using
these commands:</para>
&os; package or port in <filename
role="package">emulators/virtualbox-ose</filename>. The
port can be installed using these commands:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/emulators/virtualbox-ose</userinput>
&prompt.root; <userinput>make install clean</userinput></screen>
<para>One useful option in the configuration dialog is the
<para>One useful option in the port's configuration menu is the
<literal>GuestAdditions</literal> 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</programlisting>
special keyboard shortcut to switch) and faster video
rendering, especially in &windows; guests. The guest
additions are available in the <guimenu>Devices</guimenu>
menu, after the installation of the guest OS is
finished.</para>
menu, after the installation of the guest is finished.</para>
<para>A few configuration changes are needed before
<application>&virtualbox;</application> is started for the
@ -1181,59 +1175,51 @@ EndSection</programlisting>
during installation of
<application>&virtualbox;</application>. All users that need
access to <application>&virtualbox;</application> will have to
be added as members of this group. The <command>pw</command>
command may be used to add new members:</para>
be added as members of this group. <command>pw</command>
can be used to add new members:</para>
<screen>&prompt.root; <userinput>pw groupmod vboxusers -m <replaceable>yourusername</replaceable></userinput></screen>
<para>The default permissions for
<filename class="devicefile">/dev/vboxnetctl</filename> are
<para>The default permissions for <filename
class="devicefile">/dev/vboxnetctl</filename> are
restrictive and need to be changed for bridged
networking.</para>
<para>To test it temporarily:</para>
networking:</para>
<screen>&prompt.root; <userinput>chown root:vboxusers /dev/vboxnetctl</userinput>
&prompt.root; <userinput>chmod 0660 /dev/vboxnetctl</userinput></screen>
<para>To make the permissions change permanent, add these
<para>To make this permissions change permanent, add these
lines to <filename>/etc/devfs.conf</filename>:</para>
<programlisting>own vboxnetctl root:vboxusers
perm vboxnetctl 0660</programlisting>
<para>To launch <application>&virtualbox;</application>, either
select the <guimenuitem>Sun VirtualBox</guimenuitem> item from
the graphic environment's menu, or type the following in a
terminal:</para>
<para>To launch <application>&virtualbox;</application>,
type from a <application>&xorg;</application> session:</para>
<screen>&prompt.user; <userinput>VirtualBox</userinput></screen>
<para>For more information on configuring and using
<application>&virtualbox;</application>, please visit the
official website at
<ulink url="http://www.virtualbox.org"></ulink>. 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 <ulink
url="http://wiki.FreeBSD.org/VirtualBox"></ulink>.</para>
<application>&virtualbox;</application>, refer to the
<ulink url="http://www.virtualbox.org">official
website</ulink>. For &os;-specific information and
troubleshooting instructions, refer to the <ulink
url="http://wiki.FreeBSD.org/VirtualBox">relevant page in
the &os; wiki</ulink>.</para>
</sect2>
<sect2 id="virtualization-virtualbox-usb-support">
<title>&virtualbox; USB Support</title>
<note>
<para>These steps require VirtualBox 4.0.0 or later.</para>
</note>
<para>In order to be able to read and write to USB devices,
users need to be members of the operator group:</para>
users need to be members of
<groupname>operator</groupname>:</para>
<screen>&prompt.root; <userinput>pw groupmod operator -m <replaceable>jerry</replaceable></userinput></screen>
<para>Then, add the following to
<filename>/etc/devfs.rules</filename> (create it if it does
not exist yet):</para>
<filename>/etc/devfs.rules</filename>, or create this file if
it does not exist yet:</para>
<programlisting>[system=10]
add path 'usb/*' mode 0660 group operator</programlisting>
@ -1256,20 +1242,20 @@ add path 'usb/*' mode 0660 group operator</programlisting>
<title>&virtualbox; Host DVD/CD Access</title>
<para>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
<literal>Passthrough</literal> 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.</para>
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 <literal>Passthrough</literal> 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.</para>
<para><acronym>HAL</acronym> needs to run for
<application>&virtualbox;</application> DVD/CD functions to
work, so enable it in <filename>/etc/rc.conf</filename> and
start it (if it is not already running):</para>
start it if it is not already running:</para>
<programlisting>hald_enable="YES"</programlisting>
@ -1277,16 +1263,14 @@ add path 'usb/*' mode 0660 group operator</programlisting>
<para>In order for users to be able to use
<application>&virtualbox;</application> DVD/CD functions, they
need access to
<filename class="devicefile">/dev/xpt0</filename>, <filename
need access to <filename
class="devicefile">/dev/xpt0</filename>, <filename
class="devicefile">/dev/cd<replaceable>N</replaceable></filename>,
and <filename
class="devicefile">/dev/pass<replaceable>N</replaceable></filename>.
This is usually achieved by making the user of
<application>&virtualbox;</application>
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
<groupname>operator</groupname>. Permissions to these devices
have to be corrected by adding the following lines to
<filename>/etc/devfs.conf</filename>:</para>
<programlisting>perm cd* 0600