virtio_fs_nfs_migration: Virtiofs migration testing over NFS

[zhencliu]

The following testing matrix is covered:
cache mode:
auto, never, always, metadata
writeback:
enabled and disabled
allow-direct-io
enabled and disabled
file-handles
mandatory and never

ID: 2966

[zhencliu]

Hi @hellohellenmao , would you please review this patch? Testing on RHEL9.3 and Win2022 has passed, thanks.

[hellohellenmao]

Hi @zhencliu
For this case, still need to cover the File handles matrix as below(Also in the Setup part in polarion case)

source:
# /usr/libexec/virtiofsd --shared-dir /home/timao/virtiofsd/source_mnt/ --socket-path /home/timao/virtiofsd/source_virtiofsd.sock --inode-file-handles=mandatory --migration-mode=file-handles --modcaps=+dac_read_search --cache auto & (working and migrating using file handles)
# /usr/libexec/virtiofsd --shared-dir /home/timao/virtiofsd/source_mnt/ --socket-path /home/timao/virtiofsd/source_virtiofsd.sock --inode-file-handles=never --migration-mode=file-handles --modcaps=+dac_read_search  --cache auto & (working without file handle and migrating using file handles)
target:
# /usr/libexec/virtiofsd --shared-dir /home/timao/virtiofsd/tgt_mnt/ --socket-path /home/timao/virtiofsd/tgt_virtiofsd.sock --modcaps=+dac_read_search --cache auto &

Thanks.

[XueqiangWei]

Hi @fbq815 , @xiagao, could you please help review it? Many thanks.

[fbq815]

@zhencliu we use memory-backend-file on s390x when we use memory-backend with virtio-fs, please reference to the usage of avocado-framework/avocado-vt@85915c0

[fbq815]

@zhencliu s390x.io-github-autotest-qemu.virtio_fs_nfs_migration.file_handles_mandatory.dio.cache_mode_never.s390-virtio:ERROR: 'NoneType' object has no attribute 'close' (12.06 s)
details added in the jira task

[xiagao]

@zhencliu s390x.io-github-autotest-qemu.virtio_fs_nfs_migration.file_handles_mandatory.dio.cache_mode_never.s390-virtio:ERROR: 'NoneType' object has no attribute 'close' (12.06 s) details added in the jira task

win2025 on x86_64 also has this issue.