Bug 1847856

Summary: [virtio-win-installer]Install/uninstall exe doesn't always prompt to reboot machine
Product: Red Hat Enterprise Linux 8 Reporter: xiagao
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
virtio-win sub component: others QA Contact: xiagao
Status: CLOSED WONTFIX Docs Contact:
Severity: medium    
Priority: medium CC: ailan, menli, mtessun, vrozenfe
Version: 8.2Keywords: Reopened, Triaged
Target Milestone: rc   
Target Release: 8.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-09-24 07:26:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
tool install logs
none
setupapi.dev.log none

Description xiagao 2020-06-17 08:34:54 UTC
Created attachment 1697760 [details]
tool install logs

Description of problem:
Install/uninstall doesn't always prompt to reboot machine, we need to always ask for a reboot to be on the safe side


How reproducible:
100%

Steps to Reproduce:
1.boot up windows guest.
2.try to install/uninstall virtio driver, spice and qemu-guest-agent via virtio-win-guest-tools.exe.


Actual results:
There is no hint to reboot the machine, install log is in attachment.

Expected results:
Better to ask for a reboot after install/uninstall.

Comment 6 menli@redhat.com 2021-03-16 11:51:06 UTC
Created attachment 1763602 [details]
setupapi.dev.log

Comment 11 xiagao 2021-03-24 01:44:45 UTC
Reopen it according to comment5

Comment 13 Vadim Rozenfeld 2021-03-24 23:28:33 UTC
I still have doubts that we need to force a system reboot after successful device drivers installation
or update action.
https://docs.microsoft.com/en-us/windows-hardware/drivers/install/device-installations-and-system-restarts

However, living it to Martin and Amnon to comment on this issue.

The problem mentioned at https://bugzilla.redhat.com/show_bug.cgi?id=1847856#c5 needs to be investigated
as a separate issue.

Best regards,
Vadim

Comment 17 RHEL Program Management 2021-09-24 07:26:57 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.