A better tactic would be to run the appropriate Debian version for your matched Virtual Box needs in a virtual machine. Sounds crazy, but VB will nest within a libvirt/qemu/kvm virtual machine just fine.
For obsolete software I've done these odd things exploring possibilities. Generally, if a particular kernel or OS mix is needed then it should be the L1 VM, not Layer/level 0 aka bare metal. I mention often this should be done with the native hypervisor. If VB is a target, fine, but it is not good enough to be the L0 base, too much frosting. On a suitably stout computer performance falls off after L2 and L3, depending. Surprisingly, if those L2 and L3 vms are networked to yet another computer for display they can work well.
So, on a current Debian you'd create a Debian VM with your chosen kernel, then do from there as if it were the base machine. This L1 VM then host VB, which in turn host the odd mix. Probably a waste of time if tried on a laptop, though the laptop could maybe handle being the display utilizing virt-manager or virt-viewer remotely.
For obsolete software I've done these odd things exploring possibilities. Generally, if a particular kernel or OS mix is needed then it should be the L1 VM, not Layer/level 0 aka bare metal. I mention often this should be done with the native hypervisor. If VB is a target, fine, but it is not good enough to be the L0 base, too much frosting. On a suitably stout computer performance falls off after L2 and L3, depending. Surprisingly, if those L2 and L3 vms are networked to yet another computer for display they can work well.
So, on a current Debian you'd create a Debian VM with your chosen kernel, then do from there as if it were the base machine. This L1 VM then host VB, which in turn host the odd mix. Probably a waste of time if tried on a laptop, though the laptop could maybe handle being the display utilizing virt-manager or virt-viewer remotely.
Statistics: Posted by CwF — 2024-07-18 16:32