| 1 |
On Sun, 24 Jul 2011 17:09:13 -0700 |
| 2 |
Mark Knecht <markknecht@×××××.com> wrote: |
| 3 |
|
| 4 |
> Hi, |
| 5 |
> I just got around to trying my Virtualbox VMs under the new 3.0.0 |
| 6 |
> kernel and they aren't working. It says vboxdrv is not set up. I drop |
| 7 |
> back to 2.6.39 and they run fine. Please note I really mean only the |
| 8 |
> VMs won't start. The Vbox GUI runs fine but then cannot start the VMs. |
| 9 |
> |
| 10 |
> I used make oldconfig to get 3.0.0 working so maybe that caused the |
| 11 |
> problem but I don't yet see what's wrong looking at the config files. |
| 12 |
> |
| 13 |
> Most likely this is some problem caused by the new numbering but I |
| 14 |
> Googled around looking for a solution and didn't find one. Has anyone |
| 15 |
> else here checked Virtualbox under the new kernel? |
| 16 |
> |
| 17 |
> Note that VMWare seems to be running fine under 3.0.0, only |
| 18 |
> Virtualbox is failing. |
| 19 |
> |
| 20 |
> Thanks, |
| 21 |
> Mark |
| 22 |
> |
| 23 |
|
| 24 |
You know that these Modules have to be compiled against the running |
| 25 |
kernel? A re-emerge should do: |
| 26 |
|
| 27 |
emerge -1av virtualbox-modules |
| 28 |
|
| 29 |
Almost forgot: youd also have to reload these modules via modprobe (or |
| 30 |
rebooting *hides*) |
Archives