Fusion

 View Only

 macOS Guest: Possibly complex sharing question

metaning's profile image
metaning posted May 22, 2024 01:09 PM

So I'm still learning virtualising stuff, and was wondering if someone could check my math, so to speak...

I want to virtualise an already running iTunes configuration (for reasons) which on a real computer had its library set initially to a Local drive "Music", and then that drive was migrated to a different machine and shared over the network as an SMB share "Music".

I'd like to eliminate the SMB sharing requirement now that the drive is directly attached to the Host system on which VMWare is running.

Using VMWare's folder sharing, I can make the drive available to the guest system, but it's at /Volumes/VMWare Shared Folders/Music which will look different to the iTunes instance (which it can't, again for reasons).

So, I created a symlink in /Volumes:

sudo ln -s /Volumes/VMware\ Shared\ Folders/Music /Volumes

so now /Volumes/Music resolves to the Music volume on my host machine, which as far as I can tell, is exactly what iTunes would have seen trying to locate its library on a directly attached drive named "Music".

Does that seem right?

Thanks.

Technogeezer's profile image
Technogeezer

It is generally considered bad practice to share an Music app's folders with file sharing. Strange and not-so-good things can happen if both sides try to open Music at the same time, especially if they are running different versions of the Music app.

Your shell command is flawed as well. You're trying to create a symlink from the "/Volumes/VMware Shared Folders" mount point to /Volumes. That's going to try and overwrite /Volumes with the symlink - which is bad.  /Volumes is a folder that serves as the system-wide mount point for all external volumes on the system. macOS isn't going to like replacing that empty folder with a symlink that points to something in the symlink 

The other alternative is to investigate Apple documentation and tech notes on how to move the Music library to another place. That's easily done with current versions of macOS but you'd have to check for the version of macOS that you're virtualizing.

Why not simply move/import the files from the disk on the host into the VM? Vmware's folder sharing isn't the most robust solution.