Re: [gentoo-user] Virtualbox VMs not running under 3.0.0-gentoo
>> Yes, I believe that would be your issue. I just handled that when I first >> moved over to openrc that i just added: >> modules="vboxdrv vboxnetadp vboxnetflt" without even thinking out/dealing >> with kernel versions. >> >> Give it a whirl and see if it works after you reload 'em. > > Changed my modules file and now it works fine. > > Does what you show above work with the new methods? I'd FAR rather > have that than this mess: Yes, it does. I have virtually the same setup as you do (i.e. VirtualBox + NVIDIA) and I did not have to make any changes when upgrading to 3.0.
Re: [gentoo-user] Virtualbox VMs not running under 3.0.0-gentoo
On Sun, Jul 24, 2011 at 7:22 PM, Matthew Finkel
wrote:
> On 07/24/11 22:02, Mark Knecht wrote:
>>
>> On Sun, Jul 24, 2011 at 5:16 PM, Daniel Wagener wrote:
>>>
>>> On Sun, 24 Jul 2011 17:09:13 -0700
>>> Mark Knecht wrote:
>>>
Hi,
I just got around to trying my Virtualbox VMs under the new 3.0.0
kernel and they aren't working. It says vboxdrv is not set up. I drop
back to 2.6.39 and they run fine. Please note I really mean only the
VMs won't start. The Vbox GUI runs fine but then cannot start the VMs.
I used make oldconfig to get 3.0.0 working so maybe that caused the
problem but I don't yet see what's wrong looking at the config files.
Most likely this is some problem caused by the new numbering but I
Googled around looking for a solution and didn't find one. Has anyone
else here checked Virtualbox under the new kernel?
Note that VMWare seems to be running fine under 3.0.0, only
Virtualbox is failing.
Thanks,
Mark
>>> You know that these Modules have to be compiled against the running
>>> kernel? A re-emerge should do:
>>>
>>> emerge -1av virtualbox-modules
>>>
>>> Almost forgot: youd also have to reload these modules via modprobe (or
>>> rebooting *hides*)
>>>
>>>
>> Actually, I think I just figured it out. The new way of loading
>> modules re Baselayout/OpenRC I think requires that we tell it what
>> kernel version we're loading the modules for. I'm on the wrong machine
>> right now but this machine has this sort of stuff in
>> /etc/conf.d/modules:
>>
>> k2 ~ # cat /etc/conf.d/modules
>> # You can define a list modules for a specific kernel version,
>> # a released kernel version, a main kernel version or just a list.
>> #modules_2_6_23_gentoo_r5="ieee1394 ohci1394"
>> #modules_2_6_23="tun ieee1394"
>> #modules_2_6="tun"
>> #modules="ohci1394"
>>
>> I'm guessing I need to modify this file to tell it to load the vbox
>> modules for 3_0 kernels
>>
>> Would you concur?
>>
>> Cheers,
>> Mark
>>
> Yes, I believe that would be your issue. I just handled that when I first
> moved over to openrc that i just added:
> modules="vboxdrv vboxnetadp vboxnetflt" without even thinking out/dealing
> with kernel versions.
>
> Give it a whirl and see if it works after you reload 'em.
Changed my modules file and now it works fine.
Does what you show above work with the new methods? I'd FAR rather
have that than this mess:
# aic7xxx
modules_2_6="${modules_2_6} agpgart"
module_agpgart_args_2_6=""
modules_2_6="${modules_2_6} nvidia"
module_nvidia_args_2_6=""
modules_2_6="${modules_2_6} vboxdrv"
module_vboxdrv_args_2_6=""
modules_2_6="${modules_2_6} vboxnetflt"
module_vboxnetflt_args_2_6=""
modules_2_6="${modules_2_6} vboxnetadp"
module_vboxnetadp_args_2_6=""
modules_3_0="${modules_3_0} agpgart"
module_agpgart_args_3_0=""
modules_3_0="${modules_3_0} nvidia"
module_nvidia_args_3_0=""
modules_3_0="${modules_3_0} vboxdrv"
module_vboxdrv_args_3_0=""
modules_3_0="${modules_3_0} vboxnetflt"
module_vboxnetflt_args_3_0=""
modules_3_0="${modules_3_0} vboxnetadp"
module_vboxnetadp_args_3_0=""
Anyway, it's working now so let that be a little guidance for anyone
running into this problem with the new numbering system.
Cheers,
Mark
Re: [gentoo-user] Virtualbox VMs not running under 3.0.0-gentoo
On 07/24/11 22:02, Mark Knecht wrote: On Sun, Jul 24, 2011 at 5:16 PM, Daniel Wagener wrote: On Sun, 24 Jul 2011 17:09:13 -0700 Mark Knecht wrote: Hi, I just got around to trying my Virtualbox VMs under the new 3.0.0 kernel and they aren't working. It says vboxdrv is not set up. I drop back to 2.6.39 and they run fine. Please note I really mean only the VMs won't start. The Vbox GUI runs fine but then cannot start the VMs. I used make oldconfig to get 3.0.0 working so maybe that caused the problem but I don't yet see what's wrong looking at the config files. Most likely this is some problem caused by the new numbering but I Googled around looking for a solution and didn't find one. Has anyone else here checked Virtualbox under the new kernel? Note that VMWare seems to be running fine under 3.0.0, only Virtualbox is failing. Thanks, Mark You know that these Modules have to be compiled against the running kernel? A re-emerge should do: emerge -1av virtualbox-modules Almost forgot: youd also have to reload these modules via modprobe (or rebooting *hides*) Actually, I think I just figured it out. The new way of loading modules re Baselayout/OpenRC I think requires that we tell it what kernel version we're loading the modules for. I'm on the wrong machine right now but this machine has this sort of stuff in /etc/conf.d/modules: k2 ~ # cat /etc/conf.d/modules # You can define a list modules for a specific kernel version, # a released kernel version, a main kernel version or just a list. #modules_2_6_23_gentoo_r5="ieee1394 ohci1394" #modules_2_6_23="tun ieee1394" #modules_2_6="tun" #modules="ohci1394" I'm guessing I need to modify this file to tell it to load the vbox modules for 3_0 kernels Would you concur? Cheers, Mark Yes, I believe that would be your issue. I just handled that when I first moved over to openrc that i just added: modules="vboxdrv vboxnetadp vboxnetflt" without even thinking out/dealing with kernel versions. Give it a whirl and see if it works after you reload 'em.
Re: [gentoo-user] Virtualbox VMs not running under 3.0.0-gentoo
Mark Knecht wrote: On Sun, Jul 24, 2011 at 5:16 PM, Daniel Wagener wrote: On Sun, 24 Jul 2011 17:09:13 -0700 Mark Knecht wrote: Hi, I just got around to trying my Virtualbox VMs under the new 3.0.0 kernel and they aren't working. It says vboxdrv is not set up. I drop back to 2.6.39 and they run fine. Please note I really mean only the VMs won't start. The Vbox GUI runs fine but then cannot start the VMs. I used make oldconfig to get 3.0.0 working so maybe that caused the problem but I don't yet see what's wrong looking at the config files. Most likely this is some problem caused by the new numbering but I Googled around looking for a solution and didn't find one. Has anyone else here checked Virtualbox under the new kernel? Note that VMWare seems to be running fine under 3.0.0, only Virtualbox is failing. Thanks, Mark You know that these Modules have to be compiled against the running kernel? A re-emerge should do: emerge -1av virtualbox-modules Almost forgot: youd also have to reload these modules via modprobe (or rebooting *hides*) I'm about 500% I did all that but I'll do it again just to be sure. I use modules-rebuild -X rebuild to catch all the modules I need to rebuild as well as a few applications that over the years had problems with kernel or xorg-server changes. My list of modules& apps now numbers about 8 and I know virtualbox-modules is part of that list. None the less when I get back to that machine I'll do it again. Thanks, MArk Just to mention something stupid that I would do, and have done, don't forget to make sure the symlink is pointing to the new kernel. I did that the other day with the nvidia drivers. I scratched my head for minute because I did for once remember to rebuild the drivers before I rebooted. Sort of funny in a way. lol It's usually the other way around. One step forward, one step back. Dale :-) :-)
Re: [gentoo-user] Virtualbox VMs not running under 3.0.0-gentoo
On Sun, Jul 24, 2011 at 5:16 PM, Daniel Wagener wrote: > On Sun, 24 Jul 2011 17:09:13 -0700 > Mark Knecht wrote: > >> Hi, >> I just got around to trying my Virtualbox VMs under the new 3.0.0 >> kernel and they aren't working. It says vboxdrv is not set up. I drop >> back to 2.6.39 and they run fine. Please note I really mean only the >> VMs won't start. The Vbox GUI runs fine but then cannot start the VMs. >> >> I used make oldconfig to get 3.0.0 working so maybe that caused the >> problem but I don't yet see what's wrong looking at the config files. >> >> Most likely this is some problem caused by the new numbering but I >> Googled around looking for a solution and didn't find one. Has anyone >> else here checked Virtualbox under the new kernel? >> >> Note that VMWare seems to be running fine under 3.0.0, only >> Virtualbox is failing. >> >> Thanks, >> Mark >> > > You know that these Modules have to be compiled against the running > kernel? A re-emerge should do: > > emerge -1av virtualbox-modules > > Almost forgot: youd also have to reload these modules via modprobe (or > rebooting *hides*) > > Actually, I think I just figured it out. The new way of loading modules re Baselayout/OpenRC I think requires that we tell it what kernel version we're loading the modules for. I'm on the wrong machine right now but this machine has this sort of stuff in /etc/conf.d/modules: k2 ~ # cat /etc/conf.d/modules # You can define a list modules for a specific kernel version, # a released kernel version, a main kernel version or just a list. #modules_2_6_23_gentoo_r5="ieee1394 ohci1394" #modules_2_6_23="tun ieee1394" #modules_2_6="tun" #modules="ohci1394" I'm guessing I need to modify this file to tell it to load the vbox modules for 3_0 kernels Would you concur? Cheers, Mark
Re: [gentoo-user] Virtualbox VMs not running under 3.0.0-gentoo
On Sun, Jul 24, 2011 at 5:16 PM, Daniel Wagener wrote: > On Sun, 24 Jul 2011 17:09:13 -0700 > Mark Knecht wrote: > >> Hi, >> I just got around to trying my Virtualbox VMs under the new 3.0.0 >> kernel and they aren't working. It says vboxdrv is not set up. I drop >> back to 2.6.39 and they run fine. Please note I really mean only the >> VMs won't start. The Vbox GUI runs fine but then cannot start the VMs. >> >> I used make oldconfig to get 3.0.0 working so maybe that caused the >> problem but I don't yet see what's wrong looking at the config files. >> >> Most likely this is some problem caused by the new numbering but I >> Googled around looking for a solution and didn't find one. Has anyone >> else here checked Virtualbox under the new kernel? >> >> Note that VMWare seems to be running fine under 3.0.0, only >> Virtualbox is failing. >> >> Thanks, >> Mark >> > > You know that these Modules have to be compiled against the running > kernel? A re-emerge should do: > > emerge -1av virtualbox-modules > > Almost forgot: youd also have to reload these modules via modprobe (or > rebooting *hides*) > > I'm about 500% I did all that but I'll do it again just to be sure. I use modules-rebuild -X rebuild to catch all the modules I need to rebuild as well as a few applications that over the years had problems with kernel or xorg-server changes. My list of modules & apps now numbers about 8 and I know virtualbox-modules is part of that list. None the less when I get back to that machine I'll do it again. Thanks, MArk
Re: [gentoo-user] Virtualbox VMs not running under 3.0.0-gentoo
On Sun, 24 Jul 2011 17:09:13 -0700 Mark Knecht wrote: > Hi, >I just got around to trying my Virtualbox VMs under the new 3.0.0 > kernel and they aren't working. It says vboxdrv is not set up. I drop > back to 2.6.39 and they run fine. Please note I really mean only the > VMs won't start. The Vbox GUI runs fine but then cannot start the VMs. > >I used make oldconfig to get 3.0.0 working so maybe that caused the > problem but I don't yet see what's wrong looking at the config files. > >Most likely this is some problem caused by the new numbering but I > Googled around looking for a solution and didn't find one. Has anyone > else here checked Virtualbox under the new kernel? > >Note that VMWare seems to be running fine under 3.0.0, only > Virtualbox is failing. > > Thanks, > Mark > You know that these Modules have to be compiled against the running kernel? A re-emerge should do: emerge -1av virtualbox-modules Almost forgot: youd also have to reload these modules via modprobe (or rebooting *hides*)
