Schmill Posted November 22, 2014 Share #1 Posted November 22, 2014 (edited) Hi, I am trying to solve some issues I am having with Plex on my xpenology install. This is tiresome as once it is 'broken' it stays broken... Ideally what I want to do is setup a VM on my laptop and install xpenology and plex onto that to do some investigating. The snag is that my laptop is only a 32bit machine, so can only run a 32bit VM, whereas what I normally run on my N54L is 64bit... Can anyone give me any pointers as to how / what to install in order to run a 32bit VM based version of xpenology and nanoboot? Thanks Edited November 23, 2014 by Guest Link to comment Share on other sites More sharing options...
Dfds Posted November 23, 2014 Share #2 Posted November 23, 2014 Why not install Virtualbox on the server, see here for a guide: viewtopic.php?f=15&t=3497 Link to comment Share on other sites More sharing options...
Schmill Posted November 23, 2014 Author Share #3 Posted November 23, 2014 Because the server is already in use EDIT Oh I see, actually WITHIN Xpenology... sorry - I'll take a look Link to comment Share on other sites More sharing options...
Schmill Posted November 23, 2014 Author Share #4 Posted November 23, 2014 Nice solution - thanks (but as an aside, how DO you install a 32bit version?) Link to comment Share on other sites More sharing options...
Schmill Posted November 23, 2014 Author Share #5 Posted November 23, 2014 ...or at least it was whilst it worked. One reboot of the host later and now I can login to the phpVirtualbox screen with admin/admin, but after that I get an error explained as: Exception Object ( [message:protected] => Could not connect to host (http://127.0.0.1:18083) [string:Exception:private] => [code:protected] => 64 [file:protected] => /volume1/web/phpvirtualbox/lib/ajax.php [line:protected] => 128 [trace:Exception:private] => Array ( ) [previous:Exception:private] => ) Link to comment Share on other sites More sharing options...
Schmill Posted November 25, 2014 Author Share #6 Posted November 25, 2014 I think I've fixed the above issue - seems that virtualbox defaults to creating the VM's under /root, which fills up the system pretty darn quick. Moving the VMs out to one of my volumes seems to have solved it ( viewtopic.php?p=27400#p27400 ) Link to comment Share on other sites More sharing options...
Recommended Posts