1. Add your user to vboxusers group.<\/p>\n\n\n\n
<\/p>\n\n\n\n 2. Systemd template unit to start and stop VirtualBox VMs<\/p>\n\n\n\n The systemd template unit to start and stop a VirtualBox VM when booting up and down a PC looks like this:<\/p>\n\n\n\n As a final step to complete the installation of the systemd service unit, we need to edit the file to change the User<\/em> setting. The first line in the Service<\/em> section now reads:<\/p>\n\n\n\n Save the file with this path and name:<\/p>\n\n\n\n <\/p>\n\n\n\n 3. Enable the Systemd service for your VirtualBox VM<\/p>\n\n\n\n With the systemd template unit in place, we can enable the systemd service for a particular VirtualBox VM. All we need is the name of the VirtualBox VM. You can open up VirtualBox and read the name of the VM on the main screen. Alternatively, you can run the following command in the terminal to obtain a list with available VMs:<\/p>\n\n\n\n To enable the systemd service unit for this VM, based on our systemd template unit, we can use this command syntax:<\/p>\n\n\n\n We just need to replace <\/p>\n\n\n\n 4. Verify that Systemd started your VirtualBox VM<\/p>\n\n\n\n After rebooting your PC, Systemd should have started your VirtualBox VM, but how to verify this? If your VirtualBox VM runs an SSH server you could of course attempt to connect with it. Alternatively, you can open up the VirtualBox user interface, which indicates if a VM runs or not.<\/p>\n\n\n\n Executing the So pretty much a similar command syntax as for enabling and disabling the systemd service. Just to check the status you can run this command:<\/p>\n\n\n\n <\/p>\n\n\n\n Enjoy!<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":" 1. Add your user to vboxusers group. sudo usermod -a -G vboxusers $USER 2. Systemd template unit to start and stop VirtualBox VMs The systemd template unit to start and stop a VirtualBox VM when booting up and down a […]<\/p>\nsudo usermod -a -G vboxusers $USER<\/code><\/p>\n\n\n\n[Unit]\nDescription=VirtualBox VM %I\nAfter=network.target vboxdrv.service\nBefore=runlevel2.target shutdown.target\n\n[Service]\nUser=admin\nGroup=vboxusers\nType=forking\nRestart=no\nTimeoutSec=5min\nIgnoreSIGPIPE=no\nKillMode=process\nGuessMainPID=no\nRemainAfterExit=yes\n\nExecStart=\/usr\/bin\/VBoxManage startvm %i --type headless\nExecStop=\/usr\/bin\/VBoxManage controlvm %i acpipowerbutton\n\n[Install]\nWantedBy=multi-user.target<\/pre>\n\n\n\n
User=admin<\/code><\/p>\n\n\n\n\/etc\/systemd\/system\/vbox_vm@.service<\/code><\/p>\n\n\n\nVBoxManage list vms<\/code><\/p>\n\n\n\nsudo systemctl enable vbox_vm@<name of VM><\/code><\/p>\n\n\n\n<name of VM><\/code> with the name of our VM.<\/p>\n\n\n\nsystemctl<\/code> command from the terminal offers another method, which provides more information. Its format is:<\/p>\n\n\n\nsudo systemctl status vbox_vm@<name of VM><\/code><\/p>\n\n\n\nsudo systemctl status vbox_vm@<name of VM><\/code><\/p>\n\n\n\n