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

Warren Block wblock at FreeBSD.org
Sun Apr 3 16:29:33 UTC 2016


Author: wblock
Date: Sun Apr  3 16:29:31 2016
New Revision: 48526
URL: https://svnweb.freebsd.org/changeset/doc/48526

Log:
  Reword ambiguous wording about which processors are required for bhyve.
  De-Shatnerize some long, pausing sentences.
  
  Submitted by:	amiramix (forum user)

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 Apr  3 06:04:03 2016	(r48525)
+++ head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml	Sun Apr  3 16:29:31 2016	(r48526)
@@ -988,25 +988,25 @@ perm pass* 0660</programlisting>
     <title>&os; as a Host with
       <application>bhyve</application></title>
 
-    <para>Starting with &os; 10.0-RELEASE, the
+    <para>The
       <application>bhyve</application> <acronym>BSD</acronym>-licensed
-      hypervisor is part of the base system.  This hypervisor supports
+      hypervisor became part of the base system with &os; 10.0-RELEASE.  This hypervisor supports
       a number of guests, including &os;, OpenBSD, and many &linux;
       distributions.  Currently, <application>bhyve</application> only
       supports a serial console and does not emulate a graphical
-      console.  As a legacy-free hypervisor, it relies on the
-      virtualization offload features of newer
-      <acronym>CPU</acronym>s, instead of translating instructions and
+      console.
+      Virtualization offload features of newer
+      <acronym>CPU</acronym>s are used to avoid the legacy methods of translating instructions and
       manually managing memory mappings.</para>
 
-    <para>Due to the design of <application>bhyve</application>, it
-      requires a computer with a newer processor that supports &intel;
+    <para>The <application>bhyve</application> design
+      requires a processor that supports &intel;
       Extended Page Tables (<acronym>EPT</acronym>) or &amd; Rapid
-      Virtualization Indexing (<acronym>RVI</acronym>), also known as
-      Nested Page Tables (<acronym>NPT</acronym>).  In addition, to
-      host &linux; guests, or &os; guests with more than one
-      <acronym>vCPU</acronym>, <acronym>VMX</acronym> unrestricted
-      mode support (<acronym>UG</acronym>) is also required.  Most
+      Virtualization Indexing (<acronym>RVI</acronym>) or
+      Nested Page Tables (<acronym>NPT</acronym>).  Hosting
+      &linux; guests or &os; guests with more than one
+      <acronym>vCPU</acronym> requires <acronym>VMX</acronym> unrestricted
+      mode support (<acronym>UG</acronym>).  Most
       newer processors, specifically the &intel;  &core;
       i3/i5/i7 and &intel;  &xeon; E3/E5/E7, support these
       features.  <acronym>UG</acronym> support was introduced with
@@ -1016,14 +1016,14 @@ perm pass* 0660</programlisting>
 	xlink:href="http://ark.intel.com/search/advanced?s=t&ExtendedPageTables=true"/>.
       <acronym>RVI</acronym> is found on the third generation and
       later of the &amd.opteron; (Barcelona) processors.  The easiest
-      way to tell if a processor will support
+      way to tell if a processor supports
       <application>bhyve</application> is to run
       <command>dmesg</command> or look in
       <filename>/var/run/dmesg.boot</filename> for the
       <literal>POPCNT</literal> processor feature flag on the
-      <literal>Features2</literal> line and <literal>EPT</literal> and
+      <literal>Features2</literal> line for &amd; processors or <literal>EPT</literal> and
       <literal>UG</literal> on the <literal>VT-x</literal>
-      line.</para>
+      line for &intel; processors.</para>
 
     <sect2 xml:id="virtualization-bhyve-prep">
       <title>Preparing the Host</title>


More information about the svn-doc-all mailing list