Bug 2177673

Summary:	[virtio-win][fwcfg] Fwcfg - Windows update reports errors
Product:	Red Hat Enterprise Linux 9	Reporter:	Yvugenfi <yvugenfi>
Component:	virtio-win	Assignee:	Yvugenfi <yvugenfi>
virtio-win sub component:	virtio-win-prewhql	QA Contact:	Qianqian Zhu <qizhu>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	jinzhao, juzhang, leidwang, qizhu, vrozenfe, ymankad
Version:	9.2	Keywords:	Triaged, ZStream
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2203207 (view as bug list)		Environment:
Last Closed:	2023-09-05 09:25:42 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:	2203207

Description Yvugenfi@redhat.com 2023-03-13 10:53:52 UTC

Description of problem:
Error message:
Rejection Theme: Measure Failure Rejection Reason: Systemic Measure Failure Provide Measure ID(s): 26387215 ; 26387262 ADO bugId: 41872482: Bug ID(s) and Partner ID(s): Link to documentation: Link to reliability report (if applicable): Details: Rejected because Measure ID 26387215 (Percent of machines where the driver install process completes successfully) is failing. Please read more on "https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machines-where-driver-install-completes-successfully" Also rejected because Measure ID 26387262 (Percent of machines that installed a driver update and reported a PnP error code within two days of install) is failing. Please read more on "https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machines-installed-driver-update-and-reported-pnp-error-within-2-days" See the Plug and Play Extended Flight Report document for additional information on the failures. The "driver flight report" bug can be found by searching on Collaborate with the Submission ID. More info: https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/pnp-failure-report and https://docs.microsoft.com/en-us/collaborate/feedback-items-search#search

WS2019: https://partner.microsoft.com/en-us/dashboard/hardware/driver/13900037663368944/submission/1152921505695292063/ShippingLabel/400986558

WS2022: https://partner.microsoft.com/en-us/dashboard/hardware/driver/14512220675920185/submission/1152921505695292275/ShippingLabel/400982931

WS2016: https://partner.microsoft.com/en-us/dashboard/hardware/driver/13874752215706004/submission/1152921505695292133/ShippingLabel/400986612

Win11: https://partner.microsoft.com/en-us/dashboard/hardware/driver/14342041934756996/submission/1152921505695576774/ShippingLabel/401042005

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

Posible cause:
Can it be that fwcfg fails on a system with no vmcore device ? 
(But ACPI\QEMU0002 device is present by default) ?

If so then the entire FwCfgEvtDevicePrepareHardware logic needs to changed to let
the new driver to be loaded without HW resources allocated.

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yvugenfi@redhat.com 2023-03-14 14:21:04 UTC

Upstream PR: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/896

Comment 3 Qianqian Zhu 2023-03-20 07:24:29 UTC

Setting ITM to 16 as we need anther release to verify the issue.

Comment 4 leidwang@redhat.com 2023-03-23 03:16:31 UTC

Tested the new build with whql/function test,the results looks good to me.

1.Before this bug fix,if we install fwcfg  driver to a VM(no vmcoreinfo device), the fwcfg device status is not running.
screenshot:https://drive.google.com/file/d/1GZnkkjzRnsPDN1WrDWCEkAtT2p28qTt2/view?usp=share_link

2.After this bug fix,if we install fwcfg driver to a VM(no vmcoreinfo device), the device status is working properly.
screenshot:https://drive.google.com/file/d/1KYGetimXRphecn8A36flBXMV5XvH1_JJ/view?usp=share_link

Comment 5 Yvugenfi@redhat.com 2023-03-23 08:10:41 UTC

(In reply to leidwang from comment #4)
> Tested the new build with whql/function test,the results looks good to me.
> 
> 1.Before this bug fix,if we install fwcfg  driver to a VM(no vmcoreinfo
> device), the fwcfg device status is not running.
> screenshot:https://drive.google.com/file/d/1GZnkkjzRnsPDN1WrDWCEkAtT2p28qTt2/
> view?usp=share_link
> 
> 2.After this bug fix,if we install fwcfg driver to a VM(no vmcoreinfo
> device), the device status is working properly.
> screenshot:https://drive.google.com/file/d/1KYGetimXRphecn8A36flBXMV5XvH1_JJ/
> view?usp=share_link

Thanks a lot!