Articles, notes and random thoughts on Software Development and Technology
Installing VirtualBox Guest Additions on Fedora 16 and 17 fails because it looks like the kernel headers are not installed by default. After you’ve installed Fedora to VirtualBox, you can manually install the required kernel headers with these steps (summarized from this post)
sudo yum -y update kernel sudo yum -y install kernel-devel kernel-headers dkms gcc gcc-c++
Reboot then install the VirtualBox Guest Additions from the Devices menu.
I’ve had physical drives fail before, but this is a first. I’ve used VirtualBox on and off for years for those times when you need to fire up a guest os and it’s always worked fine, no issues. I just installed Fedora 16 on a new virtual drive image and on the first reboot after installing the VM crashed. After that point VirtualBox wouldn’t boot it any more saying the vdi headers were corrupt.
Wow, ok. Other than messing with headers physically in the image file, it appears there’s no repair options or tools. This is the first time I’ve seen this, so giving it the benefit of the doubt, I downloaded the latest version, 4.1.8, created a new vm and new disk image, and I’m installing again.