Shared Folders – File System Errors in VM

[swillits]

I have a shared folder that gets mounted though VirtualBuddyShared, and often if the file is edited in the host OS, then afterwards in the guest OS it results in ENOENT / "No such file or directory" errors when trying to read the file (with something basic like cat or tail), even though ls on the directory does show that the file is there. I have to stop and restart the VM to solve it.

The host is 15.6.1 and the guest is 26.0.

Any suggestions on how to debug this?

[insidegui]

I've had this issue myself, but unfortunately I have no suggestions right now. It could be a driver bug in macOS itself, but if someone has any suggestions please let us know.

The scenario where I've reproduced this is as follows:

1 - [HOST] Create a file in the shared directory
2 - [GUEST] Access that file
3 - [HOST] Delete that same file then recreate it
4 - [GUEST] Try to access the file again, it won't work

[swillits]

At least I'm not alone. In that particular scenario I usually get EPERM, which I've also encountered a lot. Right now I'm also seeing a strange file caching problem where:

1 – [HOST] Create a file in the shared directory with pico, write "Hello." to it
2 – [GUEST] cat the file — I see "Hello."
3 – [HOST] Modify the file with pico, write "Hello, world!" to it
4 – [GUEST] cat the file — I see "Hello." still

Weird stuff. I'm sure this all needs to be in an Apple bug report, but I don't know how exactly to file that wrt to how VirtualBuddy is involved.

[insidegui]

Weird stuff. I'm sure this all needs to be in an Apple bug report, but I don't know how exactly to file that wrt to how VirtualBuddy is involved.

You can mention VirtualBuddy in your Feedback Assistant report and even include a link to this repo, I've done that before. Just be sure to mention that it's likely a OS/driver issue otherwise they'll tell you to contact the developer 😅