[SOLVED] Cannot start VMs anymore after upgrade from Debian Stretch to Buster

[PatiB87]

Hey,

I just upgraded my Debian Stretch to Buster on my Intel NUC.
Now I cannot start my VMs anymore - which unfortunately is very important to my house...

Therefore I need your help urgently.

I can correctly list my VMs with:

Code: Select all

VBoxManage list vms

Now when I try to start any of them, I get this:

Code: Select all

Waiting for VM "PiHole" to power on...
VBoxManage: error: The virtual machine 'PiHole' has terminated unexpectedly during startup because of signal 6
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

Why reason could this have? I absolutely have no clue, yet I need these VMs to run for several services in my house and network.

Thanks for any help!!!
Patrick

EDIT: SOLVED!
I was SO STUPID to forget the "--type headless"
Command is:

Code: Select all

VBoxManage startvm PiHole --type headless

[scottgus1]

Try this web-search:

"signal 6" site:virtualbox.org

There's a few different causes.

Also consider a reinstall of Virtualbox.

[PatiB87]

Hey,
first: thanks for helping!!

Reinstall is just:

Code: Select all

sudo apt remove --purge virtualbox
sudo apt install virtualbox
sudo apt install virtualbox-dkms

Right?

But currently there should not be any issues with regular virtualbox under debian buster?

[PatiB87]

Oh mother of....

I think, I just f-ed it up:

Code: Select all

 VBoxManage startvm PiHole --type headless

fixed it! I fotgot the headless!

Reason for this maximum studpidness is:
Before the upgrade to buster, I used "PHPVirtualBox" for managing, which currently does not work.
This is not so critical but then I just did

Code: Select all

 VBoxManage startvm PiHole

via SSH and got the error.

Headless it works.

Goddamn!

Sorry for swearing!
Thanks a whole lot for helping!
Happy 2020!

Patrick

[scottgus1]

Glad you got your guests going!
That NUC looks sweet...