Bug 1545297
| Summary: | Update of RHEV-tools does not install qxl-dod driver for Win10 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Radek Duda <rduda> |
| Component: | rhev-guest-tools | Assignee: | Lev Veyde <lveyde> |
| Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.2.0 | CC: | lsvaty, lveyde, spice-qe-bugs, ylavi |
| Target Milestone: | ovirt-4.2.2 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Windows | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-15 17:56:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Radek Duda
2018-02-14 15:08:29 UTC
It's not a bug, it works like that by design, as we never add any new components to the system during an update, be it a completely new component or one that recently got support for the OS version in question. Generally during an update only existing components are updated, and no new components are being added. In order to add a new component, the customer needs to add it manually, by modifying the current installation of the RHEV Windows Guest Tools and enabling the QXL component. Once installed it will be automatically updated from that point onwards. (In reply to Lev Veyde from comment #1) > It's not a bug, it works like that by design, as we never add any new > components to the system during an update, be it a completely new component > or one that recently got support for the OS version in question. > > Generally during an update only existing components are updated, and no new > components are being added. > > In order to add a new component, the customer needs to add it manually, by > modifying the current installation of the RHEV Windows Guest Tools and > enabling the QXL component. > > Once installed it will be automatically updated from that point onwards. I think this is very inconvenient for two reasons: 1. Customer have to launch RHEV-Tools two times. For the first time he upgrades RHEV-Tools, for the second time he chooses to 'Modify' and checks 'spice driver'. How could he know that he must relaunch RHEV-Tools? Is this documented somewhere? I did not find anything about it in documentation. For me it seems logical that upgrading of RHEV-Tools should automatically install new features (you do not upgrade just installed component, but RHEV-Tools and qxl-dod driver is now part of it). 2. RHEV application provisioning tool. Automatic upgrading of RHEV-Tools does not install qxl-dod either. So Win10 VM is not fully provisioned by new RHEV-tool released and customer have to intervene manually. New qxl-dod driver is essential to have good experience of Windows10 VM usage in console - for example better handling of mouse cursor, allows multiple monitors and their automatic resizement. (In reply to Radek Duda from comment #2) > (In reply to Lev Veyde from comment #1) > > It's not a bug, it works like that by design, as we never add any new > > components to the system during an update, be it a completely new component > > or one that recently got support for the OS version in question. > > > > Generally during an update only existing components are updated, and no new > > components are being added. > > > > In order to add a new component, the customer needs to add it manually, by > > modifying the current installation of the RHEV Windows Guest Tools and > > enabling the QXL component. > > > > Once installed it will be automatically updated from that point onwards. > > I think this is very inconvenient for two reasons: > > 1. Customer have to launch RHEV-Tools two times. For the first time he > upgrades RHEV-Tools, for the second time he chooses to 'Modify' and checks > 'spice driver'. How could he know that he must relaunch RHEV-Tools? Is this > documented somewhere? I did not find anything about it in documentation. For > me it seems logical that upgrading of RHEV-Tools should automatically > install new features (you do not upgrade just installed component, but > RHEV-Tools and qxl-dod driver is now part of it). > > 2. RHEV application provisioning tool. Automatic upgrading of RHEV-Tools > does not install qxl-dod either. So Win10 VM is not fully provisioned by new > RHEV-tool released and customer have to intervene manually. > > New qxl-dod driver is essential to have good experience of Windows10 VM > usage in console - for example better handling of mouse cursor, allows > multiple monitors and their automatic resizement. I don't see this case as being that different from any other case of new components being added. Also forcefully installing the component during an update will create an issue to actually avoid installation during the update, since we don't have a 3-state option for the components. Following internal discussion we decided to implement a policy exclusion for this specific case. So now upgrade from RHEV Windows Guest Tools 4.1 (or earlier version) to 4.2 will install Spice QXL driver automatically, if appropriate. Verified on rhv-guest-tools-iso-4.2-4.el7ev.noarch 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-2018:1517 BZ<2>Jira Resync |