Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Sep 2015 21:59:29 +0000 (UTC)
From:      Warren Block <wblock@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org
Subject:   svn commit: r47345 - head/en_US.ISO8859-1/books/handbook/virtualization
Message-ID:  <201509022159.t82LxTDA049919@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: wblock
Date: Wed Sep  2 21:59:29 2015
New Revision: 47345
URL: https://svnweb.freebsd.org/changeset/doc/47345

Log:
  Update Virtualization chapter:
  Remove hidden and outdated Xen section.
  Move sect2 FreeBSD as a guest entries to sect1 entries.  They are too
  detailed to be sect2, and do not show in the TOC that way.
  Update the VirtualBox guest additions section a bit, mostly about X.

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	Wed Sep  2 21:52:57 2015	(r47344)
+++ head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml	Wed Sep  2 21:59:29 2015	(r47345)
@@ -54,15 +54,6 @@
 	  &mac; computer.</para>
       </listitem>
 
-<!--
-  Note:  There is no working/end-user ready Xen support for FreeBSD as of 07-2010.
-         Hide all information regarding Xen under FreeBSD.
-
-      <listitem>
-	<para>How to install &os; on Linux with
-	  <application>&xen;</application>.</para>
-      </listitem>
--->
       <listitem>
 	<para>How to install &os; on &microsoft.windows; with
 	  <application>Virtual PC</application>.</para>
@@ -105,11 +96,8 @@
     </itemizedlist>
   </sect1>
 
-  <sect1 xml:id="virtualization-guest">
-    <title>&os; as a Guest OS</title>
-
-    <sect2 xml:id="virtualization-guest-parallels">
-      <title><application>Parallels</application> on &macos; X</title>
+    <sect1 xml:id="virtualization-guest-parallels">
+      <title>&os; as a Guest on <application>Parallels</application> for &macos; X</title>
 
       <para><application>Parallels Desktop</application> for &mac; is
 	a commercial software product available for &intel; based
@@ -119,7 +107,7 @@
 	&macos; X, the user must configure a virtual machine and then
 	install the desired guest operating system.</para>
 
-      <sect3 xml:id="virtualization-guest-parallels-install">
+      <sect2 xml:id="virtualization-guest-parallels-install">
 	<title>Installing &os; on Parallels/&macos; X</title>
 
 	<para>The first step in installing &os; on
@@ -239,9 +227,9 @@
 	    <imagedata fileref="virtualization/parallels-freebsd13"/>
 	  </imageobject>
 	</mediaobject>
-      </sect3>
+      </sect2>
 
-      <sect3 xml:id="virtualization-guest-parallels-configure">
+      <sect2 xml:id="virtualization-guest-parallels-configure">
 	<title>Configuring &os; on
 	  <application>Parallels</application> </title>
 
@@ -292,321 +280,11 @@
 	      <xref linkend="advanced-networking"/>.</para>
 	  </step>
 	</procedure>
-      </sect3>
-    </sect2>
-
-<!--
-Deactivate/hide this section as the instructions in there do NOT work any more:
-- FreeBSD 7.0 has reached its EOL a long time ago.
-- The needed files from www.fsmware.com are not available any more, as the
-  server is dead.  So it is impossible to follow the instructions in here.
-
-jkois@FreeBSD.org, 2010-06-18
-
-    <sect2 id="virtualization-guest-xen">
-      <sect2info>
-	<authorgroup>
-	  <author>
-	    <firstname>Fukang</firstname>
-	    <surname>Chen (Loader)</surname>
-	    <contrib>Contributed by </contrib>
-	  </author>
-	</authorgroup>
-      </sect2info>
-
-      <title>&os; with &xen; on Linux</title>
-
-	<para>The <application>&xen;</application> hypervisor is an
-	  open source paravirtualization product which is now
-	  supported by the commercial XenSource company.  Guest
-	  operating systems are known as domU domains, and the host
-	  operating system is known as dom0.  The first step in
-	  running a virtual &os; instance under Linux is to install
-	  <application>&xen;</application> for Linux dom0.  The host
-	  operating system will be a Slackware Linux
-	  distribution.</para>
-
-	<sect3 id="xen-slackware-dom0">
-	  <title>Setup &xen; 3 on Linux dom0</title>
-
-	  <procedure>
-	    <step>
-	      <title>Download &xen; 3.0 from XenSource</title>
-
-	      <para>Download <ulink
-		  url="http://bits.xensource.com/oss-xen/release/3.0.4-1/src.tgz/xen-3.0.4_1-src.tgz">xen-3.0.4_1-src.tgz</ulink>;
-		from <ulink
-		url="http://www.xensource.com/"></ulink>.</para>;
-	    </step>
-
-	    <step>
-	      <title>Unpack the tarball</title>
-
-              <screen>&prompt.root; <userinput>cd xen-3.0.4_1-src</userinput>
-&prompt.root; <userinput>KERNELS="linux-2.6-xen0 linux-2.6-xenU" make world</userinput>
-&prompt.root; <userinput>make install</userinput></screen>
-
-	      <note>
-		<para>To re-compile the kernel for dom0:</para>
-
-		<screen>&prompt.root; <userinput>cd xen-3.0.4_1-src/linux-2.6.16.33-xen0</userinput>
-&prompt.root; <userinput>make menuconfig</userinput>
-&prompt.root; <userinput>make</userinput>
-&prompt.root; <userinput>make install</userinput></screen>
-
-		<para>Older version of
-		  <application>&xen;</application> may need to specify
-		  <command>make ARCH=xen menuconfig</command></para>
-	      </note>
-	    </step>
-
-	    <step>
-	      <title>Add a Menu Entry into Grub
-		<filename>menu.lst</filename></title>
-
-	      <para>Edit <filename>/boot/grub/menu.lst</filename> and
-		add the following lines:</para>
-
-	      <programlisting>title Xen-3.0.4
-root (hd0,0)
-kernel /boot/xen-3.0.4-1.gz dom0_mem=262144
-module /boot/vmlinuz-2.6.16.33-xen0 root=/dev/hda1 ro</programlisting>
-	    </step>
-
-	    <step>
-	      <title>Reboot Your Computer into &xen;</title>
-
-	      <para>First, edit
-		<filename>/etc/xen/xend-config.sxp</filename>, and add
-		the following line:</para>
-
-	      <programlisting>(network-script 'network-bridge netdev=eth0')</programlisting>
-
-	      <para>Then, we can launch
-		<application>&xen;</application>:</para>
-
-	      <screen>&prompt.root; <userinput>/etc/init.d/xend start</userinput>
-&prompt.root; <userinput>/etc/init.d/xendomains start</userinput></screen>
-
-	      <para>Our dom0 is running:</para>
-
-	      <screen>&prompt.root; <userinput>xm list</userinput>
-Name                                      ID   Mem VCPUs      State   Time(s)
-Domain-0                                   0   256     1     r&ndash;&ndash;&ndash;&ndash;&ndash;  54452.9</screen>
-	    </step>
-	  </procedure>
-	</sect3>
-
-	<sect3>
-	  <title>&os; 7-CURRENT <emphasis>domU</emphasis></title>
-
-	  <para>Download the &os; domU kernel for
-	    <application>&xen; 3.0</application> and disk image from
-	    <ulink
-	      url="http://www.fsmware.com/">http://www.fsmware.com/</ulink></para>;
-
-	  <itemizedlist>
-	    <listitem>
-	      <para><ulink
-		  url="http://www.fsmware.com/xenofreebsd/7.0/download/kernel-current">kernel-current</ulink></para>;
-	    </listitem>
-
-	    <listitem>
-	      <para><ulink
-		  url="http://www.fsmware.com/xenofreebsd/7.0/download/mdroot-7.0.bz2">mdroot-7.0.bz2</ulink></para>;
-	    </listitem>
-
-	    <listitem>
-	      <para><ulink
-		  url="http://www.fsmware.com/xenofreebsd/7.0/download/config/xmexample1.bsd">xmexample1.bsd</ulink></para>;
-	    </listitem>
-	  </itemizedlist>
-
-	  <para>Put the configuration file
-	    <filename>xmexample1.bsd</filename> into
-	    <filename>/etc/xen/</filename> and modify the related
-	    entries about where the kernel and the disk image are
-	    stored.  It should look like the following:</para>
-
-	  <programlisting>kernel = "/opt/kernel-current"
-memory = 256
-name = "freebsd"
-vif = [ '' ]
-disk = [ 'file:/opt/mdroot-7.0,hda1,w' ]
-#on_crash    = 'preserve'
-extra = "boot_verbose"
-extra += ",boot_single"
-extra += ",kern.hz=100"
-extra += ",vfs.root.mountfrom=ufs:/dev/xbd769a"</programlisting>
-
-	  <para>Uncompress <filename>mdroot-7.0.bz2</filename>.</para>
-
-	  <para>Next, the __xen_guest section in
-	    <filename>kernel-current</filename> needs to be altered to
-	    add the VIRT_BASE that
-	    <application>&xen; 3.0.3</application> requires:</para>
-
-	  <screen>&prompt.root; <userinput>objcopy kernel-current -R __xen_guest</userinput>
-&prompt.root; <userinput>perl -e 'print "LOADER=generic,GUEST_OS=freebsd,GUEST_VER=7.0,XEN_VER=xen-3.0,BSD_SYMTAB,VIRT_BASE=0xC0000000\x00"' &gt; tmp</userinput>
-&prompt.root; <userinput>objcopy kernel-current &ndash;&ndash;add-section __xen_guest=tmp</userinput></screen>
-
-	  <screen>&prompt.root; <userinput>objdump -j __xen_guest -s kernel-current</userinput>
-
-kernel-current:     file format elf32-i386
-
-Contents of section __xen_guest:
- 0000 4c4f4144 45523d67 656e6572 69632c47  LOADER=generic,G
- 0010 55455354 5f4f533d 66726565 6273642c  UEST_OS=freebsd,
- 0020 47554553 545f5645 523d372e 302c5845  GUEST_VER=7.0,XE
- 0030 4e5f5645 523d7865 6e2d332e 302c4253  N_VER=xen-3.0,BS
- 0040 445f5359 4d544142 2c564952 545f4241  D_SYMTAB,VIRT_BA
- 0050 53453d30 78433030 30303030 3000      SE=0xC0000000. </screen>
-
-	  <para>We are, now, ready to create and launch our
-	    domU:</para>
-
-	  <screen>&prompt.root; <userinput>xm create /etc/xen/xmexample1.bsd -c</userinput>
-Using config file "/etc/xen/xmexample1.bsd".
-Started domain freebsd
-WARNING: loader(8) metadata is missing!
-Copyright (c) 1992-2006 The FreeBSD Project.
-Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
-The Regents of the University of California. All rights reserved.
-FreeBSD 7.0-CURRENT #113: Wed Jan  4 06:25:43 UTC 2006
-    kmacy@freebsd7.gateway.2wire.net:/usr/home/kmacy/p4/freebsd7_xen3/src/sys/i386-xen/compile/XENCONF
-WARNING: DIAGNOSTIC option enabled, expect reduced performance.
-Xen reported: 1796.927 MHz processor.
-Timecounter "ixen" frequency 1796927000 Hz quality 0
-CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1796.93-MHz 686-class CPU)
-  Origin = "GenuineIntel"  Id = 0xf29  Stepping = 9
-  Features=0xbfebfbff&lt;FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,
-  DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE&gt;
-  Features2=0x4400&lt;CNTX-ID,&lt;b14&gt;&gt;
-real memory  = 265244672 (252 MB)
-avail memory = 255963136 (244 MB)
-xc0: &lt;Xen Console&gt; on motherboard
-cpu0 on motherboard
-Timecounters tick every 10.000 msec
-[XEN] Initialising virtual ethernet driver.
-xn0: Ethernet address: 00:16:3e:6b:de:3a
-[XEN]
-Trying to mount root from ufs:/dev/xbd769a
-WARNING: / was not properly dismounted
-Loading configuration files.
-No suitable dump device was found.
-Entropy harvesting: interrupts ethernet point_to_point kickstart.
-Starting file system checks:
-/dev/xbd769a: 18859 files, 140370 used, 113473 free (10769 frags, 12838 blocks, 4.2% fragmentation)
-Setting hostname: demo.freebsd.org.
-lo0: flags=8049&lt;UP,LOOPBACK,RUNNING,MULTICAST&gt; mtu 16384
-	  inet6 ::1 prefixlen 128
-	  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
-	  inet 127.0.0.1 netmask 0xff000000
-Additional routing options:.
-Mounting NFS file systems:.
-Starting syslogd.
-/etc/rc: WARNING: Dump device does not exist.  Savecore not run.
-ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib
-a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout
-Starting usbd.
-usb: Kernel module not available: No such file or directory
-Starting local daemons:.
-Updating motd.
-Starting sshd.
-Initial i386 initialization:.
-Additional ABI support: linux.
-Starting cron.
-Local package initialization:.
-Additional TCP options:.
-Starting background file system checks in 60 seconds.
-
-Sun Apr  1 02:11:43 UTC 2007
-
-FreeBSD/i386 (demo.freebsd.org) (xc0)
-
-login: </screen>
-
-	  <para>The domU should run the &os;&nbsp;7.0-CURRENT
-	    kernel:</para>
-
-	  <screen>&prompt.root; <userinput>uname -a</userinput>
-FreeBSD demo.freebsd.org 7.0-CURRENT FreeBSD 7.0-CURRENT #113: Wed Jan  4 06:25:43 UTC 2006
-kmacy@freebsd7.gateway.2wire.net:/usr/home/kmacy/p4/freebsd7_xen3/src/sys/i386-xen/compile/XENCONF  i386</screen>
-
-	  <para>The network can now be configured on the domU.  The
-	    &os; domU will use a specific interface called
-	    <devicename>xn0</devicename>:</para>
-
-	  <screen>&prompt.root; <userinput>ifconfig xn0 10.10.10.200 netmask 255.0.0.0</userinput>
-&prompt.root; <userinput>ifconfig</userinput>
-xn0: flags=843&lt;UP,BROADCAST,RUNNING,SIMPLEX&gt; mtu 1500
-    inet 10.10.10.200 netmask 0xff000000 broadcast 10.255.255.255
-    ether 00:16:3e:6b:de:3a
-lo0: flags=8049&lt;UP,LOOPBACK,RUNNING,MULTICAST&gt; mtu 16384
-      inet6 ::1 prefixlen 128
-      inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
-      inet 127.0.0.1 netmask 0xff000000 </screen>
-
-	  <para>On dom0 Slackware, some
-	    <application>&xen;</application> dependent network
-	    interfaces should show up:</para>
-
-	  <screen>&prompt.root; <userinput>ifconfig</userinput>
-eth0      Link encap:Ethernet  HWaddr 00:07:E9:A0:02:C2
-	  inet addr:10.10.10.130  Bcast:0.0.0.0  Mask:255.0.0.0
-	  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
-	  RX packets:815 errors:0 dropped:0 overruns:0 frame:0
-	  TX packets:1400 errors:0 dropped:0 overruns:0 carrier:0
-	  collisions:0 txqueuelen:0
-	  RX bytes:204857 (200.0 KiB)  TX bytes:129915 (126.8 KiB)
-
-lo        Link encap:Local Loopback
-	  inet addr:127.0.0.1  Mask:255.0.0.0
-	  UP LOOPBACK RUNNING  MTU:16436  Metric:1
-	  RX packets:99 errors:0 dropped:0 overruns:0 frame:0
-	  TX packets:99 errors:0 dropped:0 overruns:0 carrier:0
-	  collisions:0 txqueuelen:0
-	  RX bytes:9744 (9.5 KiB)  TX bytes:9744 (9.5 KiB)
-
-peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
-	  UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
-	  RX packets:1853349 errors:0 dropped:0 overruns:0 frame:0
-	  TX packets:952923 errors:0 dropped:0 overruns:0 carrier:0
-	  collisions:0 txqueuelen:1000
-	  RX bytes:2432115831 (2.2 GiB)  TX bytes:86528526 (82.5 MiB)
-	  Base address:0xc000 Memory:ef020000-ef040000
-
-vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
-	  UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
-	  RX packets:1400 errors:0 dropped:0 overruns:0 frame:0
-	  TX packets:815 errors:0 dropped:0 overruns:0 carrier:0
-	  collisions:0 txqueuelen:0
-	  RX bytes:129915 (126.8 KiB)  TX bytes:204857 (200.0 KiB)
-
-vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
-	  UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
-	  RX packets:3 errors:0 dropped:0 overruns:0 frame:0
-	  TX packets:2 errors:0 dropped:157 overruns:0 carrier:0
-	  collisions:0 txqueuelen:1
-	  RX bytes:140 (140.0 b)  TX bytes:158 (158.0 b)
-
-xenbr1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
-	  UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
-	  RX packets:4 errors:0 dropped:0 overruns:0 frame:0
-	  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
-	  collisions:0 txqueuelen:0
-	  RX bytes:112 (112.0 b)  TX bytes:0 (0.0 b)</screen>
-
-      <screen>&prompt.root; <userinput>brctl show</userinput>
-bridge name     bridge id           STP enabled         interfaces
-xenbr1          8000.feffffffffff   no                  vif0.1
-                                                        peth0
-                                                        vif1.0</screen>
-	</sect3>
       </sect2>
--->
-    <sect2 xml:id="virtualization-guest-virtualpc">
-      <title><application>Virtual PC</application> on
+    </sect1>
+
+    <sect1 xml:id="virtualization-guest-virtualpc">
+      <title>&os; as a Guest on <application>Virtual PC</application> for
 	&windows;</title>
 
       <para><application>Virtual PC</application> for &windows; is a
@@ -618,7 +296,7 @@ xenbr1          8000.feffffffffff   no  
 	the user can configure a virtual machine and then install the
 	desired guest operating system.</para>
 
-      <sect3 xml:id="virtualization-guest-virtualpc-install">
+      <sect2 xml:id="virtualization-guest-virtualpc-install">
 	<title>Installing &os; on <application>Virtual
 	    PC</application></title>
 
@@ -748,9 +426,9 @@ xenbr1          8000.feffffffffff   no  
 	    <imagedata fileref="virtualization/virtualpc-freebsd13"/>
 	  </imageobject>
 	</mediaobject>
-      </sect3>
+      </sect2>
 
-      <sect3 xml:id="virtualization-guest-virtualpc-configure">
+      <sect2 xml:id="virtualization-guest-virtualpc-configure">
 	<title>Configuring &os; on <application>Virtual
 	    PC</application></title>
 
@@ -803,11 +481,11 @@ xenbr1          8000.feffffffffff   no  
 	      <xref linkend="advanced-networking"/>.</para>
 	  </step>
 	</procedure>
-      </sect3>
-    </sect2>
+      </sect2>
+    </sect1>
 
-    <sect2 xml:id="virtualization-guest-vmware">
-      <title><application>VMware Fusion</application> on
+    <sect1 xml:id="virtualization-guest-vmware">
+      <title>&os; as a Guest on <application>VMware Fusion</application> for
 	&macos;</title>
 
       <para><application>VMware Fusion</application> for &mac; is a
@@ -819,7 +497,7 @@ xenbr1          8000.feffffffffff   no  
 	machine and then install the desired guest operating
 	system.</para>
 
-      <sect3 xml:id="virtualization-guest-vmware-install">
+      <sect2 xml:id="virtualization-guest-vmware-install">
 	<title>Installing &os; on <application>VMware
 	    Fusion</application></title>
 
@@ -952,9 +630,9 @@ xenbr1          8000.feffffffffff   no  
 
 	<para>After modifying the settings, boot the newly installed
 	  &os; virtual machine.</para>
-      </sect3>
+      </sect2>
 
-      <sect3 xml:id="virtualization-guest-vmware-configure">
+      <sect2 xml:id="virtualization-guest-vmware-configure">
 	<title>Configuring &os; on <application>VMware
 	    Fusion</application></title>
 
@@ -1006,12 +684,17 @@ xenbr1          8000.feffffffffff   no  
 	      <xref linkend="advanced-networking"/>.</para>
 	  </step>
 	</procedure>
-      </sect3>
-    </sect2>
+      </sect2>
+    </sect1>
 
-    <sect2 xml:id="virtualization-guest-virtualbox-guest-additions">
+    <sect1 xml:id="virtualization-guest-virtualbox-guest-additions">
       <title>&virtualbox; Guest Additions on a &os; Guest</title>
 
+      <para>&os; works well as a guest in
+	<application>&virtualbox;</application>.  The virtualization
+	software is available for most common operating systems,
+	including &os; itself.</para>
+
       <para>The <application>&virtualbox;</application> guest
 	additions provide support for:</para>
 
@@ -1038,7 +721,7 @@ xenbr1          8000.feffffffffff   no  
       </itemizedlist>
 
       <note>
-	<para>The following commands are run in the &os; guest.</para>
+	<para>These commands are run in the &os; guest.</para>
       </note>
 
       <para>First, install the
@@ -1053,17 +736,6 @@ xenbr1          8000.feffffffffff   no  
       <programlisting>vboxguest_enable="YES"
 vboxservice_enable="YES"</programlisting>
 
-      <para>When <application>Xorg</application> will be used in the
-	guest, any required supporting services must also be enabled
-	just as if the guest was a physical machine.  Typically, these
-	lines would also be added to
-	<filename>/etc/rc.conf</filename>:</para>
-
-      <programlisting>hald_enable="YES"
-dbus_enable="YES"</programlisting>
-
-      <para>See <xref linkend="x-config"/> for details.</para>
-
       <para>If &man.ntpd.8; or &man.ntpdate.8; is used, disable host
 	time synchronization:</para>
 
@@ -1075,15 +747,10 @@ dbus_enable="YES"</programlisting>
 	<filename>/etc/X11/xorg.conf</filename>:</para>
 
       <programlisting>Section "Device"
-	### Available Driver options are:-
-	### Values: &lt;i&gt;: integer, &lt;f&gt;: float, &lt;bool&gt;: "True"/"False",
-	### &lt;string&gt;: "String", &lt;freq&gt;: "&lt;f&gt; Hz/kHz/MHz"
-	### [arg]: arg optional
 	Identifier "Card0"
 	Driver "vboxvideo"
 	VendorName "InnoTek Systemberatung GmbH"
 	BoardName "VirtualBox Graphics Adapter"
-	BusID "PCI:0:2:0"
 EndSection</programlisting>
 
       <para>To use the <literal>vboxmouse</literal> driver, adjust the
@@ -1132,8 +799,7 @@ EndSection</programlisting>
     &lt;/match&gt;
   &lt;/device&gt;
 &lt;/deviceinfo&gt;</programlisting>
-    </sect2>
-  </sect1>
+    </sect1>
 
   <sect1 xml:id="virtualization-host-virtualbox">
     <title>&os; as a Host with
@@ -1181,14 +847,14 @@ EndSection</programlisting>
 
       <screen>&prompt.root; <userinput>kldload vboxdrv</userinput></screen>
 
-      <para>To ensure the module always gets loaded after a reboot,
-	add the following line to
+      <para>To ensure the module is always loaded after a reboot,
+	add this line to
 	<filename>/boot/loader.conf</filename>:</para>
 
       <programlisting>vboxdrv_load="YES"</programlisting>
 
       <para>To use the kernel modules that allow bridged or host-only
-	networking, add the following to
+	networking, add this line to
 	<filename>/etc/rc.conf</filename> and reboot the
 	computer:</para>
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201509022159.t82LxTDA049919>