Sabayon – Virtualbox Installation Woos

  • wolf
  • Tagged , ,
  • April 20, 2012
  • A little matter I would like to bring to your attention is our wiki page for Virtualbox can produce a small surprise.  The scenario is that you download Sabayon 8 version, install it and than decide to install Virtualbox and Virtualbox pulls a lot of stuff including a new kernel of 3.3.  Sabayon 8 iso comes with kernel 3.2 so when you go and install Virtualbox you are indirectly invoking a kernel upgrade.  So the question is how to install Virtualbox.

    Well, here is what I would do.  We keep our packages updated so we might as well upgrade the kernel also, but instead I would do it in a bit of different order of just doing equo install virtualbox-bin, I’d start with kernel-switcher.

    We can use equo search linux-sabayon to see what the latest kernel is.  And in my case it shows sys-kernel/linux-sabayon-3.3-r2 is the latest kernel.  To see what your current kernel version is, simply run uname -r.

    So now we can upgrade the kernel with:

    kernel-switcher switch sys-kernel/linux-sabayon-3.3-r2

    This will than upgrade the kernel and all the needed modules and add the entry to your grub.  Now at this point and time I would reboot and boot into the new kernel.  Once rebooted I would than:

    equo install virtualbox-bin

    The modules should pull, but if not:

    equo install virtualbox-modules#`uname -r`

    Continue On

    depmod -a
    modprobe vboxdrv
    modprobe vboxnetadp
    modprobe vboxnetflt
    usermod -a -G vboxusers YOUR_USER_NAME

    Now go ahead and log out and than log back in so the changes can be applied.


    To get virtualbox modules to load automatically:

        # nano /etc/conf.d/modules

    add to it:

        modules="vboxdrv vboxnetflt vboxnetadp"

    then save and exit, reboot.

    Once you have Virtualbox installed you won’t have to worry about pulling kernels, it’s just that initial install and if there is a new kernel available scenario.  If one had downloaded and install Sabayon 8 and installed Virtualbox before kernel 3.3 came out, one would never of had to fuss with a different kernel.

    The only thing we are really doing that the wiki doesn’t cover is switching the kernel first.  Why do I recommend using kernel-switcher vs just installing it all with equo install virtualbox-bin?  The main thing is, you’re changing kernels so I want to keep that process simple and smooth vs pulling it and doing a bunch of updates along side it.  In theory both methods should work, I just want to take the extra step and make sure it goes right.

    9 thoughts on “Sabayon – Virtualbox Installation Woos

    1. Don’t know if it matters,
      but (advanced)users with a Fresh installed KDE system, using the Official Sabayon 8 release of KDE (NOT the Daily iso) AND want the new kernel, need to first upgrade the system.
      Because it’s still shipped with KDE-4.7.4 , and is on sabayon-weekly repository, Kernel 3.3 is not yet in weekly repo.
      But if one decides to switch to the repository,
      and doing a kernel-switch BEFORE upgrading the system,
      kernel-switcher also pulls the packages for KDE-4.8.2

    2. Is that really the desired behavior? I know equo upgrades shouldn’t pull in kernels, but wouldn’t having an older version of VirtualBox and doing and equo upgrade pull in this kernel?

      Truthfully, I think the kernel-switcher functionality should be built into equo. If equo is attempting to install a new kernel, it should prompt the user if they would like to switch to using that kernel and install all the lovely drivers and whatnot.

      Another option would be to not switch grub to automatically boot a new kernel installed via equo and leave that up to the kernel-switcher. Actually, I almost kind of like this option better. But I don’t know how feasible it is.

    3. Desired? No, but entropy doesn’t have the ability to check and see what the kernel version environment is and than apply the same version of modules. If VB and modules were added to the initial ISOs than one wouldn’t have this problem. If you start to think about it, any initial module not installed before a new kernel is going to do this. We would have to kick out a new release for every kernel change to avoid it. VB just happens to be very popular so I foresee that one causing the most issues.

      Fabio is aware of it and at this time unsure of how to avoid this. I have stressed over and over in the past to our users that blindly updating your system is dangerous, one should always be aware of the changes that the package manager is going to perform. People will throw back at me, well I shouldn’t have to know or understand all that, and all I can think is well, good luck than. It’s no different than going to the doctor or mechanic, I want to know everything before I give the ok.

      Anyway, kernels are always a sticky situation for people.

      Patrick, I would do a equo upgrade and make sure I was current with the repo before doing a kernel switch. I would feel much safer doing that, the lesser the changes with a kernel upgrade the better.

    4. Interesting. I was thinking that even if VB had been on the iso, that an upgrade would still want to pull in a later kernel. I definitely slightly misunderstood the complicatedness of the issue.

    5. Wlofden, i know. That’s why i wrote the first comment on your article., to warn others.

      But i don’t get it. What has changed?
      Afaik, the procedure on the wiki was always right.
      In the past, installing VBox never pulled a new kernel, even when there was one available. (please correct me if i’m wrong)
      And now VBox suddenly pulls a new kernel.

    6. I don’t know what has changed or how it was for sure before as I’m not a big VB user myself. This is first I have seen users mention it.

    7. I just installed Sabayon 8 in virtualbox 4.1.12 with 4.1.12 extension.
      Sabayon has got the kernel 3.2, and Virtualboxguestaddition version 4.1.10.
      I cannot see the shared folders of the host Mac OS.
      Do I have to follow your instructions to see the host shared folders?

      Thank you in advance

    8. Spettro: no.
      If you read more carefully, you’ll see the article is about installing VB in Sabayon, not the other way around. In other words: Sabayon is the host.

    9. All the mirrors for sabayon display no data available or check sum wrong for app-emulation/virtualbox-modules-4.1.12#3.3.0-sabayon.

      I had to download from Oracle and install but it failed to build modules!

      This is a lot of work which has been doomed from the start, why it not simply archived in entropy through sulfur.

    Comments are closed.