SysAdmin Adventures

By default, USB support does not work when installing VirtualBox PUEL on a Slackware host. Essentially it is a permissions issue. There are a number of ways around it, but the simplest is this ridiculously small change to rc.S.

rc.S (downloadable rc.S.diff.gz):

This patch effectively changes the automatic permissions on USB devices so that the group owner is the plugdev group and so the group owner has write permissions. Make sure any users in the vboxusers group are also in the plugdev group… but you knew that.

In order to apply the above patch, do the following as root:

Or just make the change by hand, given how small it is.

A little warning.. although it could be related to the specific virtual-hardware setup I am running, Windows XP SP2 OEM will not activate when running as a guest inside VirtualBox v3.1.2 nor will it let you login without activation.

You get to the login screen and attempt to login and it says:
“This copy of Windows must be activated with Microsoft before you can log on. Do you want to activate Windows now?”. If you try and activate Windows over the Internet it will appear to be successful, but log you straight back off again and put you back where you started. If you try and activate over the telephone, there will be no “Installation ID” for you to give in order to activate; this is what I believe to be the root cause of the problem.

The Installation ID is generated from information about your computer including information from the graphics adapter, the hard disk controller etc. If there is a problem getting identification information from any of the devices it uses, the routine that generates an Installation ID will return 0 and you will have no ID, no activation and no use of XP.

Fun, huh?

I am still working on the problem at the moment, but I am led to believe that slip-streaming SP3 with the installation will solve the problem and that’s what I’m working on right now. It’s also possible that enough modifications to the virtual hardware configuration will bypass whatever is acting as a faulty component, but I’m hoping to avoid resolving the problem by manually tweaking every single hardware setting until I find what works.

UPDATE:
SUCCESS!! I slip-streamed SP3 into my standard SP2-OEM disk and it works perfectly, no activation issues whatsoever.