Hallo forum
I have installed Virtualbox (plugin) but i cant seem to start it up automaticly?
The function in omv web or in phpvirtualbox (set to auto start) is not working?
Virtualbox on omv4
-
- OMV 4.x
- kekec888
-
Do they log files (in the same directory as the VM files) tell you anything?
-
-
-
I guess I will have to try this on my system. I haven't used virtualbox in a long time.
-
I've the same problem after reboot of the server. The VM doesn't start automatically although activated in the settings. Here is the log file:
Code
Display MoreVirtualBox XPCOM Server 5.2.10_Debian r121806 linux.amd64 (Apr 26 2018 08:56:30) release log 00:00:00.000649 main Log opened 2018-06-19T20:37:33.943987000Z 00:00:00.000650 main Build Type: release 00:00:00.000652 main OS Product: Linux 00:00:00.000653 main OS Release: 4.16.0-0.bpo.2-amd64 00:00:00.000654 main OS Version: #1 SMP Debian 4.16.12-1~bpo9+1 (2018-06-03) 00:00:00.000669 main DMI Product Name: 00:00:00.000673 main DMI Product Version: 00:00:00.000707 main Host RAM: 15827MB (15.4GB) total, 15650MB (15.2GB) available 00:00:00.000717 main Executable: /usr/lib/virtualbox/VBoxSVC 00:00:00.000718 main Process ID: 854 00:00:00.000718 main Package type: LINUX_64BITS_GENERIC (OSE) 00:00:00.001593 main IPC socket path: /tmp/.vbox-vbox-ipc/ipcd 00:00:00.106606 nspr-2 VirtualBox: object creation starts 00:00:00.107253 nspr-2 Home directory: '/var/lib/vbox/.config/VirtualBox' 00:00:00.107845 nspr-2 Loading settings file "/var/lib/vbox/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux" 00:00:00.121896 nspr-2 HostDnsMonitorProxy::notify 00:00:00.123789 nspr-2 Failed to open "/dev/vboxdrvu", errno=2, rc=VERR_VM_DRIVER_NOT_INSTALLED 00:00:00.126465 nspr-2 VD: VDInit finished with VINF_SUCCESS 00:00:00.126521 nspr-2 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={0eb668d2-495e-5a36-8890-29999b5f030c} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0 00:00:00.132932 nspr-2 Loading settings file "/srv/dev-disk-by-label-work/VMs/Syno-DS916plus/Syno-DS916plus.vbox" with version "1.16-linux" 00:00:00.137349 nspr-2 VirtualBox: object created 00:00:00.169581 nspr-3 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'exist.'}, preserve=false aResultDetail=0 00:00:00.196483 nspr-2 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'appropriate'}, preserve=false aResultDetail=0 00:00:00.231519 nspr-3 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'linux-headers-amd64.'}, preserve=false aResultDetail=0 00:00:00.266209 nspr-2 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'fixed.'}, preserve=false aResultDetail=0
Will try the workaround from the link @kekec888Edit: the workaround didn't work because the changes were only made for "vboxdrvu" and "vboxnetctl". The permissions stay the same for "vboxdrv".
Edit 2: I found out that 60-virtualbox-dkms.rules changed the permissions of "vboxdrv" back to the old settings. Now I have
Codecrw-rw---- 1 root vboxusers 10, 58 Jun 19 23:19 vboxdrv crw-rw---- 1 root vboxusers 10, 57 Jun 19 23:19 vboxdrvu crw-rw---- 1 root vboxusers 10, 56 Jun 19 23:19 vboxnetctlAfter a reboot the VM is not in the "powered off" state but unfortunately now it shows "aborted"
-
@Huberer hmm mine stays the same, but you are right with file vboxdrv, but that doesnt seems to affect or give any errors in log...
Try this for autoboot:I made a workaround solution - i created a script in /etc/init.d/startvm
startvm file content:
--------------------------------------------------------------------------------------------------------
#!/bin/bash
#
#This init script autostarts necessary vms at boot
#and saves running vms on shutdown
# Sed explanation: sed -e 's/^.//' -e 's/.$//'
# 1. -e means to allow multiple arguments in a single sed command
# 2. 's/^.//' means to substitute (s) / at the beginning of the line (^), any character (.) / [substitute with nothing] /
# 3. 's/.$//' means to substitute (s) / any character (.), at the end of the line / [substitute with nothing] /VBOXUSER=vbox
RUNNINGVMS=$(sudo -H -u $VBOXUSER vboxmanage list runningvms | cut -d " " -f1 | sed -e 's/^.//' -e 's/.$//')
STOPPEDVMS=$(sudo -H -u $VBOXUSER vboxmanage list vms | cut -d " " -f1 | sed -e 's/^.//' -e 's/.$//')case "$1" in
start)
for i in $STOPPEDVMS
do
echo "Starting" $i "VM"
sudo -H -u $VBOXUSER vboxmanage startvm $i --type headless
sleep 5
done
;;
stop)
for i in $RUNNINGVMS
do
echo "Saving state of" $i "VM"
sudo -H -u $VBOXUSER vboxmanage controlvm $i savestate
done
;;
*)
echo "Usage: /etc/init.d/startvm {start|stop}"
exit 1
;;
esac
exit 0
--------------------------------------------------------------------------------------------------------
*This script will start all VM's and will put all VM's to savestateI ran this cmd to make it execute:
chmod +x /etc/init.d/startvmThen i insalled sysv-rc-conf to mng my rc.d :
apt-get install sysv-rc-confrun the application with:
sysv-rc-confand here i choose 2 and 6 (2 for startup and 6 for shutdown/reboot)
And now its working
Feel free to ask any questions
-
-
On my test system, I just created a VM and set it to autostart in the Virtual Machines tab of the plugin. I rebooted my system (I didn't manually shutdown the running VM) and the newly created VM was running after reboot. The plugin is doing the right thing according to the virtualbox documentation by adding pvbx/startupMode to the extraData for the VM. Not sure how the plugin is not working for some.
-
Thank you very much. I've tested your script and everything runs fine
After reboot the VM is back again. Perfect.Don't know but in my case the VM didn't start after reboot. Fortunately the script of @kekec888 runs good.
-
-
-
1. Thank you for the script... it seems to do what is expected (it starts VMs, not sure where I would see if it REALLY saved the state (or just started newly):
2. Is there a chance to enhance the script a bit:
Your scrip starts ALL VMs, but I may want to have only some started, not all.
Is that doable?
If that helped, I could change the name of the VM to start (or include) the word "AUTOSTART" if that hadThx again!
Nico
-
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!