Bug 1878144 - [Docs] Docs for InstallShield guest tools are not up to date with virtio-win 1.9.12
Summary: [Docs] Docs for InstallShield guest tools are not up to date with virtio-win ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.4.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.5.3
: ---
Assignee: rhev-docs@redhat.com
QA Contact: Ivana Saranova
URL:
Whiteboard: docscope 4.5
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-11 13:14 UTC by Petr Matyáš
Modified: 2023-09-07 03:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-07 03:51:40 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Matyáš 2020-09-11 13:14:19 UTC
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.

Version-Release number of selected component (if applicable):
virtio-win-1.9.12-2.el8.noarch

How reproducible:
always

Steps to Reproduce:
1. create a windows VM
2. attach virtio-win CD to the VM
3. check installation through cmd line and graphical interface according to the documentation

Actual results:
process differs

Expected results:
documentation should be updated to reflect latest changes

Additional info:

Comment 1 Steve Goodman 2020-09-13 12:54:19 UTC
In which RHV release does this version of virtio-win start appearing?

Comment 2 Petr Matyáš 2020-09-14 07:54:55 UTC
Technically 4.4.3 but virtio-win is provided via RHEL channels (currently nighty) so now it will be in all of them.

Comment 3 Steve Goodman 2020-10-22 16:59:02 UTC
Can you provide me

Comment 4 Steve Goodman 2020-10-29 15:43:39 UTC
(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?

Comment 5 Petr Matyáš 2020-10-30 09:20:43 UTC
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')

Comment 6 Steve Goodman 2020-11-01 16:02:15 UTC
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

Comment 7 Petr Matyáš 2020-11-02 11:42:42 UTC
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.

Comment 9 Avital Pinnick 2022-08-07 09:46:09 UTC
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


Note You need to log in before you can comment on or make changes to this bug.