1 |
On Sun, Jul 24, 2011 at 7:22 PM, Matthew Finkel |
2 |
<matthew.finkel@×××××.com> wrote: |
3 |
> On 07/24/11 22:02, Mark Knecht wrote: |
4 |
>> |
5 |
>> On Sun, Jul 24, 2011 at 5:16 PM, Daniel Wagener<stelf@×××.net> wrote: |
6 |
>>> |
7 |
>>> On Sun, 24 Jul 2011 17:09:13 -0700 |
8 |
>>> Mark Knecht<markknecht@×××××.com> wrote: |
9 |
>>> |
10 |
>>>> Hi, |
11 |
>>>> I just got around to trying my Virtualbox VMs under the new 3.0.0 |
12 |
>>>> kernel and they aren't working. It says vboxdrv is not set up. I drop |
13 |
>>>> back to 2.6.39 and they run fine. Please note I really mean only the |
14 |
>>>> VMs won't start. The Vbox GUI runs fine but then cannot start the VMs. |
15 |
>>>> |
16 |
>>>> I used make oldconfig to get 3.0.0 working so maybe that caused the |
17 |
>>>> problem but I don't yet see what's wrong looking at the config files. |
18 |
>>>> |
19 |
>>>> Most likely this is some problem caused by the new numbering but I |
20 |
>>>> Googled around looking for a solution and didn't find one. Has anyone |
21 |
>>>> else here checked Virtualbox under the new kernel? |
22 |
>>>> |
23 |
>>>> Note that VMWare seems to be running fine under 3.0.0, only |
24 |
>>>> Virtualbox is failing. |
25 |
>>>> |
26 |
>>>> Thanks, |
27 |
>>>> Mark |
28 |
>>>> |
29 |
>>> You know that these Modules have to be compiled against the running |
30 |
>>> kernel? A re-emerge should do: |
31 |
>>> |
32 |
>>> emerge -1av virtualbox-modules |
33 |
>>> |
34 |
>>> Almost forgot: youd also have to reload these modules via modprobe (or |
35 |
>>> rebooting *hides*) |
36 |
>>> |
37 |
>>> |
38 |
>> Actually, I think I just figured it out. The new way of loading |
39 |
>> modules re Baselayout/OpenRC I think requires that we tell it what |
40 |
>> kernel version we're loading the modules for. I'm on the wrong machine |
41 |
>> right now but this machine has this sort of stuff in |
42 |
>> /etc/conf.d/modules: |
43 |
>> |
44 |
>> k2 ~ # cat /etc/conf.d/modules |
45 |
>> # You can define a list modules for a specific kernel version, |
46 |
>> # a released kernel version, a main kernel version or just a list. |
47 |
>> #modules_2_6_23_gentoo_r5="ieee1394 ohci1394" |
48 |
>> #modules_2_6_23="tun ieee1394" |
49 |
>> #modules_2_6="tun" |
50 |
>> #modules="ohci1394" |
51 |
>> |
52 |
>> I'm guessing I need to modify this file to tell it to load the vbox |
53 |
>> modules for 3_0 kernels.... |
54 |
>> |
55 |
>> Would you concur? |
56 |
>> |
57 |
>> Cheers, |
58 |
>> Mark |
59 |
>> |
60 |
> Yes, I believe that would be your issue. I just handled that when I first |
61 |
> moved over to openrc that i just added: |
62 |
> modules="vboxdrv vboxnetadp vboxnetflt" without even thinking out/dealing |
63 |
> with kernel versions. |
64 |
> |
65 |
> Give it a whirl and see if it works after you reload 'em. |
66 |
|
67 |
Changed my modules file and now it works fine. |
68 |
|
69 |
Does what you show above work with the new methods? I'd FAR rather |
70 |
have that than this mess: |
71 |
|
72 |
# aic7xxx |
73 |
modules_2_6="${modules_2_6} agpgart" |
74 |
module_agpgart_args_2_6="" |
75 |
|
76 |
modules_2_6="${modules_2_6} nvidia" |
77 |
module_nvidia_args_2_6="" |
78 |
|
79 |
modules_2_6="${modules_2_6} vboxdrv" |
80 |
module_vboxdrv_args_2_6="" |
81 |
|
82 |
modules_2_6="${modules_2_6} vboxnetflt" |
83 |
module_vboxnetflt_args_2_6="" |
84 |
|
85 |
modules_2_6="${modules_2_6} vboxnetadp" |
86 |
module_vboxnetadp_args_2_6="" |
87 |
|
88 |
modules_3_0="${modules_3_0} agpgart" |
89 |
module_agpgart_args_3_0="" |
90 |
|
91 |
modules_3_0="${modules_3_0} nvidia" |
92 |
module_nvidia_args_3_0="" |
93 |
|
94 |
modules_3_0="${modules_3_0} vboxdrv" |
95 |
module_vboxdrv_args_3_0="" |
96 |
|
97 |
modules_3_0="${modules_3_0} vboxnetflt" |
98 |
module_vboxnetflt_args_3_0="" |
99 |
|
100 |
modules_3_0="${modules_3_0} vboxnetadp" |
101 |
module_vboxnetadp_args_3_0="" |
102 |
|
103 |
Anyway, it's working now so let that be a little guidance for anyone |
104 |
running into this problem with the new numbering system. |
105 |
|
106 |
Cheers, |
107 |
Mark |