Up to date Sid: Custom kernel, trying to install Virtualbox

[Ralf Mardorf]

On Wed, 2013-03-13 at 09:22 +0100, Ralf Mardorf wrote:
> On Tue, 2013-03-12 at 22:55 -0600, Bob Proulx wrote:
> > Curt Howland wrote:
> > > Also, VB was crashing my system quite reliably last time I had it
> > > installed, and I just got a new CPU. Since I assume VB was accessing
> > > some damaged part of my old CPU, I wanted to try VB before and after
> > > the CPU swap to get a before/and/after comparison.
> > 
> > I am sure you will enjoy your new machine but with the vbox driver the
> > problems you were having probably wasn't your hardware.
> > 
> >   The VirtualBox Kernel Driver Is Tainted Crap
> >   http://www.phoronix.com/scan.php?page=news_item&px=OTk5Mw
> > 
> >   RFC: virtualbox tainting.
> >   https://lkml.org/lkml/2011/10/6/317
> 
> I'm sharing virtualbox settings for Ubuntu and Arch and never had
> troubles, I used it with at least Suse too and I guess also on Debian.
> There never were issues running XP and Linux in VBox.

While on Ubuntu the modules are loaded at start up and I didn't remove
them when not working with VBox, I now will remove them. Thank you for
the link. Perhaps I get rid of issues for my Ubuntu Quantal installs.
OTOH for older Ubuntu I never experienced issues, so they might not be
VBox related. However, for my new Arch install I go another way. I don't
load modules at startup, but only if needed by script, not only for
VBox, even for the Internet and or my next install of Debian, I will do
it the same way.

It was a domain of Windows, that drivers could break audio workstations,
perhaps it became a feature for Linux too ;) and not only for audio
workstations.

Regards,
Ralf