| commit | 32187f3d902afdfa9f4d861d9612739d3391fdc3 | |
| author | Yuri Benditovich <yuri.benditovich@daynix.com> | |
| Wed, 8 Jan 2020 09:10:44 +0000 (8 11:10 +0200) | ||
| committer | Gerd Hoffmann <kraxel@redhat.com> | |
| Mon, 13 Jan 2020 08:17:31 +0000 (13 09:17 +0100) | ||
| tree | 2c5981cc8b3f3c83452fdb29c3ac652c1912bda5 | treesnapshot (tar.gz zip) |
| parent | 7bacaf5fea5729d400201106359f6803b15621af | commitdiff |
usb-redir: remove 'remote wakeup' flag from configuration descriptor
If the redirected device has this capability, Windows guest may
place the device into D2 and expect it to wake when the device
becomes active, but this will never happen. For example, when
internal Bluetooth adapter is redirected, keyboards and mice
connected to it do not work. Current commit removes this
capability (starting from machine 5.0)
Set 'usb-redir.suppress-remote-wake' property to 'off' to keep
'remote wake' as is or to 'on' to remove 'remote wake' on
4.2 or earlier.
Signed-off-by: Yuri Benditovich <yuri.benditovich@daynix.com>
Message-id: 20200108091044.18055-3-yuri.benditovich@daynix.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
If the redirected device has this capability, Windows guest may
place the device into D2 and expect it to wake when the device
becomes active, but this will never happen. For example, when
internal Bluetooth adapter is redirected, keyboards and mice
connected to it do not work. Current commit removes this
capability (starting from machine 5.0)
Set 'usb-redir.suppress-remote-wake' property to 'off' to keep
'remote wake' as is or to 'on' to remove 'remote wake' on
4.2 or earlier.
Signed-off-by: Yuri Benditovich <yuri.benditovich@daynix.com>
Message-id: 20200108091044.18055-3-yuri.benditovich@daynix.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
| hw/core/machine.c | diffblobblamehistory | |
| hw/usb/redirect.c | diffblobblamehistory |