This probably a very specialized and a bit esoteric discussion.
But it may help some people who may consider going the same route as I did. I have no Linux based players (which most Linux discussions are about it seems). I have classic Slimdevices and Logitech players. My goal is to keep them running. They rock (IMHO).
I decided to run LMS on a dedicated VM (details in my sig) because I liked the idea of immediate portability; i.e. if I upgrade my main machine, or decide to turn it off or run it elsewhere, al I have to do is spin up the virtual machine (Ubuntu 16.04 with LMS 7.9) elsewhere and it will run, right?
Unfortunately it's not quite as easy, intuitive and immediate. 3 things don't migrate well:
1. Network configuration. Go for bridged. It'll save you a lot of issues with LMS. You have to set that up in the VM management sw, not the vm itself.
2. Music directory visibility to LMS. I have no idea why that is. I would have assumed if you have the same NTFS drive connected to the exact same vm running ubuntu, hey, the fastab stuff should work right away when you connect the external NTFS drive. But that is not so. You'll have to mess about with your fstab again.
3. Network accessibility of your music collection aka Samba configuration. Gone too when you migrate the vm. Odd. I like to have that because I tend to rip new CDs on my Win10 dbPoweramp app, and then easily drop them into the music directory (owned by the Ubuntu VM).
So while that makes my goal of having "immediate migration" ability moot, I shall stick to this configuration model. Simply because, while a tad frustrating at times, it keeps my Linux command line fundamentals going some.
I have noticed that with some recent Ubuntu versions the headache had become less, but some basic stuff in the areas described above remains a tad unpredictable.
Takeaway: don't expect your OVA vm files to transparently work elsewhere, even when you bring the exact same external drive to the table...
But it may help some people who may consider going the same route as I did. I have no Linux based players (which most Linux discussions are about it seems). I have classic Slimdevices and Logitech players. My goal is to keep them running. They rock (IMHO).
I decided to run LMS on a dedicated VM (details in my sig) because I liked the idea of immediate portability; i.e. if I upgrade my main machine, or decide to turn it off or run it elsewhere, al I have to do is spin up the virtual machine (Ubuntu 16.04 with LMS 7.9) elsewhere and it will run, right?
Unfortunately it's not quite as easy, intuitive and immediate. 3 things don't migrate well:
1. Network configuration. Go for bridged. It'll save you a lot of issues with LMS. You have to set that up in the VM management sw, not the vm itself.
2. Music directory visibility to LMS. I have no idea why that is. I would have assumed if you have the same NTFS drive connected to the exact same vm running ubuntu, hey, the fastab stuff should work right away when you connect the external NTFS drive. But that is not so. You'll have to mess about with your fstab again.
3. Network accessibility of your music collection aka Samba configuration. Gone too when you migrate the vm. Odd. I like to have that because I tend to rip new CDs on my Win10 dbPoweramp app, and then easily drop them into the music directory (owned by the Ubuntu VM).
So while that makes my goal of having "immediate migration" ability moot, I shall stick to this configuration model. Simply because, while a tad frustrating at times, it keeps my Linux command line fundamentals going some.
I have noticed that with some recent Ubuntu versions the headache had become less, but some basic stuff in the areas described above remains a tad unpredictable.
Takeaway: don't expect your OVA vm files to transparently work elsewhere, even when you bring the exact same external drive to the table...