From owner-svn-doc-head@freebsd.org Wed Sep 2 22:25:42 2015 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 240399C9D3F; Wed, 2 Sep 2015 22:25:42 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org (repo.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 13476AD5; Wed, 2 Sep 2015 22:25:42 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.70]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id t82MPggK062537; Wed, 2 Sep 2015 22:25:42 GMT (envelope-from wblock@FreeBSD.org) Received: (from wblock@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id t82MPgsV062536; Wed, 2 Sep 2015 22:25:42 GMT (envelope-from wblock@FreeBSD.org) Message-Id: <201509022225.t82MPgsV062536@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: wblock set sender to wblock@FreeBSD.org using -f From: Warren Block Date: Wed, 2 Sep 2015 22:25:42 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r47347 - 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-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Sep 2015 22:25:42 -0000 Author: wblock Date: Wed Sep 2 22:25:41 2015 New Revision: 47347 URL: https://svnweb.freebsd.org/changeset/doc/47347 Log: Whitespace-only fixes, translators please ignore. 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 Wed Sep 2 22:01:42 2015 (r47346) +++ head/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml Wed Sep 2 22:25:41 2015 (r47347) @@ -96,678 +96,674 @@ - - &os; as a Guest on <application>Parallels</application> for &macos; X + + &os; as a Guest on <application>Parallels</application> for + &macos; X + + Parallels Desktop for &mac; is + a commercial software product available for &intel; based + &apple; &mac; computers running &macos; 10.4.6 or higher. &os; + is a fully supported guest operating system. Once + Parallels has been installed on + &macos; X, the user must configure a virtual machine and then + install the desired guest operating system. + + + Installing &os; on Parallels/&macos; X + + The first step in installing &os; on + Parallels is to create a new + virtual machine for installing &os;. Select + &os; as the + Guest OS Type when prompted: + + + + + + + + Choose a reasonable amount of disk and memory + depending on the plans for this virtual &os; instance. + 4GB of disk space and 512MB of RAM work well for most uses + of &os; under Parallels: + + + + + + + + + + + + + + + + + + + + + + + + + + Select the type of networking and a network + interface: + + + + + + + + + + + + + + Save and finish the configuration: + + + + + + + + + + + + + + After the &os; virtual machine has been created, &os; + can be installed on it. This is best done with an official + &os; CD/DVD or with an ISO image downloaded from an official + FTP site. Copy the appropriate ISO image to the local &mac; + filesystem or insert a CD/DVD in the &mac;'s CD drive. Click + on the disc icon in the bottom right corner of the &os; + Parallels window. This will bring + up a window that can be used to associate the CDROM drive in + the virtual machine with the ISO file on disk or with the real + CDROM drive. + + + + + + + + Once this association with the CDROM source has been + made, reboot the &os; virtual machine by clicking the reboot + icon. Parallels will reboot with a + special BIOS that first checks if there is a CDROM. + + + + + + + + In this case it will find the &os; installation media and + begin a normal &os; installation. Perform the installation, + but do not attempt to configure + &xorg; at this time. + + + + + + + + When the installation is finished, reboot into the newly + installed &os; virtual machine. + + + + + + + + + + Configuring &os; on + <application>Parallels</application> + + After &os; has been successfully installed on &macos; X + with Parallels, there are a number + of configuration steps that can be taken to optimize the + system for virtualized operation. + + + + Set Boot Loader Variables + + The most important step is to reduce the + tunable to reduce the CPU + utilization of &os; under the Parallels + environment. This is accomplished by + adding the following line to + /boot/loader.conf: + + kern.hz=100 + + Without this setting, an idle &os; + Parallels guest will use + roughly 15% of the CPU of a single processor &imac;. + After this change the usage will be closer to 5%. + + + + Create a New Kernel Configuration File + + All of the SCSI, FireWire, and USB device drivers + can be removed from a custom kernel configuration file. + Parallels provides a virtual + network adapter used by the &man.ed.4; driver, so all + network devices except for &man.ed.4; and &man.miibus.4; + can be removed from the kernel. + + + + Configure Networking + + The most basic networking setup uses DHCP to connect + the virtual machine to the same local area network as the + host &mac;. This can be accomplished by adding + ifconfig_ed0="DHCP" to + /etc/rc.conf. More advanced + networking setups are described in + . + + + + + + + &os; as a Guest on <application>Virtual PC</application> + for &windows; + + Virtual PC for &windows; is a + µsoft; software product available for free download. See + this website for the system + requirements. Once + Virtual PC has been installed on + µsoft.windows;, the user can configure a virtual machine + and then install the desired guest operating system. + + + Installing &os; on <application>Virtual + PC</application> + + The first step in installing &os; on + Virtual PC is to create a new + virtual machine for installing &os;. Select + Create a virtual machine when + prompted: + + + + + + + + + + + + + + Select Other as the + Operating system when + prompted: + + + + + + + + Then, choose a reasonable amount of disk and memory + depending on the plans for this virtual &os; instance. + 4GB of disk space and 512MB of RAM work well for most uses + of &os; under Virtual PC: + + + + + + + + + + + + + + Save and finish the configuration: + + + + + + + + Select the &os; virtual machine and click + Settings, then set the type of networking + and a network interface: + + + + + + + + + + + + + + After the &os; virtual machine has been created, &os; can + be installed on it. This is best done with an official &os; + CD/DVD or with an ISO image downloaded from an official FTP + site. Copy the appropriate ISO image to the local &windows; + filesystem or insert a CD/DVD in the CD drive, then double + click on the &os; virtual machine to boot. Then, click + CD and choose + Capture ISO Image... on the + Virtual PC window. This will bring + up a window where the CDROM drive in the virtual machine can + be associated with an ISO file on disk or with the real CDROM + drive. + + + + + + + + + + + + + + Once this association with the CDROM source has been made, + reboot the &os; virtual machine by clicking + Action and Reset. + Virtual PC will reboot with a + special BIOS that first checks for a CDROM. + + + + + + + + In this case it will find the &os; installation media + and begin a normal &os; installation. Continue with the + installation, but do not attempt to configure + &xorg; at this time. + + + + + + + + When the installation is finished, remember to eject the + CD/DVD or release the ISO image. Finally, reboot into + the newly installed &os; virtual machine. + + + + + + + + + + Configuring &os; on <application>Virtual + PC</application> + + After &os; has been successfully installed on + µsoft.windows; with Virtual PC + , there are a number of configuration + steps that can be taken to optimize the system for + virtualized operation. + + + + Set Boot Loader Variables + + The most important step is to reduce the + tunable to reduce the CPU + utilization of &os; under the + Virtual PC environment. This + is accomplished by adding the following line to + /boot/loader.conf: + + kern.hz=100 + + Without this setting, an idle &os; + Virtual PC guest OS will + use roughly 40% of the CPU of a single processor + computer. After this change, the usage will be + closer to 3%. + + + + Create a New Kernel Configuration File + + All of the SCSI, FireWire, and USB device drivers can + be removed from a custom kernel configuration file. + Virtual PC provides a virtual + network adapter used by the &man.de.4; driver, so all + network devices except for &man.de.4; and &man.miibus.4; + can be removed from the kernel. + + + + Configure Networking - Parallels Desktop for &mac; is - a commercial software product available for &intel; based - &apple; &mac; computers running &macos; 10.4.6 or higher. - &os; is a fully supported guest operating system. Once - Parallels has been installed on - &macos; X, the user must configure a virtual machine and then - install the desired guest operating system. - - - Installing &os; on Parallels/&macos; X - - The first step in installing &os; on - Parallels is to create a new - virtual machine for installing &os;. Select - &os; as the Guest OS - Type when prompted: - - - - - - - - Choose a reasonable amount of disk and memory - depending on the plans for this virtual &os; instance. - 4GB of disk space and 512MB of RAM work well for most uses - of &os; under Parallels: - - - - - - - - - - - - - - - - - - - - - - - - - - Select the type of networking and a network - interface: - - - - - - - - - - - - - - Save and finish the configuration: - - - - - - - - - - - - - - After the &os; virtual machine has been created, &os; - can be installed on it. This is best done with an - official &os; CD/DVD or with an ISO image downloaded from an - official FTP site. Copy the appropriate ISO image to the - local &mac; filesystem or insert a CD/DVD in the &mac;'s CD - drive. Click on the disc icon in the bottom right corner of - the &os; Parallels window. This - will bring up a window that can be used to associate the - CDROM drive in the virtual machine with the ISO file on disk - or with the real CDROM drive. - - - - - - - - Once this association with the CDROM source has been - made, reboot the &os; virtual machine by clicking the reboot - icon. Parallels will reboot with - a special BIOS that first checks if there is a CDROM. - - - - - - - - In this case it will find the &os; installation media - and begin a normal &os; installation. Perform the - installation, but do not attempt to configure - &xorg; at this time. - - - - - - - - When the installation is finished, reboot into the - newly installed &os; virtual machine. - - - - - - - - - - Configuring &os; on - <application>Parallels</application> - - After &os; has been successfully installed on &macos; - X with Parallels, there are a - number of configuration steps that can be taken to - optimize the system for virtualized operation. - - - - Set Boot Loader Variables - - The most important step is to reduce the - tunable to reduce the CPU - utilization of &os; under the Parallels - environment. This is accomplished by - adding the following line to - /boot/loader.conf: - - kern.hz=100 - - Without this setting, an idle &os; - Parallels guest will use - roughly 15% of the CPU of a single processor &imac;. - After this change the usage will be closer to 5%. - - - - Create a New Kernel Configuration File - - All of the SCSI, FireWire, and USB device drivers - can be removed from a custom kernel configuration file. - Parallels provides a virtual - network adapter used by the &man.ed.4; driver, so all - network devices except for &man.ed.4; and &man.miibus.4; - can be removed from the kernel. - - - - Configure Networking - - The most basic networking setup uses DHCP to connect - the virtual machine to the same local area network as - the host &mac;. This can be accomplished by adding - ifconfig_ed0="DHCP" to - /etc/rc.conf. More advanced - networking setups are described in - . - - - - - - - &os; as a Guest on <application>Virtual PC</application> for - &windows; - - Virtual PC for &windows; is a - µsoft; software product available for free download. See - this website for the system - requirements. Once Virtual - PC has been installed on µsoft.windows;, - the user can configure a virtual machine and then install the - desired guest operating system. - - - Installing &os; on <application>Virtual - PC</application> - - The first step in installing &os; on - Virtual PC is to create a new - virtual machine for installing &os;. Select - Create a virtual machine when - prompted: - - - - - - - - - - - - - - Select Other as the - Operating system when - prompted: - - - - - - - - Then, choose a reasonable amount of disk and memory - depending on the plans for this virtual &os; instance. - 4GB of disk space and 512MB of RAM work well for most uses - of &os; under Virtual PC: - - - - - - - - - - - - - - Save and finish the configuration: - - - - - - - - Select the &os; virtual machine and click - Settings, then set the type of networking - and a network interface: - - - - - - - - - - - - - - After the &os; virtual machine has been created, &os; - can be installed on it. This is best done with an - official &os; CD/DVD or with an ISO image downloaded from an - official FTP site. Copy the appropriate ISO image to the - local &windows; filesystem or insert a CD/DVD in the CD - drive, then double click on the &os; virtual machine to - boot. Then, click CD and choose - Capture ISO Image... on the - Virtual PC window. This will - bring up a window where the CDROM drive in the virtual - machine can be associated with an ISO file on disk or - with the real CDROM drive. - - - - - - - - - - - - - - Once this association with the CDROM source has been - made, reboot the &os; virtual machine by clicking - Action and Reset. - Virtual PC will reboot with a - special BIOS that first checks for a CDROM. - - - - - - - - In this case it will find the &os; installation media - and begin a normal &os; installation. Continue with the - installation, but do not attempt to configure - &xorg; at this time. - - - - - - - - When the installation is finished, remember to eject - the CD/DVD or release the ISO image. Finally, reboot into - the newly installed &os; virtual machine. - - - - - - - - - - Configuring &os; on <application>Virtual - PC</application> - - After &os; has been successfully installed on - µsoft.windows; with Virtual PC - , there are a number of configuration - steps that can be taken to optimize the system for - virtualized operation. - - - - Set Boot Loader Variables - - The most important step is to reduce the - tunable to reduce the CPU - utilization of &os; under the Virtual - PC environment. This is accomplished - by adding the following line to - /boot/loader.conf: - - kern.hz=100 - - Without this setting, an idle &os; - Virtual PC guest OS will - use roughly 40% of the CPU of a single processor - computer. After this change, the usage will be - closer to 3%. - - - - Create a New Kernel Configuration File - - All of the SCSI, FireWire, and USB device drivers - can be removed from a custom kernel configuration file. - Virtual PC provides a virtual - network adapter used by the &man.de.4; driver, so all - network devices except for &man.de.4; and &man.miibus.4; - can be removed from the kernel. - - - - Configure Networking - - The most basic networking setup uses DHCP to connect - the virtual machine to the same local area network as - the µsoft.windows; host. This can be accomplished - by adding ifconfig_de0="DHCP" to - /etc/rc.conf. More advanced - networking setups are described in - . - - - - - - - &os; as a Guest on <application>VMware Fusion</application> for - &macos; - - VMware Fusion for &mac; is a - commercial software product available for &intel; based - &apple; &mac; computers running &macos; 10.4.9 or higher. - &os; is a fully supported guest operating system. Once - VMware Fusion has been - installed on &macos; X, the user can configure a virtual - machine and then install the desired guest operating - system. - - - Installing &os; on <application>VMware - Fusion</application> - - The first step is to start VMware - Fusion which will load the Virtual - Machine Library. Click New to - create the virtual machine: - - - - - - - - This will load the New Virtual Machine Assistant. Click - Continue to proceed: - - - - - - - - Select Other as the - Operating System and either - &os; or - &os; 64-bit, as the - Version when prompted: - - - - - - - - Choose the name of the virtual machine and the directory - where it should be saved: - - - - - - - - Choose the size of the Virtual Hard Disk for the virtual - machine: - - - - - - - - Choose the method to install the virtual machine, - either from an ISO image or from a CD/DVD: - - - - - - - - Click Finish and the virtual - machine will boot: - - - - - - - - Install &os; as usual: - - - - - - - - Once the install is complete, the settings - of the virtual machine can be modified, such as memory - usage: - - - The System Hardware settings of the virtual machine - cannot be modified while the virtual machine is - running. - - - - - - - - - The number of CPUs the virtual machine will have access - to: - - - - - - - - The status of the CDROM device. Normally the - CD/DVD/ISO is disconnected from the virtual machine when it - is no longer needed. - - - - - - - - The last thing to change is how the virtual machine will - connect to the network. To allow connections to the virtual - machine from other machines besides the host, choose - Connect directly to the physical network - (Bridged). Otherwise, Share the - host's internet connection (NAT) is - preferred so that the virtual machine can have access to the - Internet, but the network cannot access the virtual - machine. - - - - - - - - After modifying the settings, boot the newly installed - &os; virtual machine. - - - - Configuring &os; on <application>VMware - Fusion</application> - - After &os; has been successfully installed on &macos; X - with VMware Fusion, there are a - number of configuration steps that can be taken to optimize - the system for virtualized operation. - - - - Set Boot Loader Variables - - The most important step is to reduce the - tunable to reduce the CPU - utilization of &os; under the - VMware Fusion environment. - This is accomplished by adding the following line to - /boot/loader.conf: - - kern.hz=100 - - Without this setting, an idle &os; - VMware Fusion guest will use - roughly 15% of the CPU of a single processor &imac;. - After this change, the usage will be closer to - 5%. - - - - Create a New Kernel Configuration File - - All of the FireWire, and USB device drivers can be - removed from a custom kernel configuration file. - VMware Fusion provides a - virtual network adapter used by the &man.em.4; driver, - so all network devices except for &man.em.4; can be - removed from the kernel. - - - - Configure Networking - - The most basic networking setup uses DHCP to connect - the virtual machine to the same local area network as - the host &mac;. This can be accomplished by adding - ifconfig_em0="DHCP" to - /etc/rc.conf. More advanced - networking setups are described in - . - - - - - - - &virtualbox; Guest Additions on a &os; Guest - - &os; works well as a guest in - &virtualbox;. The virtualization - software is available for most common operating systems, - including &os; itself. - - The &virtualbox; guest - additions provide support for: - - - - Clipboard sharing. - - - - Mouse pointer integration. - - - - Host time synchronization. - - - - Window scaling. - *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***