- Timestamp:
- Oct 2, 2024 9:46:07 AM (2 months ago)
- Location:
- trunk/doc/manual/en_US/dita
- Files:
-
- 1 deleted
- 7 edited
-
UserManual.ditamap (modified) (1 diff)
-
topics/host-guest-matrix.dita (modified) (1 diff)
-
topics/install-linux-prereq.dita (modified) (1 diff)
-
topics/ts_linux-buggy.dita (modified) (2 diffs)
-
topics/ts_win-guest-active-dir-domain.dita (modified) (1 diff)
-
topics/ts_win-guest-high-cpu.dita (modified) (1 diff)
-
topics/vboxmanage-general.dita (deleted)
-
topics/vboxmanage-intro.dita (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/dita/UserManual.ditamap
r105941 r106204 344 344 <!-- Commands Overview --> 345 345 <topicref href="topics/vboxmanage-cmd-overview.dita"/> 346 <topicref href="topics/vboxmanage-general.dita"/>347 346 <!-- The remainder of the topics in this chapter are generated from docbook XML files.--> 348 347 <topicref format="ditamap" href="topics/man_VBoxManage-common.ditamap"/> -
trunk/doc/manual/en_US/dita/topics/host-guest-matrix.dita
r105941 r106204 41 41 <row> 42 42 <entry>Arm64</entry> 43 <entry>macOS (requires Apple Silicon hardware)</entry>43 <entry>macOS (requires Apple silicon hardware)</entry> 44 44 <entry>Arm64</entry> 45 45 <entry>Linux (various distributions)</entry> -
trunk/doc/manual/en_US/dita/topics/install-linux-prereq.dita
r105841 r106204 7 7 <p>For the various versions of Linux that are supported as host operating systems, see <xref 8 8 href="hostossupport.dita#hostossupport"/>. </p> 9 <p>You may need to install the following packages on your Linux system before starting the installation. Some 10 systems will do this for you automatically when you install <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p> 9 <p>You may need to install the following package on your Linux system before starting the installation. Some systems will do this for you automatically when you install <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p> 11 10 <ul> 12 11 <li> 13 12 <p>Qt 6.5.3 or later.</p> 14 13 </li> 15 <li>16 <p>SDL 2.0 or later. This graphics library is typically called <filepath>libsdl2</filepath> or similar. </p>17 </li>18 14 </ul> 19 15 <note> 20 <p>These packages are only required if you want to run the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 21 graphical user interfaces. In particular, <userinput>VirtualBox</userinput>, the graphical VirtualBox Manager, 22 requires both Qt and SDL. If you only want to run <userinput>VBoxHeadless</userinput>, neither Qt nor SDL are 23 required. </p> 16 <p>Qt is only required if you want to run the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphical user interfaces. In particular, <userinput>VirtualBox</userinput>, the graphical VirtualBox Manager, requires Qt. If you only want to run <userinput>VBoxHeadless</userinput>, Qt is not required. </p> 24 17 </note> 25 18 </body> -
trunk/doc/manual/en_US/dita/topics/ts_linux-buggy.dita
r99797 r106204 11 11 <ul> 12 12 <li> 13 <p> 14 The Linux kernel version 2.6.18, and some 2.6.17 versions, 15 introduced a race condition that can cause boot crashes in 16 <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. Please use a kernel version 2.6.19 or later. 17 </p> 13 <p> The Linux kernel version 2.6.18, and some 2.6.17 versions, introduced a race condition that can cause boot failures in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. Use kernel version 2.6.19 or later. </p> 18 14 </li> 19 15 <li> … … 31 27 a newer kernel. 32 28 </p> 33 <p> 34 See 35 <ph>http://www.mail-archive.com/[email protected]/msg30813.html</ph> 36 for details about the kernel fix. 37 </p> 29 <p> See <xref href="http://www.mail-archive.com/[email protected]/msg30813.html" format="html" scope="external">this message</xref> for details about the kernel fix. </p> 38 30 </li> 39 31 </ul> -
trunk/doc/manual/en_US/dita/topics/ts_win-guest-active-dir-domain.dita
r99797 r106204 6 6 7 7 <body> 8 <p> 9 If a Windows guest is a member of an Active Directory domain and 10 the snapshot feature of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is used, it could be 11 removed from the Active Direcory domain after you restore an 12 older snapshot. 13 </p> 14 <p> 15 This is caused by automatic machine password changes performed 16 by Windows at regular intervals for security purposes. You can 17 disable this feature as shown in the following article from 18 Microsoft: 19 <ph>http://support.microsoft.com/kb/154501</ph>. 20 </p> 8 <p> If a Windows guest is a member of an Active Directory domain and the snapshot feature of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is used, it could be removed from the Active Directory domain after you restore an older snapshot. </p> 9 <p> This is caused by automatic machine password changes performed by Windows at regular intervals for security purposes. You can disable this feature as shown in this <xref href="http://support.microsoft.com/kb/154501" format="html" scope="external">article from Microsoft</xref>. </p> 21 10 </body> 22 11 -
trunk/doc/manual/en_US/dita/topics/ts_win-guest-high-cpu.dita
r99016 r106204 2 2 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> 3 3 <topic xml:lang="en-us" id="ts_win-guest-high-cpu"> 4 <title>Windows Guests mayCause a High CPU Load</title>4 <title>Windows Guests Cause a High CPU Load</title> 5 5 6 6 <body> 7 <p> 8 Several background applications of Windows guests, especially 9 virus scanners, are known to increase the CPU load notably even 10 if the guest appears to be idle. We recommend to deactivate 11 virus scanners within virtualized guests if possible. 12 </p> 7 <p> Several background applications in Windows guests, especially virus scanners, are known to increase the CPU load notably even if the guest appears to be idle. Deactivating virus scanners in VMs, where possible, can reduce this problem. </p> 8 <p>Windows Updates, especially on Windows 10 and Windows 11 guests, can also cause a temporary increase in guest CPU usage and storage activity. Modern Windows versions do a lot of updating in the background to deploy new features and security fixes.</p> 13 9 </body> 14 10 -
trunk/doc/manual/en_US/dita/topics/vboxmanage-intro.dita
r105941 r106204 4 4 <topic xml:lang="en-us" id="vboxmanage-intro"> 5 5 <title>Introduction</title> 6 6 7 7 <body> 8 <p>As briefly mentioned in <xref href="frontends.dita#frontends"/>, <userinput>VBoxManage</userinput> is the CLI to <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. With it, you can control <ph conkeyref="vbox-conkeyref-phrases/product-name"/> from the command line of your host operating system. <userinput>VBoxManage</userinput> supports all the features that the graphical user interface gives you access to, but it supports a lot more than that. It exposes all the features of the virtualization engine, even those that cannot be accessed from the GUI. </p> 9 <p>You will need to use the command line if you want to do the 10 following: 11 </p> 8 <p><userinput>VBoxManage</userinput> is the CLI to <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. With it, you can control <ph conkeyref="vbox-conkeyref-phrases/product-name"/> from the command line of the host operating system. <userinput>VBoxManage</userinput> supports all the features that the graphical user interface gives you access to, plus the features of the virtualization engine that can't be accessed from the GUI. </p> 9 <p>You need to use the command line to do the following: </p> 12 10 <ul> 13 11 <li> … … 18 16 </li> 19 17 <li> 20 <p> 21 Control some of the more advanced and experimental 22 configuration settings for a VM. 23 </p> 18 <p> Control some more advanced and experimental configuration settings for a VM. </p> 24 19 </li> 25 20 </ul> 26 <p>There are two main things to keep in mind when using <userinput>VBoxManage</userinput>. First, 27 <userinput>VBoxManage</userinput> must always be used with a specific subcommand, such as 28 <userinput>list</userinput> or <userinput>createvm</userinput> or <userinput>startvm</userinput>. All the 29 subcommands that <userinput>VBoxManage</userinput> supports are described in detail in <xref 30 href="vboxmanage.dita#vboxmanage"/>. </p> 31 <p>Second, most of these subcommands require that you specify a particular virtual machine after the 32 subcommand. There are two ways you can do this: </p> 33 <ul> 34 <li> 35 <p> 36 You can specify the VM name, as it is shown in the 37 <ph conkeyref = "vbox-conkeyref-phrases/product-name"/> GUI. Note that if that name contains spaces, 38 then you must enclose the entire name in double quotes. This 39 is always required with command line arguments that contain 40 spaces. For example: 41 </p> 42 <pre xml:space="preserve">VBoxManage startvm "Windows XP"</pre> 43 </li> 44 <li> 45 <p> 46 You can specify the UUID, which is the internal unique 47 identifier that <ph conkeyref = "vbox-conkeyref-phrases/product-name"/> uses to refer to the virtual 48 machine. Assuming that the VM called "Windows XP" has the UUID 49 shown below, the following command has the same effect as the 50 previous example: 51 </p> 52 <pre xml:space="preserve">VBoxManage startvm 670e746d-abea-4ba6-ad02-2a3b043810a5</pre> 53 </li> 54 </ul> 55 <p>You can enter <userinput>VBoxManage list vms</userinput> to have all currently registered VMs listed with their respective names and UUIDs. </p> 56 <p>Some typical examples of how to control <ph conkeyref="vbox-conkeyref-phrases/product-name"/> from the 57 command line are listed below: </p> 58 <ul> 59 <li> 60 <p>To create a new virtual machine from the command line and immediately register it with <ph 61 conkeyref="vbox-conkeyref-phrases/product-name"/>, use <userinput>VBoxManage createvm</userinput> with the 62 <!--option not processed within -->--register option, as follows: </p> 63 <pre xml:space="preserve">$ VBoxManage createvm --name "SUSE 15.2" --register 64 Virtual machine 'SUSE 15.2' is created. 65 UUID: c89fc351-8ec6-4f02-a048-57f4d25288e5 66 Settings file: '/home/username/VirtualBox VMs/SUSE 15.2/SUSE 15.2.vbox'</pre> 67 <p>As can be seen from the above output, a new virtual machine has been created with a new UUID and a new XML-formatted settings file. </p> 68 <p> 69 For more details, see 70 <xref href="vboxmanage-createvm.dita"/>. 71 </p> 72 </li> 73 <li> 74 <p>To show the configuration of a particular VM, use <userinput>VBoxManage showvminfo</userinput>. 75 See <xref href="vboxmanage-showvminfo.dita"/> for details and an example. </p> 76 </li> 77 <li> 78 <p>To change settings while a VM is powered off, use <userinput>VBoxManage modifyvm</userinput>. 79 For example: </p> 80 <pre xml:space="preserve">VBoxManage modifyvm "Windows XP" --memory 512</pre> 81 <p>See also <xref href="vboxmanage-modifyvm.dita"/>. </p> 82 </li> 83 <li> 84 <p>To change the storage configuration, such as to add a storage controller and then a virtual 85 disk, use <userinput>VBoxManage storagectl</userinput> and <userinput>VBoxManage storageattach</userinput>. 86 See <xref href="vboxmanage-storagectl.dita"/> and <xref href="vboxmanage-storageattach.dita"/>. </p> 87 </li> 88 <li> 89 <p>To start a VM that is currently powered off, use <userinput>VBoxManage startvm</userinput>. See <xref href="vboxmanage-startvm.dita"/>. </p> 90 </li> 91 <li> 92 <p>To change a running VM's setttings or change its state (such as pausing, saving, or powering off the VM) use <userinput>VBoxManage controlvm</userinput> See <xref href="vboxmanage-controlvm.dita"/>.</p> 93 </li> 94 </ul> 21 <p>For more information, refer to the VBoxManage command <xref href="../topics/vboxmanage-common-description.dita"/> and <xref href="../topics/vboxmanage-common-examples.dita"/>.</p> 95 22 </body> 96 23 97 24 </topic>
Note:
See TracChangeset
for help on using the changeset viewer.
