[Slackbuilds-users] Virtualbox addons and Virtualbox kernel addons
the_emmel at gmx.net
Mon Sep 12 17:07:37 UTC 2011
On Sat, Sep 10, 2011 at 02:17:07PM +0500, Ozan Türkyılmaz wrote:
> 2011/9/10 Nicolas Kovacs <info at microlinux.fr>:
> > I'm a bit confused about the virtualbox-addons and virtualbox-kernel-addons
> > SlackBuilds. I know they're supposed to be *used* within the GUEST system
> > (I've worked with Virtualbox on CentOS before), but where are they supposed
> > to be *built*? On the host or guest system?
> If they are some systems (Slackware version and kernel version etc)
> then it won't matter but if your guess different than your host, build
> on guest system.
Since we are talking about VirtualBox... I'm having a problem and maybe
one of you can help. I have built virtualbox and the virtualbox-kernel
packages on Slackware64. Now, I'm aware that Slack64 is not exactly
supported (for virttualbox, nothing said about virtualbox-kernel) and
neither is current - which might have something to do with it.
Still, it built fine and as far as I can tell it ought to work. Except
my system won't load the kernel module. dmesg says:
[11687.026629] warning: `VirtualBox' uses 32-bit capabilities (legacy
support in use)
[11788.213363] vboxdrv: Unknown symbol pv_irq_ops (err 0)
Any ideas? What confuses me is that the modul did build without
problems, I just can't use it. Any help appreciated.
As a side note, the current version is 4.1.2. Wondering if there is a
version bump planned for the slackbuild.
emmel <the_emmel at gmx.net>
Fingerprint: 60B4 D8E3 9617 900C 6726 168F D677 5AAD D40F CCE7
Certserver : hkp://pgp.mit.edu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: not available
More information about the SlackBuilds-users