|
Lines 1320-1337
Link Here
|
| 1320 |
requires a computer with a newer processor that supports &intel; |
1320 |
requires a computer with a newer processor that supports &intel; |
| 1321 |
Extended Page Tables (<acronym>EPT</acronym>) or &amd; Rapid |
1321 |
Extended Page Tables (<acronym>EPT</acronym>) or &amd; Rapid |
| 1322 |
Virtualization Indexing (<acronym>RVI</acronym>), also known as |
1322 |
Virtualization Indexing (<acronym>RVI</acronym>), also known as |
| 1323 |
Nested Page Tables (<acronym>NPT</acronym>). Most newer |
1323 |
Nested Page Tables (<acronym>NPT</acronym>). In addition, to |
| 1324 |
processors, specifically the &intel; &core; i3/i5/i7 and |
1324 |
host &linux; guests, or &os; guests with more than one vCPU, |
| 1325 |
&intel; &xeon; E3/E5/E7, support this feature. For a |
1325 |
VMX unrestricted mode support (<acronym>UG</acronym>) is also |
| 1326 |
complete list of &intel; processors that support |
1326 |
required. Most newer processors, specifically the &intel; |
| 1327 |
<acronym>EPT</acronym>, refer to <link |
1327 |
&core; i3/i5/i7 and &intel; &xeon; E3/E5/E7 support these |
|
|
1328 |
features. <acronym>UG</acronym> support was introduced with the |
| 1329 |
Westmere micro-architecture. For a complete list of &intel; |
| 1330 |
processors that support <acronym>EPT</acronym>, refer to <link |
| 1328 |
xlink:href="http://ark.intel.com/search/advanced?s=t&ExtendedPageTables=true">http://ark.intel.com/search/advanced?s=t&ExtendedPageTables=true</link>. |
1331 |
xlink:href="http://ark.intel.com/search/advanced?s=t&ExtendedPageTables=true">http://ark.intel.com/search/advanced?s=t&ExtendedPageTables=true</link>. |
| 1329 |
<acronym>RVI</acronym> is found on the 3rd generation and later |
1332 |
<acronym>RVI</acronym> is found on the 3rd generation and later |
| 1330 |
of the &amd.opteron; (Barcelona) processors. The easiest way to |
1333 |
of the &amd.opteron; (Barcelona) processors. The easiest way to |
| 1331 |
check for support of <acronym>EPT</acronym> or |
1334 |
check for support of <acronym>EPT</acronym>, |
| 1332 |
<acronym>RVI</acronym> is to look for the |
1335 |
<acronym>RVI</acronym>, or <acronym>UG</acronym> is to look for |
| 1333 |
<literal>POPCNT</literal> processor feature flag on the |
1336 |
the <literal>POPCNT</literal> processor feature flag on the |
| 1334 |
<literal>Features2</literal> line in <command>dmesg</command> or |
1337 |
<literal>Features2</literal> line and <literal>EPT</literal> and |
|
|
1338 |
<literal>UG</literal> on the <literal>VT-x</literal> line in |
| 1339 |
command>dmesg</command> or |
| 1335 |
<filename>/var/run/dmesg.boot</filename>.</para> |
1340 |
<filename>/var/run/dmesg.boot</filename>.</para> |
| 1336 |
|
1341 |
|
| 1337 |
<sect2 xml:id="virtualization-bhyve-prep"> |
1342 |
<sect2 xml:id="virtualization-bhyve-prep"> |
|
Lines 1506-1511
Link Here
|
| 1506 |
<screen>&prompt.root; <userinput>bhyvectl --destroy --vm=<replaceable>linuxguest</replaceable></userinput></screen> |
1511 |
<screen>&prompt.root; <userinput>bhyvectl --destroy --vm=<replaceable>linuxguest</replaceable></userinput></screen> |
| 1507 |
</sect2> |
1512 |
</sect2> |
| 1508 |
|
1513 |
|
|
|
1514 |
|
| 1515 |
<sect2 xml:id="virtualization-bhyve-zfs"> |
| 1516 |
<title>Using ZFS with Bhyve Guests</title> |
| 1517 |
|
| 1518 |
<para>If the host machine is running on ZFS, using ZFS volumes |
| 1519 |
instead of disk image files may provide significant performance |
| 1520 |
benefits for the bhyve guest VMs. A ZFS volume can be created |
| 1521 |
by: </para> |
| 1522 |
|
| 1523 |
<screen> |
| 1524 |
&prompt.root; <userinput>zfs create -V16G -o volmode=dev zroot/vdisk0 </screen></userinput> </screen> |
| 1525 |
|
| 1526 |
<para>Once created, the ZFS volume can be specified as the disk |
| 1527 |
drive when invoking bhyve to start the guest vm:</para> |
| 1528 |
|
| 1529 |
<screen> |
| 1530 |
&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 \ |
| 1531 |
-l com1,stdio -c <replaceable>4</replaceable> -m <replaceable>1024M</replaceable> <replaceable>linuxguest</replaceable></userinput></screen> |
| 1532 |
|
| 1533 |
</sect2> |
| 1534 |
|
| 1509 |
<sect2 xml:id="virtualization-bhyve-nmdm"> |
1535 |
<sect2 xml:id="virtualization-bhyve-nmdm"> |
| 1510 |
<title>Virtual Machine Consoles</title> |
1536 |
<title>Virtual Machine Consoles</title> |
| 1511 |
|
1537 |
|
|
Lines 1525-1530
Link Here
|
| 1525 |
(<filename>/dev/nmdm1A</filename> and |
1551 |
(<filename>/dev/nmdm1A</filename> and |
| 1526 |
<filename>/dev/nmdm1B</filename>). See &man.nmdm.4; for more |
1552 |
<filename>/dev/nmdm1B</filename>). See &man.nmdm.4; for more |
| 1527 |
information.</para> |
1553 |
information.</para> |
|
|
1554 |
<para>The example below shows how to boot the &linux; guest |
| 1555 |
created above with it's console redirected to the null modem. |
| 1556 |
&os; guests can be configured similarly.</para> |
| 1528 |
|
1557 |
|
| 1529 |
<screen>&prompt.root; <userinput>kldload nmdm</userinput> |
1558 |
<screen>&prompt.root; <userinput>kldload nmdm</userinput> |
| 1530 |
&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 \ |
1559 |
&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 \ |