Changes between Version 4 and Version 5 of Guest_resizing

Timestamp:

Mar 17, 2017 4:27:33 PM (8 years ago)

Author:

Michael Thayer

Comment:

Information about the Windows Additions

Guest_resizing

@@ -14 +14 @@
 
 In theory the guest could decide to set a slightly different size, perhaps just by one or two pixels, and the host could try to insist on the original one, but in practice this has not been observed.  What is more common is that the guest ignores the request for some reason - for example if the user has accidentally told GNOME Shell in a guest that they only want a certain resolution.  Another known problem is that on older Linux guests without kernel graphics drivers we send an ACPI monitor change notification, which a few older guests interpret as a request to cycle to the next available resolution after the resize has already taken place.  No modern Linux system is known to be affected, and as of X.Org Server 1.19 in the guest we require use of the kernel driver.
+
+== Guest Additions components ==
+=== Windows guests ===
+ * VBoxVideo: the main graphics driver loaded into the kernel.  It can tell how many screens (that is, screen connectors) the guest currently supports, and can enable and disable them as well as setting resolutions to them.  It reports this information to Windows on the guest.  It can not receive information from the host about screen changes (mode hints, monitor unplug or hotplug) itself, but provides an interface for a user-space tool which can to provide that information.  It remembers information received in the Windows registry and simply assumes when it loads that the configuration has not changed since it was last used.
+ * VBoxTray: a user-space daemon which is loaded when a user logs into Windows on the guest and runs as part of that session.  It can receive screen change information from the host and forward it to VBoxVideo.