This is the point where I try to make the system behave like a real server rather than something I manually start.
Up until now, I’ve been opening VirtualBox and starting the VM myself. That works, but it’s not how a proper server should behave.
The goal here is:
The server should start automatically when Windows boots, even if I am not logged in.
.
On the Windows host machine, I already have auto-login enabled so the system boots straight into the desktop environment without requiring manual sign-in.
This is important because it allows scheduled tasks to run immediately after startup without interruption.
I create a scheduled task in Windows Task Scheduler:
Task name: vboxboot
Run whether user is logged in or not
Trigger: At system startup
Delay: 30 seconds after boot
The task runs VirtualBox in headless mode using VBoxManage:
Program:
C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
Arguments:
startvm workbench-server --type headless
This should start the Ubuntu server VM without opening the VirtualBox GUI.
Now I test whether the VM actually starts correctly in headless mode. This is a key validation step because: If headless mode works → the server is fully autonomous If it fails → we need to adjust VM configuration
Write the long-form body for this page here.
Separate paragraphs with a blank line. Replace this placeholder with your own copy.
If the VM does not start correctly, or behaves unexpectedly, the most likely causes are:
VirtualBox not fully supporting headless mode for current config
VM display / graphics settings interfering
Ubuntu not fully initialising without GUI context
If headless mode is unstable, I will check:
Guest Additions installation inside Ubuntu
Whether the VM boots cleanly in normal GUI mode first
Whether network services still initialise correctly without display
The goal is to ensure the server is not dependent on the VirtualBox window being open.
At the end of this stage, I should have:
This is the transition from:
“a manually started lab VM”
to
“an always-on server environment”
It is the first step toward treating this setup like a real hosted system.
If headless mode works, the next stage becomes:
If it does not work, next stage becomes: