Changeset 105619 in vbox
- Timestamp:
- Aug 8, 2024 8:58:42 AM (6 months ago)
- Location:
- trunk/doc/manual/en_US/dita/topics
- Files:
-
- 15 edited
-
Introduction.dita (modified) (1 diff)
-
KnownProblems.dita (modified) (7 diffs)
-
create-vm-wizard-name-os.dita (modified) (2 diffs)
-
create-vm-wizard-virtual-hard-disk.dita (modified) (2 diffs)
-
create-vm-wizard.dita (modified) (2 diffs)
-
guestadd-clipboard-limitations.dita (modified) (1 diff)
-
guestadd-clipboard.dita (modified) (1 diff)
-
guestadd-dnd-formats.dita (modified) (1 diff)
-
guestadd-dnd-limitations.dita (modified) (1 diff)
-
guestadd-dnd.dita (modified) (1 diff)
-
guestadd-gc-file-manager-using.dita (modified) (2 diffs)
-
guestadd-gc-file-manager.dita (modified) (1 diff)
-
security_clipboard.dita (modified) (1 diff)
-
virt-why-useful.dita (modified) (1 diff)
-
virtual-media-manager.dita (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/dita/topics/Introduction.dita
r105426 r105619 6 6 <body> 7 7 <p>Welcome to <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.</p> 8 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> is a cross-platform virtualization 9 application. What does that mean? For one thing, it installs on your existing Intel or 10 AMD-based computers, whether they are running Windows, macOS, Linux, or Oracle Solaris 11 operating systems (OSes). Second, it extends the capabilities of your existing computer so 12 that it can run multiple OSes, inside multiple virtual machines, at the same time. As an 13 example, you can run Windows and Linux on your Mac, run Windows Server on your Linux server, 14 run Linux on your Windows PC, and so on, all alongside your existing applications. You can 15 install and run as many virtual machines as you like. The only practical limits are disk space 16 and memory.</p> 8 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> is a cross-platform virtualization application. That means 9 it extends the capabilities of your existing computer so that it can run multiple operating systems, inside 10 multiple virtual machines (VMs), at the same time. As an example, you can run Windows and Linux on your Mac, run 11 Windows Server on your Linux server, run Linux on your Windows PC, and so on, all alongside your existing 12 applications. You can install and run as many virtual machines as you like. The only practical limits are disk 13 space and memory.</p> 17 14 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> is deceptively simple yet also very powerful. It can run 18 15 everywhere from small embedded systems or desktop class machines all the way up to data center deployments and -
trunk/doc/manual/en_US/dita/topics/KnownProblems.dita
r105303 r105619 5 5 6 6 <body> 7 <p> 8 The following section describes known problems with this release 9 of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. Unless marked otherwise, these issues are 10 planned to be fixed in later releases. 11 </p> 7 <p>The following section describes known problems with this release of <ph 8 conkeyref="vbox-conkeyref-phrases/product-name"/>. Unless marked otherwise, these issues are planned to be fixed 9 in later releases. </p> 12 10 <ul> 13 11 <li> 14 <p> 15 The macOS installer packages for <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7 currently do 16 not include the Internal Networking feature, which is 17 available on all other platforms. This will be addressed with 18 an update of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7. For setups which depend on this 19 functionality it is best to keep using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 6.1. 20 </p> 21 </li> 22 <li> 23 <p> 24 Poor performance when using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and 25 <b outputclass="bold">Hyper-V</b> on the same host. To 26 fix this, certain Windows features like "Hyper-V Platform", 27 "Virtual Machine Platform" and "Windows Hypervisor Platform" 28 must be turned off, followed by a host reboot. 29 </p> 30 <p> 31 Additionally, the Microsoft Device Guard and Credential Guard 32 hardware readiness tool might have to be used in order to turn 33 off more features. For example, by running the following 34 command: 35 </p> 12 <p>The macOS installer packages for <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7 currently do not 13 include the Internal Networking feature, which is available on all other platforms. This will be addressed 14 with an update of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7. For setups which depend on this 15 functionality it is best to keep using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 6.1. </p> 16 </li> 17 <li> 18 <p>Poor performance when using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and <b outputclass="bold" 19 >Hyper-V</b> on the same host. To fix this, certain Windows features like "Hyper-V Platform", "Virtual 20 Machine Platform" and "Windows Hypervisor Platform" must be turned off, followed by a host reboot. </p> 21 <p>Additionally, the Microsoft Device Guard and Credential Guard hardware readiness tool might have to be used 22 in order to turn off more features. For example, by running the following command: </p> 36 23 <pre xml:space="preserve">.\DG_Readiness_Tool_vX.X.ps1 -Disable -AutoReboot</pre> 37 24 <note> 38 <p> 39 Disabling Device Guard and Credential Guard features will 40 have an impact on the overall security of the host. Please 41 contact your Administrator beforehand regarding this. 42 </p> 25 <p>Disabling Device Guard and Credential Guard features will have an impact on the overall security of the 26 host. Please contact your Administrator beforehand regarding this. </p> 43 27 </note> 44 28 </li> … … 83 67 running is currently logged in and has a desktop session. 84 68 </p> 85 <p> 86 Also, to use accounts without or with an empty password, the 87 guest's group policy must be changed. To do so, open the group 88 policy editor on the command line by typing 89 <userinput>gpedit.msc</userinput>, open the key <codeph>Computer 90 Configuration\Windows Settings\Security Settings\Local 91 Policies\Security Options</codeph> and change the value of 92 <codeph>Accounts: Limit local account use of blank passwords 93 to console logon only</codeph> to Disabled. 94 </p> 69 <p>Also, to use accounts without or with an empty password, the guest's group policy must be changed. To do so, 70 open the group policy editor on the command line by typing <userinput>gpedit.msc</userinput>, open the key 71 <codeph>Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options</codeph> 72 and change the value of <codeph>Accounts: Limit local account use of blank passwords to console logon 73 only</codeph> to Disabled. </p> 95 74 </li> 96 75 <li> … … 105 84 </li> 106 85 <li> 107 <p> 108 <b outputclass="bold">OVF import/export:</b> 109 </p> 110 <ul> 111 <li> 112 <p> 113 OVF localization, with multiple languages in a single OVF 114 file, is not yet supported. 115 </p> 116 </li> 117 <li> 118 <p> 119 Some OVF sections like StartupSection, 120 DeploymentOptionSection, and InstallSection are ignored. 121 </p> 122 </li> 123 <li> 124 <p> 125 OVF environment documents, including their property 126 sections and appliance configuration with ISO images, are 127 not yet supported. 128 </p> 129 </li> 130 <li> 131 <p> 132 Remote files using HTTP or other mechanisms are not yet 133 supported. 134 </p> 135 </li> 136 </ul> 137 </li> 138 <li> 139 <p> 140 Neither <b outputclass="bold">scale mode</b> nor 141 <b outputclass="bold">seamless mode</b> work correctly 142 with guests using OpenGL 3D features, such as with 143 Compiz-enabled window managers. 144 </p> 145 </li> 146 <li> 147 <p> 148 The RDP server in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension pack supports 149 only audio streams in format 22.05kHz stereo 16-bit. If the 150 RDP client requests any other audio format there will be no 151 audio. 152 </p> 153 </li> 154 <li> 155 <p> 156 Preserving the aspect ratio in scale mode works only on 157 Windows hosts and on macOS hosts. 158 </p> 159 </li> 160 <li> 161 <p> 162 On <b outputclass="bold">macOS hosts</b>, the following 163 features are not yet implemented: 164 </p> 86 <p><b outputclass="bold">OVF import/export:</b> 87 </p> 88 <ul> 89 <li> 90 <p>OVF localization, with multiple languages in a single OVF file, is not yet supported. </p> 91 </li> 92 <li> 93 <p>Some OVF sections like StartupSection, DeploymentOptionSection, and InstallSection are ignored. </p> 94 </li> 95 <li> 96 <p>OVF environment documents, including their property sections and appliance configuration with ISO images, 97 are not yet supported. </p> 98 </li> 99 <li> 100 <p>Remote files using HTTP or other mechanisms are not yet supported. </p> 101 </li> 102 </ul> 103 </li> 104 <li> 105 <p>Neither <b outputclass="bold">scale mode</b> nor <b outputclass="bold">seamless mode</b> work correctly with 106 guests using OpenGL 3D features, such as with Compiz-enabled window managers. </p> 107 </li> 108 <li> 109 <p>The RDP server in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension pack supports only 110 audio streams in format 22.05kHz stereo 16-bit. If the RDP client requests any other audio format there will 111 be no audio. </p> 112 </li> 113 <li> 114 <p>Preserving the aspect ratio in scale mode works only on Windows hosts and on macOS hosts. </p> 115 </li> 116 <li> 117 <p>On <b outputclass="bold">macOS hosts</b>, the following features are not yet implemented: </p> 165 118 <ul> 166 119 <li> … … 182 135 </li> 183 136 <li> 184 <p> 185 <b outputclass="bold">macOS/Arm64 (Apple silicon) host package</b> 186 </p> 187 </li> 188 <li> 189 <p> 190 <b outputclass="bold">Mac OS X guests:</b> 191 </p> 192 <ul> 193 <li> 194 <p> 195 Mac OS X guests can only run on a certain host hardware. 196 For details about license and host hardware limitations. 197 See <xref href="intro-macosxguests.dita">Mac OS X Guests</xref> and check the 198 Apple software license conditions. 199 </p> 200 </li> 201 <li> 202 <p> 203 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> does not provide Guest Additions for Mac OS 204 X at this time. 205 </p> 206 </li> 207 <li> 208 <p> 209 The graphics resolution currently defaults to 1024x768 as 210 Mac OS X falls back to the built-in EFI display support. 211 See <xref href="efividmode.dita">Video Modes in EFI</xref> for more information on 212 how to change EFI video modes. 213 </p> 214 </li> 215 <li> 216 <p> 217 Mac OS X guests only work with one CPU assigned to the VM. 218 Support for SMP will be provided in a future release. 219 </p> 220 </li> 221 <li> 222 <p> 223 Depending on your system and version of Mac OS X, you 224 might experience guest hangs after some time. This can be 225 fixed by turning off energy saving. Set the timeout to 226 "Never" in the system preferences. 227 </p> 228 </li> 229 <li> 230 <p> 231 By default, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> EFI enables debug output of 232 the Mac OS X kernel to help you diagnose boot problems. 233 Note that there is a lot of output and not all errors are 234 fatal. They would also show when using a physical Apple 235 Macintosh computer. You can turn off these messages by 236 using the following command: 237 </p> 137 <p><b outputclass="bold">macOS/Arm 64 (Apple silicon) host package</b> 138 <ul id="ul_ddr_kzn_hcc"> 139 <li> 140 <p>x86-based guest operating systems will not run</p> 141 </li> 142 <li> 143 <p>Arm(AArch64) guests only. Arm 32 is not supported at present.</p> 144 </li> 145 <li> 146 <p>Arm hosts have limitations with sound, storage, graphics, guest additions and unattended 147 installation.</p> 148 </li> 149 </ul></p> 150 </li> 151 <li> 152 <p><b outputclass="bold">Mac OS X guests:</b> 153 </p> 154 <ul> 155 <li> 156 <p>Mac OS X guests can only run on a certain host hardware. For details about license and host hardware 157 limitations. See <xref href="intro-macosxguests.dita">Mac OS X Guests</xref> and check the Apple software 158 license conditions. </p> 159 </li> 160 <li> 161 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> does not provide Guest Additions for Mac OS X at 162 this time. </p> 163 </li> 164 <li> 165 <p>The graphics resolution currently defaults to 1024x768 as Mac OS X falls back to the built-in EFI display 166 support. See <xref href="efividmode.dita">Video Modes in EFI</xref> for more information on how to change 167 EFI video modes. </p> 168 </li> 169 <li> 170 <p>Mac OS X guests only work with one CPU assigned to the VM. Support for SMP will be provided in a future 171 release. </p> 172 </li> 173 <li> 174 <p>Depending on your system and version of Mac OS X, you might experience guest hangs after some time. This 175 can be fixed by turning off energy saving. Set the timeout to "Never" in the system preferences. </p> 176 </li> 177 <li> 178 <p>By default, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> EFI enables debug output of the Mac 179 OS X kernel to help you diagnose boot problems. Note that there is a lot of output and not all errors are 180 fatal. They would also show when using a physical Apple Macintosh computer. You can turn off these 181 messages by using the following command: </p> 238 182 <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> "VBoxInternal2/EfiBootArgs" " "</pre> 239 183 <p> … … 244 188 </li> 245 189 <li> 246 <p> 247 It is currently not possible to start a Mac OS X guest in 248 safe mode by specifying the <codeph>-x</codeph> option in 249 <codeph>VBoxInternal2/EfiBootArgs</codeph> extradata. 250 </p> 190 <p>It is currently not possible to start a Mac OS X guest in safe mode by specifying the <codeph>-x</codeph> 191 option in <codeph>VBoxInternal2/EfiBootArgs</codeph> extradata. </p> 251 192 </li> 252 193 </ul> … … 258 199 <ul> 259 200 <li> 260 <p> 261 USB support on Oracle Solaris hosts requires Oracle 262 Solaris 11 version snv_124 or later. Webcams and other 263 isochronous devices are known to have poor performance. 264 </p> 265 </li> 266 <li> 267 <p> 268 Host Webcam passthrough is restricted to 640x480 frames at 269 20 frames per second due to limitations in the Oracle 270 Solaris V4L2 API. This may be addressed in a future Oracle 271 Solaris release. 272 </p> 273 </li> 274 <li> 275 <p> 276 No ACPI information, such as battery status or power 277 source, is reported to the guest. 278 </p> 279 </li> 280 <li> 281 <p> 282 No support for using wireless adapters with bridged 283 networking. 284 </p> 285 </li> 286 <li> 287 <p> 288 Crossbow-based bridged networking on Oracle Solaris 11 289 hosts does not work directly with aggregate links. 290 However, you can use <userinput>dladm</userinput> to manually 291 create a VNIC over the aggregate link and use that with a 292 VM. This limitation does not exist in Oracle Solaris 11u1 293 build 17 and later. 294 </p> 295 </li> 296 </ul> 297 </li> 298 <li> 299 <p> 300 Neither virtio nor Intel PRO/1000 drivers for 301 <b outputclass="bold">Windows XP guests</b> support 302 segmentation offloading. Therefore Windows XP guests have 303 slower transmission rates comparing to other guest types. 304 Refer to MS Knowledge base article 842264 for additional 305 information. 306 </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 </li> 204 <li> 205 <p>Host Webcam passthrough is restricted to 640x480 frames at 20 frames per second due to limitations in the 206 Oracle Solaris V4L2 API. This may be addressed in a future Oracle Solaris release. </p> 207 </li> 208 <li> 209 <p>No ACPI information, such as battery status or power source, is reported to the guest. </p> 210 </li> 211 <li> 212 <p>No support for using wireless adapters with bridged networking. </p> 213 </li> 214 <li> 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> 218 </li> 219 </ul> 220 </li> 221 <li> 222 <p>Neither virtio nor Intel PRO/1000 drivers for <b outputclass="bold">Windows XP guests</b> support 223 segmentation offloading. Therefore Windows XP guests have slower transmission rates comparing to other guest 224 types. Refer to MS Knowledge base article 842264 for additional information. </p> 307 225 </li> 308 226 <li> … … 314 232 </li> 315 233 <li> 316 <p> 317 Some guest operating systems predating ATAPI CD-ROMs may 318 exhibit long delays or entirely fail to boot in certain 319 configurations. This is most likely to happen when an 320 IDE/ATAPI CD-ROM exists alone on a primary or secondary IDE 321 channel. 322 </p> 323 <p> 324 Affected operating systems are MS OS/2 1.21: fails to boot 325 with an error message referencing COUNTRY.SYS and MS OS/2 1.3: 326 long boot delays. To avoid such problems, disable the emulated 327 IDE/ATAPI CD-ROM. The guest OS cannot use this device, anyway. 328 </p> 234 <p>Some guest operating systems predating ATAPI CD-ROMs may exhibit long delays or entirely fail to boot in 235 certain configurations. This is most likely to happen when an IDE/ATAPI CD-ROM exists alone on a primary or 236 secondary IDE channel. </p> 237 <p>Affected operating systems are MS OS/2 1.21: fails to boot with an error message referencing COUNTRY.SYS and 238 MS OS/2 1.3: long boot delays. To avoid such problems, disable the emulated IDE/ATAPI CD-ROM. The guest OS 239 cannot use this device, anyway. </p> 329 240 </li> 330 241 </ul> -
trunk/doc/manual/en_US/dita/topics/create-vm-wizard-name-os.dita
r105134 r105619 16 16 snapshots feature. See also <xref href="vboxconfigdata-machine-folder.dita">The Machine 17 17 Folder</xref>.</li> 18 <li>Select the ISO image file for the operating system you intend to install on the new VM. 19 The image file can be used directly to install an OS on the new VM as part of an 20 unattended installation, or it can be attached to a DVD drive on the new VM.</li> 18 <li>Select the ISO image file for the operating system you intend to install on the new VM. The image file can 19 be used directly to install an OS on the new VM as part of an unattended installation, or it can be attached 20 to a DVD drive on the new VM. If the image contains more than one edition, select the edition you want to 21 use.</li> 21 22 <li><ph conkeyref="vbox-conkeyref-phrases/product-name"/> will populate the <b>Type</b>, 22 23 <b>Subtype</b>, and <b>Version</b> fields if it can detect the operating system in the … … 30 31 href="intro-64bitguests.dita#intro-64bitguests"/>) but you must always set this field 31 32 to the correct value.</p></li> 32 <li>By default, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will install the 33 chosen OS using the ISO image provided, if the image supports unattended installation. See 34 also <xref 35 href="create-vm-wizard-unattended-install.dita#create-vm-wizard-unattended-install" 36 />.<p>If you prefer to install the OS, you can disable the unattended guest operating 37 system install feature by selecting <b outputclass="bold">Skip Unattended 38 Installation</b>. In that case, the selected ISO image is mounted automatically on the 39 DVD drive of the new VM and you must install the OS from there.</p><p>Not all images 33 <li>By default, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will install the chosen OS using the ISO 34 image provided, if the image supports unattended installation. See also <xref 35 href="create-vm-wizard-unattended-install.dita#create-vm-wizard-unattended-install"/>.<p>If you prefer to 36 install the OS manually, you can disable the unattended guest operating system install feature by selecting 37 <b outputclass="bold">Skip Unattended Installation</b>. In that case, the selected ISO image is mounted 38 automatically on the DVD drive of the new VM and you must install the OS from there.</p><p>Not all images 40 39 support unattended installation.</p></li> 41 40 <li>Click Next to <xref -
trunk/doc/manual/en_US/dita/topics/create-vm-wizard-virtual-hard-disk.dita
r105335 r105619 67 67 <title>Use an Existing Virtual Hard Disk</title> 68 68 </section> 69 <p>Follow these steps to use a virtual hard disk that already exists on the host. Ensure the 70 image file is in a suitable location (usually the machine folder) and not in use by other71 VMs.<ol id="ol_txk_str_pbc">69 <p>Follow these steps to use a virtual hard disk that already exists on the host. Ensure the image file is in a 70 suitable location (usually the machine folder) and not in use by other VMs.<note id="note_fzl_3tw_hcc" 71 type="caution">Data on the disk image may be deleted.</note><ol id="ol_txk_str_pbc"> 72 72 <li> 73 73 <p>Select <b outputclass="bold">Use an Existing Virtual Hard Disk File</b> … … 75 75 </li> 76 76 <li> 77 <p>Select the image file to use with the new VM, and then click <b outputclass="bold" 78 >Add</b>. </p> 77 <p>Select the image file to use with the new VM, and then click <b outputclass="bold">Add</b>. </p> 79 78 </li> 80 79 </ol></p> -
trunk/doc/manual/en_US/dita/topics/create-vm-wizard.dita
r105498 r105619 14 14 <li><xref href="create-vm-wizard-virtual-hard-disk.dita"/></li> 15 15 </ul></p> 16 <p>If you don't see the wizard, change the experience level to <b>Basic</b>. See <xref 17 href="ui-experience-level.dita"/>.</p> 16 18 <p>Once created, the virtual machine is displayed in the machine list on the left side of the 17 19 <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window, with the name that you entered on … … 19 21 <p>You can change the settings later, after you have created the VM, using the Machine 20 22 Settings.</p> 21 <p> Before you start you must have an operating system image, in ISO format, for the operating22 system you intend to install on the VM. <ph conkeyref="vbox-conkeyref-phrases/product-name"/>23 does not supply the OS or any license required to useit. </p>23 <p>You must supply an operating system image, in ISO format, for the operating system you intend to install on the 24 VM. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> does not supply the OS or any license required to use 25 it. </p> 24 26 <p><!--7.1: Note added re platforms and paragraph re ISO requirement. Reworded when removing screenshots. Subpages also updated.--></p> 25 27 <note> -
trunk/doc/manual/en_US/dita/topics/guestadd-clipboard-limitations.dita
r100417 r105619 5 5 6 6 <body> 7 <p> 8 The following limitations are known for Shared Clipboard file transfers: 9 </p> 10 <p> 11 On Linux hosts and guests, Shared Clipboard file transfers are currently limited to files only, 12 one file per transfer. Transferring symbolic links are also not supported. 13 </p> 7 <p>The following limitations are known for Shared Clipboard file transfers: </p> 8 <p>On Linux hosts and guests, Shared Clipboard file transfers are currently limited to files only, one file per 9 transfer. Transferring symbolic links is not supported. </p> 14 10 </body> 15 11 -
trunk/doc/manual/en_US/dita/topics/guestadd-clipboard.dita
r105335 r105619 9 9 guest, and vice versa. For this to work the latest version of the Guest Additions must be installed on the 10 10 guest.</p> 11 <p>For security reasons drag and drop can be configured at runtime on a per-VM basis either using the <b 12 outputclass="bold">Shared Clipboard</b> menu item in the <b outputclass="bold">Devices</b> menu of the virtual 13 machine, or the <userinput>VBoxManage</userinput> command. </p> 14 <p>The following shared clipboard settings are available: </p> 15 <ul id="ul_onq_r24_hcc"> 16 <li> 17 <p><b outputclass="bold">Disabled</b>. Disables the copy feature entirely. This is the default when creating a 18 new VM. </p> 19 </li> 20 <li> 21 <p><b outputclass="bold">Host To Guest</b>. Enables text copy operations from the host to the guest only. </p> 22 </li> 23 <li> 24 <p><b outputclass="bold">Guest To Host</b>. Enables text copy operations from the guest to the host only. </p> 25 </li> 26 <li> 27 <p><b outputclass="bold">Bidirectional</b>. Enables text copy operations in both directions: from the host to 28 the guest, and from the guest to the host. </p> 29 </li> 30 <li><b>Enable Clipboard File Transfers</b>. Allows files, in addition to text, to be copied to or from the VM. 31 </li> 32 </ul> 11 33 <p>To use the <userinput>VBoxManage</userinput> command to control the current clipboard mode, see <xref 12 34 href="vboxmanage.dita#vboxmanage"/>. The <userinput>modifyvm</userinput> and <userinput>controlvm</userinput> -
trunk/doc/manual/en_US/dita/topics/guestadd-dnd-formats.dita
r99797 r105619 5 5 6 6 <body> 7 <p> 8 As <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can run on a variety of host operating systems 9 and also supports a wide range of guests, certain data formats 10 must be translated after transfer. This is so that the 11 destination operating system, which receives the data, is able 12 to handle them in an appropriate manner. 13 </p> 7 <p>As <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can run on a variety of host operating systems and also 8 supports a wide range of guests, certain data formats must be translated after transfer. This is so that the 9 destination operating system, which receives the data, is able to handle them in an appropriate manner. </p> 14 10 <note> 15 <p> 16 When dragging files no data conversion is done in any way. For 17 example, when transferring a file from a Linux guest to a 18 Windows host the Linux-specific line endings are not converted 19 to Windows line endings. 20 </p> 11 <p>When dragging files no data conversion is done in any way. For example, when transferring a file from a Linux 12 guest to a Windows host the Linux-specific line endings are not converted to Windows line endings. </p> 21 13 </note> 22 <p> 23 The following formats are handled by the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> drag and 24 drop service: 25 </p> 14 <p>The following formats are handled by the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> drag and drop 15 service: </p> 26 16 <ul> 27 17 <li> -
trunk/doc/manual/en_US/dita/topics/guestadd-dnd-limitations.dita
r99797 r105619 5 5 6 6 <body> 7 <p> 8 The following limitations are known for drag and drop: 9 </p> 10 <p> 11 On Windows hosts, dragging and dropping content between 12 UAC-elevated (User Account Control) programs and 13 non-UAC-elevated programs is not allowed. If you start 14 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with Administrator privileges then drag and drop 15 will not work with Windows Explorer, which runs with regular 16 user privileges by default. 17 </p> 18 <p> 19 On Linux hosts and guests, programs can query for drag and drop 20 data while the drag operation is still in progress. For example, 21 on LXDE using the PCManFM file manager. This currently is not 22 supported. As a workaround, a different file manager, such as 23 Nautilus, can be used instead. 24 </p> 7 <p>The following limitations are known for drag and drop: </p> 8 <p>On Windows hosts, dragging and dropping content between UAC-elevated (User Account Control) programs and 9 non-UAC-elevated programs is not allowed. If you start <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with 10 Administrator privileges then drag and drop will not work with Windows Explorer, which runs with regular user 11 privileges by default. </p> 12 <p>On Linux hosts and guests, programs can query for drag and drop data while the drag operation is still in 13 progress. For example, on LXDE using the PCManFM file manager. This currently is not supported. As a workaround, a 14 different file manager, such as Nautilus, can be used instead. </p> 25 15 </body> 26 16 -
trunk/doc/manual/en_US/dita/topics/guestadd-dnd.dita
r105618 r105619 27 27 <p>For security reasons drag and drop can be configured at runtime on a per-VM basis either using the <b 28 28 outputclass="bold">Drag and Drop</b> menu item in the <b outputclass="bold">Devices</b> menu of the virtual 29 machine, as shown below,or the <userinput>VBoxManage</userinput> command. </p>29 machine, or the <userinput>VBoxManage</userinput> command. </p> 30 30 <p>The following drag and drop modes are available: </p> 31 31 <ul> -
trunk/doc/manual/en_US/dita/topics/guestadd-gc-file-manager-using.dita
r105618 r105619 7 7 <p>To use the Guest Control File Manager to transfer files, follow these steps. </p> 8 8 <ol> 9 <li>Ensure you have the username and password for an account on the guest system, with appropriate permissions on 10 the files you need to access.</li> 9 11 <li> 10 12 <p>Open the Guest Control File Manager. Do either of the following: </p> … … 22 24 </li> 23 25 </ul> 24 <p> 25 The left pane shows the files on the host system. 26 </p> 26 <p>The <b>Host File System</b> pane shows the files on the host system. </p> 27 27 </li> 28 28 <li> 29 <p>In the Guest Control File Manager, enter authentication credentials for a user on the guest system. </p> 30 <p>Click <b outputclass="bold">Create Session</b>. </p> 31 <p>The contents of the guest VM file system appears in the right pane of the Guest Control File Manager. </p> 29 <p>In the <b>Guest File System</b> pane, enter the <b>User Name</b> and <b>Password</b> for the user you want to 30 log in as. </p> 31 <p>Click <b outputclass="bold">Open Session</b>. </p> 32 <p>The contents of the guest VM file system appears in the <b>Guest File System</b> pane. </p> 32 33 </li> 33 34 <li> -
trunk/doc/manual/en_US/dita/topics/guestadd-gc-file-manager.dita
r105618 r105619 5 5 <!-- 7.1: new icons added, pic removed--> 6 6 <body> 7 <p> The Guest Control File Manager is a feature of the Guest Additions that enables easy copying and moving of files8 between a guest and the host system. Other file management operations provide support to create new folders and to9 rename ordelete files. </p>7 <p>If you have Guest Additions installed, you can use the Guest Control File Manager to copy files between a guest 8 and the host system. Other file management operations provide support to create new folders and to rename or 9 delete files. </p> 10 10 <p>This feature is useful when the VM window of a guest is not visible. For example, when the guest is running in 11 11 headless mode. </p> -
trunk/doc/manual/en_US/dita/topics/security_clipboard.dita
r105134 r105619 5 5 <!-- 7.1: Shared clipboard toggle in guest VM, bugref:10481; input from dev required --> 6 6 <body> 7 <p> 8 The shared clipboard enables users to share data between the 9 host and the guest. Enabling the clipboard in Bidirectional 10 mode enables the guest to read and write the host clipboard. 11 The Host to Guest mode and the Guest to Host mode limit the 12 access to one direction. If the guest is able to access the 13 host clipboard it can also potentially access sensitive data 14 from the host which is shared over the clipboard. 15 </p> 16 <p> If the guest is able to read from or write to the host clipboard then a remote user 17 connecting to the guest over the network will also gain this ability, which may not be 18 appropriate. As a consequence, the shared clipboard is disabled for new machines. </p> 7 <p>The shared clipboard enables users to share data between the host and the guest. Enabling the clipboard in 8 Bidirectional mode enables the guest to read and write the host clipboard. The Host to Guest mode and the Guest to 9 Host mode limit the access to one direction. If the guest is able to access the host clipboard it can also 10 potentially access sensitive data from the host which is shared over the clipboard. </p> 11 <p>If the guest is able to read from or write to the host clipboard then a remote user connecting to the guest over 12 the network will also gain this ability, which may not be appropriate. As a consequence, the shared clipboard is 13 disabled for new machines. </p> 19 14 </body> 20 15 -
trunk/doc/manual/en_US/dita/topics/virt-why-useful.dita
r105303 r105619 6 6 7 7 <body> 8 <p> 9 The techniques and features that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides are 10 useful in the following scenarios: 11 </p> 8 <p>The techniques and features that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides are 9 useful in the following scenarios: </p> 12 10 <ul> 13 11 <li> -
trunk/doc/manual/en_US/dita/topics/virtual-media-manager.dita
r105618 r105619 25 25 <ul> 26 26 <li> 27 <p> 28 Hard disk images, either in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s own Virtual Disk 29 Image (VDI) format, or in the third-party formats listed in 30 <xref href="vdidetails.dita#vdidetails"/>. 31 </p> 27 <p>Hard disk images, either in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s own Virtual 28 Disk Image (VDI) format, or in the third-party formats listed in <xref href="vdidetails.dita#vdidetails" 29 />. </p> 32 30 </li> 33 31 <li> 34 <p> 35 CD/DVD images in standard ISO format. 36 </p> 32 <p>CD/DVD images in standard ISO format. </p> 37 33 </li> 38 34 <li> 39 <p> 40 Floppy images in standard RAW format. 41 </p> 35 <p>Floppy images in standard RAW format. </p> 42 36 </li> 43 37 </ul> … … 96 90 released from the VMs they are attached to and removed from the known media. </p> 97 91 <note> 98 <p> 99 This option is for optical disks and floppy disks only. 100 </p> 92 <p>This option is for optical disks and floppy disks only. </p> 101 93 </note> 102 94 </li>
Note:
See TracChangeset
for help on using the changeset viewer.
