I'm going to try and revive the monthly virt status report, detailing
core virt happenings in Fedora, as well as upstream bits that are
particularly interesting for Fedora.
Any comments or suggestions welcome!
Fedora virt status for April + May 2012:
After a week slip, Fedora 17 was released Tuesday May 29! There
were 4 core virt features advertised:
Other interesting virt developments include the availability of
Gnome Boxes, which integrates virt management into the core Gnome Shell
experience. Some info here:
OpenStack Essex, the latest release of the popular cloud computing
stack, was also a Fedora 17 feature:
And finally, oVirt, an advanced server virtualization management system
based on libvirt and KVM, is fully packaged for Fedora 17:
All in all a pretty exciting release!
Since F17 is wrapped, we've started down the Fedora 18 cycle. Some
2012-07-24 Feature Submission Deadline
2012-08-07 Feature Freeze--Planning & Development Ends
2012-08-07 Branch Fedora 18 from Rawhide-- Branch Freeze
2012-08-14 Alpha Change Deadline
So the first real freeze is still two months off, plenty of time! :)
On the features front, nothing has been proposed yet, but expect
announcements in the near future.
If anyone out there has an interesting virt feature they are working
on and that they plan on getting into Fedora 18, drop this list a line
and we can help it get nominated as a part of the Fedora feature process.
Libvirt stable releases
There are now official libvirt maintenance releases:
Right not they are just for the libvirt 0.9.11 version in Fedora 17,
but 0.9.6 releases for Fedora 16 are coming soon, as started by Eric Blake:
libvirt-0.9.11.3 is now in Fedora 17:
This should mean better quality updates, and quicker turnaround on bugfixes
making their way to fedora.
Bugs of note
libvirt pinned to single CPU after suspend/resume cycle ->
all VMs running on the same single core
Basically doing suspend/resume of a machine with a running VM using
with vcpus > 1 causes a performance regression as all guest vcpus
end up running on only 1 host CPU. It sounds like a fix is finally
close to hitting upstream kernel git. Currently this affects all
supported versions of Fedora :(
For people needing an immediate fix, there are workarounds noted here:
firewalld conflicts with libvirt's default network. Basically
if firewalld is started after libvirtd has started, it blows
away the firewall rules libvirt's default network requires to
firewalld is a new stateful daemon, providing a nice dbus API for
applications to interact with iptables related bits.
This was a problem around F17 beta time, since firewalld was on
by default. However that bit was eventually reverted. You will
still see issues if you manually install firewalld though.
Medium term, libvirt will talk directly to firewalld for it's
iptables management, and everything will play nice together.
Expect that, as well as firewalld by default, in the Fedora 18
There have been some recent administrative changes.
virt-maint(a)lists.fedoraproject.org now receives many more
build notifications, as well as bugzilla mail. virt-maint is now a
good list to subscribe to if you are intersted in spam about daily
virt changes in Fedora land:
Also, we now have a nice stable place to host virt related bits on
The virtualization preview repository, which builds rawhide packages
for latest stable fedora, is now available for Fedora 17, and at the
above location. More info here: