>> > My question was if it is normal for vboxdrv not to load "on demand", and
>> > not how to load it at boot time. If it is not normal, then probably my
>> > installaion of VirtualBox is corrupt, and I'd rather fix this instead of
>> > working around the problem. If it is normal, then why do other kernel
>> > modules do load automatically on demand and vboxdrv does not?
>>
>> If you are using the official packages from www.virtualbox.org then the
>> vboxdrv module is loaded at boot time. But as you are using the OSE version
>> it depends on the package if this is supposed to work or not.
I have noticed similar failure to load the vboxdrv.ko module with Fedora
guest in vista and win7 host. What seems to be happening is that when
loading a new vbox package on the host (vanilla vbox package NOT the
OSE), followed by guest additions, vboxdrv.ko is loaded as expected afterwards.
Then when I get a new kernel for fedora, and then have to load only the
guest additions, vboxdrv.ko fails to load at boot. So from this behavior
it would appear that some part of the install is done correctly when installing
the guest additions the first time, but is done incorrectly when re-loading the
guest additions. YMMV.
=S.Coffin
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
