1

I have a Ubuntu 16.04 virtual machine that I use for development purposes. When I start the VM in headless mode through the VirtualBox UI (v6.1.16), it starts absolutely fine.

However, when I start it with the vboxmanage command from PowerShell, using

vboxmanage startvm "vm-name" --type headless

it doesn't fully start until I open the VirtualBox UI, then it seems to finish the booting process and allow me to connect via SSH.

I have no idea why I have to open the UI to finish off the boot process (it's not a time issue, I've left it for several hours before, but it always completes the boot process fine when I open the UI), is there something in the rather simple vboxmanage command I'm missing, or is there likely to be something within the VM setup itself that's preventing a full boot if the UI isn't open?

Dark Hippo
  • 1,255
  • 2
  • 15
  • 35

1 Answers1

0

This answer fixed this issue for me: https://stackoverflow.com/a/44369038/12298712

I had my first network interface as Host Adapter and second interface as NAT; I made the first interface NAT and second interface Host Adapter and my VM was able to fully boot with networking working.

If you have static addressing on those network interfaces, you'll need to update /etc/network/interfaces to update the interface names.

spartanidas
  • 123
  • 1
  • 6