Changeset 105939 in vbox
- Timestamp:
- Sep 4, 2024 7:37:02 AM (5 months ago)
- Location:
- trunk/doc/manual/en_US/dita
- Files:
-
- 36 edited
- 2 copied
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/dita/UserManual.ditamap
r105938 r105939 258 258 <topicref href="topics/guestadd-video.dita"> 259 259 <topicref href="topics/guestadd-3d.dita"/> 260 <topicref href="topics/guestadd-2d.dita"/> 260 261 </topicref> 261 262 <topicref href="topics/seamlesswindows.dita"/> … … 561 562 <topicref href="topics/ts_win-cpu-usage-rept.dita"/> 562 563 <topicref href="topics/ts_host-powermgmt.dita"/> 564 <topicref href="topics/ts_gui-2d-grayed-out.dita"/> 563 565 </topicref> 564 566 <topicref href="topics/ts_win-guests.dita"> -
trunk/doc/manual/en_US/dita/topics/ExperimentalFeatures.dita
r105938 r105939 5 5 6 6 <body> 7 <p> Some <ph conkeyref="vbox-conkeyref-phrases/product-name"/> features are labeled as experimental. Such features are provided on an "as-is" basis and are not formally supported. However, feedback and suggestions about such features are welcome. A comprehensive list of experimental features is as follows: </p> 7 <p> 8 Some <ph conkeyref="vbox-conkeyref-phrases/product-name"/> features are labeled as experimental. Such 9 features are provided on an "as-is" basis and are not formally 10 supported. However, feedback and suggestions about such features 11 are welcome. A comprehensive list of experimental features is as 12 follows: 13 </p> 8 14 <ul> 9 15 <li> … … 11 17 Hardware 3D acceleration support for Windows, Linux, and 12 18 Oracle Solaris guests 19 </p> 20 </li> 21 <li> 22 <p> 23 Hardware 2D video playback acceleration support for Windows 24 guests 13 25 </p> 14 26 </li> … … 39 51 </li> 40 52 <li> 41 <p> Using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and Hyper-V on the same host </p> 53 <p> 54 Using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and Hyper-V on the same host 55 </p> 42 56 </li> 43 57 </ul> -
trunk/doc/manual/en_US/dita/topics/KnownProblems.dita
r105938 r105939 19 19 >Hyper-V</b> on the same host. To fix this, certain Windows features like "Hyper-V Platform", "Virtual 20 20 Machine Platform" and "Windows Hypervisor Platform" must be turned off, followed by a host reboot. </p> 21 <p>On newer Windows versions, enabling the device security features Core Isolation or Memory Integrity will use Hyper-V, even if you had previously turned it off.</p>22 21 <p>Additionally, the Microsoft Device Guard and Credential Guard hardware readiness tool might have to be used 23 22 in order to turn off more features. For example, by running the following command: </p> … … 139 138 <ul id="ul_ddr_kzn_hcc"> 140 139 <li> 141 <p>x86-based guest operating systems will not run .</p>142 143 140 <p>x86-based guest operating systems will not run</p> 141 </li> 142 <li> 144 143 <p>Arm(AArch64) guests only. Arm 32 is not supported at present.</p> 145 144 </li> … … 200 199 <ul> 201 200 <li> 202 <p>USB support on Oracle Solaris hosts requires Oracle Solaris 11 FCS or later. Webcams and other isochronous devices are known to have poor performance. </p> 201 <p>USB support on Oracle Solaris hosts requires Oracle Solaris 11 version snv_124 or later. Webcams and 202 other isochronous devices are known to have poor performance. </p> 203 203 </li> 204 204 <li> … … 213 213 </li> 214 214 <li> 215 <p>Crossbow-based bridged networking on Oracle Solaris 11 hosts does not work directly with aggregate links. However, you can use <userinput>dladm</userinput> to manually create a VNIC over the aggregate link and use that with a VM. This limitation does not exist in Oracle Solaris 11 update 1 (11.1) and later. </p> 215 <p>Crossbow-based bridged networking on Oracle Solaris 11 hosts does not work directly with aggregate links. 216 However, you can use <userinput>dladm</userinput> to manually create a VNIC over the aggregate link and 217 use that with a VM. This limitation does not exist in Oracle Solaris 11u1 build 17 and later. </p> 216 218 </li> 217 219 </ul> -
trunk/doc/manual/en_US/dita/topics/arm-host-limitations.dita
r105938 r105939 3 3 <topic xml:lang="en-us" id="arm-host-limitations"> 4 4 <title>Arm Host Limitations</title> 5 <!-- 7.1: Arm platform limitations --> 5 6 <body> 6 7 <p>The following limitations apply when using an Arm platform host:</p> … … 9 10 <li><p>Only VMSVGA is supported as a graphics controller.</p></li> 10 11 <li> 11 <p>3D video acceleration isn't available on Arm hosts.</p> 12 </li> 12 <p>2D and 3D video acceleration isn't available on Arm hosts.</p> 13 </li> 14 <li><p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions are not available for Arm 15 host platforms. Therefore, features such as seamless windows and shared folders are not 16 available.</p></li> 13 17 <li><p>Unattended installation isn't available.</p></li> 14 18 <li><p>The following <b>System</b> page settings aren't available for Arm guests:</p> -
trunk/doc/manual/en_US/dita/topics/autologon_win.dita
r105938 r105939 58 58 </li> 59 59 <li> 60 <p><b outputclass="bold">Windows Vista, Windows 7, Windows 8, Windows 10 and Windows 11 guests.</b> The login subsystem does not support the so-called Secure Attention Sequence, <codeph>Ctrl+Alt+Del</codeph>. As a result, the guest's group policy settings need to be changed to not use the Secure Attention Sequence. Also, the user name given is only compared to the true user name, not the user friendly name. This means that when you rename a user, you still have to supply the original user name as Windows never renames user accounts internally. </p> 60 <p><b outputclass="bold">Windows Vista, Windows 7, Windows 8, 61 and Windows 10 guests.</b> The login subsystem does 62 not support the so-called Secure Attention Sequence, 63 <codeph>Ctrl+Alt+Del</codeph>. As a result, the guest's 64 group policy settings need to be changed to not use the 65 Secure Attention Sequence. Also, the user name given is only 66 compared to the true user name, not the user friendly name. 67 This means that when you rename a user, you still have to 68 supply the original user name as Windows never renames user 69 accounts internally. 70 </p> 61 71 </li> 62 72 <li> -
trunk/doc/manual/en_US/dita/topics/cloud-vm-control.dita
r105938 r105939 3 3 <topic xml:lang="en-us" id="cloud-vm-control"> 4 4 <title>Controlling a Cloud VM</title> 5 <!-- 7.1: OCI instance reset feature--> 5 6 <body> 6 7 <p>You can use <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> to control a cloud VM as follows: </p> -
trunk/doc/manual/en_US/dita/topics/cloud-vm-monitor.dita
r105938 r105939 3 3 <topic xml:lang="en-us" id="cloud-vm-monitor"> 4 4 <title>Monitoring Cloud VM Performance</title> 5 <!--7.1: OCI instance monitoring --> 5 6 <body> 6 7 <p>You can monitor the performance of cloud VM instances in the following ways:</p> -
trunk/doc/manual/en_US/dita/topics/create-optical-disk-image.dita
r105938 r105939 3 3 <topic xml:lang="en-us" id="create-optical-disk-image"> 4 4 <title>Creating a Virtual Optical Disk Image</title> 5 <!-- 7.1: Can now import VISO files--> 5 6 <body> 6 7 <p>Use the <b outputclass="bold">VISO Creator</b> tool to create a virtual optical disk image. This enables you to -
trunk/doc/manual/en_US/dita/topics/create-vm-wizard-name-os.dita
r105938 r105939 2 2 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> 3 3 <topic xml:lang="en-us" id="create-vm-wizard-name-os"> 4 <title>Specify Name and Operating System</title> 4 <title>Specify Name and Operating System</title> 5 <!--7.1: Subtype field added --> 5 6 <body> 6 7 <p> -
trunk/doc/manual/en_US/dita/topics/create-vm-wizard.dita
r105938 r105939 20 20 VM. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> does not supply the OS or any license required to use 21 21 it. </p> 22 <p><!--7.1: Note added re platforms and paragraph re ISO requirement. Reworded when removing screenshots. Subpages also updated.--></p> 22 23 </body> 23 24 </topic> -
trunk/doc/manual/en_US/dita/topics/features-overview.dita
r105938 r105939 11 11 <ul> 12 12 <li> 13 <p><b outputclass="bold">Portability. </b> 14 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> runs on a large number of 64-bit host operating systems. See <xref href="hostossupport.dita#hostossupport"/>. </p> 13 <p><b outputclass="bold">Portability.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 14 runs on a large number of 64-bit host operating systems. See 15 <xref href="hostossupport.dita#hostossupport"/>. 16 </p> 15 17 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> is a so-called <i>hosted</i> hypervisor, sometimes 16 18 referred to as a <i>type 2</i> hypervisor. Whereas a <i>bare-metal</i> or <i>type 1</i> hypervisor runs … … 50 52 <ul> 51 53 <li> 52 <p><b outputclass="bold">Guest multiprocessing (SMP). </b> 53 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can present up to 32 virtual CPUs to each virtual machine, irrespective of how many CPU cores are physically present on your host. </p> 54 <p><b outputclass="bold">Guest multiprocessing 55 (SMP).</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can present up to 32 56 virtual CPUs to each virtual machine, irrespective of how 57 many CPU cores are physically present on your host. 58 </p> 54 59 </li> 55 60 <li> 56 61 <p><b outputclass="bold">USB device support.</b> 57 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> implements a virtual USB controller and enables you to connect arbitrary USB devices to your virtual machines without having to install device-specific drivers on the host. USB support is not limited to certain device categories. See <xref href="settings-usb.dita#settings-usb"/>. </p> 62 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> implements a virtual USB controller and 63 enables you to connect arbitrary USB devices to your 64 virtual machines without having to install device-specific 65 drivers on the host. USB support is not limited to certain 66 device categories. See <xref href="settings-usb.dita#settings-usb"/>. 67 </p> 58 68 </li> 59 69 <li> 60 70 <p><b outputclass="bold">Hardware compatibility.</b> 61 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtualizes a vast array of virtual devices, among them many devices that are typically provided by other virtualization platforms. That includes IDE, SCSI, and SATA hard disk controllers, several virtual network cards and sound cards, virtual serial ports and an Input/Output Advanced Programmable Interrupt Controller (I/O APIC), which is found in many computer systems. This enables easy cloning of disk images from real machines and importing of third-party virtual machines into <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p> 71 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtualizes a vast array of 72 virtual devices, among them many devices that are typically provided by other 73 virtualization platforms. That includes IDE, SCSI, and SATA hard disk controllers, 74 several virtual network cards and sound cards, virtual serial ports and an 75 Input/Output Advanced Programmable Interrupt Controller (I/O APIC), which is found in 76 many computer systems. This enables easy cloning of disk images from real machines and 77 importing of third-party virtual machines into <ph 78 conkeyref="vbox-conkeyref-phrases/product-name"/>. </p> 62 79 </li> 63 80 <li> … … 77 94 <li> 78 95 <p><b outputclass="bold">Multiscreen resolutions.</b> 79 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtual machines support screen resolutions many times that of a physical screen, allowing them to be spread over a large number of screens attached to the host system. </p> 96 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtual machines support screen resolutions 97 many times that of a physical screen, allowing them to be 98 spread over a large number of screens attached to the host 99 system. 100 </p> 80 101 </li> 81 102 <li> … … 99 120 </li> 100 121 <li> 101 <p><b outputclass="bold">Multigeneration branched snapshots.</b> 102 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can save arbitrary snapshots of the state of the virtual machine. You can go back in time and revert the virtual machine to any such snapshot and start an alternative VM configuration from there, effectively creating a whole snapshot tree. See <xref href="snapshots.dita#snapshots"/>. You can create and delete snapshots while the virtual machine is running. </p> 122 <p><b outputclass="bold">Multigeneration branched 123 snapshots.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can save arbitrary 124 snapshots of the state of the virtual machine. You can go back 125 in time and revert the virtual machine to any such snapshot 126 and start an alternative VM configuration from there, 127 effectively creating a whole snapshot tree. See 128 <xref href="snapshots.dita#snapshots"/>. You can create and delete 129 snapshots while the virtual machine is running. 130 </p> 103 131 </li> 104 132 <li> 105 <p><b outputclass="bold">VM groups.</b> 106 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a groups feature that enables the user to organize and control virtual machines collectively, as well as individually. In addition to basic groups, it is also possible for any VM to be in more than one group, and for groups to be nested in a hierarchy. This means you can have groups of groups. In general, the operations that can be performed on groups are the same as those that can be applied to individual VMs: Start, Pause, Reset, Close (Save state, Send Shutdown, Poweroff), Discard Saved State, Show in File System, Sort. </p> 133 <p><b outputclass="bold">VM groups.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 134 provides a groups feature that enables the user to organize 135 and control virtual machines collectively, as well as 136 individually. In addition to basic groups, it is also possible 137 for any VM to be in more than one group, and for groups to be 138 nested in a hierarchy. This means you can have groups of 139 groups. In general, the operations that can be performed on 140 groups are the same as those that can be applied to individual 141 VMs: Start, Pause, Reset, Close (Save state, Send Shutdown, 142 Poweroff), Discard Saved State, Show in File System, Sort. 143 </p> 107 144 </li> 108 145 <li> 109 <p><b outputclass="bold">Clean architecture and unprecedented modularity.</b> 110 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has an extremely modular design with well-defined internal programming interfaces and a clean separation of client and server code. This makes it easy to control it from several interfaces at once. For example, you can start a VM simply by clicking on a button in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphical user interface and then control that machine from the command line, or even remotely. See <xref href="frontends.dita#frontends"/>. </p> 146 <p><b outputclass="bold">Clean architecture and unprecedented 147 modularity.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has an extremely modular 148 design with well-defined internal programming interfaces and a 149 clean separation of client and server code. This makes it easy 150 to control it from several interfaces at once. For example, 151 you can start a VM simply by clicking on a button in the 152 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphical user interface and then control that 153 machine from the command line, or even remotely. See 154 <xref href="frontends.dita#frontends"/>. 155 </p> 111 156 <p>Due to its modular architecture, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can also expose its 112 157 full functionality and configurability through a comprehensive <b outputclass="bold">software development kit -
trunk/doc/manual/en_US/dita/topics/frontends.dita
r105938 r105939 33 33 </li> 34 34 <li> 35 <!-- Separate mode: check with Klaus whether this needs to be covered in 7.1--> 35 36 <p><b>Separate mode.</b> A front end that is based on <userinput>VBoxHeadless</userinput>, 36 37 but does not require VRDE or an RDP viewer. See <xref href="vboxheadless-separate-mode.dita">Separate Mode</xref>.</p> -
trunk/doc/manual/en_US/dita/topics/guest-os-Arm.dita
r105938 r105939 1 1 <?xml version='1.0' encoding='UTF-8'?> 2 2 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> 3 <topic xml:lang="en-us" id="guest -os-arm">3 <topic xml:lang="en-us" id="guestossupport"> 4 4 <title>Arm Guest Operating Systems</title> 5 5 6 <body> 6 7 <p>Oracle Premier Support covers the running of the following guest OSs in a VM with an Arm platform architecture.</p> … … 19 20 </ul> 20 21 </p> 22 23 21 24 </body> 22 25 </topic> -
trunk/doc/manual/en_US/dita/topics/guest-os-legacy.dita
r105938 r105939 10 10 <p>The following legacy guest operating systems can be used with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, but only qualify for limited support because of the vintage of the technology involved. Therefore, resolution of customer issues for such legacy guest operating systems cannot be assured. </p> 11 11 <p>See also <xref href="host-guest-matrix.dita"/>.</p> 12 <p>VMs with an x86 or x86-64 platform architecture, as appropriate might run<ul id=" guest-os-other">12 <p>VMs with an x86 or x86-64 platform architecture, as appropriate might run<ul id="ul_j5n_srf_3cc"> 13 13 <li>Windows 8 and 8.1 (32-bit and 64-bit) </li> 14 14 <li>Windows 7 (32-bit and 64-bit) </li> -
trunk/doc/manual/en_US/dita/topics/guest-os-x86-64.dita
r105938 r105939 1 1 <?xml version='1.0' encoding='UTF-8'?> 2 2 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> 3 <topic xml:lang="en-us" id="guest -os-x86">3 <topic xml:lang="en-us" id="guestossupport"> 4 4 <title>x86 Guest Operating Systems</title> 5 5 6 <body> 6 7 <p>Oracle Premier Support covers the running of the following guest OSs in a VM with an x86 or x86-64 platform architecture, as appropriate.</p> -
trunk/doc/manual/en_US/dita/topics/guestadd-clipboard.dita
r105938 r105939 5 5 6 6 <body> 7 <!-- 7.1: Shared clipboard check box; clarify operation with dev --> 7 8 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to copy clipboard content from the host to the 8 9 guest, and vice versa. For this to work the latest version of the Guest Additions must be installed on the 9 guest.</p> 10 guest.</p> 10 11 <p>For security reasons drag and drop can be configured at runtime on a per-VM basis either using the <b 11 12 outputclass="bold">Shared Clipboard</b> menu item in the <b outputclass="bold">Devices</b> menu of the virtual -
trunk/doc/manual/en_US/dita/topics/guestadd-gc-file-manager.dita
r105938 r105939 3 3 <topic xml:lang="en-us" id="guestadd-gc-file-manager"> 4 4 <title>Guest Control File Manager</title> 5 <!-- 7.1: new icons added, pic removed--> 5 6 <body> 6 7 <p>If you have Guest Additions installed, you can use the Guest Control File Manager to copy files between a virtual -
trunk/doc/manual/en_US/dita/topics/guestadd-intro.dita
r105938 r105939 51 51 had manually entered an arbitrary resolution in the guest's <b outputclass="bold">Display</b> settings. See 52 52 <xref href="intro-resize-window.dita#intro-resize-window"/>. </p> 53 <p>If the Guest Additions are installed, 3D graphics for guest applications can be accelerated. See <xref href="guestadd-video.dita#guestadd-video"/>. </p> 53 <p>If the Guest Additions are installed, 3D graphics and 2D video for guest applications can be accelerated. See 54 <xref href="guestadd-video.dita#guestadd-video"/>. </p> 54 55 </li> 55 56 <li> -
trunk/doc/manual/en_US/dita/topics/gui-tools-global.dita
r105938 r105939 3 3 <topic xml:lang="en-us" id="gui-tools-global"> 4 4 <title>Global Tools</title> 5 <!-- This topic needs turned around to be global config tasks.-->5 <!-- 7.1: May be best to remove screen shots of menus. Too much of a maintenance headache. DONE. This topic needs turned around to be global config tasks.--> 6 6 <body> 7 7 <p>In the left pane of the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window, click the <b outputclass="bold" -
trunk/doc/manual/en_US/dita/topics/gui-vmgroups.dita
r105938 r105939 5 5 6 6 <body> 7 <!-- 7.1: pic removed--> 7 8 <p>Create VM groups if you want to manage several VMs together, and perform functions on them collectively, as well 8 9 as individually. </p> -
trunk/doc/manual/en_US/dita/topics/hostossupport.dita
r105938 r105939 3 3 <topic xml:lang="en-us" id="hostossupport"> 4 4 <title>Available Installation Packages</title> 5 <!-- 7.1: Arm platforms; require statement on host support --> 5 6 <body> 6 7 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> runs on the following host Operating Systems (OSs): </p> -
trunk/doc/manual/en_US/dita/topics/intro-macosxguests.dita
r105938 r105939 5 5 6 6 <body> 7 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to install and execute unmodified versions of macOS and OS X guests on supported host hardware. This feature is experimental and thus unsupported. </p>7 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to install and execute unmodified versions of macOS and OS X guests on supported host hardware. Note that this feature is experimental and thus unsupported. </p> 8 8 <p>Be aware of the following important issues before you try to install a macOS guest: </p> 9 9 <ul> -
trunk/doc/manual/en_US/dita/topics/log-viewer.dita
r105938 r105939 8 8 records system configuration and events. The <b outputclass="bold">Log Viewer</b> is a <ph 9 9 conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> tool that enables you to view and analyze system logs. </p> 10 <!-- 7.1: New pic required? Tab operation changed. Log Viewer/Filter pane. bugref:10496 11 Pic removed... still need to change/add anything?--> 10 12 <p>To display the Log Viewer, do either of the following: </p> 11 13 <ul> -
trunk/doc/manual/en_US/dita/topics/nichardware.dita
r105938 r105939 9 9 <ul> 10 10 <li> 11 <p>AMD PCNet PCI II (Am79C970A) Not available on Arm guests.</p>11 <p>AMD PCNet PCI II (Am79C970A) </p> 12 12 </li> 13 13 <li> 14 <p>AMD PCNet FAST III (Am79C973), the default setting on x86 guests. Not available on Arm guests.</p>14 <p>AMD PCNet FAST III (Am79C973), the default setting </p> 15 15 </li> 16 16 <li> -
trunk/doc/manual/en_US/dita/topics/seamlesswindows.dita
r105938 r105939 5 5 6 6 <body> 7 <p>With the <i>seamless windows</i> feature of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you can have the windows that are displayed within a virtual machine appear side by side next to the windows of your host. This feature is supported for the following x86 or x86_64guest operating systems, provided that the Guest Additions are installed: </p>7 <p>With the <i>seamless windows</i> feature of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you can have the windows that are displayed within a virtual machine appear side by side next to the windows of your host. This feature is supported for the following guest operating systems, provided that the Guest Additions are installed: </p> 8 8 <ul> 9 9 <li> -
trunk/doc/manual/en_US/dita/topics/security_clipboard.dita
r105938 r105939 3 3 <topic xml:lang="en-us" id="security_clipboard"> 4 4 <title>Clipboard</title> 5 <!-- 7.1: Shared clipboard toggle in guest VM, bugref:10481; input from dev required --> 5 6 <body> 6 7 <p>The shared clipboard enables users to share data between the host and the guest. Enabling the clipboard in -
trunk/doc/manual/en_US/dita/topics/settings-general-advanced.dita
r105938 r105939 32 32 using the <b outputclass="bold">Shared Clipboard</b> menu item in the <b outputclass="bold">Devices</b> menu 33 33 of the virtual machine. </p> 34 <!--7.1: r159813: checkbox added to the Shared Clipboard menu? --> 34 35 </li> 35 36 <li> … … 40 41 enable restricting of access in either direction. 41 42 </p> 42 <p>For drag and drop to work ,the Guest Additions need to be installed on the guest. </p>43 <p>For drag and drop to work the Guest Additions need to be installed on the guest. </p> 43 44 <note> 44 45 <p>Drag and drop is disabled by default. This setting can be changed at any time using the <b 45 46 outputclass="bold">Drag and Drop</b> menu item in the <b outputclass="bold">Devices</b> menu of the 46 47 virtual machine. </p> 47 <p>See <xref href="guestadd-dnd.dita#guestadd-dnd"/>. </p>48 48 </note> 49 <p>See <xref href="guestadd-dnd.dita#guestadd-dnd"/>. </p> 49 50 </li> 50 51 </ul> -
trunk/doc/manual/en_US/dita/topics/soft-keyb.dita
r105938 r105939 4 4 5 5 <topic xml:lang="en-us" id="soft-keyb"> 6 <!-- 7.1: pic removed--> 6 7 <title>Soft Keyboard</title> 7 8 <body> -
trunk/doc/manual/en_US/dita/topics/vbox-auth.dita
r105938 r105939 25 25 <ul> 26 26 <li> 27 <p>On Linux and Oracle Solarishosts, <userinput>VBoxAuth.so</userinput> authenticates users against the host's PAM system. </p>27 <p>On Linux hosts, <userinput>VBoxAuth.so</userinput> authenticates users against the host's PAM system. </p> 28 28 </li> 29 29 <li> -
trunk/doc/manual/en_US/dita/topics/vboxheadless-separate-mode.dita
r105938 r105939 4 4 <title>Separate Mode</title> 5 5 <body> 6 <!-- 7.1: Include this topic? Get feedback during doc review --> 6 7 <p>Separate mode is an alternative front end for local and remote virtual machines. Separate 7 8 mode is based on the <userinput>VBoxHeadless</userinput> front end but uses the <ph -
trunk/doc/manual/en_US/dita/topics/vboxmanage-intro.dita
r105938 r105939 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> 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> 9 13 <p>You will need to use the command line if you want to do the 10 14 following: … … 53 57 </li> 54 58 </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> 59 <p>You can enter <userinput>VBoxManage list vms</userinput> to have all currently registered VMs listed 60 with all their settings, including their respective names and UUIDs. </p> 56 61 <p>Some typical examples of how to control <ph conkeyref="vbox-conkeyref-phrases/product-name"/> from the 57 62 command line are listed below: </p> … … 61 66 conkeyref="vbox-conkeyref-phrases/product-name"/>, use <userinput>VBoxManage createvm</userinput> with the 62 67 <!--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. 68 <pre xml:space="preserve">$ VBoxManage createvm --name "SUSE 10.2" --register 69 VirtualBox Command Line Management Interface Version <varname>version-number</varname> 70 (C) 2005-2018 Oracle Corporation 71 All rights reserved. 72 73 Virtual machine 'SUSE 10.2' is created. 65 74 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> 75 Settings file: '/home/username/.config/VirtualBox/Machines/SUSE 10.2/SUSE 10.2.xml'</pre> 76 <p>As can be seen from the above output, a new virtual machine has been created with a new UUID and 77 a new XML settings file. </p> 68 78 <p> 69 79 For more details, see … … 86 96 See <xref href="vboxmanage-storagectl.dita"/> and <xref href="vboxmanage-storageattach.dita"/>. </p> 87 97 </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 98 <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> 99 <p>To control VM operation, use one of the following: </p> 100 <ul> 101 <li> 102 <p>To start a VM that is currently powered off, use <userinput>VBoxManage 103 startvm</userinput>. See <xref href="vboxmanage-startvm.dita"/>. </p> 104 </li> 105 <li> 106 <p>To pause or save a VM that is currently running or change some of its settings, use 107 <userinput>VBoxManage controlvm</userinput>. See <xref href="vboxmanage-controlvm.dita"/>. </p> 108 </li> 109 </ul> 93 110 </li> 94 111 </ul> -
trunk/doc/manual/en_US/dita/topics/virtintro.dita
r105938 r105939 20 20 </li> 21 21 <li> 22 <p><b outputclass="bold">Guest operating system (guest OS).</b> This is the OS that is running inside the virtual machine. Theoretically, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can run any x86 OS such as DOS, Windows, OS/2, FreeBSD, and OpenBSD on an x86 host. But to achieve near-native performance of the guest code on your machine, we had to go through a lot of optimizations that are specific to certain OSs. So while your favorite OS <i>may</i> run as a guest, we officially support and optimize for a select few, which include the most common OSs. </p> 23 <p>See <xref href="guest-os.dita"/>.</p> 22 <p><b outputclass="bold">Guest operating system (guest OS).</b> This is the OS that is running 23 inside the virtual machine. Theoretically, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can run any 24 x86 OS such as DOS, Windows, OS/2, FreeBSD, and OpenBSD. But to achieve near-native performance of the guest 25 code on your machine, we had to go through a lot of optimizations that are specific to certain OSes. So while 26 your favorite OS <i>may</i> run as a guest, we officially support and optimize for a select few, which include 27 the most common OSes. </p> 28 <p>See <xref href="guestossupport.dita#guestossupport"/>. </p> 24 29 </li> 25 30 <li> -
trunk/doc/manual/en_US/dita/topics/vm-activity-overview.dita
r105938 r105939 3 3 PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> 4 4 <topic xml:lang="en-us" id="vm-activity-overview"> 5 <!-- 7.1: Now shows activity info for cloud VMs --> 5 6 <title>VM Activity Overview</title> 6 7 <body> -
trunk/doc/manual/en_US/dita/topics/vm-activity-session-information.dita
r105938 r105939 4 4 <topic xml:lang="en-us" id="vm-activity-session-information"> 5 5 <title>Session Information Dialog</title> 6 <!-- 7.1: metrics info for OCI instances--> 7 <!-- 7.1: Add pic for cloud VM Activity info? No.. removing pics.--> 6 8 <body> 7 9 <p>The Session Information dialog includes multiple tabs that show important configuration and runtime -
trunk/doc/manual/en_US/dita/topics/vm-info.dita
r105938 r105939 3 3 PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> 4 4 <topic xml:lang="en-us" id="vm-info"> 5 <title>Monitoring of Virtual Machines</title> 5 <title>Monitoring of Virtual Machines</title> 6 <!-- 7.1: metrics info now included for OCI instances --> 6 7 <body> 7 8 <p><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> includes the following tools for viewing runtime -
trunk/doc/manual/en_US/dita/topics/vm-status-bar.dita
r105938 r105939 2 2 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> 3 3 <topic xml:lang="en-us" id="vm-status-bar"> 4 <title>Virtual Machine Status Bar</title> 4 <title>Virtual Machine Status Bar</title> 5 <!-- 7.1: Processor icon updated --> 5 6 <body> 6 7 <p>A status bar is displayed at the bottom of the virtual machine window. The status bar contains icons that enable
Note:
See TracChangeset
for help on using the changeset viewer.