Add new driver to Windows guest tools: * vioinput - for the virtio-keyboard-pci, virtio-mouse-pci, virtio-tablet-pci, and virtio-input-host-pci device on Windows 7 and newer. * qemufwcfg - for the built-in system FW Cfg device on Windows 10 and Windows Server 2016. The driver has no functionality, it only prevents an unrecognized device from showing in Device Manager. * smbus - for the built-in system SMBus device on Windows 2008. The driver has no functionality, it only prevents an unrecognized device from showing in Device Manager. * The qemupciserial driver is now signed and works on 64-bit Windows.
Since this requires considerable amount of work we will only target latest with Windows desktop and server to include these.
(In reply to Yaniv Lavi (Dary) from comment #0) > Add new driver to Windows guest tools: > > * vioinput - for the virtio-keyboard-pci, virtio-mouse-pci, > virtio-tablet-pci, and virtio-input-host-pci device on Windows 7 and > newer. Since you can't get rid of the old devices (the PS2 devices), what's the advantage of using them? Does oVirt even support them? I suspect we'll need a bug per each device or so. > > * qemufwcfg - for the built-in system FW Cfg device on > Windows 10 and Windows Server 2016. The driver has no functionality, > it only prevents an unrecognized device from showing in Device > Manager. > > * smbus - for the built-in system SMBus device on Windows > 2008. The driver has no functionality, it only prevents an > unrecognized device from showing in Device Manager. > > * The qemupciserial driver is now signed and works on 64-bit Windows.
(In reply to Yaniv Kaul from comment #2) > (In reply to Yaniv Lavi (Dary) from comment #0) > > Add new driver to Windows guest tools: > > > > * vioinput - for the virtio-keyboard-pci, virtio-mouse-pci, > > virtio-tablet-pci, and virtio-input-host-pci device on Windows 7 and > > newer. > > Since you can't get rid of the old devices (the PS2 devices), what's the > advantage of using them? The driver removes warning in the Windows device manager. > > Does oVirt even support them? I suspect we'll need a bug per each device or > so. Yes, this should be released upstream as well.
(In reply to Yaniv Lavi (Dary) from comment #3) > (In reply to Yaniv Kaul from comment #2) > > (In reply to Yaniv Lavi (Dary) from comment #0) > > > Add new driver to Windows guest tools: > > > > > > * vioinput - for the virtio-keyboard-pci, virtio-mouse-pci, > > > virtio-tablet-pci, and virtio-input-host-pci device on Windows 7 and > > > newer. > > > > Since you can't get rid of the old devices (the PS2 devices), what's the > > advantage of using them? > > The driver removes warning in the Windows device manager. Not the new virtio ones. oVirt doesn't expose them. The smbus and pciserial perhaps. > > > > > Does oVirt even support them? I suspect we'll need a bug per each device or > > so. > > Yes, this should be released upstream as well.
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0. If you think this bug should block 4.3.0 please re-target and set blocker flag.
Moving to 4.3.2 not being identified as blocker for 4.3.1.
Tested on RHV-toolsSetup_4.3_8.iso I can see drivers for qemufwcfg and smbus, however vioinput is not there. If it is not necessary it needs to be mentioned as per description it is necessary.
vioinput was handled on bug #1578764 which has been closed not having customer requests for it and so considered not necessary.
Well in that case, verified on RHV-toolsSetup_4.3_8.iso
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:1558