Is it possible to launch GUI of headless VirtualBox' machine?
Rise to the top 3% as a developer or hire one of them at Toptal: https://topt.al/25cXVn
--------------------------------------------------
Music by Eric Matyas
https://www.soundimage.org
Track title: Digital Sunset Looping
--
Chapters
00:00 Is It Possible To Launch Gui Of Headless Virtualbox' Machine?
01:06 Answer 1 Score 10
01:35 Answer 2 Score 6
01:48 Answer 3 Score 2
02:13 Answer 4 Score 1
02:30 Accepted Answer Score 1
02:43 Thank you
--
Full question
https://superuser.com/questions/469501/i...
--
Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...
--
Tags
#virtualbox #virtualmachine #remotedesktop #gui #headless
#avk47
ANSWER 1
Score 10
I just solved this problem by clicking the green arrow "Show" at the top of the VirtualBox GUI while my headless instance was already running.
I could see what the VM window would look like inside the "Preview" Pane on the VirtualBox GUI, and after clicking "Show", the VM window came up as though I had initially powered on the machine from the Virtualbox GUI.
Edit: When you close the VM window, it will give you the additional option to "Continue running in the background", so your headless instance can revert to being headless again.
ANSWER 2
Score 6
You can attach to a headless VM by running VBoxSDL --startvm <VMname> --separate
. If you run VBoxSDL
with no args you can see other options you may be interested in.
ANSWER 3
Score 2
You can click on the Show button to get the GUI of a headless VM in the VirtualBox Manager:
When you are done with using the GUI, you can detach it and your VM will go back headless.
I tested this on Windows 10 and it worked as of VirtualBox 5.1.22. Should be the same on Mac/Linux.
ANSWER 4
Score 1
After getting the same error, I just changed the default port 3389 to something else.
I used random port number (in my case 5500). Then it worked.
And disabled Windows firewall for a moment - but I don't think firewall was the problem.
ACCEPTED ANSWER
Score 1
I solved the problem - I didn't have VirtualBox extension pack installed. While it is added in Linux version of VirtualBox, you have to install it separately on Windows.