Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - virtualbox-ck-guest-modules

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: virtualbox-ck-guest-modules 5.1.14-2

Git Clone URL: https://aur-dev.archlinux.org/virtualbox-ck-modules.git (read-only)
Package Base: virtualbox-ck-modules
Description: Guest kernel modules for VirtualBox running under Linux-ck.
Upstream URL: http://virtualbox.org
Licenses: GPL
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 48
Popularity: 0.079401
First Submitted: 2012-10-16 21:53
Last Updated: 2017-02-01 21:38

Required by (0)

Sources (0)

Latest Comments

1 2 3 4 5 6 Next › Last »

graysky commented on 2016-11-20 11:51

@redbaron - Yes, this is the default now since linux-ck-skylake from [repo-ck] has a pkgbase=linux-ck-skylake. If you're using the repo for just the kernel, but not the modules, you will have to edit this PKGBUILD accordingly. Alternatively, just use [repo-ck].

redbaron commented on 2016-11-20 09:57

Problem with "_extramodules=extramodules-4.8-ck" variable, now it's changed to "_extramodules=extramodules-4.8-ck-skylake" with kernel installed from repo-ck. After editing PKGBUILD everything is ok. If possible change this on repo-ck also.

graysky commented on 2016-10-20 18:54

My mirrorlist was out-of-date it seems as the build chroot did not pull down 5.1.8 to build against. Fixed now, thanks for reporting.

Cake commented on 2016-10-20 03:02

I am not sure whether it is proper to bring up the issue here. But it seems that the virtualbox-ck-*-modules packages in repo-ck are not updated.

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:


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?