In het verleden heb ik wat kleine probleempjes ondervonden met het draaien van Arch Linux op VirtualBox.
Voordat VirtualBox 2.0 uitkwam ging er iets erg fout met de (virtuele) harde schijf. Als je een beetje meer van je harde schijf vroeg dan was er een flinke kans dat dat uitliep op een kernel panic. Om het compleet te maken, logde VirtualBox al deze schijfperikelen ook nog eens naar een logbestand. Zo raakte je op de host-machine snel gigabytes aan zinloze logbestanden kwijt.
In the past I have experienced quite some annoyances with running Arch Linux on VirtualBox.
Before VirtualBox 2.0 there was something horribly wrong with the disk drivers. If you did slightly more disk I/O than average there was a fair chance you would end up with a kernel panic. Besides, VirtualBox does some spurious logging, trying to tell you that the disk does not work properly. It was very easy to lose gigabytes of host disk space because of the ever-growing logfiles.
Just for reference I paste here the output of the lshw tool, ran on a VirtualBox (1.6.4):
The network interface used by FreeBSD when running inside VirtualBox is usually pcn0 and worked fine up to FreeBSD 6.2 (using NAT). However, the card did not seem to be working that great in FreeBSD 7.0. No IP address was being assigned and I failed to manage how to obtain one nevertheless.
Unfortunately, X.org does not work out of the box when installing it inside VirtualBox on a Gentoo guest machine.
The VESA driver didn't really work when starting X, it spitted out the following line:
Well, maybe the VirtualBox Guest Additions will help out. They installed without a glitch on the Gentoo guest, but when starting X I got a similar error as above, only VESA replaced with some VirtualBox stuff.
A common problem for people running a Linux guest on a Linux host with VirtualBox: bashing Ctrl+Alt+F1 does not have the desired effect, it switches to your first virtual terminal on your host OS while nothing happens in the guest OS. There are two ways of entering Ctrl+Alt+F1 targeting the guest OS:
- HostKey + F1 (where HostKey is often the right Ctrl key)
- First press F1, then Ctrl and then Alt. Your host OS won't pick it up but the guest OS will.
Now I've noted this down I won't forget this anymore.
I think it won't ever happen to me that NFS will 'just work'. During the process of getting server and client work together, you'll almost always encounter at least one permission denied, go to hell.
A few days ago I tried to run FreeBSD in VirtualBox. At first sight all seemed to work well, but as soon as I gave the guest system a little work to do, errors like
popped up on the console.
