Bug 1828658

Description of problem:
Windows guest BSOD when do "Scan for hardware changed" in device management.

On new virtio-win-prewhql-181 version, tested with virtio_blk disk, reproduced this issue when do rescan operation,
but on virtio-win-prewhql-180 version, tested with virtio_blk disk, cannot reproduce issue when do rescan operation.

Version-Release number of selected component (if applicable):
kernel-4.18.0-193.el8.x86_64
qemu-kvm-4.2.0-19.module+el8.2.0+6296+6b821950.x86_64
virtio-win-prewhql-181
seabios-1.13.0-1.module+el8.2.0+5520+4e5817f3.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Boot a windows guest vm attach 1 virtio_blk system disk:
==========================================================================
-blockdev node-name=file_image1,driver=file,aio=threads,filename=/home/kvm_autotest_root/images/win10-64-virtio.qcow2,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_image1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_image1 \
-device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,serial=TARGET_DISK0,bus=pci.0,addr=0x4 \
==========================================================================
2. In guest device management, do "Scan for hardware changed", or run diskpart --> rescan command.
3. check the guest status.

Actual results:
BSOD

Expected results:
No BSOD, rescan successully.

Additional info:
1. On virtio-win-prewhql-180 version, cannot reproduce this issue.
2. On version virtio-win-prewhql-181, I also tested without serial=TARGET_DISK0 on virtio-blk-pci(-device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,write-cache=on,bus=pci.0,addr=0x4), cannot reproduce this issue.