[solved] virtualbox depends on virtualbox-host-dkms?

Nooblazor · 2016-03-09 01:17:55

rlees85 wrote:

oconnor663 wrote:
Nooblazor wrote:
For the time being I just ran:
pacman -Syu --ignore virtualbox,virtualbox-host-dkms
in order to avoid dkms getting installed even if I answer that I want to keep the old modules.
That might run you into a different set of problems pretty soon, if the `virtualbox-host-modules` package is not kept up to date. @Scimmia mentioned earlier in this thread:
Scimmia wrote:
Binary modules are a huge pain. The kernel breaks the module interface every couple of releases (and I'm taking micro-version, bug fix releases) with no warning and no way to tell until things fail.
Same here. Might want to add your kernel & headers to the ignore list also and it is only a *very* temporary solution until it is set in stone that DKMS must be used going forward.
I am with Allan - the binary modules seemed a better and cleaner solution in my eyes (for the reasons already mentioned by many others above) as an end-user with multiple kernels. I won't throw my dummy out the pram over it though so please don't flame this post I am just adding my personal opinion.

Yeah pretty much my thinking here as well. Temporary not-really-a-solution type thing. Just want to see where this all leads before I make any changes or until the main virtualbox package itself updates.

twelveeighty · 2016-03-09 04:46:16

Scimmia wrote:

3. The virtualbox package is moving to DKMS only. This is also being discussed in the mailing list thread. Nobody has yet filed a coherent bug report about this.

I just opened https://bugs.archlinux.org/task/48514 to (hopefully) specifically address this.

@Scimmia, you've implied several times in this thread that the bug report(s) weren't created appropriately, so I tried to make this one as 'cut 'n dry' as possible, but please let me know if there is anything missing with this task.

Scimmia · 2016-03-09 05:08:00

twelveeighty wrote:

Scimmia wrote:
3. The virtualbox package is moving to DKMS only. This is also being discussed in the mailing list thread. Nobody has yet filed a coherent bug report about this.
I just opened https://bugs.archlinux.org/task/48514 to (hopefully) specifically address this.
@Scimmia, you've implied several times in this thread that the bug report(s) weren't created appropriately, so I tried to make this one as 'cut 'n dry' as possible, but please let me know if there is anything missing with this task.

You gave a valid reason, which puts you well ahead of the pack.

phw · 2016-03-09 08:23:27

There is a statement by Sébastien Luttringer , the maintainer of the packages, at https://lists.archlinux.org/pipermail/a … 27808.html

The ML is probably a better place for discussing the issues some people have with this. I think the forum is better suited to provide help to those struggling with this change.

amhairghin · 2016-03-10 14:42:24

And in the meantime, the package is outdated...

twelveeighty · 2016-03-10 16:30:19

amhairghin wrote:

And in the meantime, the package is outdated...

That has nothing to do with this entire thread - upstream is at 5.0.16 and we're at 5.0.14, therefore it's "outdated". Let's not pile on top of the maintainer/devs, everyone is a volunteer here. Things will work out in the end. I don't think there's anything critical in 5.0.16 vs. 5.0.14, and it's only been out for 6 days.

ooo · 2016-03-10 19:14:15

Looks like I'm still confused about this change..

I thought the idea behind deprecating binary virtualbox modules was that now that we have pacman hooks, the module would get built by a hook after every kernel upgrade. Yet that didn't happen after today's kernel upgrade to 4.4.5.

Am I missing something, or are you now supposed to run dkms manually after each kernel update?

midixinga · 2016-03-10 21:43:11

ooo wrote:

Am I missing something, or are you now supposed to run dkms manually after each kernel update?

Did you install appropriate linux-headers? For me it worked fine

ooo · 2016-03-10 21:57:12

midixinga wrote:

Did you install appropriate linux-headers? For me it worked fine

Oops. I thought I had them installed, but apparently not.

Thanks for clarification :)

Last edited by ooo (2016-03-10 21:57:20)

amhairghin · 2016-03-12 10:01:18

twelveeighty wrote:

amhairghin wrote:
And in the meantime, the package is outdated...
That has nothing to do with this entire thread - upstream is at 5.0.16 and we're at 5.0.14, therefore it's "outdated". Let's not pile on top of the maintainer/devs, everyone is a volunteer here. Things will work out in the end. I don't think there's anything critical in 5.0.16 vs. 5.0.14, and it's only been out for 6 days.

Is a small joke to ease tension

lucazade · 2016-03-12 21:16:34

after upgrading to 5.0.16 I get an error loading host modules..

-> % sudo systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since sab 2016-03-12 22:12:35 CET; 32s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 435 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 435 (code=exited, status=1/FAILURE)

-> % /usr/lib/systemd/systemd-modules-load        
Failed to find module 'vboxnetadp\nvboxnetflt\nvboxdrv\n'

-> % sudo cat /etc/modules-load.d/virtualbox.conf
vboxdrv
vboxnetadp
vboxnetflt
vboxpci

-> % lsmod | grep vbox                                 
vboxpci                24576  0
vboxnetflt             28672  0
vboxnetadp             28672  0
vboxdrv               385024  3 vboxnetadp,vboxnetflt,vboxpci

bulletmark · 2016-03-12 23:07:13

@lucazade, I see the same problem since the 5.0.16 upgrade.

timemaster · 2016-03-13 14:48:23

There is a bug in usr/lib/systemd/systemd-modules-load/virtualbox-host-dkms.conf

The file should contains 3 modules to load, separated by enter. However the file separate them by \n (newline characters when programming), and because of this modprobe see it as only one module. As it can't find a module with the name "vboxnetadp\nvboxnetflt\nvboxdrv\n" it fail.

The fix is to modify the file and replace \n with enter, so that the 3 modules are on different lines.

Last edited by timemaster (2016-03-13 14:49:02)

bwid · 2016-03-17 10:48:57

jseel001 wrote:

- Search for virtualbox and remove it. This will prompt you to remove virtualbox and the following deps: dkms, gcc, libmpc, and of course virtualbox.
- Reboot.
- Search for and install linux-headers.
- Search for and install virtualbox.
- Reboot.

Thanks, this reinstall procedure triggered the dkms compile on my system.

And no, i suspect in some cases just doing step #3 is not enough. I had linux-headers already installed (checked with pacman -Q linux-headers, and even checked that the files of the package where present).
As far as i could tell, doing "dkms autoinstall" as suggested in the wiki did nothing.

ugjka · 2016-03-17 10:53:15

If you have the kernel headers installed then reinstalling virtualbox-{host,guest}-dkms will trigger a dkms rebuild

Last edited by ugjka (2016-03-17 10:53:30)

bwid · 2016-03-17 12:17:40

I did a system upgrade on 15th, virtualbox-{guest,host}-modules where replaced and pulled in dkms package. Somehow the 70-dkms-install.hook didn't fire back then. Not sure if its just something screwed up on my system, or if i should file bugreport.

grep 'dkms\|virtualbox' /var/log/pacman.log

[2016-03-15 16:02] [ALPM] removed virtualbox-host-modules (5.0.12-2)
[2016-03-15 16:04] [ALPM] installed dkms (2.2.0.3+git151023-8)
[2016-03-15 16:04] [ALPM] installed virtualbox-host-dkms (5.0.16-3)
[2016-03-15 16:04] [ALPM] upgraded virtualbox (5.0.12-1 -> 5.0.16-3)
[2016-03-15 16:04] [ALPM-SCRIPTLET] ==> Since version 5.0.14-2 kernel modules are provided via dkms
[2016-03-15 16:04] [ALPM] upgraded virtualbox-guest-iso (5.0.12-1 -> 5.0.16-1)
[2016-03-15 16:04] [ALPM] installed virtualbox-guest-dkms (5.0.16-3)
[2016-03-15 16:04] [ALPM] upgraded virtualbox-guest-utils (5.0.12-1 -> 5.0.16-3)
[2016-03-17 09:33] [PACMAN] Running 'pacman -S dkms'
[2016-03-17 09:33] [ALPM] reinstalled dkms (2.2.0.3+git151023-8)
[2016-03-17 10:46] [ALPM] upgraded dkms (2.2.0.3+git151023-8 -> 2.2.0.3+git151023-9)
[2016-03-17 11:14] [PACMAN] Running 'pacman -R virtualbox'
[2016-03-17 11:14] [ALPM] removed virtualbox (5.0.16-3)
[2016-03-17 11:14] [PACMAN] Running 'pacman -R virtualbox-guest-dkms'
[2016-03-17 11:14] [PACMAN] Running 'pacman -R virtualbox-guest-dkms virtualbox-guest-iso virtualbox-guest-utils'
[2016-03-17 11:14] [ALPM] running '70-dkms-remove.hook'...
[2016-03-17 11:14] [ALPM-SCRIPTLET] ==> dkms -q remove -q -m vboxguest -v 5.0.16_OSE -k 4.4.5-1-ARCH
[2016-03-17 11:14] [ALPM] removed virtualbox-guest-utils (5.0.16-3)
[2016-03-17 11:14] [ALPM] removed virtualbox-guest-iso (5.0.16-1)
[2016-03-17 11:14] [ALPM] removed virtualbox-guest-dkms (5.0.16-3)
[2016-03-17 11:14] [PACMAN] Running 'pacman -R virtualbox-host-dkms'
[2016-03-17 11:14] [ALPM] running '70-dkms-remove.hook'...
[2016-03-17 11:14] [ALPM-SCRIPTLET] ==> dkms -q remove -q -m vboxhost -v 5.0.16_OSE -k 4.4.5-1-ARCH
[2016-03-17 11:14] [ALPM] removed virtualbox-host-dkms (5.0.16-3)
[2016-03-17 11:24] [PACMAN] Running 'pacman -S virtualbox'
[2016-03-17 11:24] [ALPM] installed virtualbox-host-dkms (5.0.16-3)
[2016-03-17 11:24] [ALPM] installed virtualbox (5.0.16-3)
[2016-03-17 11:24] [ALPM] running '70-dkms-install.hook'...
[2016-03-17 11:24] [ALPM-SCRIPTLET] ==> dkms -q install -m vboxhost -v 5.0.16_OSE -k 4.4.5-1-ARCH

a7arch · 2016-03-24 00:18:55

To everybody who doesn't want to install VirtualBox with that huge dkms and developer packages:
There's still the possibility to install VirtualBox "manually", without the dependencies, from their homepage! (as long as the kernel modules are available in the repo...)
But remember, VirtualBox will not be automatically updated when you go this way!!!

1) First, install the kernel modules for VirtualBox with pacman, related to your kernel version, e.g. for kernel v4.4.5-1:
linux44-virtualbox-host-modules (v5.0.16-7)
linux44-virtualbox-guest-modules (v5.0.16-7)

... and any other package you may need (e.g. virtualbox-guest-iso), but _NOT_ virtualbox itself!

2) Then download the Installer from the VirtualBox homepage (depending on the virtualbox-version your modules are made for, e.g. in this case v5.0.16-7):
https://www.virtualbox.org/wiki/Linux_Downloads
(see last download link: "All distributions", 32bit/64bit)

The extension pack for this version can be downloaded from here:
https://www.virtualbox.org/wiki/Downloads

Make the downloaded Installer executable (chmod +x VirtualBox-*.run), and start it with "sudo" from the console, e.g.:
sudo ./VirtualBox-5.0.16-105871-Linux_x86.run

3) restart PC!

VirtualBox should now be installed in /opt/VirtualBox/, and you should be able to start it with "virtualbox" from the console, or over the desktop menu...
If not, try these commands:
sudo /opt/VirtualBox/postinst-common.sh
sudo /opt/VirtualBox/vboxdrv.sh

To remove VirtualBox, run "sudo /opt/VirtualBox/uninstall.sh"

I've tested it all by myself, and it worked fine for me, but keeping in mind that the virtualbox binary kernel modules may be removed from the repo in the future, this way is at your own risk!

Hope I could help...
greetings! :-)

Last edited by a7arch (2016-03-24 00:22:01)

Scimmia · 2016-03-24 00:26:05

Yeah, don't do that.

jasonwryan · 2016-03-24 03:55:02

Scimmia wrote:

Yeah, don't do that.

If you are going to post, please include some rationale so that a7arch has some chance of learning what they ought to avoid doing. As it is, this is empty posting.

eschwartz · 2016-03-24 03:59:56

a7arch wrote:

To everybody who doesn't want to install VirtualBox with that huge dkms and developer packages:
There's still the possibility to install VirtualBox "manually", without the dependencies, from their homepage! (as long as the kernel modules are available in the repo...)
But remember, VirtualBox will not be automatically updated when you go this way!!!

Why not just do the reasonable thing and create a dummy package which provides virtualbox-host-dkms to satisfy the virtualbox package from the repos?

There is a very good reason why people install things using a package manager...

Scimmia · 2016-03-24 04:08:44

jasonwryan wrote:

Scimmia wrote:
Yeah, don't do that.
If you are going to post, please include some rationale so that a7arch has some chance of learning what they ought to avoid doing. As it is, this is empty posting.

OK, here we go then.

a7arch wrote:

To everybody who doesn't want to install VirtualBox with that huge dkms and developer packages:

The dkms package is anything but huge. The kernel headers are 30-40MB, and the rest are things the large majority of people have installed anyway.

a7arch wrote:

There's still the possibility to install VirtualBox "manually", without the dependencies, from their homepage!

Going around pacman is very, very rarely the answer.

a7arch wrote:

(as long as the kernel modules are available in the repo...)

Which they are not.

a7arch wrote:

1) First, install the kernel modules for VirtualBox with pacman, related to your kernel version, e.g. for kernel v4.4.5-1:
linux44-virtualbox-host-modules (v5.0.16-7)
linux44-virtualbox-guest-modules (v5.0.16-7)

Those packages don't exist.

a7arch wrote:

2) Then download the Installer from the VirtualBox homepage (depending on the virtualbox-version your modules are made for, e.g. in this case v5.0.16-7):
https://www.virtualbox.org/wiki/Linux_Downloads
(see last download link: "All distributions", 32bit/64bit)

The extension pack for this version can be downloaded from here:
https://www.virtualbox.org/wiki/Downloads
Make the downloaded Installer executable (chmod +x VirtualBox-*.run), and start it with "sudo" from the console, e.g.:
sudo ./VirtualBox-5.0.16-105871-Linux_x86.run

If you need to install something to the filesystem outside of your home dir, you should be using pacman. That's what the virtualbox-bin package in the AUR is for.

a7arch wrote:

VirtualBox should now be installed in /opt/VirtualBox/, and you should be able to start it with "virtualbox" from the console, or over the desktop menu...
If not, try these commands:
sudo /opt/VirtualBox/postinst-common.sh
sudo /opt/VirtualBox/vboxdrv.sh
To remove VirtualBox, run "sudo /opt/VirtualBox/uninstall.sh"

Yeah, need sudo to do anything.

a7arch wrote:

I've tested it all by myself, and it worked fine for me, but keeping in mind that the virtualbox binary kernel modules may be removed from the repo in the future, this way is at your own risk!

They were already removed. I can only assume you're not running Arch. Sounds like Manjaro.

Last edited by Scimmia (2016-03-24 04:10:06)

graysky · 2016-03-24 09:47:28

I stopped following the discussion on the ML. Has a decision been made (yay or nay) to supply the modules as precompiled packages?

TheChickenMan · 2016-03-24 10:23:41

graysky wrote:

I stopped following the discussion on the ML. Has a decision been made (yay or nay) to supply the modules as precompiled packages?

Having given everyone time to reply (not that many did...), the
consensus of those that replied is:
- Binary modules are to be provided at minimum of all kernels in [core],
with preference to providing them for all supported kernels (noting that
out-of-tree modules may not work with some patched kernels).
- There is no objection to providing DKMS modules in the repos, but this
is secondary to binary modules. No opinions were stated on whether we
ensure all modules have DKMS variants in the repos.
I decree by the power invested in me through talking the loudest, that
this is now our policy.
Allan

I had been watching this for a bit and think there have generally been good points raised and good decisions moved towards.

graysky · 2016-03-24 17:22:46

Thanks for posting the summary. I checked just now but I don't see the virtualbox-modules provided yet. Perhaps it's just a matter of time?

TheChickenMan · 2016-03-24 18:33:36

graysky wrote:

Thanks for posting the summary. I checked just now but I don't see the virtualbox-modules provided yet. Perhaps it's just a matter of time?

I think this must be a busy week for things upstairs. Gnome, xorg and plasma have updates in staging, testing now.
My crystal ball says that next week is going to be one of those weeks on the forums where 'everyone' has a problem.

Arch Linux

#76 2016-03-09 01:17:55

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#77 2016-03-09 04:46:16

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#78 2016-03-09 05:08:00

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#79 2016-03-09 08:23:27

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#80 2016-03-10 14:42:24

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#81 2016-03-10 16:30:19

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#82 2016-03-10 19:14:15

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#83 2016-03-10 21:43:11

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#84 2016-03-10 21:57:12

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#85 2016-03-12 10:01:18

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#86 2016-03-12 21:16:34

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#87 2016-03-12 23:07:13

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#88 2016-03-13 14:48:23

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#89 2016-03-17 10:48:57

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#90 2016-03-17 10:53:15

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#91 2016-03-17 12:17:40

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#92 2016-03-24 00:18:55

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#93 2016-03-24 00:26:05

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#94 2016-03-24 03:55:02

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#95 2016-03-24 03:59:56

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#96 2016-03-24 04:08:44

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#97 2016-03-24 09:47:28

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#98 2016-03-24 10:23:41

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#99 2016-03-24 17:22:46

Re: [solved] virtualbox depends on virtualbox-host-dkms?

#100 2016-03-24 18:33:36

Re: [solved] virtualbox depends on virtualbox-host-dkms?

Board footer