Have you considered changing the name in the viostor json

[zjmletang]

the name is Red Hat VirtIO SCSI Disk Device

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.

[kostyanf14]

@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 virtio-win/kvm-guest-drivers-windows#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

[zjmletang]

@kostyanf14 ,
I'm not sure if this is as expected. It seems that if we use the default name, the device found might not be the controller but the disk device. The test items for these two are different. I understand that we should be testing the controller and not the disk device（If I am wrong, please point it out to me)

This is the HLK test list under the default name

This is the HLK test list under "Red Hat Virtio SCSI controller"