search

HCK-CI / AutoHCK

AutoHCK is a tool for automating HCK/HLK testing, doing all the boilerplate steps in the process leaving you with simply choosing which driver you want to test on what os.
BSD 2-Clause "Simplified" License
23 stars 13 forks source link

Have you considered changing the name in the viostor json #400

Open zjmletang opened 5 days ago

zjmletang commented 5 days ago

the name is Red Hat VirtIO SCSI Disk Device image

However, we noticed that during the HLK test, the default device name is 'Red Hat VirtIO SCSI controller'. If we use the current default name in the JSON, it might cause the HLK test to not find the device. image

kostyanf14 commented 4 days ago

@zjmletang

First of all, we plan to remove drivers from the AutoHCK repo as this is more virtio-win-specific, something like a repo config for CI. Also, an organization can build drivers with other vendor strings but we specify RedHat.

Regarding your question, I don't understand why this happens for you because we use this config for our CI and it works.

In logs of https://github.com/virtio-win/kvm-guest-drivers-windows/pull/1110 we can found:

I, [2024-06-25T12:10:09.003415 #265270]  INFO -- : Searching for target Red Hat VirtIO SCSI Disk Device (type 0) on CL1
I, [2024-06-25T12:10:10.099774 #265270]  INFO -- : Adding target Red Hat VirtIO SCSI Disk Device on CL1 to project viostor-Win2022x64
I, [2024-06-25T12:10:18.378409 #265270]  INFO -- : Applying microsoft's playlist