From owner-svn-doc-all@FreeBSD.ORG Mon May 5 19:08:43 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D00259E1; Mon, 5 May 2014 19:08:43 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BBE715BDF; Mon, 5 May 2014 19:08:43 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s45J8h9K063023; Mon, 5 May 2014 19:08:43 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s45J8hMW062979; Mon, 5 May 2014 19:08:43 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405051908.s45J8hMW062979@svn.freebsd.org> From: Dru Lavigne Date: Mon, 5 May 2014 19:08:43 +0000 (UTC) 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 X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 May 2014 19:08:44 -0000 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 - &os; as a Host with <application>VirtualBox</application> + &os; as a Host with + <application>VirtualBox</application> &virtualbox; is an actively developed, complete virtualization package, that is available @@ -1294,38 +1295,36 @@ perm pass* 0660 &os; as a Host with <application>bhyve</application> - Starting with &os; 10.0-RELEASE, the bhyve - BSD-licensed hypervisor is part of the base system. - This hypervisor supports a number of guests, - including &os;, OpenBSD, and many &linux; distributions. - Currently, bhyve 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 CPUs, - instead of translating instructions and manually - managing memory mappings. - It also avoids emulating + Starting with &os; 10.0-RELEASE, the + bhyve BSD-licensed + hypervisor is part of the base system. This hypervisor supports + a number of guests, including &os;, OpenBSD, and many &linux; + distributions. Currently, bhyve 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 + CPUs, 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. Due to the design of bhyve, it requires a computer with a newer processor that supports &intel; - Extended Page Tables (EPT) or &amd; - Rapid Virtualization Indexing (RVI), also know - as Nested Page Tables (NPT). Most newer + Extended Page Tables (EPT) or &amd; Rapid + Virtualization Indexing (RVI), also know as + Nested Page Tables (NPT). 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 EPT, refer to http://ark.intel.com/search/advanced?s=t&ExtendedPageTables=true. - RVI is found on the 3rd - generation and later of the &amd.opteron; (Barcelona) - processors. The easiest way to check for support of - EPT or RVI is - to look for the POPCNT processor feature flag - on the Features2 line in - dmesg or + RVI is found on the 3rd generation and later + of the &amd.opteron; (Barcelona) processors. The easiest way to + check for support of EPT or + RVI is to look for the + POPCNT processor feature flag on the + Features2 line in dmesg or /var/run/dmesg.boot. @@ -1333,20 +1332,20 @@ perm pass* 0660 The first step to creating a virtual machine in bhyve is configuring the host - system. First, load the bhyve kernel - module: + system. First, load the bhyve + kernel module: &prompt.root; kldload vmm - Then, create a tap - 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 - tap interface ane the physical - interface as members. In this example, the physical interface - is igb0: + Then, create a tap 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 + tap interface ane the physical interface + as members. In this example, the physical interface is + igb0: -&prompt.root; ifconfig tap0 create + &prompt.root; ifconfig tap0 create &prompt.root; sysctl net.link.tap.up_on_open=1 net.link.tap.up_on_open: 0 -> 1 &prompt.root; ifconfig bridge0 create @@ -1358,7 +1357,8 @@ net.link.tap.up_on_open: 0 -> 1 Creating a FreeBSD Guest Create a file to use as the virtual disk for the guest - machine. Specify the size and name of the virtual disk: + machine. Specify the size and name of the virtual + disk: &prompt.root; truncate -s 16G guest.img @@ -1377,17 +1377,18 @@ FreeBSD-10.0-RELEASE-amd64-bootonly.iso the guest, defines which tap device to use, indicates which disk image to use, tells - bhyve to boot from the CD image - instead of the disk, and defines which CD - 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: + bhyve to boot from the + CD image instead of the disk, and + defines which CD 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: &prompt.root; sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 1024M -t tap0 -d guest.img -i -I FreeBSD-10.0-RELEASE-amd64-bootonly.iso guestname - 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 + 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 Yes. A small change needs to be made to make the system start with a serial console. Edit /etc/ttys and replace the @@ -1395,8 +1396,8 @@ FreeBSD-10.0-RELEASE-amd64-bootonly.iso console "/usr/libexec/getty std.9600" xterm on secure - Reboot the virtual machine. While rebooting the virtual machine - causes bhyve to exit, the + Reboot the virtual machine. While rebooting the virtual + machine causes bhyve to exit, the vmrun.sh script runs bhyve 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 sysutils/grub2-bhyve port must be first installed. - Next, create a file to use as the virtual disk for the guest - machine: + Next, create a file to use as the virtual disk for the + guest machine: &prompt.root; truncate -s 16G linux.img Starting a virtual machine with bhyve is a two step process. First - a kernel must be loaded, then the guest can be started. - The &linux; kernel is loaded with - sysutils/grub2-bhyve. - Create a device.map that + a kernel must be loaded, then the guest can be started. The + &linux; kernel is loaded with + sysutils/grub2-bhyve. Create a + device.map that grub will use to map the virtual devices to the files on the host system: @@ -1435,7 +1436,8 @@ FreeBSD-10.0-RELEASE-amd64-bootonly.iso &prompt.root; grub-bhyve -m device.map -r cd0 -M 1024M linuxguest - This will start grub. If the installation CD contains a + This will start grub. If the installation + CD contains a grub.cfg, a menu will be displayed. If not, the vmlinuz and initrd files must be located and loaded @@ -1502,13 +1504,13 @@ grub> bootsysutils/screen in order to detach and reattach to the console. It is also possible to have the console of bhyve be a null modem - device that can be accessed with cu. To do this, load - the nmdm kernel module and replace - with + device that can be accessed with cu. To do + this, load the nmdm kernel module and + replace with . The /dev/nmdm 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 (/dev/nmdm1A and /dev/nmdm1B). See &man.nmdm.4; for more information. @@ -1522,7 +1524,6 @@ Connected Ubuntu 13.10 handbook ttyS0 handbook login: - @@ -1552,8 +1553,7 @@ crw------- 1 root wheel 0x1a1 Mar 17 In order to configure the system to start bhyve guests at boot time, add - the following entries to in the following - files: + the following entries to in the following files: