Only in doc/manual/en_US/images: dnd-modes.png
diff -wrud doc/manual/en_US/user_AdvancedTopics.xml ../branches/VBox-4.3/doc/manual/en_US/user_AdvancedTopics.xml
--- doc/manual/en_US/user_AdvancedTopics.xml 2014-04-11 17:29:11.149166619 +0200
+++ ../branches/VBox-4.3/doc/manual/en_US/user_AdvancedTopics.xml 2014-04-23 13:47:48.665996755 +0200
@@ -943,7 +943,7 @@
- Linux and Solaris hosts
+ Linux hosts
When the webcam is detached from the host the emulated webcam device is
automatically detached from the guest only if the webcam is streaming video.
@@ -3467,4 +3467,36 @@
+
+ Experimental support for passing through SSE4.1 / SSE4.2 instructions
+
+ To provide SSE 4.1 / SSE 4.2 support to guests, the host CPU has to
+ implement these instruction sets. Starting with VirtualBox 4.3.8 it is
+ possible to enable these instructions for certain guests using the
+ following commands:VBoxManage setextradata "VM name" VBoxInternal/CPUM/SSE4.1 1
+VBoxManage setextradata "VM name" VBoxInternal/CPUM/SSE4.2 1
+
+ These are a per-VM settings and they are turned off by default.
+
+
+
+
+ Support for keyboard indicators synchronization
+
+
+ This feature makes the host keyboard lights match those of the virtual machine's virtual
+ keyboard when the machine window is selected. It is currently implemented for Mac OS X and
+ Windows hosts and available as of releases 4.2.24 and 4.3.8. The feature can be enabled using
+ the following command:
+
+
+ VBoxManage setextradata "VM name" GUI/HidLedsSync "1"
+
+
+ In order to disable it, use the same command but change "1" to "0", or use the VBoxManage
+ command to remove the extra data. This is a per-VM setting and it is disabled by default.
+
+
+
+
diff -wrud doc/manual/en_US/user_BasicConcepts.xml ../branches/VBox-4.3/doc/manual/en_US/user_BasicConcepts.xml
--- doc/manual/en_US/user_BasicConcepts.xml 2014-05-19 09:37:23.687566268 +0200
+++ ../branches/VBox-4.3/doc/manual/en_US/user_BasicConcepts.xml 2014-05-19 16:23:40.888190446 +0200
@@ -369,7 +369,7 @@
- Snapshot Folder
+ Snapshot folder
By default, VirtualBox saves snapshot data together with
@@ -380,7 +380,7 @@
- Shared Clipboard
+ Shared clipboard
You can select here whether the clipboard of the guest
@@ -405,35 +405,29 @@
Drag'n'Drop
- This setting allows to enable support for drag'n drop: Select
- an object (e.g. a file) from the host or guest and directly copy
- or open it on the guest or host. Multiple per-VM drag'n drop modes
- allow restricting access in either direction.
-
- For drag'n drop to work the Guest Additions need to be
- installed on the guest.
-
- Drag'n drop is disabled by default. This setting can be
- changed at any time using the "Drag'n'Drop" menu item in the
- "Devices" menu of the virtual machine.
-
- See for more information.
-
- Experimental support for drag and drop was added
- with VirtualBox 4.2.
+ This setting allows to enable Drag and Drop: Select a file
+ on the desktop, click the left mouse button, move the mouse
+ to the VM window and release the mouse button. The file is
+ copied from the host to the guest. This feature is currently
+ only implemented for Linux guests and only for copying files
+ from the host to the guest.Support
+ for Drag'n'Drop was added with VirtualBox 4.2
- Removable Media
+ Removable media: remember runtime changes
+
If this is checked, VirtualBox will save the state of what
- media has been mounted between several runs of a virtual machine.
+ media has been mounted between several runs of a virtual
+ machine.
- Mini ToolBar
+ Mini toolbar
+
In full screen or seamless mode, VirtualBox can display a
small toolbar that contains some of the items that are normally
diff -wrud doc/manual/en_US/user_GuestAdditions.xml ../branches/VBox-4.3/doc/manual/en_US/user_GuestAdditions.xml
--- doc/manual/en_US/user_GuestAdditions.xml 2014-05-19 09:37:23.679566268 +0200
+++ ../branches/VBox-4.3/doc/manual/en_US/user_GuestAdditions.xml 2014-05-19 16:23:40.884190446 +0200
@@ -1079,14 +1079,6 @@
Currently only Linux and Solaris Guest Additions support
symlinks.
-
-
- For security reasons the guest OS is not allowed to create
- symlinks by default. If you trust the guest OS to not abuse the
- functionality, you can enable creation of symlinks for "sharename"
- with:
- VBoxManage setextradata "VM name" VBoxInternal2/SharedFoldersEnableSymlinksCreate/sharename 1
-
@@ -1247,110 +1239,6 @@
-
- Drag'n Drop
-
- Starting with version 4.4, VirtualBox supports to drag'n drop content
- from the host to the guest and vice versa. For this to work the latest Guest
- Additions must be installed on the guest.
-
- Drag'n drop transparently allows copying or opening files, directories
- and even certain clipboard formats from one end to the other, e.g. from the
- host to the guest or from the guest to the host. One then can perform drag'n
- drop operations between the host and a VM as it would be a native drag'n drop
- operation on the host OS.
-
- At the moment drag'n drop is implemented for Windows- and X-Windows-based
- systems, both, on host and guest side. As X-Windows sports different drag'n drop
- protocols only the most used one, XDND, is supported for now. Applications using
- other protocols (such as Motif or OffiX) will not be recognized by VirtualBox.
-
- In context of using drag'n drop the origin of the data is called
- source, that is, where the actual data comes
- from and is specified. On the other hand there is the
- target, which specifies where the data from
- the source should go to. Transferring data from the source to the target can
- be done in various ways, e.g. copying, moving or linking.At
- the moment only copying of data is supported. Moving or linking is not yet
- implemented.
-
- When transferring data from the host to the guest OS, the host in this
- case is the source, whereas the guest OS is the target. However, when doing
- it the other way around, that is, transferring data from the guest OS to the
- host, the guest OS this time became the source and the host is the target.
-
- For security reasons drag'n drop can be configured at runtime
- on a per-VM basis either using the "Drag'n'Drop" menu item in the "Devices" menu
- of the virtual machine or VBoxManage: The following four modes are available:
-
-
-
-
-
-
-
-
-
- Disabled disables the drag'n drop
- entirely. This is the default when creating new VMs.
-
-
- Host To Guest enables performing
- drag'n drop operations from the host to the guest only.
-
-
- Guest To Host enables performing
- drag'n drop operations from the guest to the host only.
-
-
- Bidirectional enables performing
- drag'n drop operations to both directions, e.g. from the host to the guest
- and vice versa.
-
-
-
- Drag'n drop support depends on the frontend being used; at the
- moment only the VirtualBox Manager frontend provides this
- functionality.
-
- To use VBoxManage for controlling the current drag'n drop mode, see . The commands modifyvm
- and controlvm allow setting the VM's current
- drag'n drop mode via command line.
-
-
- Supported formats
-
- As VirtualBox can run on a variety of host OSes and also supports a wide
- range of guests, certain data formats must be translated after those
- got transfered over so that the target OS (that is, the side which receiving the
- data) is able to handle them in an appropriate manner.
-
- When dragging files however, no data conversion is done in any way, e.g.
- when transferring a file from a Linux guest to a Windows host the Linux-specific
- line endings won't be converted to Windows ones.
-
- The following formats are handled by the VirtualBox drag'n drop service:
-
-
- Plain text, from applications such as
- text editors, internet browsers and terminal windows
-
-
- Files, from file managers such
- as Windows explorer, Nautilus and Finder
-
-
- Directories, where the same applies
- as for files
-
-
-
-
-
-
-
Hardware-accelerated graphics
diff -wrud doc/manual/en_US/user_Installation.xml ../branches/VBox-4.3/doc/manual/en_US/user_Installation.xml
--- doc/manual/en_US/user_Installation.xml 2013-12-12 12:10:24.371210371 +0100
+++ ../branches/VBox-4.3/doc/manual/en_US/user_Installation.xml 2013-10-16 10:44:59.299988346 +0200
@@ -825,6 +825,11 @@
Configuring a zone for running VirtualBox
+ Starting with VirtualBox 1.6 it is possible to run VirtualBox from
+ within Solaris zones. For an introduction of Solaris zones, please refer
+ to http://www.sun.com/bigadmin/features/articles/solaris_zones.jsp.
+
Assuming that VirtualBox has already been installed into your
zone, you need to give the zone access to VirtualBox's device node. This
is done by performing the following steps. Start a root terminal and
@@ -832,9 +837,6 @@
zonecfg -z vboxzone
- Replace "vboxzone" with the name of the zone in which you intend
- to run VirtualBox.
-
Inside the zonecfg prompt add the
device resource and
match properties to the zone. Here's
@@ -843,18 +845,19 @@
zonecfg:vboxzone>add device
zonecfg:vboxzone:device>set match=/dev/vboxdrv
zonecfg:vboxzone:device>end
-zonecfg:vboxzone>add device
-zonecfg:vboxzone:device>set match=/dev/vboxdrvu
-zonecfg:vboxzone:device>end
+zonecfg:vboxzone>verify
zonecfg:vboxzone>exit
If you are running VirtualBox 2.2.0 or above on Solaris 11 or
- above, you may add a device for /dev/vboxusbmon
- too, similar to what was shown above. This does not apply to Solaris 10
- hosts due to lack of USB support.
+ Nevada hosts, you should add a device for
+ /dev/vboxusbmon too, similar to what
+ was shown above. This does not apply to Solaris 10 hosts due to lack of
+ USB support.
- Next reboot the zone using zoneadm
- and you should be able to run VirtualBox from within the configured zone.
+ Replace "vboxzone" with the name of the zone in which you intend
+ to run VirtualBox. Next reboot the zone using
+ zoneadm and you should be able to run
+ VirtualBox from within the configured zone.
diff -wrud doc/manual/en_US/user_KnownIssues.xml ../branches/VBox-4.3/doc/manual/en_US/user_KnownIssues.xml
--- doc/manual/en_US/user_KnownIssues.xml 2014-05-19 09:37:23.679566268 +0200
+++ ../branches/VBox-4.3/doc/manual/en_US/user_KnownIssues.xml 2014-05-19 16:23:40.884190446 +0200
@@ -75,6 +75,13 @@
+ 64-bit guests on some 32-bit host systems
+ with VT-x can cause instabilities to your system. If you
+ experience this, do not attempt to execute 64-bit guests. Refer to the
+ VirtualBox user forum for additional information.
+
+
+
NX (no execute, data execution
prevention) only works for guests running on 64-bit hosts
or guests running on 32-bit hosts with PAE enabled and requires that
@@ -247,12 +254,6 @@
- Host Webcam passthrough is restricted to 640x480 frames at
- 20 frames per second due to limitations in the Solaris V4L2 API.
- This may be addressed in a future Solaris release.
-
-
-
No ACPI information (battery status, power source) is
reported to the guest.
@@ -266,8 +267,8 @@
Crossbow-based bridged networking on Solaris 11 hosts does
not work directly with aggregate links. However, you can manually
create a VNIC (using dladm) over
- the aggregate link and use that with a VM. This limitation does
- not exist in Solaris 11u1 build 17 and newer.
+ the aggregate link and use that with a VM. This technical
+ limitation will be addressed in a future Solaris 11 release.
Only in doc/manual/en_US/: UserManual.asciidoc
Only in doc/manual/en_US/: user_Networking.xml~
diff -wrud doc/manual/en_US/user_VBoxManage.xml ../branches/VBox-4.3/doc/manual/en_US/user_VBoxManage.xml
--- doc/manual/en_US/user_VBoxManage.xml 2014-05-19 09:37:23.679566268 +0200
+++ ../branches/VBox-4.3/doc/manual/en_US/user_VBoxManage.xml 2014-03-31 10:41:28.006445347 +0200
@@ -98,7 +98,7 @@
To change settings while a VM is powered off, use
VBoxManage modifyvm, e.g. as
- follows:VBoxManage modifyvm "Windows XP" --memory 512
+ follows:VBoxManage modifyvm "Windows XP" --memory "512MB"
For details, see .
@@ -937,10 +937,9 @@
- Miscellaneous settings
+ Serial port, audio, clipboard and USB settings
- The following other hardware settings, such as serial port, audio,
- clipboard, drag'n drop, monitor and USB settings are available through
+ The following other hardware settings are available through
VBoxManage modifyvm:
--uart<1-N> off|<I/O base>
@@ -1008,18 +1007,9 @@
--clipboard
disabled|hosttoguest|guesttohost|bidirectional:
- With this setting, you can select if and how the guest or host
- operating system's clipboard should be shared with the host or guest;
- see . This requires that the Guest
- Additions be installed in the virtual machine.
-
-
-
- --draganddrop
- disabled|hosttoguest|guesttohost|bidirectional:
- With this setting, you can select the current drag'n drop mode
- being used between the host and the virtual machine;
- see . This requires that the Guest
+ With this setting, you can select whether the guest operating
+ system's clipboard should be shared with the host; see . This requires that the Guest
Additions be installed in the virtual machine.
@@ -1041,8 +1031,6 @@
see for details.
-
-
@@ -1060,8 +1048,6 @@
default.
-
-
--vrdeport
default|<ports>: A port or a range of ports
@@ -1523,8 +1509,6 @@
VM's running state:
-
-
The setlinkstate<1-N>
operation connects or disconnects virtual network cables from their
@@ -1549,43 +1533,6 @@
- With the "nictrace" options, you can optionally trace
- network traffic by dumping it to a file, for debugging
- purposes.
-
- With --nictrace<1-N>
- on|off, you can enable network tracing for a
- particular virtual network card.
-
- If enabled, you must specify with
- --nictracefile<1-N>
- <filename> what file the trace should be
- logged to.
-
-
-
-
-
- nicproperty<1-N>
- <paramname>="paramvalue":
- This option, in combination with "nicgenericdrv" allows you to
- pass parameters to rarely-used network backends.
- Those parameters are backend engine-specific, and are different
- between UDP Tunnel and the VDE backend drivers. For example,
- please see .
-
-
-
-
- The guestmemoryballoon
- operation changes the size of the guest memory balloon, that is,
- memory allocated by the VirtualBox Guest Additions from the guest
- operating system and returned to the hypervisor for re-use by other
- virtual machines. This must be specified in megabytes. For details,
- see .
-
-
-
usbattach and
usbdettach make host USB devices
visible to the virtual machine on the fly, without the need for
@@ -1597,24 +1544,6 @@
- clipboard
- disabled|hosttoguest|guesttohost|bidirectional:
- With this setting, you can select if and how the guest or host
- operating system's clipboard should be shared with the host or guest;
- see . This requires that the Guest
- Additions be installed in the virtual machine.
-
-
-
- draganddrop
- disabled|hosttoguest|guesttohost|bidirectional:
- With this setting, you can select the current drag'n drop mode
- being used between the host and the virtual machine;
- see . This requires that the Guest
- Additions be installed in the virtual machine.
-
-
-
vrde on|off lets you enable or
disable the VRDE server, if it is installed.
@@ -1628,7 +1557,6 @@
linkend="vboxmanage-modifyvm-other" />.
-
setvideomodehint requests that
the guest system change to a particular video mode. This requires that
@@ -1641,23 +1569,19 @@
of the guest display and saves it in PNG format.
-
-
The setcredentials operation is
used for remote logons in Windows guests. For details, please refer to
.
-
-
- --plugcpu|unplugcpu
- <id>: If CPU hot-plugging is enabled, this adds
- a virtual CPU to the virtual machines (or removes one).
- <id> specifies the index of
- the virtual CPU to be added or removed and must be a number from 0
- to the maximum no. of CPUs configured. CPU 0 can never be removed.
+ The guestmemoryballoon
+ operation changes the size of the guest memory balloon, that is,
+ memory allocated by the VirtualBox Guest Additions from the guest
+ operating system and returned to the hypervisor for re-use by other
+ virtual machines. This must be specified in megabytes. For details,
+ see .
@@ -1666,9 +1590,6 @@
time a virtual CPU can use. A value of 50 implies a single virtual CPU
can use up to 50% of a single host CPU.
-
-
-
@@ -2078,7 +1999,7 @@
[--add <ide/sata/scsi/floppy>]
[--controller <LsiLogic|LSILogicSAS|BusLogic|
IntelAhci|PIIX3|PIIX4|ICH6|I82078>]
- [--sataportcount <1-30>]
+ [--portcount <1-30>]
[--hostiocache on|off]
[--bootable on|off]
[--remove]
@@ -2119,7 +2040,7 @@
- --sataportcount
+ --portcount
This determines how many ports the SATA controller should
@@ -2811,8 +2732,8 @@
VBoxManage guestcontrol
- The guestcontrol commands allow you
- to control certain things inside a guest from the host. Please see The "guestcontrol" commands allow you to control certain things
+ inside a guest from the host. Please see for an introduction.
Generally, the syntax is as follows: