Just for the hell for it, I installed the Linux kernel 5.11 in --Current (from /testing) and then installed the guest additions, and I booted up the first time just fine. Running VirtualBox 6.1.18r142142

-edit

I also pulled the latest --Current and rebuilt the iso just fyi. I rebooted the VM yet again, and still no errors.

1 members found this post helpful.

Running VirtualBox-6.1.19-143492-Linux_amd64.run with 5.11.9, soon to be 5.11.10

1 members found this post helpful.

Rebuilt --Current and installed Kernel 5.11.11 and then guest additions, and booted up just fine. The only weird behavior I have seen from virtualbox is when issuing the command to upgrade to 5.11 at one point there was no more text scrolling by when doing package install/upgrades and I thought maybe the VM just locked up, I have never seen this behavior before - but I waited patiently and eventually the VM unlocked itself after the upgrade - but I don't know why virtualbox acts thats way.

I saw this a few weeks ago. Don't know what combination of VirtualBox I was using at the time. I've now settled on Slackware 14.2 with TestBuilds

VirtualBox-6.1.19-142995-Linux_amd64.run
VBoxGuestAdditions_6.1.19-142994.iso

The only problem with this combination is that I can't run scripts from a shared folder unless I explicitly call them within a shell environment i.e. ksh or bash which was a bit of a nuisance. Got round that by a rsync from the shared folder to a non shared folder and calling the scripts from the non-shared folder.

1 members found this post helpful.

A new test build, 6.1.19 revision 143581 and a companion extension pack have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

Edit in: Installed and running perfectly with -current and the 5.11.11 kernel.

1 members found this post helpful.

Thanks for the info on new build!

I managed to (finally) make it running here as well, thanks to info in post #18

Thank you! ctrlaltca


current (updated as of earlier today Apr 3)
5.11.11
VirtualBox 6.1.19 revision 143581

1 members found this post helpful.

I have a windows 10 guest. I am running kernel-5.10.27 and installed the test build VirtualBox-6.1.19-143581 and extension pack. Seems to work fine.

1 members found this post helpful.

A new test build, 6.1.19 revision 143633 and a companion extension pack have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

1 members found this post helpful.

A new test build, 6.1.19 revision 143678 and a companion extension pack have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

That is two new test builds in one day. We must be getting close to a new "stable" release of VirtualBox.

1 members found this post helpful.

A new test build, 6.1.19 revision 143777, and extension pack version 6.1.19-143767, have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

Edit in: Both have been installed and are working fine with -current and the 5.12-rc7 kernel.

1 members found this post helpful.

They haven't updated their main page yet, but the newest Stable release, VirtualBox-6.1.20, can be downloaded from here,
https://www.virtualbox.org/wiki/Downloads

The change log, https://www.virtualbox.org/wiki/Changelog-6.1#v20

Edit in: Installed and working perfectly in -current with the 5.12-rc8 kernel.

3 members found this post helpful.

I would recommend that you create an Oracle account, if you don't already have one, and post in the Oracle VirtualBox forums with appropriate logs there, where those logs contain lots of useful information about hosts, guests, physical and virtual hardware, device drivers, etc... and much more detail about what's actually happening around crashes for practical troubleshooting efforts.

1 members found this post helpful.

Installed in stable with the 4.4.240 kernel. Guest running -current with the 5.10.31 kernel and GuestAdditions. Seems to do what it's supposed to do except when i run a script from a shared folder I get this message

My workaround is using /etc/rc.d/rc.local to rsync the contents of the shared directory to a non shared directory and run the script from non shared directory a bit of a nuisance, but the scripts then work. Strange.

I did report it to our friends at oracle, but it might have got lost with everything else that was going on

Before I report it again I shall test with -current host and -current guest.

Cheers for now

1 members found this post helpful.

VirtualBox 6.1.20 running ok with kernel 5.11.15. Debian vm has it´s state loading and saving ok.

1 members found this post helpful.

Now that 6.1.20 is out, I am able to successfully install guest additions for --Current using the 5.10 series. It boots up with no issues this time thankfully.