Yes there are loads of “how to enable Aero in Virtualbox” posts out there, but they are all long too long 
References:
Something I discovered ages ago (so long ago that my trial license expired) but forgot to post is that you can get an LTM VE to work in Virtual Box.
To get started download the ESX image from the F5 VE Trial Page, when you get the download import the OVA into virtualbox.
The only thing I needed to tweak after the import was the interface settings, you need two intels and a PCNet, the PCNet is the management interface. Set the PCNet to host only networking, give your laptop/pc an ip address on the host only network a 192.168.1 address and you’re good to go!
You may experience HIGH CPU issues after boot, but since these boxes are based on linux, you can use the divider=10 centos trick.
Enjoy your virtual load balancing!
My how to get ACS 5.1 running in VirtualBox is one of my more popular posts; recently I was asked if 5.2 would work, the answer is yes!
I’ve posted an updated ks.cfg … if you compare it to the old one the only real difference is an updated set of version numbers, all the other instructions are exactly the same….well, except now centos 4.7 can be found in the vault 
Next I plan to see if I can make this work in EC2 as I recon a cloud based ACS server would be pretty cool, wish me luck and enjoy the 5.2 goodness!
One of the things I’d really like is process priorities for virtual box. In the forum I posted a couple of shell commands that I regularly type… which gets a bit tedious, following a recent article on lifehacker reviewing mac text expanding I’ve been prompted to automate a few things… below is a little shell script to lower the priority (renice) of all running virtual machines.
The advantage of doing this is that your host machine stays snappy, responsive and won’t get too over-loaded by jobs on your VMs!
#!/bin/bash
ps -xo pid,command | grep -v grep | grep startvm | while read line ;
do
procID=`echo $line | awk '{print $1}'`
sudo renice +10 -p $procID
done
The above code works on a mac; although I haven’t tested it, I recon to get it running on Linux you need to update the PS command, by swapping the x for an e… like this….
#!/bin/bash
ps -eo pid,command | grep -v grep | grep startvm | while read line ;
do
procID=`echo $line | awk '{print $1}'`
sudo renice +10 -p $procID
done
Have fun, suggestions and improvements welcome.
After much swearing and hackerizing I’m happy to post a screenshot of Cisco’s ACS running in VirtualBox
Before I explain what I’ve done, a quick message for “the stupids”
No I won’t post a virtual machine for you to download
Buy a license or an appliance
The rest of this post is a run though of what I did, if you get bored easily skip to the summary.
The story is I’ve got a customer who wants dot1x with ACS5 and I need a box to play with before breaking their network; having read through the docs on cisco.com I noticed that vmware was a supported platform for evaluation, as awesome as that is, carrying around an ESXi server isn’t as convenient as you’d think so I boldly dropped the CD into my VirtualBox and booted to see what happened…. if only it was that simple!!!!!
As expected the installer crapped out early on complaining that VirtualBox is not a valid hardware configuration, so I decided to have a poke around the ISO image and had a moment of realisation.. THANK YOU CISCO FOR CHOOSING CENTOS!
Cisco choosing an open-source installation mechanism means that with a bit of googling I could customise the install process to work in VirtualBox…. sweeet!
To get started I followed the install guide to build a VirtualBox appliance that resembled the supported vmware machine, some things to note:
This is a summary of my VirtualBox configuration…
If you’re hoping to follow my process, I assume you’ve already downloaded from cisco a copy of the ACS_v5.1.0.44.iso and sorted an eval license.
Looking at the contents of the CD I could see that the KickStart file was rejecting my hardware configuration. In my early attempts I edited ks.cfg removing everything between %pre and %post removed the line that said %include and rebuilt the ISO; this had limited success, I could boot further on my new ISO but found that anaconda crapped out as it was unable to find the CD from which it booted … Very Odd!
Messing with the kickstart file and having to rebuild the ISO each time got boring very quickly, especially since it wouldn’t boot into anaconda stage two. I decided to move to a network based installed, I setup a web server on my laptop, downloaded CentOS-4.7-i386-bin1of4.iso and booted my guest from that using linux askmethod at the loader. On my web server I copied the contents of the ACS CD into a directory (including . hidden files), during the centos boot I was able to install “everything” from the ACS directory on web server giving me yet more limited success (Everything was installed – including the Cisco packages – but unusable).
The next step was to get my web installation to read my kickstart file, the ks.cfg has a load of finalization which looked like it created files that the cisco packages would need. I had to change the permissions of the directory to give me write access (CD files copied as RO since the CD was RO). So my edited ks.cfg has nothing between %pre & %post plus the %include line deleted, the result had massive drawback, I’d inadvertently removed the disk layout; I have since concluded that my earlier attempt with everything installed but broke also had issues due to incorrect filesystem partitions.
To put the filesystem layout back into the kickstart file I inserted the following:
part / --fstype ext3 --size=100 --grow part /localdisk --fstype ext3 --size=5120 part /recovery --fstype ext3 --size=1008 part /storedconfig --fstype ext3 --size=981 part /storeddata --fstype ext3 --size=2048 part swap --size=2048
To get the Centos Server to now boot from both the kickstart file and install from my webserver I now have to boot with linux ks=http://192.168.56.1/~nick/ACS/ks.cfg (this is instead of linux askmethod) and replace the line that says cdrom with url --url http://192.168.56.1/~nick/ACS.
After all that trial & error I was finally there! I have attached my ks.cfg for your reference and here is a summary of the steps to reproduce.
Note: During my playing the anaconda installer crapped out a couple of times, just starting the process again seemed to fix the issue, some bottleneck on virtualbox disk accesses could be the problem.
Hope that all makes sense, happy hacking!
I’ve imported my windows box into VirtualBox (howto) and noticed that the keyboard layout is all screwed up.
My Googling suggests that a German and Swedish bloke/bird/person have fixed this issue but no-one in the UK.
Attached is my UK Keyboard layout, also the source file so you can use microsoft keyboard layout creator to make your own.
To use, simply unzip, run setup, and then in your keyboard settings (control panel) change to “English UK – Apple MacBook Pro” … you may wish to remove the default UK keyboard to avoid confusion.
This works well for me in VirtualBox, I would expect it to work in VMWARE / Parallels but I’ve not tested it, as with everything I do YMMV