FYI for now I have disabled the VM and simply spun up the Windows LMS
app - it's far less trouble right now.
That said I will most definitely re-create an Ubuntu VM with better
built-in portability, but it will require a little research. :-) Fact of
the matter is that the old VM has been very
I have been reading the different suggestions with great interest.
There are man ways to skin this particular cat indeed. :-)
The main lesson is that it isn't as straight-forward as I thought it
would be, as evidenced by all the replies, too.
I have decided to create an entirely new VM over
Yes my bad, it's not WINS, it's in the regular Netbios protocol.
Works via broadcasts over the LAN.
https://support.microsoft.com/en-us/help/119493/netbios-over-tcp-ip-name-resolution-and-wins
https://support.microsoft.com/en-us/help/172218/microsoft-tcp-ip-host-name-resolution-order
Looks like
epoch1970 wrote:
> WINS name resolution will take care of that, its built in Windows
> machines. No need for a DNS server.
Wins has "just the same (in this case)" as DNS" - to use it youll need
to setup a Winsserver with a static IP for all the clients.
To activate wins in these days you'll
Which is entirely why I suggested hgfs mount in the first couple of
posts...
-Transcoded from Matt's brain by Tapatalk-
--
Hardware: 3x Touch, 1x Radio, 2x Receivers, 1 HP Microserver NAS with
Debian+LMS 7.9.0
Music: ~1300 CDs, as 450 GB of 16/44k FLACs. No less than 3x 24/44k
albums..
DJanGo wrote:
> To use e.g \\DESKTOP\music - you'll need an active local dns
> Server.
> Most of the homeusers / people who think they need "that" sort of howto
> didnt know nothing about setting up a DNS Server.
WINS name resolution will take care of that, itÂ’s built in Windows
machines. No
epoch1970 wrote:
> 3. If the SMB shares use names, e.g \\DESKTOP\music or \\MYVM\newstuff
> then there shouldn't be a problem. If sharing/mounting by IP address,
> there could be a problem across installs?
To use e.g \\DESKTOP\music - you'll need an active local dns
Server.
Most of the
pablolie wrote:
> 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
ok...
Since he only wrotes "Ubuntu" you would think of Ubuntu Desktop and me
on Ubunti Server.
> For someone that just wants to enjoy their music on LMS Those should go the
> Windows Way... *lol*
Must be a reason to run a lms on linux on a Windows System.
> Takeaway: don't expect your OVA vm
DJanGo wrote:
> Hi,
> your 1.st and 2.nd statement didnt match together...
> And its not helping any further to this topic - you need to adjust
> things whenever something outside changes.
>
> There is a lot more brain involved to handle a task like that as just
> use a out of the box fedore
Zounder1 wrote:
> Vortexbox is a super simple lightweight Linux distribution *that
> includes LMS, Samba shares and a bunch of useful utilities.* It is dead
> simple to install and setup.
>
> I have used Virtualization for over 10 years and* I always try and setup
> VMs that are as lightweight
pablolie wrote:
> Takeaway: don't expect your OVA vm files to transparently work
> elsewhere, even when you bring the exact same external drive to the
> table...
You cant expect a funtion from a tool thats never designed for this
function...
Using the Network in Bridge Mode:
The origin LMS was
Hm, next time you want to Virtualize LMS, I would strongly suggest you
create a VM using Vortexbox.
Vortexbox is a super simple lightweight Linux distribution that includes
LMS, Samba shares and a bunch of useful utilities. It is dead simple to
install and setup.
I have used Virtualization for
You could use two vmdks... ;) Yeah I would generally say that's a
better idea than lumping it all in one big image.
You could also get the shared folders stuff working. That will always
consistently mount the same windows content in the same place anytime
you power up the VM.
-Transcoded from
drmatt wrote:
> Yes. Or several glued together in an LVM volume group (I wouldn't create
> vmdks bigger than 2TB). Back it up from inside the VM if you prefer, you
> don't have to back it up as a single entity, it doesn't really matter
> how you do it. Rsync it to another machine, copy it to
d6jg wrote:
> Thats going to result in a very very large VMDK File which I would
> suggest will be impossible to back up as a single entity.
>
> If the host was Linux and not Windows things would be dead easy,Yes. Or
> several glued together in an LVM volume group (I wouldn't create
vmdks
drmatt wrote:
> You can fix #2 by either using "shared folders" in vmware to present
> local filesystems to the VM (then mount the hgfs volume inside the VM),
> or what I'd probably do is move all the files into the VM, on a vmdk,
> and have *it* serve them with samba. Then it does indeed become
You can fix #2 by either using "shared folders" in vmware to present
local filesystems to the VM (then mount the hgfs volume inside the VM),
or what I'd probably do is move all the files into the VM anyway, and
have *it* serve them with samba. Then it does indeed become self
contained and
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 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
19 matches
Mail list logo
