Skip to main content

Installing Fedora 16 on VirtualBox

Installing Fedora 16 on Virtualbox is a no sweat activity. But for those uninitiated it probably helps to provide a little guidance. See below for one of the many possible configurations:
General
Name: f16
OS Type: Fedora

System
Base Memory: 1024 MB
Processor(s): 1
Execution Cap: 100%
Boot Order: CD/DVD-ROM, Hard Disk
VT-x/AMD-V: Enabled
Nested Paging: Enabled
 
Display 
Video Memory: 128 MB
3D Acceleration: Enabled
2D Video Acceleration: Disabled
Remote Desktop Server: Disabled
 
Storage
IDE Controller
  IDE Secondary Master (CD/DVD): Empty
SATA Controller 
  SATA Port 0: f16.vdi (Normal, 80.00 GB)
 
Audio
Host Driver: Windows DirectSound
Controller: ICH AC97
 
Network
Adapter 1: Intel PRO/1000 MT Desktop (NAT)
 
Serial Ports
Disabled

USB
Device Filters: 0 (0 active)
This is typical configuration with NAT networking. So guest can connect to the outside world but the outside world cannot connect to the guest directly.

For this exercise, I use live CD as the media for installation. This should be available directly from Fedora or from a mirror site near you, this sample link is from University of Texas.

With LiveCD available and VirtualBox guest configured, it is now time to power-up the guest and start breezing through the installation. Since the base install is easy, I will just show the highlights during install.

Figure 1. Boot screen

Figure 2. First sign that Fedora 16 does not like VirtualBox or VirtualBox does not like Fedora 16 ;) . Basically this tells us that GNOME 3 detected that the machine is not good enough to run GNOME 3 goodies. The bar now is higher to use GNOME 3, need more powerful machine to enjoy it. But it does fallback pretty good.

Figure 3. Fedora 16 live in fallback mode. Got selected Install Hard Drive here to start installing the software.

Figure 4. Select keyboard

Figure 5. Storage device, using iSCSI? Don't know what it means? Pick the first one.

Figure 6. You are warned, this will destroy any existing data ;)

Figure 7. Hostname, provide name as you like.

Figure 8. Pick your time zone. This is used by the system to figure out your local time.

Figure 9. Set root account password

Figure 10. You familiar with partitioning hard disk and specific layout? Nope? Use default

Figure 11. You are being warned again, this will destroy existing layout and of course data.

Figure 12. Installation complete, that was easy.

Figure 13. Welcome to Fedora!!!

Figure 14. Licensing... you using this at home? Yes, just accept it.

Figure 15. Date and time, do you want to keep your time sync with the rest of the world? Enable Synchronize date and time over the network.

Figure 16. Create user that you will be using on this machine on regular basis

Figure 17. Hardware profile, wanna help a little bit Fedora? Then send profile to them

Figure 18. Login screen

Figure 19. GNOME 3 fallback desktop

Now you should have a working Fedora 16 installation in VirtualBox. If you are adventurous and wanna see how full GNOME 3 looks like, then follow along.

Ensure that everything is updated/current:
$: sudo yum check-update
$: sudo yum update
Install supporting libraries and gcc to compile VirtualBox modules:
$: sudo yum -y install gcc kernel-devel
From VirtualBox client window for this guest machine, do Devices | Install Guest Additions... Once ISO is detected, from the terminal do:
$: cd /media/VBOXADDITIONS_4.1.8_75467
Of course, replace the folder above with the version of your VirtualBox. Once inside that folder do:
$: sudo ./VBoxLinuxAdditions.run
Wait for the installation to complete and reboot. Ok, the pain is not over yet. For some reason SELinux and VirtualBox guest additions does not like each other, so we need to let VirtualBox guest additions be exempted from the prying eyes of SELinux. So, do:
$: sudo grep gnome-session-c /var/log/audit/audit.log | audit2allow -M mypol
$: sudo semodule -i mypol.pp
Reboot and congratulations... you now have a GNOME 3 desktop running in VirtualBox. But this is a very short lived celebration as VirtualBox and GNOME 3 are not best of friends :). I find it that it is not stable and gets into your way getting things done. Like not refreshing properly, lock-ups, buttons not responding as you would have expected. To cut the story short, I have to force GNOME 3 to run in fallback mode. Now it is not too bad.

Fedora 16 is free, and I am not directly contributing to the distribution, so the best I can do is praise for the hard work and may the team have the desire to continue to improve the distribution and hopefully in the future get with VirtualBox team and iron out the problems with the integration between these two great projects.

~ts

Comments

Popular posts from this blog

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re

The following add-ins could not be started MonoDevelop.GnomePlatform

Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.