I accidentally a word.


AQEMU Now Packaged for Fedora

It has taken some time but my AQEMU package has been accepted by the Fedora Project.

    “AQEMU is a GUI to the QEMU and KVM emulators, written in Qt4. The program has a user-friendly interface for setting the majority of QEMU and KVM options.

It is an open source project started by Andrey Rijov and while a little rough around the edges a viable alternative to virt-manager, particularly for KDE Users.

The packages currently exist in the updates-testing repositories for Fedora 15, Fedora 16, and the yet to be formally released Fedora 17. To install the package on your chosen Fedora release run:

    # yum install –enablerepo=updates-testing aqemu

If you want to help speed up the process for getting AQEMU into the stable repositories be sure to test the package(s) and login to Bohdi to add karma!


Network Bridging in Fedora 16 Without Disabling NetworkManager

Creating a network bridge to allow virtual machines direct access to the network, rather than using network address translation (NAT), is not a new concept. It is however a task that has become more complex since most popular Linux distributions switched to using NetworkManager for, you guessed it, network management.

NetworkManager, unlike the old network management tools, does not currently support the creation of network bridges. As a result of this oversight most articles I have seen on the web which discuss creation of network bridges on Linux recommend turning NetworkManager off. While this is indeed a valid way to handle the problem, it means that you must either manage all network interfaces using the old network management tools or switch NetworkManager on and off as needed.

Personally while I do have a need to create network bridges on a regular basis for my virtual machines I also prefer using the userland tools built on top of NetworkManager to manage my wireless connections.

To this end today I will be illustrating how to create a network bridge on a physical Ethernet interface managed by the old network service while continuing to run NetworkManager for my other connections. As usual my weapon of choice is Fedora, in this case version 16 which has just been released. Let’s get started!


Before getting started make sure your existing network configuration is working by running ifconfig. In particular take note of the device name for your Ethernet device, if you have just moved to Fedora you may find it has changed from what you are used to.

$ ifconfig
p5p1      Link encap:Ethernet  HWaddr 78:84:3C:E0:C8:6D 
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::7a84:3cff:fee0:c86d/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:911 errors:0 dropped:0 overruns:0 frame:0
          TX packets:127 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:108021 (105.4 KiB)  TX bytes:10874 (10.6 KiB)
wlan0     Link encap:Ethernet  HWaddr 90:00:4E:C0:5A:0D
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::9200:4eff:fec0:5a0d/64 Scope:Link
          RX packets:1300699 errors:0 dropped:0 overruns:0 frame:0
          TX packets:860018 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1695740220 (1.5 GiB)  TX bytes:102433188 (97.6 MiB)

From the output we can see that my onboard Ethernet card, which used to be referred to as eth0, is now referred to as p5p1. Importantly we can also see that both devices are up and working.

Stop Services

Before changing the network configuration files it is important to ensure that both the NetworkManager and network services are stopped. You must be root, or have root permissions via sudo, to perform this action.

# systemctl stop NetworkManager.service
# systemctl stop network.service

Stopping the network services can take some time. Note that usually only NetworkManager will be running, after all being able to run both at the same time is what we are out to achieve! Check that both services have actually stopped before continuing.

# systemctl status NetworkManager.service
# systemctl status network.service

The service’s current state will be listed in the ‘Active:’ field in the readout from each command.

Prepare to be Bridged

Change into the directory where the network configuration scripts live.

# cd /etc/sysconfig/network-scripts/

The configuration scripts for your network interfaces live in this folder. The script for each interface is named ifcfg-. So in my case the configuration for the wireless interface is ifcfg-wlan0 and the configuration for the physical Ethernet interface is ifcfg-p5p1.

As the wireless interface is to continue to be managed by NetworkManager no changes are required to its configuration. We do however need to make changes to the configuration of the physical Ethernet interface so that it is ready to be bridged.

Open the configuration for the physical Ethernet interface in your favourite text editor:

# vim ifcfg-p5p1

The exact contents will vary depending on your exact installation. Mine looks like this:


In particular note that the interface is brought up on boot, uses DHCP to obtain a network address, and is currently controlled my NetworkManager. The HWADDR listed is just the MAC address of the device, generally it should be left as is.

To prepare the device to be bridged we need to make two changes:

  1. Set NM_CONTROLLED to “no”, telling NetworkManager not to manage this interface.
  2. Add the line BRIDGE=”br0″ to indicate that the device is to be used by a bridge called br0.

The resultant file is as follows:

At this point only half the configuration is complete. We now need to define the bridge itself.

Define the Bridge

Unlike the Ethernet interface configuration the configuration for the bridge will not exist yet. You will need to create it, usually the first bridge is called br0 and defined in the configuration file ifcfg-br0.

Create the file and add the following contents to it:


This sets up the bridge as an interface that uses DHCP to obtain a network address, starts on boot, and most importantly is not controlled by NetworkManager (not that NetworkManager knows how to control it anyway, but I digress).

Bringing it Up

Now that we’ve configured the bridge, it’s time to bring network services back up. The order in which you start the two services should not matter as the configurations explicitly say which devices should not be controlled by NetworkManager.

# systemctl start NetworkManager.service
# systemctl start network.service

If the services do not come up as expected check the output of systemctl status for the service(s) that fail(s). Other hints may also be present in /var/log/messages. One particular thing to look out for which I have encountered is SELinux issues affecting the DHCP client started by the network service.

Check ifconfig again to verify that both your wireless interface and your new bridge interface have been brought up successfully and have an IP address. Note that the physical Ethernet device will not have an IP address listed, it is instead assigned to the bridge.

Making it Stick

Once both services are running side by side it is necessary to ensure that both will start on reboot.

# systemctl enable NetworkManager.service
# systemctl enable network.service


You have now successfully setup a network bridge while keeping your other network interfaces managed using NetworkManager. In particular this means you can continue to use the userland tools to manager your wireless connections while having a bridge which can be used by your Virtual Machines.

Here is the way the bridge appears in Virtual Machine Manager’s network interface view:


Give your desktop a new look with the elementary icon theme

This post migrated from http://blogs.fedoraproject.org/wp/sgordon/2011/04/03/give-your-desktop-a-new-look-with-the-elementary-icon-theme/

Looking to give your desktop a new look? Try the elementary icon theme. These icons are available in the default Fedora repository for F14. As such they can be installed by issuing the following yum command:

# yum install elementary-icon-theme

To activate the icon theme Gnome users should:

  1. Access System -> Preferences -> Appearance.
  2. With the current overall theme selected click Customize.
  3. Select the Icons tab on the Customize Theme dialog box.
  4. Select elementary or elementary-monochrome from the list provided.
  5. Click Close on both dialog boxes to apply and save the changes.

The instructions for users of other desktop environments such as KDE, XFCE or LXDE will differ. Consult the documentation for your desktop environment of choice if you are unable to find the appropriate settings.


linux.conf.au wrap-up

This post has been migrated from http://blogs.fedoraproject.org/wp/sgordon/2011/02/08/linux-conf-au-wrap-up/

As I mentioned in my previous post last week I attended linux.conf.au which was this year held in 2011. I thought I might do a quick wrap-up linking not only the presentation I made at the Cloud Mini-conf but also some other presentations I attended during the week which might be of interest to other Fedora users.

A colleague and I presented a talk called Deltacloud – Abstracting for Freedom providing an introduction to Deltacloud and the Aeolus Project. The video from the talk is available online as are the slides.  Some specific talks I feel might be relevant or of interest to Fedora users are linked below:

There are of course plenty of other presentations that took place during the week. The videos for these are being made available at http://linuxconfau.blip.tv.


In search of unicorns

This post has been migrated from http://blogs.fedoraproject.org/wp/sgordon/2011/01/28/in-search-of-unicorns/

Over the last week I have had the pleasure of attending linux.conf.au which was held in my home city of Brisbane, Australia. Overall it was a great experience and I hope to write up on some of the specific experiences I had which might be more specifically interesting to the Fedora community over the coming weeks.

Right now however I would like to touch on the ‘Training Allies’ session I attended as part of the Haeksen mini-conference. Effectively the session was an opportunity to review some examples of discrimination which arise from time to time in the FOSS world and indeed the IT industry as a whole.
One of the specific scenarios discussed was the use of pornographic and sexually explicit imagery in conference presentations. As those running the mini-conf detailed some experiences from their own pasts where they had seen this occur and others from the crowd chimed in I distinctly remember rolling my eyes somewhat. In my mind we have long since passed the point where anyone in the industry thought this was acceptable or in any way necessary, right?

Then Friday’s keynote speech rolled around. The full text of the speech and the slides can be found here.  While not everyone might be offended by the slides I think most readers will be observant enough to work out which ones some might not have considered appropriate for a conference which draws attendees from all walks of life. I have no doubt Mark Pesce also realised that some slides would be controversial and this was the intention of including them but that still does not make it acceptable.
Some will debate the linux.conf.au rules word for word, others will be offended by the idea that conference presentations are being censored in some way (or not, as it turns out, otherwise we wouldn’t be having this dialog). I’m not going to try address every argument that either has been made or is likely to be made in defense of this presentation. In fact I’m not even going to directly address any.

The sole purpose of this post is to register that in my personal opinion that such events are not at all helpful in an environment where we are trying to attract individuals, businesses, and governments to open source. They are also completely avoidable and therefore un-necessary.

I will also say I am not sure what the point of having a rule regarding the use of sexually explicit images in presentations is if the enforcement to back it up consists of allowing the presentation to continue unhindered and issue a lame duck apology retrospectively. I do however appreciate the difficult position this scenario put the room organiser in. Ultimately conference organisers shouldn’t require such a rule and be able to rely on the professionalism of community members and people recognising the social consequences of their actions as is traditionally done, alas we can dream.


FOSS drivers for ATI Mobility HD 5xxx (Evergreen series) on Fedora 14

This post has been migrated from http://blogs.fedoraproject.org/wp/sgordon/2010/12/20/foss-drivers-for-ati-mobility-hd-5xxx-evergreen-series-on-fedora-14/

I have had a laptop with an ATI Mobility HD 5xxx video card for some time now. Getting 3D support for this card on Linux has been painful. Unsupported by the FOSS driver included in Fedora releases the only option has been to install the proprietary Catalyst driver. The Catalyst driver works when available but often releases lag long after the versions of Xorg included in the latest Fedora.

I have recently discovered, via a post on fedoraforum.org, that the updated version of the FOSS driver which is currently in the rawhide repository includes support for cards in this series! To install it you can use the following commands (note that the first is only required if you have previously installed the Catalyst drivers):

# yum install fedora-release-rawhide
# yum update --enablerepo=rawhide --nogpgcheck kernel libdrm mesa-* xorg* cairo pixman
# yum remove fedora-release-rawhide

I had some issues with the graphical boot when I rebooted following the installation. By editing my grub settings to ommit the rhgb parameter I was able to successfully boot into my graphical environment which now has 3D acceleration!