We're seeing limitations in host -> macOS VM changes syncing. Were using Anka, but we've also tried others. We're actually doing the exact implementation that others (the ones we found that are open source) do.
Here is a breakdown of what's supported:
| Create new file/folder | Host → Guest | ✅ Yes | New paths appear in the guest |
| Create new file/folder | Guest → Host | ✅ Yes | New paths appear on the host |
| Read existing contents | Host → Guest | ✅ Yes | Contents present at mount time are visible |
| Modify file in place | Guest → Host | ✅ Yes | Guest edits are written through to the host |
| Modify file in place | Host → Guest | ❌ No | Guest keeps stale contents for already-accessed files (macOS virtiofs caching) |
| Delete file/folder | Guest → Host | ✅ Yes | Removal is reflected on the host |
| Delete file/folder | Host → Guest | ❌ No | Guest still sees the path after the host deletes it (cached) |
Replace via temp + rename() (atomic) | Host → Guest | ✅ Yes | New inode/dentry; recommended way to update files from the host |
We're requesting a way to disable caching and/or allow the unsupported actions in the table to be supported.