I have done the following
Steps to reproduce
Virtualization.framework has a bug with opening hardlinks in some cases, which is how our single file mount idea is structured (we create a hardlink to the file they asked to share). Keeping this open so we can revert back to our hardlink approach on some builds when it is fixed.
Current behavior
Sometimes opening a single file mount returns EACCES.
Expected behavior
Opening hardlinks in the guest to work, and not return EACCES.
Environment
Relevant log output
Code of Conduct
I have done the following
Steps to reproduce
Virtualization.framework has a bug with opening hardlinks in some cases, which is how our single file mount idea is structured (we create a hardlink to the file they asked to share). Keeping this open so we can revert back to our hardlink approach on some builds when it is fixed.
Current behavior
Sometimes opening a single file mount returns EACCES.
Expected behavior
Opening hardlinks in the guest to work, and not return EACCES.
Environment
Relevant log output
Code of Conduct