Xiaoling_Gao

@zhenyzha @YongxueHong Call for your review,thanks.

> Hello @xiagao , please take a look, thanks! I'm confused with the fact the shared dir is NOT seen at guest. Maybe you need to add numa config. guest_numa_nodes...

(1/3) Host_RHEL.m9.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.2.0.x86_64.io-github-autotest-qemu.virtio_fs_multi_users_access.localgroup_users.q35: STARTED (1/3) Host_RHEL.m9.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.2.0.x86_64.io-github-autotest-qemu.virtio_fs_multi_users_access.localgroup_users.q35: PASS (70.30 s) (2/3) Host_RHEL.m9.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.virtio_fs_multi_users_access.localgroup_users.q35: STARTED (2/3) Host_RHEL.m9.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.virtio_fs_multi_users_access.localgroup_users.q35: PASS (344.81 s) (3/3) Host_RHEL.m9.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.virtio_fs_multi_users_access.domain_users.q35: STARTED (3/3) Host_RHEL.m9.u1.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.virtio_fs_multi_users_access.domain_users.q35: PASS (373.04 s) Here are two minor issues. 1....

Thanks @nickzhq. I hit the following error on win10-i386, seems PsExec.exe does't work well on win10-i386. ShellCmdError: Shell command failed: '%systemdrive%\\/PsExec.exe /accepteula -u user1 -p U1pwd345?a %systemdrive%\\cmd_io_test.bat' (status: 1, output:...

Virtiofs and balloon related config are all included. The results are also good. LGTM (1/5) Host_RHEL.m8.u8.product_rhel.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.unattended_install.cdrom.extra_cdrom_ks.default_install.aio_threads.q35: STARTED (1/5) Host_RHEL.m8.u8.product_rhel.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.unattended_install.cdrom.extra_cdrom_ks.default_install.aio_threads.q35: PASS (1426.63 s) (2/5) Host_RHEL.m8.u8.product_rhel.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.balloon_in_use.with_shutdown.during_bg_test.q35: STARTED (2/5) Host_RHEL.m8.u8.product_rhel.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.balloon_in_use.with_shutdown.during_bg_test.q35: PASS (696.60 s)...

Test two cases related with virtiofs and balloon, both of them passed. (1/2) Host_RHEL.m9.u2.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.virtio_fs_share_data.with_cache.auto.q35: STARTED (1/2) Host_RHEL.m9.u2.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.virtio_fs_share_data.with_cache.auto.q35: PASS (241.84 s) (2/2) Host_RHEL.m9.u2.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.balloon_check.balloon_evict_and_enlarge.balloon_base.q35: STARTED (2/2) Host_RHEL.m9.u2.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2022.x86_64.io-github-autotest-qemu.balloon_check.balloon_evict_and_enlarge.balloon_base.q35: PASS (686.91 s) LGTM.

I tried to reproduce this issue with the latest rust virtiofsd and virtio driver(242) on Win11 guest, but didn't reproduce it. 1. Mounted one virtiofs shared dir. 2. Run fio...

> > 2. C:\Program Files (x86)\fio\fio\fio.exe" --name=stress --filename=Z:/test_file --ioengine=windowsaio --rw=write --direct=1 --size=1G --iodepth=256 --numjobs=128 --runtime=180000 --thread --bs=64k > > Where is fio.exe? I only have C:\Program Files\Virtio-Win\VioFS\virtiofs.exe Hi, you can...

> @kostyanf14 I ran virtiofsd 1.8.0 on Unraid and ran into the same memory leak. Could you share what io test did you do on the shared folder? I also...

I reproduced this issue with multiple source mapping from host to Win11 guest. Using IOmeter software to create a lot of disk read/write activity on the virtiofs shares. Here are...