Hello Jean-Philippe,
On 19/05/14 01:02, MENGUAL Jean-Philippe wrote:
You will find the update patch for user manual here:
http://manager.accelibreinfo.eu/update_vbox.txt
Thank you very much, applied in subversion. I am attaching the current
diff of trunk to 4.3 in case you would like to do that. Unfortunately
there seem to be a few irrelevant reformatting changes which make the
diff file longer.
Thanks again.
Regards,
Michael
--
ORACLE Deutschland B.V. & Co. KG Michael Thayer
Werkstrasse 24 VirtualBox engineering
71384 Weinstadt, Germany mailto:[email protected]
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Geschäftsführer: Jürgen Kunz
Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher
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 @@
</sect2>
<sect2>
- <title>Linux and Solaris hosts</title>
+ <title>Linux hosts</title>
<para>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 @@
</sect1>
+ <sect1 id="sse412passthrough">
+ <title>Experimental support for passing through SSE4.1 / SSE4.2 instructions</title>
+ <para>
+ 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:</para><screen>VBoxManage setextradata "VM name" VBoxInternal/CPUM/SSE4.1 1
+VBoxManage setextradata "VM name" VBoxInternal/CPUM/SSE4.2 1</screen>
+ <para>
+ These are a per-VM settings and they are turned off by default.
+ </para>
+ </sect1>
+
+ <sect1 id="hidledssync">
+ <title>Support for keyboard indicators synchronization</title>
+
+ <para>
+ 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:
+ </para>
+
+ <screen>VBoxManage setextradata "VM name" GUI/HidLedsSync "1"</screen>
+
+ <para>
+ 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.
+ </para>
+
+ </sect1>
+
</chapter>
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 @@
<para><glosslist>
<glossentry>
- <glossterm>Snapshot Folder</glossterm>
+ <glossterm>Snapshot folder</glossterm>
<glossdef>
<para>By default, VirtualBox saves snapshot data together with
@@ -380,7 +380,7 @@
</glossentry>
<glossentry>
- <glossterm>Shared Clipboard</glossterm>
+ <glossterm>Shared clipboard</glossterm>
<glossdef>
<para>You can select here whether the clipboard of the guest
@@ -405,35 +405,29 @@
<glossentry>
<glossterm>Drag'n'Drop</glossterm>
<glossdef>
- <para>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.</para>
-
- <para>For drag'n drop to work the Guest Additions need to be
- installed on the guest.</para>
-
- <note>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.</note>
-
- <para>See <xref linkend="guestadd-dnd"/> for more information.</para>
-
- <footnote><para>Experimental support for drag and drop was added
- with VirtualBox 4.2.</para></footnote>
+ <para>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.<footnote><para>Support
+ for Drag'n'Drop was added with VirtualBox 4.2</para></footnote></para>
</glossdef>
</glossentry>
<glossentry>
- <glossterm>Removable Media</glossterm>
+ <glossterm>Removable media: remember runtime changes</glossterm>
+
<glossdef>
<para>If this is checked, VirtualBox will save the state of what
- media has been mounted between several runs of a virtual machine.</para>
+ media has been mounted between several runs of a virtual
+ machine.</para>
</glossdef>
</glossentry>
<glossentry>
- <glossterm>Mini ToolBar</glossterm>
+ <glossterm>Mini toolbar</glossterm>
+
<glossdef>
<para>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 @@
<para>Currently only Linux and Solaris Guest Additions support
symlinks.</para>
</listitem>
-
- <listitem>
- <para>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:
- <screen>VBoxManage setextradata "VM name" VBoxInternal2/SharedFoldersEnableSymlinksCreate/sharename 1</screen></para>
- </listitem>
</orderedlist></para>
<sect2 id="sf_mount_manual">
@@ -1247,110 +1239,6 @@
</sect2>
</sect1>
- <sect1 id="guestadd-dnd">
- <title>Drag'n Drop</title>
-
- <para>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.</para>
-
- <para>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.</para>
-
- <para>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.</para>
-
- <para>In context of using drag'n drop the origin of the data is called
- <emphasis role="bold">source</emphasis>, that is, where the actual data comes
- from and is specified. On the other hand there is the
- <emphasis role="bold">target</emphasis>, 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.<footnote><para>At
- the moment only copying of data is supported. Moving or linking is not yet
- implemented.</para></footnote></para>
-
- <para>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.</para>
-
- <para>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:
-
- <para><mediaobject>
- <imageobject>
- <imagedata align="center" fileref="images/dnd-modes.png"
- width="10cm" />
- </imageobject>
- </mediaobject></para>
-
- <itemizedlist>
- <listitem>
- <para><emphasis role="bold">Disabled</emphasis> disables the drag'n drop
- entirely. This is the default when creating new VMs.</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold">Host To Guest</emphasis> enables performing
- drag'n drop operations from the host to the guest only.</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold">Guest To Host</emphasis> enables performing
- drag'n drop operations from the guest to the host only.</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold">Bidirectional</emphasis> enables performing
- drag'n drop operations to both directions, e.g. from the host to the guest
- and vice versa.</para>
- </listitem>
- </itemizedlist></para>
-
- <note><para>Drag'n drop support depends on the frontend being used; at the
- moment only the VirtualBox Manager frontend provides this
- functionality.</para></note>
-
- <para>To use VBoxManage for controlling the current drag'n drop mode, see <xref
- linkend="vboxmanage" />. The commands <computeroutput>modifyvm</computeroutput>
- and <computeroutput>controlvm</computeroutput> allow setting the VM's current
- drag'n drop mode via command line.</para>
-
- <sect2 id="guestadd-dnd-formats">
- <title>Supported formats</title>
-
- <para>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.</para>
-
- <note><para>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.</para></note>
-
- <para>The following formats are handled by the VirtualBox drag'n drop service:
- <itemizedlist>
- <listitem>
- <para><emphasis role="bold">Plain text</emphasis>, from applications such as
- text editors, internet browsers and terminal windows</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold">Files</emphasis>, from file managers such
- as Windows explorer, Nautilus and Finder</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold">Directories</emphasis>, where the same applies
- as for files</para>
- </listitem>
- </itemizedlist>
- </para>
- </sect2>
-
- </sect1>
-
<sect1 id="guestadd-video">
<title>Hardware-accelerated graphics</title>
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 @@
<sect2 id="solaris-zones">
<title>Configuring a zone for running VirtualBox</title>
+ <para>Starting with VirtualBox 1.6 it is possible to run VirtualBox from
+ within Solaris zones. For an introduction of Solaris zones, please refer
+ to <ulink
+ url="http://www.sun.com/bigadmin/features/articles/solaris_zones.jsp";>http://www.sun.com/bigadmin/features/articles/solaris_zones.jsp</ulink>.</para>
+
<para>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 @@
<screen>zonecfg -z vboxzone</screen>
- <para>Replace "vboxzone" with the name of the zone in which you intend
- to run VirtualBox.</para>
-
<para>Inside the <computeroutput>zonecfg</computeroutput> prompt add the
<computeroutput>device</computeroutput> resource and
<computeroutput>match</computeroutput> properties to the zone. Here's
@@ -843,18 +845,19 @@
<screen>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</screen>
<para>If you are running VirtualBox 2.2.0 or above on Solaris 11 or
- above, you may add a device for <computeroutput>/dev/vboxusbmon</computeroutput>
- too, similar to what was shown above. This does not apply to Solaris 10
- hosts due to lack of USB support.</para>
+ Nevada hosts, you should add a device for
+ <computeroutput>/dev/vboxusbmon</computeroutput> too, similar to what
+ was shown above. This does not apply to Solaris 10 hosts due to lack of
+ USB support.</para>
- <para>Next reboot the zone using <computeroutput>zoneadm</computeroutput>
- and you should be able to run VirtualBox from within the configured zone.</para>
+ <para>Replace "vboxzone" with the name of the zone in which you intend
+ to run VirtualBox. Next reboot the zone using
+ <computeroutput>zoneadm</computeroutput> and you should be able to run
+ VirtualBox from within the configured zone.</para>
</sect2>
</sect1>
</chapter>
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 @@
</listitem>
<listitem>
+ <para><emphasis role="bold">64-bit guests on some 32-bit host systems
+ with VT-x</emphasis> 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.</para>
+ </listitem>
+
+ <listitem>
<para><emphasis role="bold">NX (no execute, data execution
prevention)</emphasis> 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 @@
</listitem>
<listitem>
- <para>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.</para>
- </listitem>
-
- <listitem>
<para>No ACPI information (battery status, power source) is
reported to the guest.</para>
</listitem>
@@ -266,8 +267,8 @@
<para>Crossbow-based bridged networking on Solaris 11 hosts does
not work directly with aggregate links. However, you can manually
create a VNIC (using <computeroutput>dladm</computeroutput>) over
- the aggregate link and use that with a VM. This limitation does
- not exist in Solaris 11u1 build 17 and newer.</para>
+ the aggregate link and use that with a VM. This technical
+ limitation will be addressed in a future Solaris 11 release.</para>
</listitem>
</itemizedlist></para>
</listitem>
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 @@
<listitem>
<para>To change settings while a VM is powered off, use
<computeroutput>VBoxManage modifyvm</computeroutput>, e.g. as
- follows:<screen>VBoxManage modifyvm "Windows XP" --memory 512</screen></para>
+ follows:<screen>VBoxManage modifyvm "Windows XP" --memory "512MB"</screen></para>
<para>For details, see <xref linkend="vboxmanage-modifyvm" />.</para>
</listitem>
@@ -937,10 +937,9 @@
</sect2>
<sect2 id="vboxmanage-modifyvm-other">
- <title>Miscellaneous settings</title>
+ <title>Serial port, audio, clipboard and USB settings</title>
- <para>The following other hardware settings, such as serial port, audio,
- clipboard, drag'n drop, monitor and USB settings are available through
+ <para>The following other hardware settings are available through
<computeroutput>VBoxManage modifyvm</computeroutput>:<itemizedlist>
<listitem>
<para><computeroutput>--uart<1-N> off|<I/O base>
@@ -1008,18 +1007,9 @@
<listitem>
<para><computeroutput>--clipboard
disabled|hosttoguest|guesttohost|bidirectional</computeroutput>:
- 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 <xref linkend="generalsettings" />. This requires that the Guest
- Additions be installed in the virtual machine.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--draganddrop
- disabled|hosttoguest|guesttohost|bidirectional</computeroutput>:
- With this setting, you can select the current drag'n drop mode
- being used between the host and the virtual machine;
- see <xref linkend="guestadd-dnd" />. 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 <xref
+ linkend="generalsettings" />. This requires that the Guest
Additions be installed in the virtual machine.</para>
</listitem>
@@ -1041,8 +1031,6 @@
see <xref linkend="settings-usb" /> for details.</para>
</listitem>
</itemizedlist></para>
-
- <!-- @todo r=andy Document tracing-* commands -->
</sect2>
<sect2 id="vboxmanage-modifyvm-vrde">
@@ -1060,8 +1048,6 @@
default.</para>
</listitem>
- <!-- @todo r=andy Document vrdeproperty -->
-
<listitem>
<para><computeroutput>--vrdeport
default|<ports></computeroutput>: A port or a range of ports
@@ -1523,8 +1509,6 @@
VM's running state:</para>
<itemizedlist>
- <!-- @todo r=andy Document keyboardputscancode -->
-
<listitem>
<para>The <computeroutput>setlinkstate<1-N></computeroutput>
operation connects or disconnects virtual network cables from their
@@ -1549,43 +1533,6 @@
</listitem>
<listitem>
- <para>With the "nictrace" options, you can optionally trace
- network traffic by dumping it to a file, for debugging
- purposes.</para>
-
- <para>With <computeroutput>--nictrace<1-N>
- on|off</computeroutput>, you can enable network tracing for a
- particular virtual network card.</para>
-
- <para>If enabled, you must specify with
- <computeroutput>--nictracefile<1-N>
- <filename></computeroutput> what file the trace should be
- logged to.</para>
- </listitem>
-
- <!-- @todo r=andy Document nicpromisc -->
-
- <listitem>
- <para><computeroutput>nicproperty<1-N>
- <paramname>="paramvalue"</computeroutput>:
- This option, in combination with "nicgenericdrv" allows you to
- pass parameters to rarely-used network backends.</para><para>
- Those parameters are backend engine-specific, and are different
- between UDP Tunnel and the VDE backend drivers. For example,
- please see <xref linkend="network_udp_tunnel" />.
- </para>
- </listitem>
-
- <listitem>
- <para>The <computeroutput>guestmemoryballoon</computeroutput>
- 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 <xref linkend="guestadd-balloon" />.</para>
- </listitem>
-
- <listitem>
<para><computeroutput>usbattach</computeroutput> and
<computeroutput>usbdettach</computeroutput> make host USB devices
visible to the virtual machine on the fly, without the need for
@@ -1597,24 +1544,6 @@
</listitem>
<listitem>
- <para><computeroutput>clipboard
- disabled|hosttoguest|guesttohost|bidirectional</computeroutput>:
- 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 <xref linkend="generalsettings" />. This requires that the Guest
- Additions be installed in the virtual machine.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>draganddrop
- disabled|hosttoguest|guesttohost|bidirectional</computeroutput>:
- With this setting, you can select the current drag'n drop mode
- being used between the host and the virtual machine;
- see <xref linkend="guestadd-dnd" />. This requires that the Guest
- Additions be installed in the virtual machine.</para>
- </listitem>
-
- <listitem>
<para><computeroutput>vrde on|off</computeroutput> lets you enable or
disable the VRDE server, if it is installed.</para>
</listitem>
@@ -1628,7 +1557,6 @@
linkend="vboxmanage-modifyvm-other" />.</para>
</listitem>
-
<listitem>
<para><computeroutput>setvideomodehint</computeroutput> 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.</para>
</listitem>
- <!-- @todo r=andy Document vcpenabled + vcpscreens! -->
-
<listitem>
<para>The <computeroutput>setcredentials</computeroutput> operation is
used for remote logons in Windows guests. For details, please refer to
<xref linkend="autologon" />.</para>
</listitem>
- <!-- @todo r=andy Document teleport! -->
-
<listitem>
- <para><computeroutput>--plugcpu|unplugcpu
- <id></computeroutput>: If CPU hot-plugging is enabled, this adds
- a virtual CPU to the virtual machines (or removes one).
- <computeroutput><id></computeroutput> 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.</para>
+ <para>The <computeroutput>guestmemoryballoon</computeroutput>
+ 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 <xref linkend="guestadd-balloon" />.</para>
</listitem>
<listitem>
@@ -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.</para>
</listitem>
-
- <!-- @todo r=andy Document webcam! -->
-
</itemizedlist>
</sect1>
@@ -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]</screen>
@@ -2119,7 +2040,7 @@
</glossentry>
<glossentry>
- <glossterm><computeroutput>--sataportcount</computeroutput></glossterm>
+ <glossterm><computeroutput>--portcount</computeroutput></glossterm>
<glossdef>
<para>This determines how many ports the SATA controller should
@@ -2811,8 +2732,8 @@
<sect1 id="vboxmanage-guestcontrol">
<title>VBoxManage guestcontrol</title>
- <para>The <computeroutput>guestcontrol</computeroutput> commands allow you
- to control certain things inside a guest from the host. Please see <xref
+ <para>The "guestcontrol" commands allow you to control certain things
+ inside a guest from the host. Please see <xref
linkend="guestadd-guestcontrol" /> for an introduction.</para>
<para>Generally, the syntax is as follows:</para>
_______________________________________________
vbox-dev mailing list
[email protected]
https://www.virtualbox.org/mailman/listinfo/vbox-dev
