Package Details: virtualbox-ck-host-modules 5.0.20-4

Git Clone URL: https://aur.archlinux.org/virtualbox-ck-modules.git (read-only)
Package Base: virtualbox-ck-modules
Description: Host kernel modules for VirtualBox running under Linux-ck.
Upstream URL: http://virtualbox.org
Licenses: GPL
Conflicts: virtualbox-ck-host-modules-atom, virtualbox-ck-host-modules-barcelona, virtualbox-ck-host-modules-broadwell, virtualbox-ck-host-modules-bulldozer, virtualbox-ck-host-modules-core2, virtualbox-ck-host-modules-corex, virtualbox-ck-host-modules-haswell, virtualbox-ck-host-modules-ivybridge, virtualbox-ck-host-modules-k10, virtualbox-ck-host-modules-kx, virtualbox-ck-host-modules-nehalem, virtualbox-ck-host-modules-p4, virtualbox-ck-host-modules-pentm, virtualbox-ck-host-modules-piledriver, virtualbox-ck-host-modules-sandybridge, virtualbox-ck-host-modules-silvermont, virtualbox-ck-host-modules-skylake
Provides: VIRTUALBOX-HOST-MODULES
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 46
Popularity: 2.811678
First Submitted: 2012-10-16 21:53
Last Updated: 2016-05-23 19:28

Required by (0)

Sources (0)

Latest Comments

artafinde commented on 2016-05-24 10:28

I think snack is right. From what I understood as long as your have no `virtualbox*-guest-*` package installed you won't have issues with the failed modules. Also from the comments here you have two options:
1. If you use repo-ck then just use the packages provided for your CPU and remove `virtualbox-*-dkms` packages.
2. If, on the other hand, you are building your own kernel then you can, either let DKMS build the modules on each kernel install (with hooks), pr you can manually do so with this AUR package. graysky suggest (if not recommends) to build your own packages instead of DKMS.

So no bug here just a little confusion with the DKMS, hooks and packages provided.

snack commented on 2016-05-24 08:23

@graysky I installed virtualbox-host-modules-arch 5.0.20-3 and I get no module load error in journalctl when booting the stock kernel. Just some lines like these:

mag 24 10:01:21 elric systemd-modules-load[156]: Inserted module 'vboxdrv'
mag 24 10:01:21 elric kernel: vboxdrv: Successfully loaded version 5.0.20_OSE (interface 0x00240000)
mag 24 10:01:21 elric kernel: VBoxPciLinuxInit
mag 24 10:01:21 elric systemd-modules-load[156]: Inserted module 'vboxpci'
mag 24 10:01:21 elric systemd-modules-load[156]: Inserted module 'vboxnetadp'
mag 24 10:01:21 elric kernel: VBoxNetAdp: Successfully started.
mag 24 10:01:21 elric kernel: VBoxNetFlt: Successfully started.
mag 24 10:01:21 elric systemd-modules-load[156]: Inserted module 'vboxnetflt'

but no "Failed to find module" message like you got. In fact, /usr/lib/modules-load.d/virtualbox-host-modules-arch.conf contains:

vboxdrv
vboxpci
vboxnetadp
vboxnetflt

so none of the guilty modules is present (like in /usr/lib/modules-load.d/virtualbox-host-modules-arch.conf for virtualbox-ck-host-modules-core2 5.0.20-4). So I'd say that the problem is solved and that no bug report has to be opened. Am I right?

snack commented on 2016-05-24 07:53

@graysky Thanks, I will open a bug as soon as I can (I'm at work now so I have to find time for rebooting with the stock kernel, fill the bug report etc.). Thank you for your hjelp.

artafinde commented on 2016-05-24 07:13

Great since I build my own kernel with modprobed I can omit those and use dkms (until I found I don't trust them either ;) ), cheers

graysky commented on 2016-05-23 22:56

@art - Yes, that was my point although I don't see my entire reply in the thread below. I said (or so I thought) that the pre-built modules are useful for [repo-ck] users and redundant for regular users since a build dep will build them automatically unless you mask the hooks for it. Personally, I do not like dkms for module management. I have tried it before and found it to be less than reliable.

artafinde commented on 2016-05-23 21:50

@graysky slightly irrelevant with my question but useful info nevertheless.

Since the hooks are in place now and the modules are built when the new kernel installs aren't these two packages redundant anyway?

graysky commented on 2016-05-23 21:32

@artafinde - Yes, that is lame as you essentially build them twice, once for dkms and once for the package. You can mask the dkms build hooks if you really want to: https://bbs.archlinux.org/viewtopic.php?pid=1610194#p1610194

artafinde commented on 2016-05-23 21:29

I have an issue when trying to build the package for virtualbox-ck-host-modules.The package depends on virtualbox-guest-dkms because it's a requirement for the virtualbox-ck-guest-modules. Since I don't want the guest package I have to follow the below process to build:
- install virtualbox-guest-dkms
- build both virtualbox-ck-host-modules and virtualbox-ck-guest-modules
- install virtualbox-ck-host-modules
- remove virtualbox-guest-dkms

The is relevant to the one snack has because the package virtualbox-guest-dkms comes with a file such as
$ cat /usr/lib/modules-load.d/virtualbox-guest-dkms.conf
vboxguest
vboxsf
vboxvideo

Is there a way to avoid the dependency installation?

graysky commented on 2016-05-23 19:16

@snack - First off, you found a bug (copy/paste error on my part) with regard to the modules being targeted which I will fix (thank you).

Secondly, I can confirm the behavior you reported on my system running ck-generic... but I am unsure how to interpret it... upon booting the requisite modules are autoloaded as they should be. Calling `sudo /usr/lib/systemd/systemd-modules-load` does indeed give the 3 errors you posted as well... is that a bug in that modules already loaded are mistakenly called missing?

EDIT: When I look in my journalctl, I get these conflicting lines:
May 23 15:17:03 relic systemd-modules-load[179]: Failed to find module 'vboxguest'
May 23 15:17:03 relic systemd-modules-load[179]: Failed to find module 'vboxsf'
May 23 15:17:03 relic systemd-modules-load[179]: Failed to find module 'vboxvideo'
May 23 15:17:03 relic systemd-modules-load[179]: Inserted module 'vboxdrv'
May 23 15:17:02 relic systemd-modules-load[179]: Inserted module 'vboxpci'
May 23 15:17:02 relic systemd-modules-load[179]: Inserted module 'vboxnetadp'
May 23 15:17:02 relic systemd-modules-load[179]: Inserted module 'vboxnetflt'

EDIT2: As a test, I installed the official packages and found that upon booting into the ARCH kernel, the same errors are written to the journal yet the modules are loaded. Perhaps you have indeed found a bug. Will you review and open a Flyspray against the official package?

snack commented on 2016-05-23 17:08

Recently I realized that the systemd unit systemd-modules-load fails during boot. I think that the problem might be related to this package (core2 flavor); launching the unit manually I get:

$ sudo /usr/lib/systemd/systemd-modules-load
Failed to find module 'vboxguest'
Failed to find module 'vboxsf'
Failed to find module 'vboxvideo'

These modules are listed in /usr/lib/modules-load.d/virtualbox-ck-host-modules-core2.conf, and it seems strange to me that 'vboxguest' module is referred in the host-modules package files, but maybe it's fine and the problem lies somewhere else.
I have these virtualbox packages installed:

virtualbox 5.0.20-1
virtualbox-ck-host-modules-core2 5.0.20-3

All comments