virtio_fs_migration_kill_daemon: new case #4301

hellohellenmao · 2025-04-15T08:45:26Z

Kill the virtiofsd process during the migration process
Check that the VM is still running but the mount dir is not accessable.

ID: 3260

hellohellenmao · 2025-06-06T09:48:36Z

(1/2) Host_RHEL.m9.u6.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.6.0.x86_64.io-github-autotest-qemu.virtio_fs_migration_kill_daemon.source_daemon.q35: STARTED
(1/2) Host_RHEL.m9.u6.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.6.0.x86_64.io-github-autotest-qemu.virtio_fs_migration_kill_daemon.source_daemon.q35: PASS (148.98 s)
(2/2) Host_RHEL.m9.u6.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.6.0.x86_64.io-github-autotest-qemu.virtio_fs_migration_kill_daemon.target_daemon.q35: STARTED
(2/2) Host_RHEL.m9.u6.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.6.0.x86_64.io-github-autotest-qemu.virtio_fs_migration_kill_daemon.target_daemon.q35: PASS (147.33 s)

hellohellenmao · 2025-06-09T06:54:28Z

Rhel guest:
(1/2) Host_RHEL.m9.u6.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.6.0.x86_64.io-github-autotest-qemu.virtio_fs_migration_kill_daemon.source_daemon.q35: STARTED
(1/2) Host_RHEL.m9.u6.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.6.0.x86_64.io-github-autotest-qemu.virtio_fs_migration_kill_daemon.source_daemon.q35: PASS (147.63 s)
(2/2) Host_RHEL.m9.u6.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.6.0.x86_64.io-github-autotest-qemu.virtio_fs_migration_kill_daemon.target_daemon.q35: STARTED
(2/2) Host_RHEL.m9.u6.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.6.0.x86_64.io-github-autotest-qemu.virtio_fs_migration_kill_daemon.target_daemon.q35: PASS (150.61 s)

Windows guest:
(1/2) Host_RHEL.m9.u6.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2019.x86_64.io-github-autotest-qemu.virtio_fs_migration_kill_daemon.source_daemon.q35: STARTED
(1/2) Host_RHEL.m9.u6.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2019.x86_64.io-github-autotest-qemu.virtio_fs_migration_kill_daemon.source_daemon.q35: PASS (163.43 s)
(2/2) Host_RHEL.m9.u6.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2019.x86_64.io-github-autotest-qemu.virtio_fs_migration_kill_daemon.target_daemon.q35: STARTED
(2/2) Host_RHEL.m9.u6.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win2019.x86_64.io-github-autotest-qemu.virtio_fs_migration_kill_daemon.target_daemon.q35: PASS (202.13 s)

hellohellenmao · 2025-06-09T06:54:54Z

@xiagao @zhencliu Could you please help to take a review here? Thanks

qemu/tests/virtio_fs_migration_kill_daemon.py

zhencliu · 2025-06-23T09:15:58Z

qemu/tests/virtio_fs_migration_kill_daemon.py

+                    test.log.debug("Check the mount dir, which should be accessable")
+                    if os_type == "windows":
+                        if session.cmd_status(f"dir {fs_dest}\\", timeout=10):
+                            test.fail(


You will get a timedout exception if failed, so test.fail will not be executed

qemu/tests/virtio_fs_migration_kill_daemon.py

qemu/tests/cfg/virtio_fs_migration_kill_daemon.cfg

1. Kill the virtiofsd process during the migration process 2. Check that the VM's and mount directory's status Signed-off-by: Tingting Mao <[email protected]>

hellohellenmao force-pushed the 3260 branch 2 times, most recently from 68d73e9 to e51845f Compare April 15, 2025 09:05

hellohellenmao changed the title ~~virtio_fs_migration_kill_daemon: new case~~ virtio_fs_migration_kill_daemon: new case(WIP) Apr 15, 2025

hellohellenmao force-pushed the 3260 branch 9 times, most recently from c65a996 to d37cbc1 Compare April 18, 2025 02:45

hellohellenmao force-pushed the 3260 branch 18 times, most recently from 390026c to b344e3b Compare June 5, 2025 06:24

hellohellenmao force-pushed the 3260 branch 8 times, most recently from fcc0bb7 to ba7ee72 Compare June 6, 2025 09:40

hellohellenmao force-pushed the 3260 branch 4 times, most recently from 082ab31 to 394639a Compare June 9, 2025 06:11

hellohellenmao changed the title ~~virtio_fs_migration_kill_daemon: new case(WIP)~~ virtio_fs_migration_kill_daemon: new case Jun 9, 2025