Bug 1878144
Summary: | [Docs] Docs for InstallShield guest tools are not up to date with virtio-win 1.9.12 | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Petr Matyáš <pmatyas> |
Component: | Documentation | Assignee: | rhev-docs <rhev-docs> |
Status: | CLOSED WONTFIX | QA Contact: | Ivana Saranova <isaranov> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.4.1 | CC: | apinnick, ctomasko, lsurette, mhicks, srevivo |
Target Milestone: | ovirt-4.5.3 | Keywords: | Documentation |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | docscope 4.5 | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-07 03:51:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Docs | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Petr Matyáš
2020-09-11 13:14:19 UTC
In which RHV release does this version of virtio-win start appearing? Technically 4.4.3 but virtio-win is provided via RHEL channels (currently nighty) so now it will be in all of them. Can you provide me (In reply to Petr Matyáš from comment #0) > Description of problem: > With the introduction of virtio-win 1.9.12 the process for installing GT > will differ, instead of running the msi-s there is now an exe file for this. > Also guide for automated(command line) installation needs updating for the > same reasons. Besides the file being an exe instead of an MSI, are there any other differences? What are the file names now? File name is 'virtio-win-guest-tools.exe', the installation through UI is the same. There is a difference in console installation, we can't select only specific drivers to install as with the msi, all the drivers are installed by default. This can be done when 'virtio-win-gt-x64.msi' is used for drivers installation (same arguments as with the previous virtio-win) and then install qemu and ovirt guest-agents from their respective msis ('ovirt-guest-agent-x64.msi' and 'guest-agent/qemu-ga-x86_64.msi') Petr, Why do I still see the msi files in the list of packages for virtio-win-1.9.12-2 [1]: /usr/share/virtio-win/installer/virtio-win-gt-x64.msi /usr/share/virtio-win/installer/virtio-win-gt-x86.msi /usr/share/virtio-win/installer/virtio-win-guest-tools.exe [1] https://centos.pkgs.org/8/centos-appstream-x86_64/virtio-win-1.9.12-2.el8.noarch.rpm.html Those files are still there, but their functionality changed a little bit, those msi's don't install guest agents currently, as I mentioned in comment#5. CLI installation procedure for installing/upgrading guest tools on Windows VMs needs to be checked and updated, if necessary. Modules: source/documentation/virtual_machine_management_guide/topics/Installing_the_Guest_Agents_and_Drivers_on_Windows.adoc source/documentation/virtual_machine_management_guide/topics/Updating_the_Guest_Agents_and_Drivers_on_Windows.adoc |