- Timestamp:
- Jul 12, 2024 1:03:17 PM (10 months ago)
- svn:sync-xref-src-repo-rev:
- 163956
- Location:
- trunk/doc/manual/en_US/dita/topics
- Files:
-
- 32 edited
-
KnownProblems.dita (modified) (3 diffs)
-
arm-host-limitations.dita (modified) (1 diff)
-
auth-config-using.dita (modified) (3 diffs)
-
clone.dita (modified) (1 diff)
-
cloud-create-cloud-profile.dita (modified) (1 diff)
-
cloud-export-oci.dita (modified) (1 diff)
-
cloud-import-oci.dita (modified) (1 diff)
-
cloud-using-cloud-networks.dita (modified) (1 diff)
-
cloud-using-cloud-profile-manager.dita (modified) (1 diff)
-
cloud-vm-add.dita (modified) (1 diff)
-
collect-debug-info.dita (modified) (3 diffs)
-
glossentry-com.dita (modified) (1 diff)
-
glossentry-vrde.dita (modified) (1 diff)
-
guestadd-guestprops.dita (modified) (2 diffs)
-
gui-machine-list.dita (modified) (1 diff)
-
harddiskcontrollers.dita (modified) (3 diffs)
-
hostossupport.dita (modified) (1 diff)
-
install-mac-performing.dita (modified) (1 diff)
-
install-win-performing.dita (modified) (1 diff)
-
intro-running.dita (modified) (1 diff)
-
mountingadditionsiso.dita (modified) (1 diff)
-
nested-virt.dita (modified) (2 diffs)
-
nestedpaging.dita (modified) (3 diffs)
-
ovf-export-appliance.dita (modified) (1 diff)
-
serialports.dita (modified) (1 diff)
-
settings-motherboard.dita (modified) (2 diffs)
-
snapshots-contents.dita (modified) (1 diff)
-
vbox-auth.dita (modified) (2 diffs)
-
vboxconfigdata-machine-folder.dita (modified) (2 diffs)
-
vboxheadless-examples.dita (modified) (2 diffs)
-
vboxheadless-see-also.dita (modified) (1 diff)
-
virt-why-useful.dita (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/dita/topics/KnownProblems.dita
r105176 r105303 3 3 <topic xml:lang="en-us" id="KnownProblems"> 4 4 <title>Known Issues</title> 5 5 6 6 <body> 7 7 <p> … … 183 183 <li> 184 184 <p> 185 <b outputclass="bold">macOS/Arm64 (Apple silicon) host 186 package</b> 185 <b outputclass="bold">macOS/Arm64 (Apple silicon) host package</b> 187 186 </p> 188 187 </li> … … 331 330 </ul> 332 331 </body> 333 332 334 333 </topic> -
trunk/doc/manual/en_US/dita/topics/arm-host-limitations.dita
r105166 r105303 5 5 <!-- 7.1: Arm platform limitations --> 6 6 <body> 7 <p> 7 <p>The following limitations apply when using an Arm platform host:</p> 8 8 <ul><li><p>Virtual machines must use an Arm-based guest operating system. Running an x86-based guest operating 9 9 system on an Arm host platform is not supported. </p></li> -
trunk/doc/manual/en_US/dita/topics/auth-config-using.dita
r99797 r105303 3 3 <topic xml:lang="en-us" id="auth-config-using"> 4 4 <title>Configuring and Using Authentication</title> 5 5 6 6 <body> 7 7 <p> … … 11 11 <ul> 12 12 <li> 13 <p> 14 When using remote iSCSI storage and the storage server requires authentication, an 13 <p> When using remote iSCSI storage and the storage server requires authentication, an 15 14 initiator secret can optionally be supplied with the <userinput>VBoxManage 16 storageattach</userinput> command. As long as no settings password is provided, by using15 storageattach</userinput> command. As long as no settings password is provided, by using 17 16 the command line option <codeph>--settingspwfile</codeph>, then this secret is stored 18 <i>unencrypted</i> in the machine configuration and is therefore potentially readable on17 <i>unencrypted</i> in the machine configuration and is therefore potentially readable on 19 18 the host. See <xref href="storage-iscsi.dita">iSCSI Servers</xref> and <xref 20 href="vboxmanage-storageattach.dita">VBoxManage storageattach</xref>. 21 </p> 19 href="vboxmanage-storageattach.dita">VBoxManage storageattach</xref>. </p> 22 20 </li> 23 21 <li> … … 32 30 </ul> 33 31 </body> 34 32 35 33 </topic> -
trunk/doc/manual/en_US/dita/topics/clone.dita
r105289 r105303 135 135 </li> 136 136 </ul> 137 <p> 138 Click <b outputclass="bold">Finish</b> to start the clone 139 operation. 140 </p> 141 <p> 142 The duration of the clone operation depends on the size and number 143 of attached disk images. In addition, the clone operation saves 144 all the differencing disk images of a snapshot. 145 </p> 146 <p> 147 You can also use the <userinput>VBoxManage clonevm</userinput> command to clone a VM. See 148 <xref href="vboxmanage-clonevm.dita"/>. 149 </p> 137 <p>Click <b outputclass="bold">Finish</b> to start the clone operation. </p> 138 <p>The duration of the clone operation depends on the size and number of attached disk images. In addition, the 139 clone operation saves all the differencing disk images of a snapshot. </p> 140 <p>You can also use the <userinput>VBoxManage clonevm</userinput> command to clone a VM. See <xref 141 href="vboxmanage-clonevm.dita"/>. </p> 150 142 </body> 151 143 152 144 </topic> -
trunk/doc/manual/en_US/dita/topics/cloud-create-cloud-profile.dita
r105289 r105303 71 71 <ul> 72 72 <li> 73 <p> 74 Automatically, by using the <b outputclass="bold">Cloud 75 Profile Manager</b>. See 76 <xref href="cloud-using-cloud-profile-manager.dita#cloud-using-cloud-profile-manager"/>. 77 </p> 78 <p> 79 The Cloud Profile Manager is a <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> tool that enables 80 you to create, edit, and manage cloud profiles for your 81 cloud service accounts. 82 </p> 73 <p>Automatically, by using the <b outputclass="bold">Cloud Profile Manager</b>. See <xref 74 href="cloud-using-cloud-profile-manager.dita#cloud-using-cloud-profile-manager"/>. </p> 75 <p>The Cloud Profile Manager is a <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> tool that enables you to 76 create, edit, and manage cloud profiles for your cloud service accounts. </p> 83 77 </li> 84 78 <li> 85 <p> 86 Automatically, by using the <userinput>VBoxManage cloudprofile</userinput> command. See 87 <xref href="vboxmanage-cloudprofile.dita"/>. 88 </p> 79 <p>Automatically, by using the <userinput>VBoxManage cloudprofile</userinput> command. See <xref 80 href="vboxmanage-cloudprofile.dita"/>. </p> 89 81 </li> 90 82 <li> 91 <p> 92 Manually, by creating an <filepath>oci_config</filepath> 93 file in your <ph conkeyref="vbox-conkeyref-phrases/product-name"/> global configuration directory. 94 For example, this is 95 <filepath>$HOME/.config/VirtualBox/oci_config</filepath> on 96 a Linux host. 97 </p> 83 <p>Manually, by creating an <filepath>oci_config</filepath> file in your <ph 84 conkeyref="vbox-conkeyref-phrases/product-name"/> global configuration directory. For example, this is 85 <filepath>$HOME/.config/VirtualBox/oci_config</filepath> on a Linux host. </p> 98 86 </li> 99 87 <li> 100 <p> 101 Manually, by creating a <filepath>config</filepath> file in 102 your <ph conkeyref="vbox-conkeyref-phrases/oci"/> configuration directory. For example, this is 103 <filepath>$HOME/.oci/config</filepath> on a Linux host. 104 </p> 105 <p> 106 This is the same file that is used by the <ph conkeyref="vbox-conkeyref-phrases/oci"/> command line 107 interface. 108 </p> 109 <p> 110 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> automatically uses the 111 <filepath>config</filepath> file if no cloud profile file is 112 present in your global configuration directory. 113 Alternatively, you can import this file manually into the 114 Cloud Profile Manager. 115 </p> 88 <p>Manually, by creating a <filepath>config</filepath> file in your <ph conkeyref="vbox-conkeyref-phrases/oci"/> 89 configuration directory. For example, this is <filepath>$HOME/.oci/config</filepath> on a Linux host. </p> 90 <p>This is the same file that is used by the <ph conkeyref="vbox-conkeyref-phrases/oci"/> command line 91 interface. </p> 92 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> automatically uses the <filepath>config</filepath> file 93 if no cloud profile file is present in your global configuration directory. Alternatively, you can import this 94 file manually into the Cloud Profile Manager. </p> 116 95 </li> 117 96 </ul> 118 97 </body> 119 98 120 99 </topic> -
trunk/doc/manual/en_US/dita/topics/cloud-export-oci.dita
r105289 r105303 78 78 </li> 79 79 </ul> 80 <p> 81 Click <b outputclass="bold">Finish</b> to continue. 82 </p> 80 <p>Click <b outputclass="bold">Finish</b> to continue. </p> 83 81 </li> 84 82 <li> 85 <p> 86 (Optional) Depending on the selection in the 87 <b outputclass="bold">Machine Creation</b> field, the 88 <b outputclass="bold">Appliance Settings</b> page may 89 be displayed before or after export. This screen enables you 90 to configure settings for the cloud instance, such as Shape 91 and Disk Size. 92 </p> 93 <p> 94 Click <b outputclass="bold">Finish</b>. The VM is 95 exported to <ph conkeyref="vbox-conkeyref-phrases/oci"/>. 96 </p> 97 <p> 98 Depending on the <b outputclass="bold">Machine 99 Creation</b> setting, a cloud instance may be started 100 after upload to <ph conkeyref="vbox-conkeyref-phrases/oci"/> is completed. 101 </p> 83 <p>(Optional) Depending on the selection in the <b outputclass="bold">Machine Creation</b> field, the <b 84 outputclass="bold">Appliance Settings</b> page may be displayed before or after export. This screen enables 85 you to configure settings for the cloud instance, such as Shape and Disk Size. </p> 86 <p>Click <b outputclass="bold">Finish</b>. The VM is exported to <ph conkeyref="vbox-conkeyref-phrases/oci"/>. </p> 87 <p>Depending on the <b outputclass="bold">Machine Creation</b> setting, a cloud instance may be started after 88 upload to <ph conkeyref="vbox-conkeyref-phrases/oci"/> is completed. </p> 102 89 </li> 103 90 <li> 104 <p> 105 Monitor the export process by using the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console. 106 </p> 91 <p>Monitor the export process by using the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console. </p> 107 92 </li> 108 93 </ol> 109 <p> 110 You can also use the <userinput>VBoxManage export</userinput> command to export a VM to 111 <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="vboxmanage-export.dita"/>. 112 </p> 94 <p>You can also use the <userinput>VBoxManage export</userinput> command to export a VM to <ph 95 conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="vboxmanage-export.dita"/>. </p> 113 96 </body> 114 97 </topic> -
trunk/doc/manual/en_US/dita/topics/cloud-import-oci.dita
r105289 r105303 33 33 </image> 34 34 </fig> 35 <p> 36 Click <b outputclass="bold">Finish</b> to import the 37 instance from <ph conkeyref="vbox-conkeyref-phrases/oci"/>. 38 </p> 35 <p>Click <b outputclass="bold">Finish</b> to import the instance from <ph conkeyref="vbox-conkeyref-phrases/oci" 36 />. </p> 39 37 </li> 40 38 <li> 41 <p> 42 Monitor the import process by using the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console. 43 </p> 39 <p>Monitor the import process by using the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console. </p> 44 40 </li> 45 41 </ol> 46 <p> 47 You can also use the <userinput>VBoxManage import</userinput> command to import an instance 48 from <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="vboxmanage-import.dita"/>. 49 </p> 42 <p>You can also use the <userinput>VBoxManage import</userinput> command to import an instance from <ph 43 conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="vboxmanage-import.dita"/>. </p> 50 44 </body> 51 45 </topic> -
trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-networks.dita
r105134 r105303 4 4 <title>Using a Cloud Network</title> 5 5 <body> 6 <p> 7 A cloud network is a type of network that can be used for 8 connections from a local VM to a remote <ph conkeyref="vbox-conkeyref-phrases/oci"/> cloud instance. 9 </p> 10 <p> 11 To create and use a cloud network, do the following: 12 </p> 6 <p>A cloud network is a type of network that can be used for connections from a local VM to a remote <ph 7 conkeyref="vbox-conkeyref-phrases/oci"/> cloud instance. </p> 8 <p>To create and use a cloud network, do the following: </p> 13 9 <ol> 14 10 <li> 15 <p> 16 Set up a virtual cloud network on <ph conkeyref="vbox-conkeyref-phrases/oci"/>. 17 </p> 18 <p> 19 The following steps create and configure a virtual cloud 20 network (VCN) on <ph conkeyref="vbox-conkeyref-phrases/oci"/>. The VCN is used to tunnel network 21 traffic across the cloud. 22 </p> 11 <p>Set up a virtual cloud network on <ph conkeyref="vbox-conkeyref-phrases/oci"/>. </p> 12 <p>The following steps create and configure a virtual cloud network (VCN) on <ph 13 conkeyref="vbox-conkeyref-phrases/oci"/>. The VCN is used to tunnel network traffic across the cloud. </p> 23 14 <ol> 24 15 <li> 25 <p> 26 Ensure that you have a cloud profile for connecting to 27 <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="cloud-create-cloud-profile.dita#cloud-create-cloud-profile"/>. 28 </p> 16 <p>Ensure that you have a cloud profile for connecting to <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See 17 <xref href="cloud-create-cloud-profile.dita#cloud-create-cloud-profile"/>. </p> 29 18 </li> 30 19 <li> 31 <p> 32 Run the following <userinput>VBoxManage cloud</userinput> 33 command: 34 </p> 20 <p>Run the following <userinput>VBoxManage cloud</userinput> command: </p> 35 21 <pre xml:space="preserve">VBoxManage cloud --provider="OCI" --profile="vbox-oci" network setup</pre> 36 <p> 37 where <codeph>vbox-oci</codeph> is the name of your 38 cloud profile. 39 </p> 40 <p> 41 Other options are available for the <userinput>VBoxManage cloud network 42 setup</userinput> command, to enable you to configure details for the VCN. For 43 example, you can configure the operating system used for the cloud gateway instance 44 and the IP address range used by the tunneling network. See <xref href="vboxmanage-cloud.dita"/>. 45 </p> 46 <p> 47 For best results, use an Oracle Linux 7 instance for the 48 cloud gateway. This is the default option. 49 </p> 22 <p>where <codeph>vbox-oci</codeph> is the name of your cloud profile. </p> 23 <p>Other options are available for the <userinput>VBoxManage cloud network setup</userinput> command, to 24 enable you to configure details for the VCN. For example, you can configure the operating system used for 25 the cloud gateway instance and the IP address range used by the tunneling network. See <xref 26 href="vboxmanage-cloud.dita"/>. </p> 27 <p>For best results, use an Oracle Linux 7 instance for the cloud gateway. This is the default option. </p> 50 28 </li> 51 29 </ol> 52 30 </li> 53 31 <li> 54 <p> 55 Register the new cloud network with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. 56 </p> 57 <p> 58 Use the <b outputclass="bold">Cloud Networks</b> tab 59 in the <b outputclass="bold">Network Manager</b> 60 tool. See 61 <xref href="network-manager-cloud-network-tab.dita#network-manager-cloud-network-tab"/>. 62 </p> 32 <p>Register the new cloud network with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p> 33 <p>Use the <b outputclass="bold">Cloud Networks</b> tab in the <b outputclass="bold">Network Manager</b> tool. 34 See <xref href="network-manager-cloud-network-tab.dita#network-manager-cloud-network-tab"/>. </p> 63 35 </li> 64 36 <li> 65 <p> 66 Add cloud network adaptors to the local VMs that will use 67 the cloud network. See <xref href="network_cloud.dita#network_cloud"/>. 68 </p> 37 <p>Add cloud network adaptors to the local VMs that will use the cloud network. See <xref 38 href="network_cloud.dita#network_cloud"/>. </p> 69 39 </li> 70 40 </ol> 71 41 </body> 72 42 73 43 </topic> -
trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-profile-manager.dita
r105289 r105303 125 125 <li> 126 126 <p>Click <b outputclass="bold">Properties</b> to show the cloud profile settings. </p> 127 <p> 127 <p>Double-click the appropriate field to change the value. </p> 128 128 </li> 129 129 <li> -
trunk/doc/manual/en_US/dita/topics/cloud-vm-add.dita
r105289 r105303 11 11 <ol> 12 12 <li> 13 <p> 13 <p>Click a cloud profile in the <b outputclass="bold">OCI</b> group. </p> 14 14 <p>The cloud VMs for the selected cloud profile are displayed. </p> 15 15 </li> -
trunk/doc/manual/en_US/dita/topics/collect-debug-info.dita
r99797 r105303 3 3 <topic xml:lang="en-us" id="collect-debug-info"> 4 4 <title>Collecting Debugging Information</title> 5 5 6 6 <body> 7 7 <p> … … 56 56 <p><ph>http://www.virtualbox.org/wiki/Core_dump</ph>. 57 57 </p> 58 <p> 59 You can also use <userinput>VBoxManage debugvm</userinput> to create a dump of a complete 60 virtual machine. See <xref href="vboxmanage-debugvm.dita">VBoxManage debugvm</xref>. 61 </p> 58 <p> You can also use <userinput>VBoxManage debugvm</userinput> to create a dump of a complete 59 virtual machine. See <xref href="vboxmanage-debugvm.dita">VBoxManage debugvm</xref>. </p> 62 60 <p> 63 61 For network related problems, it is often helpful to capture a … … 81 79 </p> 82 80 </body> 83 81 84 82 </topic> -
trunk/doc/manual/en_US/dita/topics/glossentry-com.dita
r105176 r105303 7 7 COM enables applications to provide application programming interfaces which can be 8 8 accessed from various other programming languages and applications. 9 9 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> makes use of COM both internally and externally to provide a 10 10 comprehensive API to third party developers. 11 11 </glossdef> 12 12 </glossentry> 13 -
trunk/doc/manual/en_US/dita/topics/glossentry-vrde.dita
r105176 r105303 5 5 <glossdef> 6 6 VirtualBox Remote Desktop Extension. This interface is built into 7 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to allow <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension packages8 7 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to allow <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 8 extension packages to supply remote access to virtual machines. An <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension 9 9 package by Oracle provides VRDP support. 10 10 See <xref href="vrde.dita">Remote Display (VRDP Support)</xref>. -
trunk/doc/manual/en_US/dita/topics/guestadd-guestprops.dita
r99797 r105303 3 3 <topic xml:lang="en-us" id="guestadd-guestprops"> 4 4 <title>Guest Properties</title> 5 5 6 6 <body> 7 7 <p> … … 51 51 virtual machine's <b outputclass="bold">Machine</b> menu. 52 52 </p> 53 <p> 54 A more flexible way to use this channel is with the <userinput>VBoxManage 55 guestproperty</userinput> command. See <xref href="vboxmanage-guestproperty.dita"/>. 56 For example, to have <i>all</i> the available guest properties for a given running VM 57 listed with their respective values, use this command: 58 </p> 53 <p> A more flexible way to use this channel is with the <userinput>VBoxManage 54 guestproperty</userinput> command. See <xref href="vboxmanage-guestproperty.dita"/>. 55 For example, to have <i>all</i> the available guest properties for a given running VM 56 listed with their respective values, use this command: </p> 59 57 <pre xml:space="preserve">$ VBoxManage guestproperty enumerate "Windows Vista III" 60 58 VirtualBox Command Line Management Interface Version <varname>version-number</varname> -
trunk/doc/manual/en_US/dita/topics/gui-machine-list.dita
r105289 r105303 9 9 <ul> 10 10 <li> 11 <p> 11 <p>Right-click the virtual machine name, to display menu options. </p> 12 12 </li> 13 13 <li> 14 <p> 14 <p>Click the Machine Tools menu icon, to the right of the virtual machine name. See <xref 15 15 href="gui-tools-machine.dita#gui-tools-machine"/>. </p> 16 16 </li> -
trunk/doc/manual/en_US/dita/topics/harddiskcontrollers.dita
r105176 r105303 3 3 <topic xml:lang="en-us" id="harddiskcontrollers"> 4 4 <title>Hard Disk Controllers</title> 5 5 6 6 <body> 7 7 <p> … … 109 109 virtual disks to it. 110 110 </p> 111 <p> 112 To change the IDE compatibility mode settings for the SATA controller, see <xref 113 href="vboxmanage-storagectl.dita"/>. 114 </p> 111 <p> To change the IDE compatibility mode settings for the SATA controller, see <xref 112 href="vboxmanage-storagectl.dita"/>. </p> 115 113 </li> 116 114 <li> … … 298 296 </p> 299 297 </body> 300 298 301 299 </topic> -
trunk/doc/manual/en_US/dita/topics/hostossupport.dita
r105289 r105303 84 84 </li> 85 85 </ul> 86 <p> 86 <p>It should be possible to use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on 87 87 most systems based on Linux kernel 2.6 or later, using either the <ph 88 88 conkeyref="vbox-conkeyref-phrases/product-name"/> installer or by doing a manual -
trunk/doc/manual/en_US/dita/topics/install-mac-performing.dita
r105289 r105303 9 9 <ol> 10 10 <li> 11 <p> 11 <p>Double-click the <filepath>dmg</filepath> file, to mount the contents. </p> 12 12 </li> 13 13 <li> -
trunk/doc/manual/en_US/dita/topics/install-win-performing.dita
r105289 r105303 48 48 <p>See, for example: <ph>http://www.python.org/download/windows/</ph>. </p> 49 49 <note> 50 <p> 50 <p>Python version 3 is required. Python version 2.x is no longer supported. </p> 51 51 </note> 52 52 </li> -
trunk/doc/manual/en_US/dita/topics/intro-running.dita
r105289 r105303 14 14 </li> 15 15 <li> 16 <p> 17 Select the VM's entry in the machine list in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, and 18 click <b outputclass="bold">Start</b> in the toolbar 19 the top of the window. 20 </p> 16 <p> Select the VM's name in the machine list in <ph 17 conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, and click <b outputclass="bold">Start</b> 18 in the toolbar the top of the window. </p> 21 19 </li> 22 20 <li> -
trunk/doc/manual/en_US/dita/topics/mountingadditionsiso.dita
r105176 r105303 71 71 </li> 72 72 <li> 73 <p> On macOS hosts, this file is in the application bundle of <ph73 <p> On macOS hosts, this file is in the application bundle of <ph 74 74 conkeyref="vbox-conkeyref-phrases/product-name"/>. Right-click the <ph 75 75 conkeyref="vbox-conkeyref-phrases/product-name"/> icon in Finder and choose <b 76 76 outputclass="bold">Show Package Contents</b>. The file is located in the 77 <filepath>Contents/MacOS</filepath> folder. </p>77 <filepath>Contents/MacOS</filepath> folder. </p> 78 78 </li> 79 79 <li> -
trunk/doc/manual/en_US/dita/topics/nested-virt.dita
r99797 r105303 3 3 <topic xml:lang="en-us" id="nested-virt"> 4 4 <title>Nested Virtualization</title> 5 5 6 6 <body> 7 7 <p> … … 32 32 </li> 33 33 <li> 34 <p> 35 Use the <codeph>--nested-hw-virt</codeph> option of the <userinput>VBoxManage 36 modifyvm</userinput> command to enable or disable nested virtualization. See 37 <xref href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>. 38 </p> 34 <p> Use the <codeph>--nested-hw-virt</codeph> option of the <userinput>VBoxManage 35 modifyvm</userinput> command to enable or disable nested virtualization. See <xref 36 href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>. </p> 39 37 </li> 40 38 </ul> 41 39 </body> 42 40 43 41 </topic> -
trunk/doc/manual/en_US/dita/topics/nestedpaging.dita
r99797 r105303 3 3 <topic xml:lang="en-us" id="nestedpaging"> 4 4 <title>Nested Paging and VPIDs</title> 5 5 6 6 <body> 7 7 <p> … … 41 41 Core i7 (Nehalem) processors. 42 42 </p> 43 <p> 44 If nested paging is enabled, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> hypervisor can also use <i>large 45 pages</i> to reduce TLB usage and overhead. This can yield a performance improvement of 46 up to 5%. To enable this feature for a VM, you use the <userinput>VBoxManage modifyvm --large-pages</userinput> 47 command. See <xref href="vboxmanage-modifyvm.dita">VBoxManage 48 modifyvm</xref>. 49 </p> 43 <p> If nested paging is enabled, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> hypervisor can also use <i>large 44 pages</i> to reduce TLB usage and overhead. This can yield a performance improvement of 45 up to 5%. To enable this feature for a VM, you use the <userinput>VBoxManage modifyvm 46 --large-pages</userinput> command. See <xref href="vboxmanage-modifyvm.dita">VBoxManage 47 modifyvm</xref>. </p> 50 48 <p> 51 49 If you have an Intel CPU with EPT, please consult … … 67 65 </ul> 68 66 </body> 69 67 70 68 </topic> -
trunk/doc/manual/en_US/dita/topics/ovf-export-appliance.dita
r105289 r105303 51 51 </li> 52 52 <li> 53 <p> 54 Click <b outputclass="bold">Next</b> to show the 55 <b outputclass="bold">Appliance Settings</b> page. 56 </p> 57 <p> 58 You can edit settings for the virtual appliance. For 59 example, you can change the name of the virtual appliance or 60 add product information, such as vendor details or license 61 text. 62 </p> 63 <p> 64 Double-click the appropriate field to change its value. 65 </p> 53 <p>Click <b outputclass="bold">Next</b> to show the <b outputclass="bold">Appliance Settings</b> page. </p> 54 <p>You can edit settings for the virtual appliance. For example, you can change the name of the virtual 55 appliance or add product information, such as vendor details or license text. </p> 56 <p>Double-click the appropriate field to change its value. </p> 66 57 </li> 67 58 <li> 68 <p> 69 Click <b outputclass="bold">Finish</b> to begin the 70 export process. Note that this operation might take several 71 minutes. 72 </p> 59 <p>Click <b outputclass="bold">Finish</b> to begin the export process. Note that this operation might take 60 several minutes. </p> 73 61 </li> 74 62 </ol> 75 <p> 76 You can use the <userinput>VBoxManage export</userinput> command to export an appliance. See 77 <xref href="vboxmanage-export.dita"/>. 78 </p> 63 <p>You can use the <userinput>VBoxManage export</userinput> command to export an appliance. See <xref 64 href="vboxmanage-export.dita"/>. </p> 79 65 </body> 80 66 81 67 </topic> -
trunk/doc/manual/en_US/dita/topics/serialports.dita
r105289 r105303 3 3 <topic xml:lang="en-us" id="serialports"> 4 4 <title>Serial Ports</title> 5 5 6 6 <body> 7 <p> 8 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports the use of virtual serial ports in a 9 virtual machine. 10 </p> 11 <p> 12 Ever since the original IBM PC, personal computers have been 13 equipped with one or two serial ports, also called COM ports by 14 DOS and Windows. Serial ports were commonly used with modems, and 15 some computer mice used to be connected to serial ports before USB 16 became commonplace. 17 </p> 18 <p> 19 While serial ports are no longer as common as they used to be, 20 there are still some important uses left for them. For example, 21 serial ports can be used to set up a primitive network over a 22 null-modem cable, in case Ethernet is not available. Also, serial 23 ports are indispensable for system programmers needing to do 24 kernel debugging, since kernel debugging software usually 25 interacts with developers over a serial port. With virtual serial 26 ports, system programmers can do kernel debugging on a virtual 27 machine instead of needing a real computer to connect to. 28 </p> 29 <p> 30 If a virtual serial port is enabled, the guest OS sees a standard 31 16550A compatible UART device. Other UART types can be configured 32 using the <userinput>VBoxManage modifyvm</userinput> command. Both 33 receiving and transmitting data is supported. How this virtual 34 serial port is then connected to the host is configurable, and the 35 details depend on your host OS. 36 </p> 37 <p> 38 You can use either the Settings tabs or the <userinput>VBoxManage</userinput> command to set 39 up virtual serial ports. For the latter, see <xref href="vboxmanage-modifyvm.dita"/> for 40 information on the <codeph>--uart</codeph>, <codeph>--uart-mode</codeph> and 41 <codeph>--uart-type</codeph> options. 42 </p> 43 <p> 44 You can configure up to four virtual serial ports per virtual 45 machine. For each device, you must set the following: 46 </p> 7 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports the use of virtual serial ports in a virtual 8 machine. </p> 9 <p>Ever since the original IBM PC, personal computers have been equipped with one or two serial ports, also called 10 COM ports by DOS and Windows. Serial ports were commonly used with modems, and some computer mice used to be 11 connected to serial ports before USB became commonplace. </p> 12 <p>While serial ports are no longer as common as they used to be, there are still some important uses left for them. 13 For example, serial ports can be used to set up a primitive network over a null-modem cable, in case Ethernet is 14 not available. Also, serial ports are indispensable for system programmers needing to do kernel debugging, since 15 kernel debugging software usually interacts with developers over a serial port. With virtual serial ports, system 16 programmers can do kernel debugging on a virtual machine instead of needing a real computer to connect to. </p> 17 <p>If a virtual serial port is enabled, the guest OS sees a standard 16550A compatible UART device. Other UART types 18 can be configured using the <userinput>VBoxManage modifyvm</userinput> command. Both receiving and transmitting 19 data is supported. How this virtual serial port is then connected to the host is configurable, and the details 20 depend on your host OS. </p> 21 <p>You can use either the Settings tabs or the <userinput>VBoxManage</userinput> command to set up virtual serial 22 ports. For the latter, see <xref href="vboxmanage-modifyvm.dita"/> for information on the <codeph>--uart</codeph>, 23 <codeph>--uart-mode</codeph> and <codeph>--uart-type</codeph> options. </p> 24 <p>You can configure up to four virtual serial ports per virtual machine. For each device, you must set the 25 following: </p> 47 26 <ol> 48 27 <li> -
trunk/doc/manual/en_US/dita/topics/settings-motherboard.dita
r105289 r105303 31 31 settings), the network, or none of these. 32 32 </p> 33 <p> 34 If you select <b outputclass="bold">Network</b>, the VM will attempt to boot from a 35 network using the PXE mechanism. This needs to be configured in detail on the command 36 line. See <xref href="vboxmanage-modifyvm.dita"/>. 37 </p> 33 <p>If you select <b outputclass="bold">Network</b>, the VM will attempt to boot from a network using the PXE 34 mechanism. This needs to be configured in detail on the command line. See <xref 35 href="vboxmanage-modifyvm.dita"/>. </p> 38 36 </li> 39 37 <li> … … 121 119 </li> 122 120 </ul> 123 <p> 124 In addition, you can turn off the <b outputclass="bold">Advanced 125 Configuration and Power Interface (ACPI)</b> which 126 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to the guest OS by default. 127 </p> 128 <p> 129 ACPI is the current industry standard to allow OSes to recognize hardware, configure 130 motherboards and other devices and manage power. As most computers contain this feature and 131 Windows and Linux support ACPI, it is also enabled by default in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. ACPI 132 can only be turned off using the command line. See <xref href="vboxmanage-modifyvm.dita"/>. 133 </p> 121 <p>In addition, you can turn off the <b outputclass="bold">Advanced Configuration and Power Interface (ACPI)</b> 122 which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to the guest OS by default. </p> 123 <p>ACPI is the current industry standard to allow OSes to recognize hardware, configure motherboards and other 124 devices and manage power. As most computers contain this feature and Windows and Linux support ACPI, it is also 125 enabled by default in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. ACPI can only be turned off using the 126 command line. See <xref href="vboxmanage-modifyvm.dita"/>. </p> 134 127 <note> 135 <p> 136 All Windows OSes install different kernels, depending on 137 whether ACPI is available. This means that ACPI <i>must 138 not be turned off</i> after installation of a Windows 139 guest OS. However, turning it on after installation will have 140 no effect. 141 </p> 128 <p>All Windows OSes install different kernels, depending on whether ACPI is available. This means that ACPI 129 <i>must not be turned off</i> after installation of a Windows guest OS. However, turning it on after 130 installation will have no effect. </p> 142 131 </note> 143 132 </body> 144 133 145 134 </topic> -
trunk/doc/manual/en_US/dita/topics/snapshots-contents.dita
r99797 r105303 6 6 7 7 <body> 8 <p> 9 Think of a snapshot as a point in time that you have preserved. 10 More formally, a snapshot consists of the following: 11 </p> 8 <p>Think of a snapshot as a point in time that you have preserved. More formally, a snapshot consists 9 of the following: </p> 12 10 <ul> 13 11 <li> 14 <p> 15 The snapshot contains a complete copy of the VM settings, 16 including the hardware configuration, so that when you 17 restore a snapshot, the VM settings are restored as well. 18 For example, if you changed the hard disk configuration or 19 the VM's system settings, that change is undone when you 20 restore the snapshot. 21 </p> 22 <p> 23 The copy of the settings is stored in the machine 24 configuration, an XML text file, and thus occupies very 25 little space. 26 </p> 12 <p>The snapshot contains a complete copy of the VM settings, including the hardware 13 configuration, so that when you restore a snapshot, the VM settings are restored as well. For example, if you 14 changed the hard disk configuration or the VM's system settings, that change is undone when you restore the 15 snapshot. </p> 16 <p>The copy of the settings is stored in the machine configuration, an XML text file, and thus 17 occupies very little space. </p> 27 18 </li> 28 19 <li> 29 <p> 30 The complete state of all the virtual disks attached to the 31 machine is preserved. Going back to a snapshot means that 32 all changes that had been made to the machine's disks, file 33 by file and bit by bit, will be undone as well. Files that 34 were since created will disappear, files that were deleted 35 will be restored, changes to files will be reverted. 36 </p> 37 <p> 38 Strictly speaking, this is only true for virtual hard disks 39 in "normal" mode. You can configure disks to behave 40 differently with snapshots, see 41 <xref href="hdimagewrites.dita#hdimagewrites"/>. In technical terms, it is 42 not the virtual disk itself that is restored when a snapshot 43 is restored. Instead, when a snapshot is taken, 44 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates differencing images which contain 45 only the changes since the snapshot were taken. When the 46 snapshot is restored, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> throws away that 47 differencing image, thus going back to the previous state. 48 This is both faster and uses less disk space. For the 49 details, which can be complex, see 50 <xref href="diffimages.dita#diffimages"/>. 51 </p> 52 <p> 53 Creating the differencing image as such does not occupy much 54 space on the host disk initially, since the differencing 55 image will initially be empty and grow dynamically later 56 with each write operation to the disk. The longer you use 57 the machine after having created the snapshot, however, the 58 more the differencing image will grow in size. 59 </p> 20 <p>The complete state of all the virtual disks attached to the machine is preserved. Going back 21 to a snapshot means that all changes that had been made to the machine's disks, file by file and bit by bit, 22 will be undone. Files that were since created will disappear, files that were deleted will be restored, 23 changes to files will be reverted. </p> 24 <p>Strictly speaking, this is only true for virtual hard disks in "normal" mode. You can 25 configure disks to behave differently with snapshots, see <xref href="hdimagewrites.dita#hdimagewrites"/>. In 26 technical terms, it is not the virtual disk itself that is restored when a snapshot is restored. Instead, when 27 a snapshot is taken, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates differencing images which 28 contain only the changes since the snapshot were taken. When the snapshot is restored, <ph 29 conkeyref="vbox-conkeyref-phrases/product-name"/> throws away that differencing image, thus going back to 30 the previous state. This is both faster and uses less disk space. For the details, which can be complex, see 31 <xref href="diffimages.dita#diffimages"/>. </p> 32 <p>Creating the differencing image as such does not occupy much space on the host disk 33 initially, since the differencing image will initially be empty and grow dynamically later with each write 34 operation to the disk. The longer you use the machine after having created the snapshot, however, the more the 35 differencing image will grow in size. </p> 60 36 </li> 61 37 <li> 62 <p> 63 If you took a snapshot while the machine was running, the 64 memory state of the machine is also saved in the snapshot. 65 This is in the same way that memory can be saved when you 66 close a VM window. When you restore such a snapshot, 67 execution resumes at exactly the point when the snapshot was 68 taken. 69 </p> 70 <p> 71 The memory state file can be as large as the memory size of 72 the VM and will therefore occupy considerable disk space. 73 </p> 38 <p>If you took a snapshot while the machine was running, the memory state of the machine is also 39 saved in the snapshot. This is in the same way that memory can be saved when you close a VM window. When you 40 restore such a snapshot, execution resumes at exactly the point when the snapshot was taken. </p> 41 <p>The memory state file can be as large as the memory size of the VM and will therefore occupy 42 considerable disk space. </p> 74 43 </li> 75 44 </ul> -
trunk/doc/manual/en_US/dita/topics/vbox-auth.dita
r99797 r105303 3 3 <topic xml:lang="en-us" id="vbox-auth"> 4 4 <title>RDP Authentication</title> 5 5 6 6 <body> 7 <p> 8 For each virtual machine that is remotely accessible using RDP, you can individually 9 determine if and how client connections are authenticated. For this, use the 7 <p> For each virtual machine that is remotely accessible using RDP, you can individually 8 determine if and how client connections are authenticated. For this, use the 10 9 <userinput>VBoxManage modifyvm</userinput> command with the 11 <codeph>--vrde-auth-type</codeph> option. See <xref href="vboxmanage-modifyvm.dita"> 12 VBoxManage modifyvm</xref>. The following methods of authentication are available: 13 </p> 10 <codeph>--vrde-auth-type</codeph> option. See <xref href="vboxmanage-modifyvm.dita" 11 >VBoxManage modifyvm</xref>. The following methods of authentication are available: </p> 14 12 <ul> 15 13 <li> … … 160 158 </p> 161 159 </body> 162 160 163 161 </topic> -
trunk/doc/manual/en_US/dita/topics/vboxconfigdata-machine-folder.dita
r105134 r105303 3 3 <topic xml:lang="en-us" id="vboxconfigdata-machine-folder"> 4 4 <title>The Machine Folder</title> 5 5 6 6 <body> 7 7 <p> … … 89 89 change the location of its snapshots folder in the VM settings. 90 90 </p> 91 <p> 92 You can change the default machine folder by selecting <b outputclass="bold">Preferences</b> 93 from the <b outputclass="bold">File</b> menu in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> main window. Then, in 94 the displayed window, click on the <b outputclass="bold">General</b> tab. Alternatively, use 95 the <userinput>VBoxManage setproperty machinefolder</userinput> command. See 96 <xref href="vboxmanage-setproperty.dita">VBoxManage setproperty</xref>. 97 </p> 91 <p> You can change the default machine folder by selecting <b outputclass="bold">Preferences</b> 92 from the <b outputclass="bold">File</b> menu in the <ph 93 conkeyref="vbox-conkeyref-phrases/product-name"/> main window. Then, in the displayed 94 window, click the <b outputclass="bold">General</b> tab. Alternatively, use the 95 <userinput>VBoxManage setproperty machinefolder</userinput> command. See <xref 96 href="vboxmanage-setproperty.dita">VBoxManage setproperty</xref>. </p> 98 97 </body> 99 98 100 99 </topic> -
trunk/doc/manual/en_US/dita/topics/vboxheadless-examples.dita
r105300 r105303 1 1 <?xml version="1.0" encoding="utf-8"?> 2 2 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> 3 <topic rev="refsect1" id="vboxheadless-examples"> <title>Examples</title><body>4 5 3 <topic rev="refsect1" id="vboxheadless-examples"> 4 <title>Examples</title> 5 <body> 6 6 <p rev="para"> 7 7 The following command starts the <codeph rev="literal">ol7u4</codeph> VM: 8 8 </p> 9 <screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u4"</screen>9 <screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u4"</screen> 10 10 <p rev="para"> 11 11 The following command starts the <codeph rev="literal">ol7u6</codeph> VM in 12 12 the Paused state. 13 13 </p> 14 <screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u6" --start-paused</screen>14 <screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u6" --start-paused</screen> 15 15 <p rev="para"> 16 16 The following command starts the <codeph rev="literal">ol7u6</codeph> VM and … … 18 18 <filepath rev="filename">ol7u6-recording</filepath> WebM file. 19 19 </p> 20 <screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u6" --capture --filename ol7u6-recording.webm</screen> 21 </body></topic> 20 <screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u6" --capture --filename ol7u6-recording.webm</screen> 21 </body> 22 </topic> -
trunk/doc/manual/en_US/dita/topics/vboxheadless-see-also.dita
r105300 r105303 1 1 <?xml version="1.0" encoding="utf-8"?> 2 2 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> 3 <topic rev="refsect1" id="vboxheadless-see-also"> <title>See Also</title><body>4 5 <p rev="para">6 7 <xref href="vboxmanage-startvm.dita#vboxmanage-startvm"/> 8 </p>9 </body></topic>3 <topic rev="refsect1" id="vboxheadless-see-also"> 4 <title>See Also</title> 5 <body> 6 <p rev="para"><xref href="vboxmanage-list.dita#vboxmanage-list"/>, 7 <xref href="vboxmanage-startvm.dita#vboxmanage-startvm"/></p> 8 </body> 9 </topic> -
trunk/doc/manual/en_US/dita/topics/virt-why-useful.dita
r99797 r105303 12 12 <ul> 13 13 <li> 14 <p> 15 <b outputclass="bold">Running multiple operating systems 16 simultaneously.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to run 17 more than one OS at a time. This way, you can run software 18 written for one OS on another, such as Windows software on 19 Linux or a Mac, without having to reboot to use it. Since you 20 can configure what kinds of <i>virtual</i> 21 hardware should be presented to each such OS, you can install 22 an old OS such as DOS or OS/2 even if your real computer's 23 hardware is no longer supported by that OS. 24 </p> 14 <p><b outputclass="bold">Running multiple operating systems simultaneously.</b> 15 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to run more than one OS at a time. This way, 16 you can run software written for one OS on another, such as Windows software on Linux or a Mac, without having 17 to reboot to use it. Since you can configure what kinds of <i>virtual</i> hardware should be presented to each 18 such OS, you can install an old OS such as DOS or OS/2 even if your real computer's hardware is no longer 19 supported by that OS. </p> 25 20 </li> 26 21 <li> 27 <p> 28 <b outputclass="bold">Easier software 29 installations.</b> Software vendors can use virtual 30 machines to ship entire software configurations. For example, 31 installing a complete mail server solution on a real machine 32 can be a tedious task. With <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, such a complex 33 setup, often called an <i>appliance</i>, can be 34 packed into a virtual machine. Installing and running a mail 35 server becomes as easy as importing such an appliance into 36 <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. 37 </p> 22 <p><b outputclass="bold">Easier software installations.</b> Software vendors can use virtual 23 machines to ship entire software configurations. For example, installing a complete mail server solution on a 24 real machine can be a tedious task. With <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, such a complex 25 setup, often called an <i>appliance</i>, can be packed into a virtual machine. Installing and running a mail 26 server becomes as easy as importing such an appliance into <ph conkeyref="vbox-conkeyref-phrases/product-name" 27 />. </p> 38 28 </li> 39 29 <li> 40 <p> 41 <b outputclass="bold">Testing and disaster 42 recovery.</b> Once installed, a virtual machine and its 43 virtual hard disks can be considered a 44 <i>container</i> that can be arbitrarily frozen, 45 woken up, copied, backed up, and transported between hosts. 46 </p> 47 <p> 48 Using virtual machines enables you to build and test a 49 multi-node networked service, for example. Issues with 50 networking, operating system, and software configuration can 51 be investigated easily. 52 </p> 53 <p> 54 In addition to that, with the use of another <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 55 feature called <i>snapshots</i>, one can save a 56 particular state of a virtual machine and revert back to that 57 state, if necessary. This way, one can freely experiment with 58 a computing environment. If something goes wrong, such as 59 problems after installing software or infecting the guest with 60 a virus, you can easily switch back to a previous snapshot and 61 avoid the need of frequent backups and restores. 62 </p> 63 <p> 64 Any number of snapshots can be created, allowing you to travel 65 back and forward in virtual machine time. You can delete 66 snapshots while a VM is running to reclaim disk space. 67 </p> 30 <p><b outputclass="bold">Testing and disaster recovery.</b> Once installed, a virtual machine and 31 its virtual hard disks can be considered a <i>container</i> that can be arbitrarily frozen, woken up, copied, 32 backed up, and transported between hosts. </p> 33 <p>Using virtual machines enables you to build and test a multinode networked 34 service, for example. Issues with networking, operating system, and software configuration 35 can be investigated easily. </p> 36 <p>In addition to that, with the use of another <ph conkeyref="vbox-conkeyref-phrases/product-name" 37 /> feature called <i>snapshots</i>, one can save a particular state of a virtual machine and revert back to 38 that state, if necessary. This way, one can freely experiment with a computing environment. If something goes 39 wrong, such as problems after installing software or infecting the guest with a virus, you can easily switch 40 back to a previous snapshot and avoid the need of frequent backups and restores. </p> 41 <p>Any number of snapshots can be created, allowing you to travel back and forward in virtual 42 machine time. You can delete snapshots while a VM is running to reclaim disk space. </p> 68 43 </li> 69 44 <li> 70 <p> 71 <b outputclass="bold">Infrastructure consolidation.</b> 72 Virtualization can significantly reduce hardware and 73 electricity costs. Most of the time, computers today only use 74 a fraction of their potential power and run with low average 75 system loads. A lot of hardware resources as well as 76 electricity is thereby wasted. So, instead of running many 77 such physical computers that are only partially used, one can 78 pack many virtual machines onto a few powerful hosts and 79 balance the loads between them. 80 </p> 45 <p><b outputclass="bold">Infrastructure consolidation.</b> Virtualization can significantly reduce 46 hardware and electricity costs. Most of the time, computers today only use a fraction of their potential power 47 and run with low average system loads. A lot of hardware resources as well as electricity is thereby wasted. 48 So, instead of running many such physical computers that are only partially used, one can pack many virtual 49 machines onto a few powerful hosts and balance the loads between them. </p> 81 50 </li> 82 51 </ul>
Note:
See TracChangeset
for help on using the changeset viewer.
