3.2. SPICE Guest Agent

BZ#683164
A new installer is available for the SPICE agent, which enables the local mouse when connecting to a Windows Server virtual machine.

BZ#683166
Previously, you could not start the SPICE agent on Windows Server guests if the QXL driver was not installed. This dependency has been removed and you can now use the SPICE agent on Windows Server guests without the QXL driver.

BZ#691421
Previously, upgrade from the 2.2 version of the SPICE agent to the 3.0 version failed on 32-bit Windows 7 and Windows XP guests. The upgrade process has been updated and you can now upgrade successfully.

BZ#719140
Previously, using the SPICE agent on Windows 7 guests could result in unexpected behavior, such as some features of the agent not working. This was caused by a bug in the VDService agent where services would be run in a different thread than the main service thread, which resulted in a race condition. The agent has been updated and services are now run in the main service thread, so the agent performs as expected.

BZ#722980
Previously, using the SPICE agent on Windows 7 guests could result in unexpected behavior, such as some features of the agent not working. This was caused by a bug in the VDService agent where services would be run in a different thread than the main service thread, which resulted in a race condition. The agent has been updated and services are now run in the main service thread, so the agent performs as expected.

BZ#725734
Previously, if you were running the SPICE agent on Windows guests and left the SPICE session idle, the mouse would become unavailable because the driver would complete pending read operations, which resulted in error codes that made the agent hang. The agent has been updated to ignore these particular error codes and the mouse now behaves as expected.