There are two possible solutions according with László (And both solutions are mentioned in other network too) as follows:
My readings told me it’s because the newer kernel loads and inits kvm module by default, whereas the previous version did not. This makes impossible for Virtualbox to init virtualization on its own, so the sulotion is either to disable kvm initialization in GRUB adding a kernel parameter ( kvm.enable_virt_at_load=0 ) , or blacklist kvm module via /etc/modprobe.d/something.conf.
Therefore:
Question
How to disable KVM initialization?: GRUB vs modprobe.d
My main concern is which one is either better or recommendable and why?.
Using modprobe.d is better because it is simpler.
If you use grub you have to edit /etc/default/grub, then do update-grub to build a new grub.cfg file, then if your linux is not the one controlling grub you have to go to the grub controlling linux and do update-grub there.
If it were a module, you could remove it from the current running kernel with modprobe -r modulename
but
I am not sure if kvm is a module? Do you know?