avocado-vt
avocado-vt copied to clipboard
update driverstore path to get driver status
For INF isolation all drivers moved to DriverStore (C:\WINDOWS\system32\DriverStore\FileRepository). Each installation creates a new directory in the DriverStore folder depending on the driver hash. ID: 2220
(1/1) Host_RHEL.m9.u5.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2025.x86_64.io-github-autotest-qemu.block_resize.with_iozone.with_data_disk.fmt_qcow2.default_partition.q35: STARTED (1/1) Host_RHEL.m9.u5.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2025.x86_64.io-github-autotest-qemu.block_resize.with_iozone.with_data_disk.fmt_qcow2.default_partition.q35: PASS (280.00 s)
Hi @xiagao
Thanks for your fix, I found an another issue with this patch: There're 2 vioscsi.sys file exists, and with this code, it will attach 2 file in one command, that will fail. I pasted the log link to the issue.
Thanks~ Peixiu
@peixiu The patch was updated, could you please have another try? Thank you.
Hi @xiagao
Thanks for your fix, I found an another issue with this patch, you can see this picture:
There're 2 vioscsi.sys file exists, and with this code, it will attach 2 file in one command, that will fail. I pasted the log link to the issue.
Thanks~ Peixiu
Hi @yanglei-rh, You may need to know this problem. Our netkvm also can meet this problem.
Hi @xiagao Thanks for your fix, I found an another issue with this patch, you can see this picture:
There're 2 vioscsi.sys file exists, and with this code, it will attach 2 file in one command, that will fail. I pasted the log link to the issue. Thanks~ Peixiu
Hi @yanglei-rh, You may need to know this problem. Our netkvm also can meet this problem.
This issue is fixed in this patch.
@leidwang Could you please help review this patch?
@peixiu The patch was updated, could you please have another try? Thank you.
Tested with the latest code, The single_driver_install can be passed. Thanks!
Acked-by: Peixiu Hou [email protected]
This patch also can help resolve "ERROR: netkvm driver is not running" issues.
@vivianQizhu Could you please help review? Thanks.
(4/6) Host_RHEL.m9.u5.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win11.x86_64.io-github-autotest-qemu.block_resize.with_iozone.with_data_disk.fmt_qcow2.default_partition.q35: STARTED (4/6) Host_RHEL.m9.u5.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win11.x86_64.io-github-autotest-qemu.block_resize.with_iozone.with_data_disk.fmt_qcow2.default_partition.q35: PASS (329.47 s) (5/6) Host_RHEL.m9.u5.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2019.x86_64.io-github-autotest-qemu.block_resize.with_iozone.with_data_disk.fmt_qcow2.default_partition.q35: STARTED (5/6) Host_RHEL.m9.u5.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2019.x86_64.io-github-autotest-qemu.block_resize.with_iozone.with_data_disk.fmt_qcow2.default_partition.q35: PASS (534.04 s) (6/6) Host_RHEL.m9.u5.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.block_resize.with_iozone.with_data_disk.fmt_qcow2.default_partition.q35: STARTED (6/6) Host_RHEL.m9.u5.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.block_resize.with_iozone.with_data_disk.fmt_qcow2.default_partition.q35: PASS (348.90 s) @vivianQizhu Could you please have a check it?