Index: en_US.ISO8859-1/books/handbook/virtualization/chapter.xml =================================================================== --- en_US.ISO8859-1/books/handbook/virtualization/chapter.xml +++ en_US.ISO8859-1/books/handbook/virtualization/chapter.xml @@ -605,533 +605,561 @@ --> - - <application>Virtual PC</application> on - &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> + + <application>Virtual PC</application> on + &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 + . + + + + + + + <application>VMware Fusion</application> on + &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 - 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 - . - - - - - - - <application>VMware Fusion</application> on - &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. - + The &virtualbox; guest + additions provide support for: - - 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 - - The &virtualbox; guest - additions provide support for: - - - - Clipboard sharing. - - - - Mouse pointer integration. - - - - Host time synchronization. - - - - Window scaling. - - - - Seamless mode. - - - - - The following commands are run in the &os; guest. - - - First, install the - emulators/virtualbox-ose-additions package - or port in the &os; guest. This will install the port: - - &prompt.root; cd /usr/ports/emulators/virtualbox-ose-additions && make install clean - - Add these lines to - /etc/rc.conf: - - vboxguest_enable="YES" -vboxservice_enable="YES" + + + Clipboard sharing. + - When Xorg will be used in the - guest, any required supporting services must also be enabled - just as if the guest was a physical machine. Typically, these - lines would also be added to - /etc/rc.conf: + + Mouse pointer integration. + -hald_enable="YES" -dbus_enable="YES" + + Host time synchronization. + - See for details. + + Window scaling. + - If &man.ntpd.8; or &man.ntpdate.8; is used, disable host - time synchronization: + + Seamless mode. + + - vboxservice_flags="--disable-timesync" - - Xorg will automatically - recognize the vboxvideo driver. - It can also be manually entered in - /etc/X11/xorg.conf: - - Section "Device" - ### Available Driver options are:- - ### Values: <i>: integer, <f>: float, <bool>: "True"/"False", - ### <string>: "String", <freq>: "<f> Hz/kHz/MHz" - ### [arg]: arg optional - Identifier "Card0" - Driver "vboxvideo" - VendorName "InnoTek Systemberatung GmbH" - BoardName "VirtualBox Graphics Adapter" - BusID "PCI:0:2:0" -EndSection - - To use the vboxmouse driver, adjust the - mouse section in - /etc/X11/xorg.conf: - - Section "InputDevice" - Identifier "Mouse0" - Driver "vboxmouse" -EndSection - - HAL users should create the following - /usr/local/etc/hal/fdi/policy/90-vboxguest.fdi - or copy it from - /usr/local/share/hal/fdi/policy/10osvendor/90-vboxguest.fdi: + + The following commands are run in the &os; + guest. + + + First, install the + emulators/virtualbox-ose-additions + package or port in the &os; guest. This will install the + port: + + &prompt.root; cd /usr/ports/emulators/virtualbox-ose-additions && make install clean + + Add these lines to + /etc/rc.conf: + + vboxguest_enable="YES" + vboxservice_enable="YES" + + When Xorg will be used in + the guest, any required supporting services must also be + enabled just as if the guest was a physical machine. + Typically, these lines would also be added to + /etc/rc.conf: + + hald_enable="YES" + dbus_enable="YES" + + See for details. + + If &man.ntpd.8; or &man.ntpdate.8; is used, disable + host time synchronization: + + vboxservice_flags="--disable-timesync" + + Xorg will automatically + recognize the vboxvideo driver. + It can also be manually entered in + /etc/X11/xorg.conf: + + Section "Device" + ### Available Driver options are:- + ### Values: <i>: integer, <f>: float, <bool>: "True"/"False", + ### <string>: "String", <freq>: "<f> Hz/kHz/MHz" + ### [arg]: arg optional + Identifier "Card0" + Driver "vboxvideo" + VendorName "InnoTek Systemberatung GmbH" + BoardName "VirtualBox Graphics Adapter" + BusID "PCI:0:2:0" + EndSection + + To use the vboxmouse driver, adjust + the mouse section in + /etc/X11/xorg.conf: + + Section "InputDevice" + Identifier "Mouse0" + Driver "vboxmouse" + EndSection + + HAL users should create the + following + /usr/local/etc/hal/fdi/policy/90-vboxguest.fdi + or copy it from + /usr/local/share/hal/fdi/policy/10osvendor/90-vboxguest.fdi: - <?xml version="1.0" encoding="utf-8"?> -<!-- + <?xml version="1.0" encoding="utf-8"?> + <!-- # Sun VirtualBox # Hal driver description for the vboxmouse driver # $Id: chapter.xml,v 1.33 2012-03-17 04:53:52 eadler Exp $ - Copyright (C) 2008-2009 Sun Microsystems, Inc. + Copyright (C) 2008-2009 Sun Microsystems, Inc. - This file is part of VirtualBox Open Source Edition (OSE, as - available from http://www.virtualbox.org. This file is free software; - you can redistribute it and/or modify it under the terms of the GNU - General Public License (GPL) as published by the Free Software - Foundation, in version 2 as it comes in the "COPYING" file of the - VirtualBox OSE distribution. VirtualBox OSE is distributed in the - hope that it will be useful, but WITHOUT ANY WARRANTY of any kind. - - Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa - Clara, CA 95054 USA or visit http://www.sun.com if you need - additional information or have any questions. ---> -<deviceinfo version="0.2"> - <device> - <match key="info.subsystem" string="pci"> - <match key="info.product" string="VirtualBox guest Service"> - <append key="info.capabilities" type="strlist">input</append> - <append key="info.capabilities" type="strlist">input.mouse</append> - <merge key="input.x11_driver" type="string">vboxmouse</merge> - <merge key="input.device" type="string">/dev/vboxguest</merge> - </match> - </match> - </device> -</deviceinfo> + This file is part of VirtualBox Open Source Edition (OSE, as + available from http://www.virtualbox.org. This file is free software; + you can redistribute it and/or modify it under the terms of the GNU + General Public License (GPL) as published by the Free Software + Foundation, in version 2 as it comes in the "COPYING" file of the + VirtualBox OSE distribution. VirtualBox OSE is distributed in the + hope that it will be useful, but WITHOUT ANY WARRANTY of any kind. + + Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa + Clara, CA 95054 USA or visit http://www.sun.com if you need + additional information or have any questions. + --> + <deviceinfo version="0.2"> + <device> + <match key="info.subsystem" string="pci"> + <match key="info.product" string="VirtualBox guest Service"> + <append key="info.capabilities" type="strlist">input</append> + <append key="info.capabilities" type="strlist">input.mouse</append> + <merge key="input.x11_driver" type="string">vboxmouse</merge> + <merge key="input.device" type="string">/dev/vboxguest</merge> + </match> + </match> + </device> + </deviceinfo> @@ -1320,18 +1348,23 @@ requires a computer with a newer processor that supports &intel; Extended Page Tables (EPT) or &amd; Rapid Virtualization Indexing (RVI), also known 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 NPT). In addition, to + host &linux; guests, or &os; guests with more than one vCPU, + VMX unrestricted mode support (UG) is also + required. Most newer processors, specifically the &intel;  + &core; i3/i5/i7 and &intel; &xeon; E3/E5/E7 support these + features. UG support was introduced with the + Westmere micro-architecture. 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 third generation and + later of the &amd.opteron; (Barcelona) processors. The easiest + way to check for support of EPT, + RVI, or UG is to look for + the POPCNT processor feature flag on the + Features2 line and EPT and + UG on the VT-x line in + dmesg or /var/run/dmesg.boot. @@ -1506,6 +1539,24 @@ &prompt.root; bhyvectl --destroy --vm=linuxguest + + + Using ZFS with Bhyve Guests + + If the host machine is running on ZFS, using ZFS volumes + instead of disk image files may provide significant + performance benefits for the bhyve guest VMs. A ZFS volume + can be created by: + + &prompt.root; zfs create -V16G -o volmode=dev zroot/vdisk0 + + Once created, the ZFS volume can be specified as the disk + drive when invoking bhyve to start the guest vm: + + &prompt.root; bhyve -AI -H -P -s 0:0,hostbridge -s 1:0,lpc -s 2:0,virtio-net,tap1 -s3:0,ahci-hd,/dev/zroot/vdisk0 \ + -l com1,stdio -c 4 -m 1024M linuxguest + + Virtual Machine Consoles @@ -1525,6 +1576,9 @@ (/dev/nmdm1A and /dev/nmdm1B). See &man.nmdm.4; for more information. + The example below shows how to boot the &linux; guest + created above with the console redirected to the null modem. + &os; guests can be configured similarly. &prompt.root; kldload nmdm &prompt.root; 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 \