Changeset 105300 in vbox for trunk/doc/manual
- Timestamp:
- Jul 12, 2024 11:53:09 AM (7 months ago)
- Location:
- trunk/doc/manual/en_US/dita/topics
- Files:
-
- 14 edited
-
cloningvdis.dita (modified) (2 diffs)
-
cloud-vm-new.dita (modified) (1 diff)
-
cloud-vm-remove.dita (modified) (1 diff)
-
glossentry-amdv.dita (modified) (1 diff)
-
install-win-installdir-req.dita (modified) (1 diff)
-
intro-installing.dita (modified) (1 diff)
-
iocaching.dita (modified) (3 diffs)
-
keyb_mouse_normal.dita (modified) (1 diff)
-
ovf-import-appliance.dita (modified) (1 diff)
-
preferences.dita (modified) (1 diff)
-
vboxheadless-examples.dita (modified) (2 diffs)
-
vboxheadless-see-also.dita (modified) (1 diff)
-
vboxmanage-intro.dita (modified) (5 diffs)
-
virtintro.dita (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/dita/topics/cloningvdis.dita
r99797 r105300 3 3 <topic xml:lang="en-us" id="cloningvdis"> 4 4 <title>Cloning Disk Images</title> 5 5 6 6 <body> 7 <p> 8 You can duplicate hard disk image files on the same host to quickly produce a second virtual 7 <p> You can duplicate hard disk image files on the same host to quickly produce a second virtual 9 8 machine with the same OS setup. However, you should <i>only</i> make copies of virtual disk 10 images using the utility supplied with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. See 11 <xrefhref="vboxmanage-clonemedium.dita"/>. This is because <ph conkeyref="vbox-conkeyref-phrases/product-name"/> assigns a UUID to9 images using the utility supplied with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. See <xref 10 href="vboxmanage-clonemedium.dita"/>. This is because <ph conkeyref="vbox-conkeyref-phrases/product-name"/> assigns a UUID to 12 11 each disk image, which is also stored inside the image, and <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will refuse 13 12 to work with two images that use the same number. If you do accidentally try to reimport a 14 13 disk image which you copied normally, you can make a second copy using the 15 <userinput>VBoxManage clonevm</userinput> command and import that instead. 16 </p> 14 <userinput>VBoxManage clonevm</userinput> command and import that instead. </p> 17 15 <p> 18 16 Note that Linux distributions identify the boot hard disk from the … … 32 30 <pre xml:space="preserve">hdparm -i /dev/sda</pre> 33 31 </body> 34 32 35 33 </topic> -
trunk/doc/manual/en_US/dita/topics/cloud-vm-new.dita
r105289 r105300 10 10 <ol> 11 11 <li> 12 <p> 12 <p>Click a cloud profile in the <b outputclass="bold">OCI</b> group. </p> 13 13 <p>The cloud VMs for the selected cloud profile are displayed. </p> 14 14 </li> -
trunk/doc/manual/en_US/dita/topics/cloud-vm-remove.dita
r105289 r105300 6 6 <body> 7 7 <p>You can use <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> to remove a cloud VM as follows: </p> 8 <p> 8 <p>Right-click the cloud VM name and select <b outputclass="bold">Remove</b>. </p> 9 9 <ul> 10 10 <li> -
trunk/doc/manual/en_US/dita/topics/glossentry-amdv.dita
r99409 r105300 6 6 The hardware virtualization features built into modern AMD processors. 7 7 See <xref href="hwvirt.dita">Hardware Virtualization</xref>. 8 </glossdef>8 </glossdef> 9 9 </glossentry> 10 -
trunk/doc/manual/en_US/dita/topics/install-win-installdir-req.dita
r105289 r105300 16 16 Authenticated Users S-1-5-11:(OI)(CI)(RX) 17 17 Authenticated Users S-1-5-11:(DE,WD,AD,WEA,WA) 18 </pre> 18 </pre>Directory inheritance must also be disabled for all parent directories. </p> 19 19 <p>You can use the <codeph>icacls</codeph> Windows command line tool to modify a directory to meet the security 20 20 requirements. For example: <pre xml:space="preserve"> -
trunk/doc/manual/en_US/dita/topics/intro-installing.dita
r105289 r105300 15 15 <ul> 16 16 <li> 17 <p><b outputclass="bold">Base package.</b> The base 18 package consists of all open source components and is licensed 19 under the GNU General Public License V3. 20 </p> 17 <p><b outputclass="bold">Base package.</b> The base package consists of all open source 18 components and is licensed under the GNU General Public License V3. </p> 21 19 </li> 22 20 <li> -
trunk/doc/manual/en_US/dita/topics/iocaching.dita
r99797 r105300 3 3 <topic xml:lang="en-us" id="iocaching"> 4 4 <title>Host Input/Output Caching</title> 5 5 6 6 <body> 7 7 <p> … … 88 88 </p> 89 89 <pre xml:space="preserve">VBoxManage storagectl "VM name" --name <controllername> --hostiocache off</pre> 90 <p> 91 See <xref href="vboxmanage-storagectl.dita"/>. 92 </p> 90 <p> See <xref href="vboxmanage-storagectl.dita"/>. </p> 93 91 <p> 94 92 For the above reasons, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses SATA controllers by … … 96 94 </p> 97 95 </body> 98 96 99 97 </topic> -
trunk/doc/manual/en_US/dita/topics/keyb_mouse_normal.dita
r105289 r105300 38 38 <ul> 39 39 <li> 40 <p> 41 Your <b outputclass="bold">keyboard</b> is owned by 42 the VM if the VM window on your host desktop has the 43 keyboard focus. If you have many windows open in your guest 44 OS, the window that has the focus in your VM is used. This 45 means that if you want to enter text within your VM, click 46 on the title bar of your VM window first. 47 </p> 48 <p> 49 To release keyboard ownership, press the Host key. As 50 explained above, this is typically the right Ctrl key. 51 </p> 52 <p> 53 Note that while the VM owns the keyboard, some key 54 sequences, such as Alt+Tab, will no longer be seen by the 55 host, but will go to the guest instead. After you press the 56 Host key to reenable the host keyboard, all key presses will 57 go through the host again, so that sequences such as Alt+Tab 58 will no longer reach the guest. For technical reasons it may 59 not be possible for the VM to get all keyboard input even 60 when it does own the keyboard. Examples of this are the 61 Ctrl+Alt+Del sequence on Windows hosts or single keys 62 grabbed by other applications on X11 hosts such as the GNOME 63 desktop Locate Pointer feature. 64 </p> 40 <p>Your <b outputclass="bold">keyboard</b> is owned by the VM if the VM window on your host desktop has the 41 keyboard focus. If you have many windows open in your guest OS, the window that has the focus in your VM is 42 used. This means that if you want to enter text within your VM, click the title bar of your VM window first. </p> 43 <p>To release keyboard ownership, press the Host key. As explained above, this is typically the right Ctrl key. </p> 44 <p>Note that while the VM owns the keyboard, some key sequences, such as Alt+Tab, will no longer be seen by the 45 host, but will go to the guest instead. After you press the Host key to reenable the host keyboard, all key 46 presses will go through the host again, so that sequences such as Alt+Tab will no longer reach the guest. For 47 technical reasons it may not be possible for the VM to get all keyboard input even when it does own the 48 keyboard. Examples of this are the Ctrl+Alt+Del sequence on Windows hosts or single keys grabbed by other 49 applications on X11 hosts such as the GNOME desktop Locate Pointer feature. </p> 65 50 </li> 66 51 <li> 67 <p> 68 Your <b outputclass="bold">mouse</b> is owned by the 69 VM only after you have clicked in the VM window. The host 70 mouse pointer will disappear, and your mouse will drive the 71 guest's pointer instead of your normal mouse pointer. 72 </p> 73 <p> 74 Note that mouse ownership is independent of that of the 75 keyboard. Even after you have clicked on a titlebar to be 76 able to enter text into the VM window, your mouse is not 77 necessarily owned by the VM yet. 78 </p> 79 <p> 80 To release ownership of your mouse by the VM, press the Host 81 key. 82 </p> 52 <p>Your <b outputclass="bold">mouse</b> is owned by the VM only after you have clicked in the VM window. The 53 host mouse pointer will disappear, and your mouse will drive the guest's pointer instead of your normal mouse 54 pointer. </p> 55 <p>Note that mouse ownership is independent of that of the keyboard. Even after you have clicked on a titlebar 56 to be able to enter text into the VM window, your mouse is not necessarily owned by the VM yet. </p> 57 <p>To release ownership of your mouse by the VM, press the Host key. </p> 83 58 </li> 84 59 </ul> 85 <p> 86 As this behavior is inconvenient, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a set 87 of tools and device drivers for guest systems called the 88 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions. These tools make VM keyboard and 89 mouse operations much more seamless. Most importantly, the Guest 90 Additions suppress the second "guest" mouse pointer and make 91 your host mouse pointer work directly in the guest. See 92 <xref href="guestadditions.dita#guestadditions"/>. 93 </p> 60 <p>As this behavior is inconvenient, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a set of tools 61 and device drivers for guest systems called the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest 62 Additions. These tools make VM keyboard and mouse operations much more seamless. Most importantly, the Guest 63 Additions suppress the second "guest" mouse pointer and make your host mouse pointer work directly in the guest. 64 See <xref href="guestadditions.dita#guestadditions"/>. </p> 94 65 </body> 95 66 -
trunk/doc/manual/en_US/dita/topics/ovf-import-appliance.dita
r105289 r105300 8 8 <ol> 9 9 <li> 10 <p> 10 <p>Double-click the OVF or OVA file. </p> 11 11 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates file type associations automatically for any 12 12 OVF and OVA files on your host OS. </p> -
trunk/doc/manual/en_US/dita/topics/preferences.dita
r105289 r105300 17 17 </li> 18 18 <li> 19 <p> 19 <p>Click <b outputclass="bold">Preferences</b> on the Welcome screen in <ph 20 20 conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. </p> 21 21 </li> -
trunk/doc/manual/en_US/dita/topics/vboxheadless-examples.dita
r105294 r105300 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"> 4 <title>Examples</title>5 <body>3 <topic rev="refsect1" id="vboxheadless-examples"><title>Examples</title><body> 4 5 6 6 <p rev="para"> 7 7 The following command starts the <codeph rev="literal">ol7u4</codeph> VM: 8 8 </p> 9 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 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> 22 </topic> 20 <screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u6" --capture --filename ol7u6-recording.webm</screen> 21 </body></topic> -
trunk/doc/manual/en_US/dita/topics/vboxheadless-see-also.dita
r105294 r105300 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"> 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>3 <topic rev="refsect1" id="vboxheadless-see-also"><title>See Also</title><body> 4 5 <p rev="para"> 6 <xref href="vboxmanage-list.dita#vboxmanage-list"/>, 7 <xref href="vboxmanage-startvm.dita#vboxmanage-startvm"/> 8 </p> 9 </body></topic> -
trunk/doc/manual/en_US/dita/topics/vboxmanage-intro.dita
r99497 r105300 6 6 7 7 <body> 8 <p> 9 As briefly mentioned in <xref href="frontends.dita#frontends"/>, 10 <userinput>VBoxManage</userinput> is the command-line interface to 11 Oracle VM VirtualBox. With it, you can completely control Oracle VM VirtualBox 12 from the command line of your host operating system. 13 <userinput>VBoxManage</userinput> supports all the features that the 14 graphical user interface gives you access to, but it supports a 15 lot more than that. It exposes all the features of the 16 virtualization engine, even those that cannot be accessed from the 17 GUI. 18 </p> 19 <p> 20 You will need to use the command line if you want to do the 8 <p>As briefly mentioned in <xref href="frontends.dita#frontends"/>, <userinput>VBoxManage</userinput> is 9 the command-line interface to <ph conkeyref = "vbox-conkeyref-phrases/product-name"/>. With it, you can completely control <ph conkeyref = "vbox-conkeyref-phrases/product-name"/> from the 10 command line of your host operating system. <userinput>VBoxManage</userinput> supports all the features that the 11 graphical user interface gives you access to, but it supports a lot more than that. It exposes all the features of 12 the virtualization engine, even those that cannot be accessed from the GUI. </p> 13 <p>You will need to use the command line if you want to do the 21 14 following: 22 15 </p> … … 35 28 </li> 36 29 </ul> 37 <p> 38 There are two main things to keep in mind when using 39 <userinput>VBoxManage</userinput>. First, 40 <userinput>VBoxManage</userinput> must always be used with a specific 41 subcommand, such as <userinput>list</userinput> or 42 <userinput>createvm</userinput> or <userinput>startvm</userinput>. All the 43 subcommands that <userinput>VBoxManage</userinput> supports are 44 described in detail in <xref href="vboxmanage.dita#vboxmanage"/>. 45 </p> 46 <p> 47 Second, most of these subcommands require that you specify a 48 particular virtual machine after the subcommand. There are two 49 ways you can do this: 50 </p> 30 <p>There are two main things to keep in mind when using <userinput>VBoxManage</userinput>. First, 31 <userinput>VBoxManage</userinput> must always be used with a specific subcommand, such as 32 <userinput>list</userinput> or <userinput>createvm</userinput> or <userinput>startvm</userinput>. All the 33 subcommands that <userinput>VBoxManage</userinput> supports are described in detail in <xref 34 href="vboxmanage.dita#vboxmanage"/>. </p> 35 <p>Second, most of these subcommands require that you specify a particular virtual machine after the 36 subcommand. There are two ways you can do this: </p> 51 37 <ul> 52 38 <li> 53 39 <p> 54 40 You can specify the VM name, as it is shown in the 55 Oracle VM VirtualBoxGUI. Note that if that name contains spaces,41 <ph conkeyref = "vbox-conkeyref-phrases/product-name"/> GUI. Note that if that name contains spaces, 56 42 then you must enclose the entire name in double quotes. This 57 43 is always required with command line arguments that contain … … 63 49 <p> 64 50 You can specify the UUID, which is the internal unique 65 identifier that Oracle VM VirtualBoxuses to refer to the virtual51 identifier that <ph conkeyref = "vbox-conkeyref-phrases/product-name"/> uses to refer to the virtual 66 52 machine. Assuming that the VM called "Windows XP" has the UUID 67 53 shown below, the following command has the same effect as the … … 77 63 </p> 78 64 <p> 79 Some typical examples of how to control Oracle VM VirtualBoxfrom the65 Some typical examples of how to control <ph conkeyref = "vbox-conkeyref-phrases/product-name"/> from the 80 66 command line are listed below: 81 67 </p> … … 84 70 <p> 85 71 To create a new virtual machine from the command line and 86 immediately register it with Oracle VM VirtualBox, use72 immediately register it with <ph conkeyref = "vbox-conkeyref-phrases/product-name"/>, use 87 73 <userinput>VBoxManage createvm</userinput> with the 88 74 <!--option not processed within -->--register option, as follows: -
trunk/doc/manual/en_US/dita/topics/virtintro.dita
r105289 r105300 6 6 7 7 <body> 8 <p> 9 When dealing with virtualization, and also for understanding the 10 following chapters of this documentation, it helps to acquaint 11 oneself with a bit of crucial terminology, especially the 12 following terms: 13 </p> 8 <p>When dealing with virtualization, and also for understanding the following 9 chapters of this documentation, it helps to acquaint yourself with some important terminology, 10 especially the following terms: </p> 14 11 <ul> 15 12 <li>
Note:
See TracChangeset
for help on using the changeset viewer.
