Bug 1861229

My bad. Will fix it soon.
Thanks,
Vadim.

Hi Dehan,

Can you give a try to build b193
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1456891

Thanks,
Vadim.

(In reply to Vadim Rozenfeld from comment #6)

> https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1456891

this version is working. and testing virtio-vga cases from that sheet now.
thanks

(In reply to Vadim Rozenfeld from comment #0)
> Description of problem:
> Currently there is no custom driver to support virtio-gpu device on Windows
> platforms
> 
> Version-Release number of selected component (if applicable):
> Windows8/8.1/10
Hi Vadim,
From this, I also wanna double confirm with you that virtio-gpu device is not supported windows server like win2012/win2016/win2019 right? 
thanks

(In reply to dehanmeng from comment #8)
> (In reply to Vadim Rozenfeld from comment #0)
> > Description of problem:
> > Currently there is no custom driver to support virtio-gpu device on Windows
> > platforms
> > 
> > Version-Release number of selected component (if applicable):
> > Windows8/8.1/10
> Hi Vadim,
> From this, I also wanna double confirm with you that virtio-gpu device is
> not supported windows server like win2012/win2016/win2019 right? 
> thanks

You should be able to run:
- Win8 driver on WS2012 and WS2012R2
- Win10 on WS2016 and WS2019

Just for your information:
Technically, DOD (Display Only Drivers) are supposed to be used on server platforms only,
while desktops systems should be equipped with Full WDDM drivers.

Thanks Dehan,

couple of things : 
- to pass "Verify VESA and CEA ...." parameter ".edid=off" needs to be added  to virtio-vga device
- "test for EDID Requirements.." is a manual test. It's dependes on a user input if it succeeds or fails.
- I need to see the entire qemu command line for all platforms, because it's a bit strange that "opsstendby"
says that S3/S4 are not supported.

Best,
Vadim.

(In reply to Vadim Rozenfeld from comment #13)
> Thanks Dehan,
> 
> couple of things : 
> - to pass "Verify VESA and CEA ...." parameter ".edid=off" needs to be added
> to virtio-vga device
> - "test for EDID Requirements.." is a manual test. It's dependes on a user
> input if it succeeds or fails.
> - I need to see the entire qemu command line for all platforms, because it's
> a bit strange that "opsstendby"
> says that S3/S4 are not supported.
> 
> Best,
> Vadim.

Huge thanks, Vadim,
for now I'm running 194 whql test and I'll do what you said as above in the first two points so that I'll update 194 test result pkgs then. and for entire qemu-command line I've update into that link as comment 12, you can have a check with that. 
thanks
Dehan.

Hi Basil,
Can you please comment on the server features that need to be activated
to make HCK happy?

Many thanks,
Vadim.

(In reply to Vadim Rozenfeld from comment #17)
> Hi Basil,
> Can you please comment on the server features that need to be activated
> to make HCK happy?
> 
> Many thanks,
> Vadim.

Hi Vadim,

First I must say that I didn't get to a point where all the tests passed yet,
this means that the following steps should solve some of the failures but not all.
In my setup, I used Windows server 2019 core version, so first of all i installed
Windows Feature On Demand package.
Installation instructions: https://docs.microsoft.com/en-us/windows-server/get-started-19/install-fod-19#:~:text=The%20Server%20Core%20App%20Compatibility,)%2C%20see%20Features%20On%20Demand.
ISO download link: https://software-download.microsoft.com/download/pr/17763.1.180914-1434.rs5_release_amd64fre_SERVER-FOD-PACKAGES_OEM_amd64fre_MULTI.iso 

Also for DXGI tests, make sure to download the right graphics package for hlk and install it on client.
For windows 2019 use the package for 1809.
Download link: https://docs.microsoft.com/en-us/windows-hardware/test/hlk/#graphics

reviewing the failures from HLK packages above, most of the failures look like 
cancelled tests that failed to run.
if the case is missing packages then relevant errors might be seen on the client during test run.
access to the test setup (studio & client) might be more informative than HLK package.

Thanks,
Basil

(In reply to Basil Salman from comment #19)
> (In reply to Vadim Rozenfeld from comment #17)
> > Hi Basil,
> > Can you please comment on the server features that need to be activated
> > to make HCK happy?
> > 
> > Many thanks,
> > Vadim.
> 
> Hi Vadim,
> 
> First I must say that I didn't get to a point where all the tests passed yet,
> this means that the following steps should solve some of the failures but
> not all.
> In my setup, I used Windows server 2019 core version, so first of all i
> installed
> Windows Feature On Demand package.
> Installation instructions:
> https://docs.microsoft.com/en-us/windows-server/get-started-19/install-fod-
> 19#:~:text=The%20Server%20Core%20App%20Compatibility,
> )%2C%20see%20Features%20On%20Demand.
> ISO download link:
> https://software-download.microsoft.com/download/pr/17763.1.180914-1434.
> rs5_release_amd64fre_SERVER-FOD-PACKAGES_OEM_amd64fre_MULTI.iso 
> 
> Also for DXGI tests, make sure to download the right graphics package for
> hlk and install it on client.
> For windows 2019 use the package for 1809.
> Download link:
> https://docs.microsoft.com/en-us/windows-hardware/test/hlk/#graphics
> 
> reviewing the failures from HLK packages above, most of the failures look
> like 
> cancelled tests that failed to run.
> if the case is missing packages then relevant errors might be seen on the
> client during test run.
> access to the test setup (studio & client) might be more informative than
> HLK package.
> 
> Thanks,
> Basil

Thank you a lot, Basil.
Best,
Vadim.

Hi Vadim,
We all know that the ITM16 is comming, so I spent a lot of time to test the basic cases and debug for whql test. here are some situations we're facing right now. paste them here so that we can make sure whether we'll release this viogpudo driver to customer on time.

[1]For functional test: win10-like/win8-like guest can run all basic cases, I mean those guest which are just installed one device virtio-vga in guest. all cases can pass without existed bugs. those existed bugs are hitting problems with multiple viogpudo driver.

[2] For whql test: 
  1). win10-like guest: still have four jobs got failed:
    (1). DXGI Gamma Ramps
    (2). Gamma correction
    (3). Gamma correction (WoW64)
    (4). HyperVisor Code Integrity Readiness Test  --> will be fixed like you said.
  2). Win8-64/win2012-64 still hit black screen situation; win8.1-64 and win2012R2 like following:
    (1). Device driver INF Verification Test (Certification)
    (2). Display mode filter check
    (3). DXGI Gamma Ramps
    (4). VSYNC inphase
    (5). WDDM CCD Test for Forced Projection
    (6). WDDM CCD Test for QueryHardware Caps
    (7). WDDM CCD Test Validation of Basic Topology(Single Mon)
    (8). WDDM CCD Test for verifying the display device connectivity status
    (9). Driver Memory Test
    Still working on debug them. Could you please help to resolve them? appreciate it.
according above situations to discuss what this bug's status should be. if you get any ideas, please let me know.

Thanks a lot
Dehan Meng

(In reply to dehanmeng from comment #27)
>     (4). HyperVisor Code Integrity Readiness Test  --> will be fixed like
> you said.

Hi Dehan,
Can you please give a try to a new driver from build 196 available at 
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1509663

Thanks,
Vadim.

(In reply to Vadim Rozenfeld from comment #28)
> (In reply to dehanmeng from comment #27)
> >     (4). HyperVisor Code Integrity Readiness Test  --> will be fixed like
> > you said.
> 
> Hi Dehan,
> Can you please give a try to a new driver from build 196 available at 
> https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1509663
> 
> Thanks,
> Vadim.

Hi Vadim,
Whether the qemu-command-line sort of like the stuff from below link will hit "Graphic disabled display", because the guest hit lots of time problems like that, and the process of testing stopped. anyway, I debugged them and they're running looks good for now. result will be update today anyway.
thanks
Dehan

recently hit a uncommon problem 'bsod' for testing guest-agent on win10-20H20_x86 guest, case is 42-Host_RHEL.m8.u4.product_av.qcow2.virtio_scsi.up.virtio_net.Guest.Win10.x86_64.io-github-autotest-qemu.qemu_guest_agent.virtio_serial.check_os_info.q35,

packages version:
    kernel-4.18.0-278.el8.dt3.x86_64
    qemu-kvm-5.2.0-4.module+el8.4.0+9676+589043b9.x86_64
    virtio-win-prewhql-193
    seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
    RHEL-8.4.0-20210128.d.2

log link here: http://fileshare.englab.nay.redhat.com/pub/logs/win10_20H2_32_guest_agent/test-results/42-Host_RHEL.m8.u4.product_av.qcow2.virtio_scsi.up.virtio_net.Guest.Win10.i386.io-github-autotest-qemu.qemu_guest_agent.virtio_serial.check_os_info.q35/

(In reply to dehanmeng from comment #40)

(In reply to dehanmeng from comment #40)
> recently hit a uncommon problem 'bsod' for testing guest-agent on
> win10-20H20_x86 guest, case is
> 42-Host_RHEL.m8.u4.product_av.qcow2.virtio_scsi.up.virtio_net.Guest.Win10.
> x86_64.io-github-autotest-qemu.qemu_guest_agent.virtio_serial.check_os_info.
> q35,

sorry, update to wrong place, ignore it.

Hi all, 

The good news is the whql test for guests 'Win10-32/Win10-64/win2019/win2016' has been all passed with virtio-win-prewhql-196.iso. report will be updated soon. so now there are just leave win8-like guests still get fail jobs. thanks for you all efforts.

Best,
Dehan Meng

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (virtio-win bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:1959