The famous Linux-based penetration testing arsenal can run in VirtualBox. In the meanwhile, some tricks are needed to have the latest version fully functional with VirtualBox.
For the ST’HACK Ethical Hacking Contest tonight in Bordeaux (France), everything must be ready for the battle. MacBooks are armed, scripts are ready to be launched and beers are waiting in the fridge. During the preparation, BackTrack 5 R2 was installed on every teammate computers.
VirtualBox is of course the most suitable virtualization solution to run BackTrack. Unfortunately, with this latest version of BackTrack, the VirtualBox Guest Additions cannot be installed on a fresh new install. Fortunately after some modifications, everything can be fixed to compile these additions for the 3.2.6 Linux Kernel of BackTrack 5 R2.
Edit: VirtualBox Guest Additions solution updated with new fixes.
Download and Install
- BackTrack: http://www.backtrack-linux.org/downloads/
- VirtualBox + Oracle VM Extension Pack: https://www.virtualbox.org/wiki/Downloads
If you want support for USB 2.0 devices you must download and install Oracle VM Extension Pack for VirtualBox!
I will not describe the steps to install BackTrack on VirtualBox. A lot of tutorials can be found on the Internet to upgrade to BackTrack 5 R2 or to make a fresh install. But here are some screenshots about the VirtualBox configuration for my MacBook Air i7 1.8Ghz.
Issue #1 (solved): USB device descriptor error
usb 1-1: Device descriptor read/8, error -110 usb 1-1: Device descriptor read/64, error -110
Number of Processor for the Guest OS must be set to 1 or eventually 2…
For example, my MacBook Air has a Core i7 inside, multithreading displays 4 virtual cores. So I have to set a maximum of 2 cores to BackTrack VM Guest to fix this issue. (Even if the recommended number of cores VirtualBox displays is 4).
Issue #2 (solved): VirtualBox Guest Additions
After a fresh new install of BackTrack 5 R2, you should have no issues installing VirtualBox Guest Additions… So, before applying these patches, make sure the installation of VirtualBox Guest Additions fails.
After upgraded from an old version of BackTrack to BackTrack 5 R2, you can face issues installing VirtualBox Guest Additions. These two kinds of errors can occur and lead to a vboxguest kernel extension impossible to load.
The headers for the current running kernel were not found. If the following module compilation fails then this could be the reason.
Building the main Guest Additions module ...fail! (Look at /var/log/vboxadd-install.log to find out what went wrong)
Both issues result to:
Starting the VirtualBox Guest Additions ...fail! (modprobe vboxguest failed)
apt-get install linux-headers-$(uname -r) linux-headers xserver-xorg xserver-xorg-core file-roller # file-roller not needed cd /usr/src/ tar jxf /usr/src/linux-source-3.2.6.tar.bz2 rm /usr/src/linux ln -s /usr/src/linux-source-3.2.6 /usr/src/linux rm /usr/src/linux-headers-3.2.6/include/asm ln -s /usr/src/linux-source-3.2.6/arch/x86/include/asm /usr/src/linux-headers-3.2.6/include/asm ln -s /usr/src/linux-headers-3.2.6 /lib/modules/3.2.6/build ln -s /usr/src/linux-source-3.2.6/arch/x86/Makefile_32.cpu /usr/src/linux-headers-3.2.6/arch/x86/Makefile_32.cpu # Solution required for BackTrack x86 version by SphaZ
Please make sure you have linux-source-3.2.6.tar.bz2 into your /usr/src/ directory… Just in case you need it:
Ready to install VBOXADDITIONS
Verifying archive integrity... All good. Uncompressing VirtualBox 4.1.10 Guest Additions for Linux.......... VirtualBox Guest Additions installer Removing installed version 4.1.10 of VirtualBox Guest Additions... tar: Record size = 8 blocks Removing existing VirtualBox DKMS kernel modules ...done. Removing existing VirtualBox non-DKMS kernel modules ...done. Building the VirtualBox Guest Additions kernel modules Building the main Guest Additions module ...done. Building the shared folder support module ...done. Building the OpenGL support module ...done. Doing non-kernel setup of the Guest Additions ...done. You should restart your guest to make sure the new modules are actually used Installing the Window System drivers Installing X.Org Server 1.7 modules ...done. Setting up the Window System to use the Guest Additions ...done. You may need to restart the hal service and the Window System (or just restart the guest system) to enable the Guest Additions. Installing graphics libraries and desktop services components ...done. Press Return to close this window...
Good job, reboot and enjoy adaptative screen resolution, smooth mouse moves, folder sharing and copy/paste from Host to Guest and vis versa.
Incoming search terms:
- backtrack virtualbox (102)
- Error! Bad return status for module build on kernel: 3 2 6 (i686) (88)
- /var/log/vboxadd-install log (59)
- backtrack macbook air (58)
- backtrack 5 virtualbox (58)
- backtrack 5 r2 virtualbox guest additions (48)
- error! bad return status for module build on kernel: 3 2 6 (x86_64) (43)
- backtrack virtualbox guest additions (37)
- backtrack 5 virtualbox guest additions (35)
- backtrack on macbook air (33)
Ok, it’s been about 4 days I’m working on it, and it’s almost done.
Let me explain a little bit about what I’m trying to build…
I bought another 500Gb Hard Drive, the same as the one I already have in my computer. I wanted to set up a RAID 0 with it, but unfortunately my Mother Board don’t have any RAID Controller on it, and I don’t want to buy one. So I had to choose between Windows RAID Software or MacOS RAID Software… The choice was very easy to make, Windows don’t allow any RAID between partitions, but only between entire Hard Drives. Thus I started to learn a bit about how to make a Software RAID under Snow Leopard… that’s quite easy to do I thus created a RAID 0 for my OS X. But The hard work just began… let me explain why
First of all, you can’t make any RAID between MBR & GUID partitions :/ so you have to make a choice between MBR or GUID for both drives… I heard on insanelymac forums that MBR is a very old partitioning system, and OSX runs faster to access your partitions with GUID. But the fact is that Windows Bootloader sucks with GUID and you know about Seven… there’s no more boot.ini file, everything is wrote into a BCD file to make things harder to access… so… because I love challenges I have chosen GUID
Ok so let’s suppose I want to install Seven onto one of my GUID Drives… it seems easy, but it’s not! Windows don’t understand GUID, so it’ll create a MBR Drive for the bootloader xD (Yeah that’s right!! It sucks!!). So the solution is to install Windows Seven on your second Hard Drive, and let the installer create a bootloader on the first drive that will become a MBR drive.