RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1784744 - [virtio-win] guest can not boot up due to virtio-win-installer remove option uninstalls all drivers including OS driver
Summary: [virtio-win] guest can not boot up due to virtio-win-installer remove option ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virtio-win
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.2
Assignee: Gal Zaidman
QA Contact: lijin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-18 08:59 UTC by lijin
Modified: 2021-01-08 17:46 UTC (History)
4 users (show)

Fixed In Version: virtio-win-1.9.10-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-04 12:27:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
guest bsod screenshot after reboot (21.77 KB, image/png)
2019-12-18 08:59 UTC, lijin
no flags Details

Description lijin 2019-12-18 08:59:17 UTC
Created attachment 1646050 [details]
guest bsod screenshot after reboot

Description of problem:


Version-Release number of selected component (if applicable):
virtio-win-1.9.10-2.el8/virtio-win-installer-1.9.10-1

How reproducible:
100%

Steps to Reproduce:
1.boot up a windows guest with ide system disk:
    -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \
    -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2 \
    -device ide-drive,id=image1,drive=drive_image1,serial=SYSTEM_DISK0 \

2.run virtio-win-gt-x86.msi in guest and click "install"

3.shutdown the guest, and boot it up with scsi system disk
    -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \
    -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/home/kvm_autotest_root/images/win2016-64-virtio-scsi.qcow2 \
    -device scsi-hd,id=image1,drive=drive_image1,serial=SYSTEM_DISK0 \

4.run virtio-win-gt-x86.msi in guest and click "remove"

5.reboot guest

Actual results:
after step4, all drivers are uninstalled, include the guest os system disk drive
after step5, guest bsod due to inaccessible boot device

Expected results:
during remove, we can select which drivers we want to remove instead of remove all of them

Additional info:

Comment 2 lijin 2019-12-19 10:43:10 UTC
Check with latest virtio-win-installer-1.9.10-3, viostor and vioscsi drivers are remained after remove operation. 
So guest system disk drivers keep in guest, vm does not bsod.

Change status to verified.

Comment 4 errata-xmlrpc 2020-02-04 12:27:28 UTC
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-2020:0351


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