In anticipation of 15 becoming official soon, I downloaded current for the first time yesterday. (Being from the if-it-ain't-broke-don't-fix-it school, I've been perfectly content with 14.2 these last years...
) The ISO boots fine on real hardware, but fails every time trying to boot in VirtualBox with it. The VM halts and VBox enters "Guru Meditation" mode immediately upon the slackDVD boot-up "freeing initrd memory." (see attached screen shot.)
I've tried every tweak in the VBox settings I can think of: increasing RAM, reducing to 1 CPU, changing "chipsets," disabling acceleration, etc. I also tried physical media and .iso file; as well as booting both huge.s and kms.s kernels. Still no dice...
I feel like it's just gotta be one little thing I'm missing: perhaps a VBox setting or passing a parameter to the kernel on the command line..?
(Or could it be more fundamental? Perhaps booting a guest to linux 5.13 on a host running linux 4.4 will never work? That seems far-fetched to me, but not being a VBox expert/enthusiast by any means, I'm not really qualified to rule it out.)
Any suggestions would be much appreciated.
TIA,
Jay
(For the record, this is VBox 5.0.40, built using unmodified SBo script (w/ addons), running on slack64-14.2.)
In fact, scanning over the VBox changelog, it looks like no 5.x series kernels are supported before VBox 6. (Maybe I'll just install current on an old laptop and forget about "virtualization"...)
