Bug 1652422
| Summary: | [virtio-win][vioscsi+viostor] Flush test failed with error "Caught std::exception: invalid stoi argument" -- win2019 guest | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Peixiu Hou <phou> | ||||||||
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||||||
| virtio-win sub component: | virtio-win-prewhql | QA Contact: | lijin <lijin> | ||||||||
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |||||||||
| Severity: | high | ||||||||||
| Priority: | medium | CC: | ailan, bruce.chen, knoel, lijin, phou, virt-bugs, xiagao, yvugenfi | ||||||||
| Version: | 8.0 | Keywords: | TestBlocker | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | 8.0 | ||||||||||
| 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: | 2019-06-14 01:20:23 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: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1659244 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Peixiu Hou
2018-11-22 03:42:46 UTC
Created attachment 1507869 [details]
win2019 flush test failed package
viostor driver hit the same issue on win2019. do we fully copy with the flush test requirements (I mostly mean PDU controlled over SNMP) as described at https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/2dec1f67-b506-4434-8bdf-763147ad8f0b ? Thanks, Vadim. (In reply to Vadim Rozenfeld from comment #3) > do we fully copy with the flush test requirements (I mostly mean PDU > controlled over SNMP) as described at > https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/2dec1f67- > b506-4434-8bdf-763147ad8f0b ? > Hi vadim, We do not set any configuration for other guest as well, only hit this issue on HLK 1809 version. And I checked the link your pasted, it seems Flush Test for win10-1809 and win2019 have not been updated, shows supported latest release is win10-1803. As we tested before, the flush test step in HLK 1809 is different with in HLK 1803, I saved the pictures for both controller, please refer to attachments. Thanks~ Peixiu > Thanks, > Vadim. Created attachment 1512024 [details]
Flush test steps on HLK 1803 controller
Created attachment 1512025 [details]
Flush test steps on HLK 1809 controller
(In reply to Peixiu Hou from comment #5) > Created attachment 1512024 [details] > Flush test steps on HLK 1803 controller could you please post hlkx file? Thanks, Vadim. Support case opened with MS: Incident Title "Flush Test" is failing on Windows 10 1809 and Windows Server 2019 for paravirtualized storage adapters Support Request Number:118122719493805 MS answer: Hello Yan Vugenfirer, To pass “Flush Test” for Windows server 2019, please reference manual errata# 41719. And I’ll confirm with our product team if you can use this errata for Windows 10 1809 submission. Thanks very much! Best Regards, Tianwei Yang (In reply to Yan Vugenfirer from comment #10) > MS answer: > > Hello Yan Vugenfirer, > > To pass “Flush Test” for Windows server 2019, please reference manual > errata# 41719. > > And I’ll confirm with our product team if you can use this errata for > Windows 10 1809 submission. Thanks very much! > > Best Regards, > Tianwei Yang Hi,Yan We hit the same issue on Windows10-32/64 1809, can we use the errata# 41719 ? Thanks, xiaoling (In reply to xiagao from comment #14) > (In reply to Yan Vugenfirer from comment #10) > > MS answer: > > > > Hello Yan Vugenfirer, > > > > To pass “Flush Test” for Windows server 2019, please reference manual > > errata# 41719. > > > > And I’ll confirm with our product team if you can use this errata for > > Windows 10 1809 submission. Thanks very much! > > > > Best Regards, > > Tianwei Yang > > Hi,Yan > > We hit the same issue on Windows10-32/64 1809, can we use the errata# 41719 ? > > Thanks, > xiaoling Yes. When I asked for Windows Server 2019 erratum, I also asked them for Windows 10 1809. Hi,Yan We also hit the same issue on Win10-32/64 1909, can we use the manual errata# 41719 ? Thanks, xiaoling (In reply to xiagao from comment #17) > Hi,Yan > > We also hit the same issue on Win10-32/64 1909, can we use the manual > errata# 41719 ? > > Thanks, > xiaoling Yes. Hi, Yan We also hit the same issue on Windows 10 1809 or later. Could you tell us How to use errata# 41719 to pass the HLK"? Best Wishes, Bruce Chen (In reply to Bruce from comment #19) > Hi, Yan > > We also hit the same issue on Windows 10 1809 or later. Could you tell us > How to use errata# 41719 to pass the HLK"? > > Best Wishes, > Bruce Chen IIRC it was a manual errata. You need to apply for it. There is some guideline how to do it at https://github.com/virtio-win/kvm-guest-drivers-windows/issues/216 As far as I remember it is applicable for the next versions as well. I suggest to make a submission and reference the manual errata as usual. If the submission will fail, please tell me and I will open a support case with MS. Best regards, Yan. (In reply to Bruce from comment #19) > Hi, Yan > > We also hit the same issue on Windows 10 1809 or later. Could you tell us > How to use errata# 41719 to pass the HLK"? > > Best Wishes, > Bruce Chen Sorry, my mistake. Each company needs to apply for the manual errata. You should open support ticket with MS: https://support.microsoft.com/en-us/getsupport?wf=0&tenant=ClassicCommercial&oaspworkflow=start_1.0.0.0&locale=en-us&supportregion=en-us&pesid=15720&ccsid=636045111834205065 Hi,Yan We also hit the same issue on Windows 2022, can we use the manual errata# 41719 ? Thanks, Peixiu (In reply to Peixiu Hou from comment #23) > Hi,Yan > > We also hit the same issue on Windows 2022, can we use the manual errata# > 41719 ? > > Thanks, > Peixiu Hi Peixiu, I think it is better to ask for the new errata for Windows 2022. Please write the exact build you are using for Windows 2022 and the HLK Kit version. Also, please open a new BZ. Thanks, Yan. (In reply to Yvugenfi from comment #24) > (In reply to Peixiu Hou from comment #23) > > Hi,Yan > > > > We also hit the same issue on Windows 2022, can we use the manual errata# > > 41719 ? > > > > Thanks, > > Peixiu > > Hi Peixiu, > > I think it is better to ask for the new errata for Windows 2022. > > Please write the exact build you are using for Windows 2022 and the HLK Kit > version. > > Also, please open a new BZ. > Hi Yan, I Filed a new bz for this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1968234 Thanks a lot~ Peixiu > Thanks, > Yan. |