Changeset View
Standalone View
chapter.xml
Context not available. | |||||
requires a computer with a newer processor that supports &intel; | requires a computer with a newer processor that supports &intel; | ||||
Extended Page Tables (<acronym>EPT</acronym>) or &amd; Rapid | Extended Page Tables (<acronym>EPT</acronym>) or &amd; Rapid | ||||
Virtualization Indexing (<acronym>RVI</acronym>), also known as | Virtualization Indexing (<acronym>RVI</acronym>), also known as | ||||
Nested Page Tables (<acronym>NPT</acronym>). Most newer | Nested Page Tables (<acronym>NPT</acronym>). In addition, to | ||||
processors, specifically the &intel; &core; i3/i5/i7 and | host &linux; guests, or &os; guests with more than one vCPU, | ||||
&intel; &xeon; E3/E5/E7, support this feature. For a | VMX unrestricted mode support (<acronym>UG</acronym>) is also | ||||
complete list of &intel; processors that support | required. Most newer processors, specifically the &intel; | ||||
<acronym>EPT</acronym>, refer to <link | &core; i3/i5/i7 and &intel; &xeon; E3/E5/E7 support these | ||||
xlink:href="http://ark.intel.com/search/advanced?s=t&ExtendedPageTables=true">http://ark.intel.com/search/advanced?s=t&ExtendedPageTables=true</link>. | features. <acronym>UG</acronym> support was introduced with | ||||
<acronym>RVI</acronym> is found on the 3rd generation and later | Intel's Westmere micro-architecture. For a complete list of | ||||
of the &amd.opteron; (Barcelona) processors. The easiest way to | &intel; processors that support <acronym>EPT</acronym>, refer to | ||||
check for support of <acronym>EPT</acronym> or | <link xlink:href="http://ark.intel.com/search/advanced?s=t&ExtendedPageTables=true">http://ark.intel.com/search/advanced?s=t&ExtendedPageTables=true</link>. | ||||
wblock: When the content of a <link> is the same as the href, it can just be left empty:
<link xlink… | |||||
<acronym>RVI</acronym> is to look for the | <acronym>RVI</acronym> is found on the third generation and | ||||
<literal>POPCNT</literal> processor feature flag on the | later of the &amd.opteron; (Barcelona) processors. The easiest | ||||
<literal>Features2</literal> line in <command>dmesg</command> or | way to 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> | <filename>/var/run/dmesg.boot</filename>.</para> | ||||
<sect2 xml:id="virtualization-bhyve-prep"> | <sect2 xml:id="virtualization-bhyve-prep"> | ||||
Context not available. | |||||
<screen>&prompt.root; <userinput>bhyvectl --destroy --vm=<replaceable>linuxguest</replaceable></userinput></screen> | <screen>&prompt.root; <userinput>bhyvectl --destroy --vm=<replaceable>linuxguest</replaceable></userinput></screen> | ||||
</sect2> | </sect2> | ||||
<sect2 xml:id="virtualization-bhyve-zfs"> | |||||
<title>Using ZFS with Bhyve Guests</title> | |||||
wblockUnsubmitted Done Inline ActionsReserved words should not be capitalized in titles. There is disagreement over how this should be handled, but I would use the man page reference here. Also, "ZFS" is an acronym: <title>Using <acronym>ZFS</acronym> with &man.bhyve.8; Guests</title> wblock: Reserved words should not be capitalized in titles. There is disagreement over how this should… | |||||
sd_beastie.ioAuthorUnsubmitted Not Done Inline ActionsTo match what the rest of the document is doing, perhaps surrounding lowercased bhyve with the <application /> element might be reasonable. Similar to the section header. sd_beastie.io: To match what the rest of the document is doing, perhaps surrounding lowercased bhyve with the… | |||||
<para>If the host machine is running on ZFS, using ZFS volumes | |||||
wblockUnsubmitted Done Inline ActionsThis is kind of a confusing sentence. Really, I think it is trying to say: <para>If the host machine has ZFS, using ZFS volumes (Just an idea, you might have a better way to say that.) wblock: This is kind of a confusing sentence. Really, I think it is trying to say:
<para>If the host… | |||||
instead of disk image files may provide significant | |||||
wblockUnsubmitted Done Inline Actions"May" usually means permission. "Might" or "can" are usually better for probability. "Can" is good here: instead of disk image files can provide significant wblock: "May" usually means permission. "Might" or "can" are usually better for probability. "Can" is… | |||||
performance benefits for the guest VMs. A ZFS volume | |||||
wblockUnsubmitted Done Inline Actions<acronym> tags... wblock: <acronym> tags... | |||||
can be created by:</para> | |||||
<screen>&prompt.root; <userinput>zfs create -V16G -o volmode=dev zroot/vdisk0</userinput> </screen> | |||||
wblockUnsubmitted Done Inline ActionsThe indent might not be right, but Phabricator is easily confused by that, so it's hard to tell. <screen> should be indented the same as the <para> tag above it. Also, some of those parameters should have <replaceable> tags, showing that they are values the user would choose for themselves: zfs create -V<replaceable>16G</replaceable> -o volmode=dev <replaceable>zroot/vdisk0</replaceable> wblock: The indent might not be right, but Phabricator is easily confused by that, so it's hard to tell. | |||||
allanjudeUnsubmitted Done Inline Actionsuse the <replaceable> tags around anything the user is supposed to change, (16G and zroot/vdisk0) allanjude: use the <replaceable> tags around anything the user is supposed to change, (16G and… | |||||
<para>Once created, the ZFS volume can be specified as the disk | |||||
wblockUnsubmitted Done Inline Actions"Once created" and "using bhyve" are kind of givens, here. Maybe just reword: When starting the guest <acronym>VM</acronym>, specify the <acronym>ZFS</acronym> volume as the disk drive: (Yes, "VM" is an acronym too. Pretend I noticed that above.) wblock: "Once created" and "using bhyve" are kind of givens, here. Maybe just reword:
When starting… | |||||
drive when starting the guest vm using bhyve:</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/zvol/zroot/vdisk0 \ -l com1,stdio -c <replaceable>4</replaceable> -m <replaceable>1024M</replaceable> <replaceable>linuxguest</replaceable></userinput></screen> | |||||
allanjudeUnsubmitted Done Inline Actionsreplaceable tags on the zvol path allanjude: replaceable tags on the zvol path | |||||
wblockUnsubmitted Done Inline ActionsIndentation might be off. More of the parameters should be specified as replaceable (particularly the name of the ZFS volume). Phabricator is probably "helping" with the line wrap after the backslash, so it's probably right but looks wrong. wblock: Indentation might be off. More of the parameters should be specified as replaceable… | |||||
</sect2> | |||||
<sect2 xml:id="virtualization-bhyve-nmdm"> | <sect2 xml:id="virtualization-bhyve-nmdm"> | ||||
<title>Virtual Machine Consoles</title> | <title>Virtual Machine Consoles</title> | ||||
Context not available. | |||||
<filename>/dev/nmdm1B</filename>). See &man.nmdm.4; for more | <filename>/dev/nmdm1B</filename>). See &man.nmdm.4; for more | ||||
information.</para> | information.</para> | ||||
<para>The example below shows how to boot the &linux; guest | |||||
wblockUnsubmitted Done Inline Actions"The example below" is not terrible, but even better is to avoid the need to say that at all: The &linux; guest created in the previous example can be started with the console redirected to the null modem: wblock: "The example below" is not terrible, but even better is to avoid the need to say that at all… | |||||
created above with the console redirected to the null modem. | |||||
&os; guests can be configured similarly.</para> | |||||
wblockUnsubmitted Done Inline ActionsThis is kind of confusing, especially when it is shown before the example. "Similarly" is also vague, meaning "like this, but different", so the reader (me, in this case) immediately asks "different how?" Maybe make the paragraph leading up to this example more general. "Consoles of &os; and &linux; <acronym>VM</acronym> guests can be redirected to the null modem device. To redirect the console of the &linux; guest created in the previous example: (this replaces the earlier two sentences, if you see what I mean) wblock: This is kind of confusing, especially when it is shown before the example. "Similarly" is also… | |||||
sd_beastie.ioAuthorUnsubmitted Not Done Inline ActionsRemoving my change here as it seems its already quite obvious. sd_beastie.io: Removing my change here as it seems its already quite obvious. | |||||
<screen>&prompt.root; <userinput>kldload nmdm</userinput> | <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 \ | &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 \ | ||||
allanjudeUnsubmitted Done Inline Actionsseems my original version missed the replaceable tag on ./linux.img allanjude: seems my original version missed the replaceable tag on ./linux.img | |||||
wblockUnsubmitted Done Inline ActionsSame warning about <replaceables>, be consistent with what was shown earlier. wblock: Same warning about <replaceables>, be consistent with what was shown earlier. | |||||
-l com1,<replaceable>/dev/nmdm0A</replaceable> -c <replaceable>4</replaceable> -m <replaceable>1024M</replaceable> <replaceable>linuxguest</replaceable></userinput> | -l com1,<replaceable>/dev/nmdm0A</replaceable> -c <replaceable>4</replaceable> -m <replaceable>1024M</replaceable> <replaceable>linuxguest</replaceable></userinput> | ||||
Context not available. |
When the content of a <link> is the same as the href, it can just be left empty:
<link xlink:href="http://something"></link>
or the even shorter form
<link xlink:href="http://something"/>
See https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/docbook-markup-links.html#idp60797136