2026604 – Windows guest does not present fault (slow response) disk

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

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 2026604 - Windows guest does not present fault (slow response) disk

Summary: Windows guest does not present fault (slow response) disk

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 9
Classification:	Red Hat
Component:	qemu-kvm
Sub Component:
Version:	9.0
Hardware:	Unspecified
OS:	Windows
Priority:	high
Severity:	high
Target Milestone:	rc
Target Release:	---
Assignee:	Vadim Rozenfeld
QA Contact:	qing.wang
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2021-11-25 09:44 UTC by qing.wang
Modified:	2023-09-19 13:01 UTC (History)
CC List:	12 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-09-19 13:01:31 UTC
Type:	---
Target Upstream Version:
Embargoed:
Dependent Products:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHEL-5007	0	None	Migrated	None	2023-09-19 13:00:30 UTC
Red Hat Issue Tracker	RHELPLAN-103932	0	None	None	None	2021-11-25 09:45:11 UTC

Description qing.wang 2021-11-25 09:44:46 UTC

Description of problem:

Emulate one fault disk, it will delay IO about 5 minutes.

Pass-through the disk to vm and boot it. The vm boot slowly.

The disk can be found in disk management after boot.




Version-Release number of selected component (if applicable):

Red Hat Enterprise Linux release 9.0 Beta (Plow)
5.14.0-1.7.1.el9.x86_64
qemu-kvm-6.1.0-8.el9.x86_64
seabios-bin-1.14.0-6.el9.noarch
edk2-ovmf-20210527gite1999b264f1f-6.el9.noarch
virtio-win-prewhql-0.1-214.iso

(qemu-kvm-6.0.0-13.el9_b.5.x86_64 same result)

How reproducible:
100%

Steps to Reproduce:
1. emulate fault disk

1.1 create scsi_debug disk ==>/dev/sdb
modprobe scsi_debug  dev_size_mb=128

1.2 create dm disk with fault sector ==> /dev/mapper/baddisk

dmsetup create baddisk << EOF
0 160000 linear /dev/sdd 0
160000 5 delay /dev/sdd 160000 0 /dev/sdd 160000 300000
160005 80000 linear /dev/sdd 160005
EOF

1.3 export the dm disk 
(workspace) root@dell-per440-07 /home/vbugs $ targetcli ls
o- / ..................................................................... [...]
  o- backstores .......................................................... [...]
  | o- block .............................................. [Storage Objects: 1]
  | | o- device.baddisk .. [/dev/mapper/baddisk (117.2MiB) write-thru activated]
  | |   o- alua ............................................... [ALUA Groups: 1]
  | |     o- default_tg_pt_gp ................... [ALUA state: Active/optimized]
  | o- fileio ............................................. [Storage Objects: 0]
  | o- pscsi .............................................. [Storage Objects: 0]
  | o- ramdisk ............................................ [Storage Objects: 0]
  o- iscsi ........................................................ [Targets: 1]
  | o- iqn.2019-12.com.redhat:kvm-qe ................................. [TPGs: 1]
  |   o- tpg1 .............................................. [gen-acls, no-auth]
  |     o- acls ...................................................... [ACLs: 0]
  |     o- luns ...................................................... [LUNs: 1]
  |     | o- lun0  [block/device.baddisk (/dev/mapper/baddisk) (default_tg_pt_gp)]
  |     o- portals ................................................ [Portals: 1]
  |       o- 0.0.0.0:3260 ................................................. [OK]
  o- loopback ..................................................... [Targets: 0]

1.4 attach the iscsi disk ==> sde



lsblk:
sdd                              8:48   0   128M  0 disk 
 --baddisk                      253:3    0 117.2M  0 dm   
sde                              8:64   0 117.2M  0 disk


2.pass-through the disk and boot it
/usr/libexec/qemu-kvm \
    -name 'avocado-vt-vm1'  \
    -sandbox on  \
    -machine pc,memory-backend=mem-machine_mem  \
    -nodefaults \
    -device VGA,bus=pci.0,addr=0x2 \
    -m 30720 \
    -object memory-backend-ram,size=30720M,id=mem-machine_mem  \
    -smp 10,maxcpus=10,cores=5,threads=1,dies=1,sockets=2  \
    -cpu 'Cascadelake-Server-noTSX',hv_stimer,hv_synic,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi,+kvm_pv_unhalt \
    \
    -device ich9-usb-ehci1,id=usb1,addr=0x1d.0x7,multifunction=on,bus=pci.0 \
    -device ich9-usb-uhci1,id=usb1.0,multifunction=on,masterbus=usb1.0,addr=0x1d.0x0,firstport=0,bus=pci.0 \
    -device ich9-usb-uhci2,id=usb1.1,multifunction=on,masterbus=usb1.0,addr=0x1d.0x2,firstport=2,bus=pci.0 \
    -device ich9-usb-uhci3,id=usb1.2,multifunction=on,masterbus=usb1.0,addr=0x1d.0x4,firstport=4,bus=pci.0 \
    -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
    -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x3 \
    -blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/home/kvm_autotest_root/images/win2019-64-virtio-scsi.qcow2,cache.direct=on,cache.no-flush=off \
    -blockdev node-name=drive_image1,driver=qcow2,read-only=off,cache.direct=on,cache.no-flush=off,file=file_image1 \
    -device scsi-hd,id=image1,drive=drive_image1,write-cache=on \
    -blockdev node-name=host_device_stg0,driver=host_device,auto-read-only=on,discard=unmap,aio=threads,filename=/dev/sde,cache.direct=on,cache.no-flush=off \
    -blockdev node-name=drive_stg0,driver=raw,read-only=off,cache.direct=on,cache.no-flush=off,file=host_device_stg0 \
    -device scsi-block,id=stg0,drive=drive_stg0 \
    -device virtio-net-pci,mac=9a:a7:e2:63:66:14,id=idRtFaeP,netdev=idABy47V,bus=pci.0,addr=0x4  \
    -netdev tap,id=idABy47V,vhost=on \
    -blockdev node-name=file_cd1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/home/kvm_autotest_root/iso/windows/winutils.iso,cache.direct=on,cache.no-flush=off \
    -blockdev node-name=drive_cd1,driver=raw,read-only=on,cache.direct=on,cache.no-flush=off,file=file_cd1 \
    -device scsi-cd,id=cd1,drive=drive_cd1  \
    -rtc base=localtime,clock=host,driftfix=slew  \
    -boot menu=off,order=cdn,once=c,strict=off \
    -vnc :5 \
     -rtc base=localtime,clock=host,driftfix=slew  \
     -boot menu=off,order=cdn,once=c,strict=off \
     -enable-kvm \
     -monitor stdio \
    -qmp tcp:0:5955,server=on,wait=off \




3.wait for the guest boot,the check the disk
wmic diskdrive get index
or disk managerment.

Actual results:
Not found the disk


Expected results:
The disk should exist and usable.


Additional info:
  
No issue on
Red Hat Enterprise Linux release 8.4 (Ootpa)
4.18.0-305.el8.x86_64
qemu-kvm-5.2.0-16.module+el8.4.0+13043+9eb47245.11.x86_64
seabios-bin-1.13.0-2.module+el8.3.0+7353+9de0a3cc.noarch
edk2-ovmf-20200602gitca407c7246bf-4.el8.noarch
virtio-win-prewhql-0.1-214.iso

and

Red Hat Enterprise Linux release 8.2 (Ootpa)
4.18.0-305.el8.x86_64
qemu-kvm-4.2.0-18.module+el8.2.0+6278+dfae3426.x86_64
seabios-bin-1.13.0-1.module+el8.2.0+5520+4e5817f3.noarch
seabios-1.13.0-1.module+el8.2.0+5520+4e5817f3.x86_64
edk2-ovmf-20190829git37eef91017ad-9.el8.noarch
virtio-win-prewhql-0.1-214.iso


There is no issue on RHEL guest.
And RHEL guest boot fast.The fault disk looks like does not affect the boot.

Comment 1 John Ferlan 2021-12-03 17:04:01 UTC

Meirav - looks like something only on Windows - perhaps someone from your team has a better chance than someone on Klaus' team.  Perhaps also needs to switch component/subcomponent - that's not clear to me though.

Comment 3 Klaus Heinrich Kiwi 2022-02-21 13:36:31 UTC

Looks like this one is a guest-side driver problem, so moving to windows sst.

Comment 4 Vadim Rozenfeld 2022-02-23 01:55:59 UTC

can we give try to the drivers from build 215?
Thanks,
Vadim.

Comment 5 qing.wang 2022-02-23 06:41:35 UTC

Hit same issue on
Red Hat Enterprise Linux release 9.0 Beta (Plow)
5.14.0-56.el9.x86_64
qemu-kvm-6.2.0-9.el9.x86_64
seabios-bin-1.15.0-1.el9.noarch
edk2-ovmf-20220126gitbb1bba3d77-2.el9.noarch
virtio-win-prewhql-0.1-215.iso

Comment 12 qing.wang 2023-01-20 09:37:03 UTC

Hit same issue on

Red Hat Enterprise Linux release 9.2 Beta (Plow)
5.14.0-200.el9.x86_64
qemu-kvm-7.2.0-1.el9.stefanha202301041547.x86_64
seabios-bin-1.16.1-1.el9.noarch
edk2-ovmf-20221207gitfff6d81270b5-1.el9.noarch

python ConfigTest.py --testcase=block_iscsi_fault_disk --guestname=Win2019 --driveformat=virtio_scsi --firmware=default_bios   --customsparams="cdrom_virtio = isos/windows/virtio-win-prewhql-0.1-214.iso"

Comment 21 RHEL Program Management 2023-09-19 12:58:34 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 22 RHEL Program Management 2023-09-19 13:01:31 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

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