Serviio won't work when VMWare Workstation is installed
Posted: Fri May 17, 2013 12:23 amHi,
I am running Serviio on Linux without problems for a while. For my work I had to install VMWare (and I cannot remove it).
Whenever there is a new kernel for Linux (Ubuntu 12.04) that sometimes comes with a daily update, VMWare needs to compile some stuff in the kernel and do a lot of other network stuff at startup. After that Serviio won't be visible to any device anymore (Samsung TV, Android Mobile, etc.). Due to VMWare there are two additional IP-Adresses under 'Bound IP Adress'. I can set any available address or put it on automatically - it won't work anymore.
MiniDLNA will still work. All devices can see it even if VMWare is installed.
When a new kernel is installed by the Linux update, Serviio will be visible again to all devices. Everything works flawlessly. Still I need VMWare for my work and eventually I need to start it up, let it make changes to the kernel and stuff which will kill Serviio
Any idea how I can fix this? As I mentioned, manually setting the IP in 'Bound IP Address' doesn't work!
I am running Serviio on Linux without problems for a while. For my work I had to install VMWare (and I cannot remove it).
Whenever there is a new kernel for Linux (Ubuntu 12.04) that sometimes comes with a daily update, VMWare needs to compile some stuff in the kernel and do a lot of other network stuff at startup. After that Serviio won't be visible to any device anymore (Samsung TV, Android Mobile, etc.). Due to VMWare there are two additional IP-Adresses under 'Bound IP Adress'. I can set any available address or put it on automatically - it won't work anymore.
MiniDLNA will still work. All devices can see it even if VMWare is installed.
When a new kernel is installed by the Linux update, Serviio will be visible again to all devices. Everything works flawlessly. Still I need VMWare for my work and eventually I need to start it up, let it make changes to the kernel and stuff which will kill Serviio
Any idea how I can fix this? As I mentioned, manually setting the IP in 'Bound IP Address' doesn't work!
