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 1968234 - [virtio-win][vioscsi+viostor] Flush test failed with error "Caught std::exception: invalid stoi argument" -- win2022 guest
Summary: [virtio-win][vioscsi+viostor] Flush test failed with error "Caught std::excep...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.0
Hardware: x86_64
OS: Windows
medium
high
Target Milestone: rc
: 9.0
Assignee: Yvugenfi@redhat.com
QA Contact: Peixiu Hou
URL:
Whiteboard:
: 1968235 1968236 (view as bug list)
Depends On:
Blocks: 1968312
TreeView+ depends on / blocked
 
Reported: 2021-06-07 01:51 UTC by Peixiu Hou
Modified: 2023-05-28 01:30 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-07 08:15:11 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Peixiu Hou 2021-06-07 01:51:16 UTC 
Description of problem:
On Windows 2022 guest, the whql job "Flush Test" failed with error "Caught std::exception: invalid stoi argument". Hit this issue for both vioscsi and viostor driver.

Used latest HLK for Windows Server 2022:
  Manager Version: 2.7.3522.0
  Controller Version: 10.1.20348.20348
  Studio Version: 10.0.20348.1


Version-Release number of selected component (if applicable):
Guest os: Windows 2022
kernel-4.18.0-310.el8.x86_64
qemu-kvm-6.0.0-18.module+el8.5.0+11243+5269aaa1.x86_64
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
virtio-win-prewhql-199

How reproducible:
100%

Steps to Reproduce:
1. Boot Windows 2022 server up:
/usr/libexec/qemu-kvm -name 199SCS226435CAB -enable-kvm -m 6G -smp 8 -uuid 47f7b3a9-0072-4991-bc68-f2dbba29c2c5 -nodefaults -cpu Skylake-Server,hv_stimer,hv_synic,hv_time,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi -chardev socket,id=charmonitor,path=/tmp/199SCS226435CAB,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=199SCS226435CAB,node-name=my_file -blockdev driver=raw,node-name=my,file=my_file -device ide-hd,drive=my,id=ide0-0-0,bus=ide.0,unit=0 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/iso/ISO/Win2022/Windows_InsiderPreview_Server_vNext_en-us_20344.iso,node-name=my_cd,read-only=on -blockdev driver=raw,node-name=mycd,file=my_cd,read-only=on -device ide-cd,drive=mycd,id=ide0-1-0,bus=ide.1,unit=0 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=199SCS226435CAB.iso,node-name=my_iso,read-only=on -blockdev driver=raw,node-name=myiso,file=my_iso,read-only=on -device ide-cd,drive=myiso,id=ide0-1-1 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -M q35 -device pcie-root-port,bus=pcie.0,id=root1.0,multifunction=on,port=0x10,chassis=1,addr=0x7 -device pcie-root-port,bus=pcie.0,id=root2.0,port=0x11,chassis=2,addr=0x7.0x1 -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device e1000e,bus=root1.0,netdev=hostnet0,id=net0,mac=00:52:0d:27:06:07 -vga std -device virtio-scsi-pci,id=scsi0,bus=root2.0,num_queues=8 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=199SCS226435CAB_test.raw,node-name=my_scsi -blockdev driver=raw,node-name=myscsi,file=my_scsi -device scsi-hd,bus=scsi0.0,drive=myscsi,id=scsi-disk0,serial=whql_test

2. On HLK studio submit the job "Flush Test" 
3. Check the result

Actual results:
Failed

Expected results:
Passed

Additional info:
We have a manual errata# 41719 for Win10/win2019 guest, but for Windows server 2022, as we discussed, it's better to ask a new errata for it, thanks~
Comment 1 Peixiu Hou 2021-06-07 01:55:53 UTC 
*** Bug 1968235 has been marked as a duplicate of this bug. ***
Comment 2 Peixiu Hou 2021-06-07 01:58:05 UTC 
*** Bug 1968236 has been marked as a duplicate of this bug. ***
Comment 3 Peixiu Hou 2021-06-07 02:12:38 UTC 
Windows server 2022 info:
  OS Name: Microsoft Windows Server 2022 Datacenter
  Version: 10.0.20344 Build 20344

Thanks~
Peixiu
Comment 9 yimsong 2021-08-27 07:22:00 UTC 
Hit the same issue on win11 for both vioscsi and viostor driver,should we file a separate bug to track it？
Comment 10 Yvugenfi@redhat.com 2021-08-30 07:49:09 UTC 
(In reply to yimsong from comment #9)
> Hit the same issue on win11 for both vioscsi and viostor driver,should we
> file a separate bug to track it？

No need.
Comment 13 leidwang@redhat.com 2021-09-17 09:56:12 UTC 
Still hit this issue with virtio-win-prewhql-0.1-210(both vioscsi and viostor)

Error message:
Caught std::exception: invalid stoi argument
Comment 18 Peixiu Hou 2021-09-27 05:29:03 UTC 
Thanks all~ As comment#9 and comment#17, changed this issue to verified.
Note You need to log in before you can comment on or make changes to this bug.