virtio_fs_localfs_migration: Migrate localfs with different cache modes #4184
Conversation
zhencliu
force-pushed
the
virtiofs_migration_localfs
branch
10 times, most recently
from
70593da
to
7eb9f47
Compare
|
hi @hellohellenmao , would you please review this patch? I am not sure if this patch meet your expectation, I just follow Your palorion case's steps |
zhencliu
force-pushed
the
virtiofs_migration_localfs
branch
3 times, most recently
from
b8d9be4
to
54bce23
Compare
|
hi @hellohellenmao , would you please review it again? All test metrix was covered IMO, thanks. The following testing matrix is covered: Single node migration, with different localfs. |
|
Testing Win2022 and RHEL9.3 guest OS, all passed |
zhencliu
force-pushed
the
virtiofs_migration_localfs
branch
3 times, most recently
from
1662e04
to
2a44523
Compare
|
@xiagao Could you please help to take a review from windows perspective? |
Sure, will work on it after other tasks on hand. |
|
@fbq815 Could you please help to review here? Thanks. |
zhencliu
force-pushed
the
virtiofs_migration_localfs
branch
from
2a44523
to
44f08b6
Compare
| fs_driver = virtio-fs | ||
| fs_source_type = mount | ||
| fs_source_dir_fs = /var/tmp/virtio_fs_source | ||
| fs_source_dir_targetfs = /var/tmp/virtio_fs_target |
There was a problem hiding this comment.
Another thing to confirm with @hellohellenmao :
The migration happened on two nodes and the systemdisk is located in NFS server, is that correct?
There was a problem hiding this comment.
IMO systemdisk is not a problem as we are doing single node migration, the fs exported is the key
There was a problem hiding this comment.
Make sense. Then it's okay for single node migration.
The following testing matrix is covered: cache mode: auto, never, always, metadata writeback: enabled and disabled allow-direct-io enabled and disabled fs: single fs and two fs Signed-off-by: Zhenchao Liu <[email protected]>
zhencliu
force-pushed
the
virtiofs_migration_localfs
branch
from
44f08b6
to
550fa74
Compare
ID: 2967