[Pkg-virtualbox-devel] Bug#880005: closed by Gianfranco Costamagna <locutusofborg at debian.org> (unreproducible)

[Ralf Jung]

Hi,

>> In fact, "modprobe vboxdrv" works, as I indicated in my original email.
>> After doing so, VirtualBox works fine.  But something is wrong if I have
>> to load the module manually.
> 
> 
> well, I install sid/buster machines in VM weekly, and *never* had this issue,
> except for dkms failures.
> Can you please try to see if the module is not blacklisted, or some udev rule
> fails?

It does not seem to be blacklisted:

> $ cat /etc/modprobe.d/*
> # The microcode module attempts to apply a microcode update when
> # it autoloads.  This is not always safe, so we block it by default.
> blacklist microcode
> # modprobe information used for DKMS modules
> #
> # This is a stub file, should be edited when needed,
> # used by default by DKMS.
> # The microcode module attempts to apply a microcode update when
> # it autoloads.  This is not always safe, so we block it by default.
> blacklist microcode

Not sure about udev, where would I check that? "vbox" does not appear
anywhere in syslog or dmesg.

> Can you please try with a clean system?

I installed this laptop just a few weeks ago, it is pretty clean.
VirtualBox has always had that problem on this machine.  On my previous
laptop, things still worked fine.

How and when and by whom *should* vboxdrv get liaded?

Kind regards,
Ralf