os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- domU -> DomU

Browse source 
- use <errorname> instead of <literal> for errors
- fix commands in <screen> example
- format assignments consistently

Reviewed by:	bcr
Differential Revision:	https://reviews.freebsd.org/D11267
This commit is contained in:
Bjoern Heidotting 2017-06-23 12:33:07 +00:00
parent eda011c13e
commit 612ab119d2
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=50396
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
en_US.ISO8859-1/books/handbook/virtualization/chapter.xml
View file

@ -1449,7 +1449,7 @@ ifconfig_bridge0="addm <replaceable>igb0</replaceable> addm <replaceable>tap0</r
for the Dom0 integration. An entry to for the Dom0 integration. An entry to
<filename>/etc/sysctl.conf</filename> disables the limit on <filename>/etc/sysctl.conf</filename> disables the limit on
how many pages of memory are allowed to be wired. Otherwise, how many pages of memory are allowed to be wired. Otherwise,
domU VMs with higher memory requirements will not run.</para> DomU VMs with higher memory requirements will not run.</para>
<screen>&prompt.root; <userinput>sysrc -f /etc/sysctl.conf vm.max_wired=-1</userinput></screen> <screen>&prompt.root; <userinput>sysrc -f /etc/sysctl.conf vm.max_wired=-1</userinput></screen>
@ -1457,8 +1457,8 @@ ifconfig_bridge0="addm <replaceable>igb0</replaceable> addm <replaceable>tap0</r
<filename>/etc/login.conf</filename>, setting the <filename>/etc/login.conf</filename>, setting the
<literal>memorylocked</literal> option to <literal>memorylocked</literal> option to
<literal>unlimited</literal>. Otherwise, creating DomU <literal>unlimited</literal>. Otherwise, creating DomU
domains may fail with <literal>Cannot allocate domains may fail with <errorname>Cannot allocate
memory</literal> errors. After making the change to memory</errorname> errors. After making the change to
<filename>/etc/login.conf</filename>, run <filename>/etc/login.conf</filename>, run
<command>cap_mkdb</command> to update the capability database. <command>cap_mkdb</command> to update the capability database.
See <xref linkend="security-resourcelimits"/> for See <xref linkend="security-resourcelimits"/> for
@ -1483,8 +1483,8 @@ ifconfig_bridge0="addm <replaceable>igb0</replaceable> addm <replaceable>tap0</r
defined.</para> defined.</para>
<screen>&prompt.root; <userinput>sysrc -f /boot/loader.conf hw.pci.mcfg=0</userinput> <screen>&prompt.root; <userinput>sysrc -f /boot/loader.conf hw.pci.mcfg=0</userinput>
&prompt.root; <userinput>xen_kernel="/boot/xen"</userinput> &prompt.root; <userinput>sysrc -f /boot/loader.conf xen_kernel="/boot/xen"</userinput>
&prompt.root; <userinput>xen_cmdline="dom0_mem=<replaceable>8192M</replaceable> dom0_max_vcpus=<replaceable>4</replaceable> dom0pvh=1 console=com1,vga com1=115200,8n1 guest_loglvl=all loglvl=all"</userinput></screen> &prompt.root; <userinput>sysrc -f /boot/loader.conf xen_cmdline="dom0_mem=<replaceable>8192M</replaceable> dom0_max_vcpus=<replaceable>4</replaceable> dom0pvh=1 console=com1,vga com1=115200,8n1 guest_loglvl=all loglvl=all"</userinput></screen>
<para>Log files that &xen; creates for the Dom0 and DomU VMs <para>Log files that &xen; creates for the Dom0 and DomU VMs
are stored in <filename>/var/log/xen</filename>. This are stored in <filename>/var/log/xen</filename>. This
@ -1537,7 +1537,7 @@ Domain-0 0 8192 4 r----- 962.0<
that were defined in <filename>/boot/loader.conf</filename> that were defined in <filename>/boot/loader.conf</filename>
earlier. More information can be found in the <link earlier. More information can be found in the <link
xlink:href="https://www.xenproject.org/help/documentation.html">&xen; xlink:href="https://www.xenproject.org/help/documentation.html">&xen;
Documentation</link>. NDomU guest VMs can now be Documentation</link>. DomU guest VMs can now be
created.</para> created.</para>
</sect2> </sect2>
@ -1579,8 +1579,8 @@ disk = [
] ]
vnc = 1 <co xml:id="co-xen-vnc"/> vnc = 1 <co xml:id="co-xen-vnc"/>
vnclisten = "0.0.0.0" vnclisten = "0.0.0.0"
serial="pty" serial = "pty"
usbdevice="tablet"</screen> usbdevice = "tablet"</screen>
<para>These lines are explained in more detail:</para> <para>These lines are explained in more detail:</para>