Page 1 of 1

Tough installation : VirtualBox 5.2.22 and ADM 3.3.2.RJ12

PostPosted: Tue Jul 09, 2019 12:58 am
by sksbir
Here is how I finally managed to install a VM fedora 64 server successfully on my AS5002T NAS, without HDMI output.

- Install VirtualBox 5.2.22.r05 and Virtualbox extension pack 5.2.22.r02 ==> OK.
- Starting phpvirtualbox from ADM interface, using Firefox. ==> OK
- creating my VM : Fedora 64, using the right ISO, enabling remote display ( or it was enabled by default , cannot remember now ) ==> OK
- starting VM : FAIL . That is : VM is starting, and I can even see the console of my VM in thumbnail format on the "details" view . But noway to switch to "console" tab, and start acting threw console.

I had to change the property of remote desktop server port.. not port, but IP, and you cannot do that from GUI. I needed to replace '' with IP of my NAS on local network.
==> logged has root on NAS, edit /volume1/.@root/VirtualBox VMs/((myVM))/((myVM)).vbox
And update this section :
Code: Select all
          <Property name="Address" value="((myip))"/>
          <Property name="TCP/Address" value="((myip))"/>
          <Property name="TCP/Ports" value="3389"/>

After that, console was working either from RDP client on my local network, but also from phpvirtualbox.

Once Fedora server installed and updated, trying to mount shared folders.
- first following this tutorial : ... -hat-rhel/
FAIL: VirtualBox Guest Additions: modprobe vboxsf failed

Solution is here : ... /#comments , "You should download VBoxGuestAdditions from here. Check note on step 3"
"here" is , Downloaded from "Latest 5.2.x test builds" table , line Guest Additions 5.2.x revision 131558
Mounted this iso instead of Iso provided by extension pack, and ran again installation steps.

After that, my VM worked fine.

[EDIT 2019-08
problem is back with ADM 3.4.1.R7Q4 , and virtualbox 5.2.22.r07
When mounting vboxsf FS , getting "protocol error" message.
- trying to install VirtualBox 5.2.33 Guest Additions : same problem.
Everything reverts to normal after MOUNTING the shared volumes ( encrypted and not automatically mounted shared volumes ) where shared folders are located.