Date: Mon, 5 May 2014 19:08:43 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44765 - head/en_US.ISO8859-1/books/handbook/virtualization Message-ID: <201405051908.s45J8hMW062979@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Mon May 5 19:08:43 2014 New Revision: 44765 URL: http://svnweb.freebsd.org/changeset/doc/44765 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems 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 Mon May 5 18:55:19 2014 (r44764) +++ head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml Mon May 5 19:08:43 2014 (r44765) @@ -1126,7 +1126,8 @@ EndSection</programlisting> </sect1> <sect1 xml:id="virtualization-host-virtualbox"> - <title>&os; as a Host with <application>VirtualBox</application></title> + <title>&os; as a Host with + <application>VirtualBox</application></title> <para><application>&virtualbox;</application> is an actively developed, complete virtualization package, that is available @@ -1294,38 +1295,36 @@ perm pass* 0660</programlisting> <title>&os; as a Host with <application>bhyve</application></title> - <para>Starting with &os; 10.0-RELEASE, the <application>bhyve</application> - <acronym>BSD</acronym>-licensed hypervisor is part of the base system. - 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 manually - managing memory mappings. - It also avoids emulating + <para>Starting with &os; 10.0-RELEASE, the + <application>bhyve</application> <acronym>BSD</acronym>-licensed + hypervisor is part of the base system. 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 + manually managing memory mappings. It also avoids emulating compatible hardware for the guest and instead relies on para-virtualization drivers. In &os;, these are provided by the &man.virtio.4; driver.</para> <para>Due to the design of <application>bhyve</application>, it 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 know - as Nested Page Tables (<acronym>NPT</acronym>). Most newer + Extended Page Tables (<acronym>EPT</acronym>) or &amd; Rapid + Virtualization Indexing (<acronym>RVI</acronym>), also know as + Nested Page Tables (<acronym>NPT</acronym>). Most newer processors, specifically the &intel; &core; i3/i5/i7 and &intel; &xeon; E3/E5/E7, support this feature. 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&ExtendedPageTables=true">http://ark.intel.com/search/advanced?s=t&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 + <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 <filename>/var/run/dmesg.boot</filename>.</para> <sect2 xml:id="virtualization-bhyve-prep"> @@ -1333,20 +1332,20 @@ perm pass* 0660</programlisting> <para>The first step to creating a virtual machine in <application>bhyve</application> is configuring the host - system. First, load the <application>bhyve</application> kernel - module:</para> + system. First, load the <application>bhyve</application> + kernel module:</para> <screen>&prompt.root; <userinput>kldload vmm</userinput></screen> - <para>Then, create a <filename>tap</filename> - interface for the network device in the virtual machine to - attach to. In order for the network device to participate in - the network, also create a bridge interface containing the - <filename>tap</filename> interface ane the physical - interface as members. In this example, the physical interface - is <replaceable>igb0</replaceable>:</para> + <para>Then, create a <filename>tap</filename> interface for the + network device in the virtual machine to attach to. In order + for the network device to participate in the network, also + create a bridge interface containing the + <filename>tap</filename> interface ane the physical interface + as members. In this example, the physical interface is + <replaceable>igb0</replaceable>:</para> -<screen>&prompt.root; <userinput>ifconfig <replaceable>tap0</replaceable> create</userinput> + <screen>&prompt.root; <userinput>ifconfig <replaceable>tap0</replaceable> create</userinput> &prompt.root; <userinput>sysctl net.link.tap.up_on_open=1</userinput> net.link.tap.up_on_open: 0 -> 1 &prompt.root; <userinput>ifconfig <replaceable>bridge0</replaceable> create</userinput> @@ -1358,7 +1357,8 @@ net.link.tap.up_on_open: 0 -> 1 <title>Creating a FreeBSD Guest</title> <para>Create a file to use as the virtual disk for the guest - machine. Specify the size and name of the virtual disk:</para> + machine. Specify the size and name of the virtual + disk:</para> <screen>&prompt.root; <userinput>truncate -s <replaceable>16G</replaceable> <replaceable>guest.img</replaceable></userinput></screen> @@ -1377,17 +1377,18 @@ FreeBSD-10.0-RELEASE-amd64-bootonly.iso the guest, <option>-t</option> defines which <filename>tap</filename> device to use, <option>-d</option> indicates which disk image to use, <option>-i</option> tells - <application>bhyve</application> to boot from the <acronym>CD</acronym> image - instead of the disk, and <option>-I</option> defines which <acronym>CD</acronym> - image to use. The last parameter is the name of the - virtual machine, used to track the running machines. This example starts - the virtual machine in installation mode:</para> + <application>bhyve</application> to boot from the + <acronym>CD</acronym> image instead of the disk, and + <option>-I</option> defines which <acronym>CD</acronym> image + to use. The last parameter is the name of the virtual + machine, used to track the running machines. This example + starts the virtual machine in installation mode:</para> <screen>&prompt.root; <userinput>sh /usr/share/examples/bhyve/vmrun.sh -c <replaceable>4</replaceable> -m <replaceable>1024M</replaceable> -t tap0 -d <replaceable>guest.img</replaceable> -i -I <replaceable>FreeBSD-10.0-RELEASE-amd64-bootonly.iso</replaceable> <replaceable>guestname</replaceable></userinput></screen> - <para>The virtual machine will boot and start the installer. After - installing a system in the virtual machine, when the system - asks about dropping in to a shell at the end of the + <para>The virtual machine will boot and start the installer. + After installing a system in the virtual machine, when the + system asks about dropping in to a shell at the end of the installation, choose <guibutton>Yes</guibutton>. A small change needs to be made to make the system start with a serial console. Edit <filename>/etc/ttys</filename> and replace the @@ -1395,8 +1396,8 @@ FreeBSD-10.0-RELEASE-amd64-bootonly.iso <programlisting>console "/usr/libexec/getty std.9600" xterm on secure</programlisting> - <para>Reboot the virtual machine. While rebooting the virtual machine - causes <application>bhyve</application> to exit, the + <para>Reboot the virtual machine. While rebooting the virtual + machine causes <application>bhyve</application> to exit, the <filename>vmrun.sh</filename> script runs <command>bhyve</command> in a loop and will automatically restart it. When this happens, choose the reboot option from @@ -1413,17 +1414,17 @@ FreeBSD-10.0-RELEASE-amd64-bootonly.iso <package>sysutils/grub2-bhyve</package> port must be first installed.</para> - <para>Next, create a file to use as the virtual disk for the guest - machine:</para> + <para>Next, create a file to use as the virtual disk for the + guest machine:</para> <screen>&prompt.root; <userinput>truncate -s <replaceable>16G</replaceable> <replaceable>linux.img</replaceable></userinput></screen> <para>Starting a virtual machine with <application>bhyve</application> is a two step process. First - a kernel must be loaded, then the guest can be started. - The &linux; kernel is loaded with - <package>sysutils/grub2-bhyve</package>. - Create a <filename>device.map</filename> that + a kernel must be loaded, then the guest can be started. The + &linux; kernel is loaded with + <package>sysutils/grub2-bhyve</package>. Create a + <filename>device.map</filename> that <application>grub</application> will use to map the virtual devices to the files on the host system:</para> @@ -1435,7 +1436,8 @@ FreeBSD-10.0-RELEASE-amd64-bootonly.iso <screen>&prompt.root; <userinput>grub-bhyve -m device.map -r cd0 -M <replaceable>1024M</replaceable> <replaceable>linuxguest</replaceable></userinput></screen> - <para>This will start grub. If the installation <acronym>CD</acronym> contains a + <para>This will start grub. If the installation + <acronym>CD</acronym> contains a <filename>grub.cfg</filename>, a menu will be displayed. If not, the <literal>vmlinuz</literal> and <literal>initrd</literal> files must be located and loaded @@ -1502,13 +1504,13 @@ grub> <userinput>boot</userinput></scree <package>sysutils/screen</package> in order to detach and reattach to the console. It is also possible to have the console of <application>bhyve</application> be a null modem - device that can be accessed with <command>cu</command>. To do this, load - the <filename>nmdm</filename> kernel module and replace - <option>-l com1,stdio</option> with + device that can be accessed with <command>cu</command>. To do + this, load the <filename>nmdm</filename> kernel module and + replace <option>-l com1,stdio</option> with <option>-l com1,/dev/nmdm0A</option>. The <filename>/dev/nmdm</filename> devices are created - automatically as needed, where each is a pair, corresponding to the two ends - of the null modem cable + automatically as needed, where each is a pair, corresponding + to the two ends of the null modem cable (<filename>/dev/nmdm1A</filename> and <filename>/dev/nmdm1B</filename>). See &man.nmdm.4; for more information.</para> @@ -1522,7 +1524,6 @@ Connected Ubuntu 13.10 handbook ttyS0 handbook login:</screen> - </sect2> <sect2 xml:id="virtualization-bhyve-managing"> @@ -1552,8 +1553,7 @@ crw------- 1 root wheel 0x1a1 Mar 17 <para>In order to configure the system to start <application>bhyve</application> guests at boot time, add - the following entries to in the following - files:</para> + the following entries to in the following files:</para> <procedure> <step>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201405051908.s45J8hMW062979>