I think I found the problem:  The virtualbox systemd unit (well, the
init script, really) was disabled.  I am pretty sure that I did not
disable it, so I am not sure how this happened.

Maybe it would be better for virtualbox to use modules-load.d instead of
an init script when systemd is available?  In fact, virtualbox is
currently the *only* legacy init script on my system.

; Ralf

Reply via email to