On Mon, Jul 23, 2012 at 2:17 AM, Karol Babioch <karol@xxxxxxxxxx> wrote: > Hi, > > Am 23.07.2012 02:01, schrieb Sébastien Luttringer: >> You will be able to build your virtualbox modules by running >> $ dkms install vboxhost/4.1.18 >> or you can let dkms rc script compile/install/load your modules with >> $ rc.d start dkms To be clear You can still use virtualbox-modules to have your module pre-compiled for the arch kernel. If you have a custom kernel or want compile yourself your modules your can use virtualbox-sources (as before). > Is this supposed once every time your kernel changes or can this be run > every time during boot? I'm not sure to understand your question. You can consider vboxbuild == dkms install vboxhost/4.1.18. (you can use dkms autoinstall for short). So it's supposed to be run like vboxbuild. Adding dkms into your DAEMONS will ensure that needed modules will be builded (for the running kernel) and loaded at startup. If you reboot after vbox upgrade, your new modules will be compiled for your kernel and loaded. After a kernel upgrade you can wait until your reboot to have module builded and loaded. But if you want upgrade without reboot, you should: kill virtualbox dkms autoinstall (old vboxbuild) rmmod vbox* modprode vbox* rerun virtualbox > Are there systemd unit files for this? Not yet. Patch welcomed. -- Sébastien "Seblu" Luttringer www.seblu.net
