Attachment 158786 Details for Bug 201578 – SVN diff en_US.ISO8859-1/books/handbook/virtualization/chapter.xml

[patch] SVN diff en_US.ISO8859-1/books/handbook/virtualization/chapter.xml

virtualization_chapter.diff (text/plain), 3.86 KB, created by Shawn Debnath on 2015-07-15 04:22:12 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Shawn Debnath

Created: 2015-07-15 04:22:12 UTC

Size: 3.86 KB

patch

obsolete

>Index: chapter.xml
>===================================================================
>--- chapter.xml	(revision 46961)
>+++ chapter.xml	(working copy)
>@@ -1320,18 +1320,23 @@
>       requires a computer with a newer 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>).  Most newer
>-      processors, specifically the &intel;&nbsp;&core; i3/i5/i7 and
>-      &intel;&nbsp;&xeon; E3/E5/E7, support this feature.  For a
>-      complete list of &intel; processors that support
>-      <acronym>EPT</acronym>, refer to <link
>+      Nested Page Tables (<acronym>NPT</acronym>).  In addition, to
>+      host &linux; guests, or &os; guests with more than one vCPU,
>+      VMX unrestricted mode support (<acronym>UG</acronym>) is also
>+      required. Most newer processors, specifically the &intel;&nbsp;
>+      &core; i3/i5/i7 and &intel;&nbsp;&xeon; E3/E5/E7 support these
>+      features. <acronym>UG</acronym> support was introduced with the
>+      Westmere micro-architecture.  For a complete list of &intel;
>+      processors that support <acronym>EPT</acronym>, refer to <link
>       xlink:href="http://ark.intel.com/search/advanced?s=t&amp;ExtendedPageTables=true">http://ark.intel.com/search/advanced?s=t&amp;ExtendedPageTables=true</link>.
>       <acronym>RVI</acronym> is found on the 3rd  generation and later
>       of the &amd.opteron; (Barcelona) processors.  The easiest way to
>-      check for support of <acronym>EPT</acronym> or
>-      <acronym>RVI</acronym> is to look for the
>-      <literal>POPCNT</literal> processor feature flag on the
>-      <literal>Features2</literal> line in <command>dmesg</command> or
>+      check for support of <acronym>EPT</acronym>,
>+      <acronym>RVI</acronym>, or <acronym>UG</acronym> is to look for
>+      the <literal>POPCNT</literal> processor feature flag on the
>+      <literal>Features2</literal> line and <literal>EPT</literal> and
>+      <literal>UG</literal> on the <literal>VT-x</literal> line in
>+      command>dmesg</command> or
>       <filename>/var/run/dmesg.boot</filename>.</para>
> 
>     <sect2 xml:id="virtualization-bhyve-prep">
>@@ -1506,6 +1511,27 @@
>       <screen>&prompt.root; <userinput>bhyvectl --destroy --vm=<replaceable>linuxguest</replaceable></userinput></screen>
>     </sect2>
> 
>+
>+    <sect2 xml:id="virtualization-bhyve-zfs">
>+      <title>Using ZFS with Bhyve Guests</title>
>+
>+      <para>If the host machine is running on ZFS, using ZFS volumes
>+      instead of disk image files may provide significant performance
>+      benefits for the bhyve guest VMs.  A ZFS volume can be created
>+      by:  </para>
>+
>+      <screen>
>+        &prompt.root; <userinput>zfs create -V16G -o volmode=dev zroot/vdisk0 </screen></userinput> </screen>
>+
>+      <para>Once created, the ZFS volume can be specified as the disk
>+      drive when invoking bhyve to start the guest vm:</para>
>+
>+      <screen>
>+        &prompt.root; <userinput>bhyve -AI -H -P -s 0:0,hostbridge -s 1:0,lpc -s 2:0,virtio-net,tap1 -s3:0,ahci-hd,/dev/zroot/vdisk0 \
>+	-l com1,stdio -c <replaceable>4</replaceable> -m <replaceable>1024M</replaceable> <replaceable>linuxguest</replaceable></userinput></screen>
>+
>+    </sect2>
>+
>     <sect2 xml:id="virtualization-bhyve-nmdm">
>       <title>Virtual Machine Consoles</title>
> 
>@@ -1525,6 +1551,9 @@
> 	(<filename>/dev/nmdm1A</filename> and
> 	<filename>/dev/nmdm1B</filename>).  See &man.nmdm.4; for more
> 	information.</para>
>+      <para>The example below shows how to boot the &linux; guest
>+	created above with it's console redirected to the null modem.
>+	&os; guests can be configured similarly.</para>
> 
>       <screen>&prompt.root; <userinput>kldload nmdm</userinput>
> &prompt.root; <userinput>bhyve -AI -H -P -s 0:0,hostbridge -s 1:0,lpc -s 2:0,virtio-net,tap1 -s 3:0,virtio-blk,./linux.img \

Actions: View | Diff

Attachments on bug 201578: 158786 | 158788 | 158789 | 158813 | 159023