Vadim Rozenfeld

@kroese Does it happen during fresh install or the driver update? Can you post the qemu command line to try reproducing the problem? Thanks, Vadim.

@kroese Are you working on unintended install or trying to add virtio-win drivers to WinPE image? Btw, how does it work on Win11 22H2/23H2 ? Thanks, Vadim.

The pvpanic-pci driver in virtio-win-0.1.248 is not attestation signed. Unfortunately, the upcoming public release virtio-win-0.1.262 (which should be available in a week) will also have the same problem. We will...

@YanVugenfirer sure. vrozenfe@milly:/run/media/vrozenfe/virtio-win-0.1.266/pvpanic$ tree -f * | grep -i pvpanic-pci ├── 2k16/amd64/pvpanic-pci.cat ├── 2k16/amd64/pvpanic-pci.inf ├── 2k19/amd64/pvpanic-pci.cat ├── 2k19/amd64/pvpanic-pci.inf ├── 2k22/amd64/pvpanic-pci.cat ├── 2k22/amd64/pvpanic-pci.inf │   ├── 2k25/amd64/pvpanic-pci.cat │   ├── 2k25/amd64/pvpanic-pci.inf ├── 2k25/ARM64/pvpanic-pci.cat...

@6-dehan Do we have a Jira issue for tracing this problem? Thanks, Vadim.

@kroese Please ping me at vrozenfe_at_redhat_dot_com Best, Vadim.

@kroese We normally use Windows images distributed via the official Microsoft channels like MSDN subscription. We do use images distributed via Microsoft Partner Centre Portal Canary channel and Windows Insider...

@kroese Let me check it on IoT LTSC image 26100.1.240331-1435.ge_release_CLIENT_IOT_LTSC_EVAL_x64FRE_en-us.iso available from MSDN subscription download first. Best, Vadim.

Didn't have any problem installing viogpudo driver on 26100.1.240331-1435.ge_release_CLIENT_IOT_LTSC_EVAL_x64FRE_en-us.iso (qemu) info version 8.2.50v8.2.0-645-g977542ded7 [vrozenfe@milly tmp]$ uname -a Linux milly 6.5.12-100.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Nov 20 22:28:44 UTC 2023 x86_64...