svn commit: r52160 - head/en_US.ISO8859-1/books/handbook/virtualization

[Benedict Reuschling]

Author: bcr
Date: Sun Aug 19 12:15:31 2018
New Revision: 52160
URL: https://svnweb.freebsd.org/changeset/doc/52160

Log:
  Cleanup (non user visible) whitespace issues and rewrap long lines.

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	Sun Aug 19 12:09:31 2018	(r52159)
+++ head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml	Sun Aug 19 12:15:31 2018	(r52160)
@@ -101,7 +101,7 @@
 
       <listitem>
 	<para>Know how to <link linkend="ports">install additional
-	   third-party software</link>.</para>
+	    third-party software</link>.</para>
       </listitem>
     </itemizedlist>
   </sect1>
@@ -921,24 +921,24 @@ perm    vboxnetctl 0660</programlisting>
       <title>&virtualbox; USB Support</title>
 
       <para><application>&virtualbox;</application> can be configured
-      to pass <acronym>USB</acronym> devices through to the guest
-      operating system.  The host controller of the OSE version is
-      limited to emulating <acronym>USB</acronym> 1.1 devices until
-      the extension pack supporting <acronym>USB</acronym> 2.0 and 3.0
-      devices becomes available on &os;.</para>
+	to pass <acronym>USB</acronym> devices through to the guest
+	operating system.  The host controller of the OSE version is
+	limited to emulating <acronym>USB</acronym> 1.1 devices until
+	the extension pack supporting <acronym>USB</acronym> 2.0 and
+	3.0 devices becomes available on &os;.</para>
 
-      <para>For <application>&virtualbox;</application> to be
-      aware of <acronym>USB</acronym> devices attached to the
-      machine, the user needs to be a member of the <systemitem
-      class="groupname">operator</systemitem> group.</para>
+      <para>For <application>&virtualbox;</application> to be aware of
+	<acronym>USB</acronym> devices attached to the machine, the
+	user needs to be a member of the <systemitem
+	  class="groupname">operator</systemitem> group.</para>
 
       <screen>&prompt.root; <userinput>pw groupmod operator -m <replaceable>yourusername</replaceable></userinput></screen>
 
       <para>Restart the login session and
-      <application>&virtualbox;</application> for these changes to take
-      effect, and create <acronym>USB</acronym> filters as
-      necessary.</para>
-      </sect2>
+	<application>&virtualbox;</application> for these changes to
+	take effect, and create <acronym>USB</acronym> filters as
+	necessary.</para>
+    </sect2>
 
     <sect2 xml:id="virtualization-virtualbox-host-dvd-cd-access">
       <title>&virtualbox; Host
@@ -1202,16 +1202,16 @@ grub> <userinput>boot</userinput></screen>
 	that are not supported by the other loaders.</para>
 
       <para>In order to make use of the <acronym>UEFI</acronym>
-        support in <application>bhyve</application>, first obtain the
-        <acronym>UEFI</acronym> firmware images.  This can be done
-	by installing <package>sysutils/bhyve-firmware</package>
-	port or package.</para>
+	support in <application>bhyve</application>, first obtain the
+	<acronym>UEFI</acronym> firmware images.  This can be done by
+	installing <package>sysutils/bhyve-firmware</package> port or
+	package.</para>
 
-      <para>With the firmware in place, add the flags
-	<option>-l bootrom,<replaceable>/path/to/firmware</replaceable></option>
-	to your <application>bhyve</application> command line.
-	The actual <application>bhyve</application> command may look
-	like this:</para>
+      <para>With the firmware in place, add the flags <option>-l
+	  bootrom,<replaceable>/path/to/firmware</replaceable></option>
+	to your <application>bhyve</application> command line.  The
+	actual <application>bhyve</application> command may look like
+	this:</para>
 
       <screen>&prompt.root; <userinput>bhyve -AHP -s 0:0,hostbridge -s 1:0,lpc \
 -s 2:0,virtio-net,<replaceable>tap1</replaceable> -s 3:0,virtio-blk,<replaceable>./disk.img</replaceable> \
@@ -1220,8 +1220,8 @@ grub> <userinput>boot</userinput></screen>
 <replaceable>guest</replaceable></userinput></screen>
 
       <para><package>sysutils/bhyve-firmware</package> also contains a
-	<acronym>CSM</acronym>-enabled firmware, to boot guests with no
-	<acronym>UEFI</acronym> support in legacy
+	<acronym>CSM</acronym>-enabled firmware, to boot guests with
+	no <acronym>UEFI</acronym> support in legacy
 	<acronym>BIOS</acronym> mode:</para>
 
       <screen>&prompt.root; <userinput>bhyve -AHP -s 0:0,hostbridge -s 1:0,lpc \
@@ -1235,12 +1235,13 @@ grub> <userinput>boot</userinput></screen>
       <title>Graphical <acronym>UEFI</acronym> Framebuffer for
 	<application>bhyve</application> Guests</title>
 
-      <para>The <acronym>UEFI</acronym> firmware support is particularly
-	useful with predominantly graphical guest operating systems
-	such as Microsoft &windows;.</para>
+      <para>The <acronym>UEFI</acronym> firmware support is
+	particularly useful with predominantly graphical guest
+	operating systems such as Microsoft &windows;.</para>
 
       <para>Support for the UEFI-GOP framebuffer may also be enabled
-	with the <option>-s 29,fbuf,tcp=<replaceable>0.0.0.0:5900</replaceable></option>
+	with the <option>-s
+	  29,fbuf,tcp=<replaceable>0.0.0.0:5900</replaceable></option>
 	flags.  The framebuffer resolution may be configured with
 	<option>w=<replaceable>800</replaceable></option> and
 	<option>h=<replaceable>600</replaceable></option>, and
@@ -1251,7 +1252,7 @@ grub> <userinput>boot</userinput></screen>
 	<acronym>VNC</acronym> protocol.</para>
 
       <para>The resulting <application>bhyve</application> command
-        would look like this:</para>
+	would look like this:</para>
 
       <screen>&prompt.root; <userinput>bhyve -AHP -s 0:0,hostbridge -s 31:0,lpc \
 -s 2:0,virtio-net,<replaceable>tap1</replaceable> -s 3:0,virtio-blk,<replaceable>./disk.img</replaceable> \