Fedora Weekly News Issue 173
Welcome to Fedora Weekly News Issue 173 for the week ending April 26th,
This week's issue starts with a welcome double dose of FedoraPlanet
coverage, providing news and views from around the Fedora community. Our
Ambassadors beat shares the LinuxFest Northwest experience. Developments
covers the controversy over "PulseAudio: A Hearty and Robust Exchange of
Ideas" and in Translation word comes of Fedora 11 Release Notes
proofreading readiness. Configuration conflagration of Wacom graphics
tablets is revealed in the Art beat. The Fedora Weekly Webcomic divines
an unbreakable future. We're brought up to date with SecurityAdvisories
for Fedora 9 and 10, and the Virtualization beat completes the issue
with updates on virtualization status in Fedora, with specifics on a new
libvirt 0.6.3 release, a new libguestfs 1.0.10 release, and KVM
migration support in Fedora 11, to name but a few!
If you are interested in contributing to Fedora Weekly News, please see
our 'join' page. We welcome reader feedback:
FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala
1.1 Planet Fedora
1.2.1 Fedora first at LinuxFest Northwest
1.2.2 Got Ambassador News?
1.3.1 Fedora 10 Packages in dist-f11
1.3.2 Bugzilla Passwords
1.3.3 PulseAudio: A Hearty and Robust Exchange of Ideas
1.3.4 Re-starting udev
1.3.5 Fedora Bug-tracker Independent from Red Hat ?
1.3.6 FOSS Needs a Central Bugtracker ?
1.4.1 Fedora 11 Preview Release Notes Proof-reading
1.4.2 Fedora 11 User Guide f11-tx Branch Available
1.4.3 New Members in FLP
1.5.1 Cleaning the Queue
1.5.2 Graphic Tablets
1.6 Fedora Weekly Webcomic
1.7 Security Advisories
1.7.1 Fedora 10 Security Advisories
1.7.2 Fedora 9 Security Advisories
1.8.1 Fedora Virtualization List
184.108.40.206 New Release libguestfs 1.0.10
220.127.116.11 Only libvirt Bug Fixes in updates-testing
18.104.22.168 Fedora Virtualization Status Report
1.8.2 Fedora Xen List
22.214.171.124 Dom0 Kernel Not Before 2.6.31
1.8.3 Libvirt List
126.96.36.199 New Release libvirt 0.6.3
188.8.131.52 KVM Migration Support in F11
== Planet Fedora ==
In this section, we cover the highlights of Planet Fedora - an
aggregation of blogs from Fedora contributors worldwide.
Contributing Writer: Adam Batkin
The Planet Fedora beat recently took a short vacation, but is back this
week fully refreshed. This issue not only contains posts from the past
week, but also a few highlights from the preceding two weeks when there
was no coverage.
Eric Christensen announced a new policy for deleting pages on the
Fedora Project Wiki.
Martin Sourada chronicled a few of the many features that can be
expected with the upcoming Fedora 11 (Leonidas): Intel Kernel Mode
Setting, faster boot times, better USB camera support, touchpad
improvements (and a new tab within the Mouse Preferences applet),
PackageKit interface updates, the use of Presto to shrink updates
downloads (which could use some additional testing, for anyone
interested) and more. And with the release of the Synaptics 1.1 driver,
Peter Hutterer described some of its new features, including
additional details about multi-touch support.
Seth Vidal analyzed the Source RPMS that make up various Fedora
releases since F7 to find the average number of patches per RPM.
Happily, the numbers have been slowly but steadily decreasing.
Silas Sewell demonstrated funcshell a new project to build a shell
interface around func with all of the features expected of a shell
including tab completion, persistent history and integrated help.
Josh Boyer mused over "The updates conundrum" and the often larger
than expected number of updates in released Fedora versions. "When I see
a package update submitted that just takes a package to the latest
upstream release, I always question it in my head (and sometimes in the
update). I realize that upstream releases often fix bugs that effect
users, however the update should say that at a minimum and it generally
doesn't. Many times there is an update like this that seems to just be
'because it's the newest!'"
Luis Villa questioned whether it might make sense to have a full-time
QA person for Xorg with costs shared across some of the many contributor
Marc Ferguson shared an Abbot and Costello "Who's on First" parody in
which Abbott attempts to purchase a computer from Costello.
Venkatesh Hariharan wrote an article that appeared in Network
Computing's India edition, titled "Reaping the benefits of open source".
Lubomir Rintel scripted a set of bash functions to automatically
label terminal windows (and tabs).
Matthew Daniels summarized his experiences at POSSCON2009 (Palmetto
Open Source Software Conference) in which a number of interesting and
prominent people spoke including Red Hat's CIO, Lee Congdon, among
Amit Shah re-evaluated the performance of a number of Linux
filesystem and option combinations.
== Ambassadors ==
In this section, we cover Fedora Ambassadors Project.
Contributing Writer: Larry Cafiero
=== Fedora first at LinuxFest Northwest ===
Fedora was on hand for the LinuxFest Northwest in Bellingham,
Washington, USA, on Saturday and Sunday, and Fedora was "first" insofar
as it was the first booth for folks come to when they entered the hall
at Bellingham Technical College.
Saturday was a busy day for Fedora at LinuxFest Northwest. Larry Cafiero
gave a presentation before the Fedora Activity Day, which drew about 30
people. The FAD at LFNW revolved around three different projects: The
4th Grade Math Project for OLPC, an F11 bug fest, and general Fedora
questions-and-answers. The flexibility of the event was its strength,
and its weakness was the timing, so while it was overall a success,
there were still a few bugs in the FAD system.
Karsten Wade gave his "Participate or Die" talk on Saturday afternoon --
a talk that is destined for a keynote at some fortunate Linux festival
(Open Source World missed out by denying it, pity). On Sunday, Jesse
Keating gave two presentations today -- sneak-peeking at F11 and Modular
Infrastructure Design with Messaging (the official name) -- and
sandwiched between them was Clint Savage's Fedora Remix gig.
A significant amount of buttons, media and stickers were given out, as
well as some T-shirts for the Fedora faithful.
=== Got Ambassador News? ===
Any Ambassador news tips from around the Fedora community can be
submitted to me by e-mailing lcafiero-AT-fedoraproject-DOT-org and I'd
be glad to put it in this weekly report.
== Developments ==
In this section the people, personalities and debates on the
@fedora-devel mailing list are summarized.
Contributing Writer: Oisin Feeley
=== Fedora 10 Packages in dist-f11 ===
Kalev Lember drew attention to the issue of .fc10 packages ending up
in rawhide by error during the freeze. Kalev worried that he had done
something wrong to make the rawhide composes pull .fc10 rpms from the
Fedora 10 stable-updates repository.
Josh Boyer thanked Kalev for identifying the issue and explained that it
was an error due to koji tag inheritance. Jesse Keating added that
his efforts to ease tag requests had forgotten to take tag inheritance
into account but that he would fix this shortly.
=== Bugzilla Passwords ===
Another thread about bugzilla (see also this FWN#173 "FOSS Needs a
Central Bugtracker" and "Fedora Bugtracker Independent from Red Hat?")
concerned itself with the automated requirement to change to a new
user password. Felix Miata was upset that he could not use previous
passwords: "If you won't let me choose my password, I have no use for
you. I have too many systems and web browsers to use and too many places
that need passwords for any site to decide I can't use my choice of
password [...] I've changed banks over lesser stupidities."
Matthias Saou and Ian Weller suggested a dirty work-around.
Konstantin Ryabitsev suggested using supergenpass. Basil Mohamed
Gohar and Adam Williamson liked the GNOME combination of Password
Generator and Revelation.
After some questioning of the motivations and need for such password
changes Jesse Keating rationalized regular password changes a little
sarcastically: "There is a theory that changing passwords on a regular
bases lessens the risk of somebody's password being stolen and used
nefariously. Depending on the account compromised the damage increases
from nuisance to legally damaging[...]" and suggested that a more
worthwhile discussion would be "[...] whether or not the pains we hit
here are worth the pains we'd encounter by running our own instance of
This questioning started the list that there was "[...] a plausible
case that doesn't involve Red Hat data - not-yet-public security issues
- was subsequently cited. Even if we split Fedora bugzilla from Red Hat
bugzilla, it'll still contain sensitive data."
to hone-in on the idea that the changes were done mainly to fulfil
Red Hat business requirements and Adam Williamson
=== PulseAudio: A Hearty and Robust Exchange of Ideas ===
Executive summary: a long flamewar resulted in at least three things:
1)the original problem over how to individually control volumes on the
"Master" and "PCM" channels was solved; 2)a subsidiary problem of
graphical control allowing selection of the input device was rectified
by re-packaging the old gnome-alsamixer; 3)tension between the
Desktop team, FESCo, the Board and everyone else was increased. Read on
only if you must.
A long, multi-thread flamewar over the (dis)advantages of the new
VolumeControl (more specifically gnome-volume-control) applet in Fedora
11 smoked and crackled. The gnome-volume-control applet provides a
highly simplified interface to the PulseAudio sound server, itself a
source of contention for some time. The extent of this simplification
contrasted to the old volume-control applets which talked directly to
ALSA and exposed all the details of a card was emphasized in
screenshots of the "Alsa-Mixer-O-Doom" posted by Dave Jones and Will
Woods. A bugzilla filed by Adam Williamson explains that hiding the
mixer channels makes it difficult to handle many scenarios which require
the adjustment of specific mixer channels in order to achieve basic
Although there has been prolonged sniping at PulseAudio for some time
this week's dispute seemed more unpleasant and prolonged than many. Its
tangled, sprawling mess eventually drew in FESCo and flung its tendrils
into issues of whether FESCo should dictate UI design and the possible
reversion of the entire "VolumeControl" feature, and whether
FESCo had jurisdiction over what went into the Desktop spin.
The first thread started in Callum Lerwick's request for
information on how to adjust volume informations on individual channels.
He explained that he was hooking a second computer up to the "line-in"
to share speakers and needed to adjust the PCM volume. Bastien Nocera
thought that Callum's use case was esoteric and would not be
accomodated. He suggested using PulseAudio over the network instead. A
later report by Joonas Sarajärvi suggested this should be possible.
Things went downhill from then on when Callum asked for "[...] an
option to get the old damn panel applet back [or] at least a secret
gconf key to do what I want?" and characterized the Volume Control
applet as "immature". Bastien's response was that the applet had
been described for over a year on the wiki and he suggested the GConf
was not of use because the volume control worked at the level of
PulseAudio and not ALSA. Lennart Poettering also suggested that
on the command-line would provide the level of control desired for those
who wanted "pretty exotic feature[s and] weird stuff like [playing audio
through line-in]." Many insults were exchanged. Kevin Kofler
helpfully responded to Callum Lerwick's complaint that Pidgin alert
sounds exploded his speakers with the suggestion that he edit
flat-volumes = no
Following suggestions from Lennart and Kevin Kofler success was finally
achieved in loading the alsa-sink module so that the PCM volume
could be controlled.
Elsewhere in this thread Lennart provided several high-level overviews
of how sound should be handled on a desktop including obsoleting playing
audio CDs via the classic "analog" path
A question from Andreas Thiemann asked how it came about that while his
sound volume was acceptable with the MS Windows software mixer set to
75% and the physical speaker volume set to 50% he needed to set all of
the physical volume, gnome-volume-control and the PCM volume (via an
ALSA mixer) to 100% to achieve similar volumes on GNU/Linux. Lennart
explained that this was due to insufficient information in the alsa
mixer init database and that patches to this database from anyone
needing to manually fix their settings would be very useful. Apparently
"[...] unning alsamixer -c0 alsa will remember [the fixed settings] and
hence [users] never get annoyed by [sound problems] anymore so they
don't remember to post [these patches to the database.]" Lennart
expanded on how to generate such patches to alsa-utils'
/lib/alsa/init/hda. Adam Williamson worried that the roots of this
specific problem lay elsewhere.
The aforementioned database suggested to David Woodhouse a need
for a way for users to manually tweak their sound settings for the
inevitable cases in which the database lacked (or contained inaccurate)
information on specific hardware. David also explained that the new
VolumeControl applet was not yet ready for prime-time in his opinion.
The thread was summarized beautifully by Fernando Lopez-Lezcano as
an infinite loop.
A second thread was started by Dimi Paun in which he bemoaned some
unspecific problems with sound in Fedora 11. This was met with mixed
anecdotal statements confirming or denying the general assertion and a
request for specific bugzilla entries.
A third thread was initiated by Adam Williamson. He proposed "[...]
in the spirit of light rather than heat [to] include by default an
alternative GUI app which allows direct access to the mixer channels.
This won't be an applet or anything else persistent, just an application
that you can choose to run if you need that level of access[.]" It
should be noted that this proposal addressed a different problem to the
one expressed by Callum Lerwick (solved as noted above by poking around
at ALSA), instead it addressed some of the other relatively frequent
By this time tempers were very frayed and although there was strong
agreement that this temporary, stop-gap measure was a good compromise
for Fedora 11 there were plenty of histrionics. Jesse Keating 's
suggestion that the alternative GUI application contain "some text [...]
that instructs people to file bugs [so] we can capture the use cases
that the default mixer is missing and help the developers better target
things" was dismissed by Olivier Galibert Olivier asserted that
Lennart would not fix such bugs: "You may not have noticed, but when
people indicate a case that is seemingly not supported by PA,
politely and everything, the answer by the main PA developer is either
one or both of `don't use PA then' or `your use case is rare and
uninteresting and won't be supported'." David Woodhouse reinforced
the point and argued that too many bugs were closed by PulseAudio
developers as WONTFIX. Adam Williamson returned to his central point
which was that "[...] new g-v-c has no way to select the input device.
If the default does not happen to be the one you actually want to record
from, you're stuck. The rest of the cases discussed have really been
either bugs or corner cases and I'm not too concerned about those, the
bugs will be fixed and we shouldn't worry about corner cases too much.
Input switching is the biggie, and it is not a `legacy use case', it is
half of the functionality of any sound adapter. Lennart has acknowledged
this as a missing feature that will be added in the F12 timeframe, which
is why I've already said that as long as that happens - and most of the
`the slider doesn't really control my volume' bugs are fixed - I'd be
happy for the alternative mixer not to be installed by default from F12
Lennart responded to arguments from Kevin Kofler and David Woodhouse
that the new gnome-volume-control was too simplified with an assertion
that most current soundcards offloaded signal processing to CPUs with
MMX and SSE extension. This, he argued, meant that "the only controls
that are really necessary are NOT those which control signal processing
but those which control routing."
Towards the end of all this FESCo held its weekly meeting and the IRC
logs contain a full record of what KevinFenzi's "FESCo Meeting
Summary for 2009-04-24" handily summarizes as: "Long and contentious
discussion about concerns with the VolumeControl feature. FESCo decided
to get gnome-alsamixer packaged and added to the default desktop
live/install spins to allow users whos use cases are not covered
currently by VolumeControl to have a GUI way to adjust mixer settings.
Hopefully this will be dropped/revisited in F12." David Woodhouse
described this as a compromise about which he had serious
Christopher Aillon expressed unhappiness with post-freeze changes
and cited the unhappy example of Codeina. Jesse Keating refuted the
comparison as "[...] a compromise for the sake of F11 was reached, one
that doesn't require any changes to existing software, only the addition
of one package. Comparing it to the Codina fiasco isn't exactly fair."
An insightful discussion about the relationship between the "desktop
spin" and the "default spin" was conducted between Paul W. Frields,
Toshio Kuratomi and others. KevinFenzi and Adam Williamson did
not agree with Paul that the functionality provided by
gnome-alsamixer was "bit-twiddling" and saw it instead as basic and
As of going to press personal abuse of Lennart Poettering continued
=== Re-starting udev ===
Following a security flaw in udev for which patches were quickly
made available "Dennis J." asked: "What is the proper procedure to
update infrastructure components like udev or hal without rebooting the
machine? udev for example doesn't have an init script." Dennis pointed
out that with virtualization becoming more common reboots of host
machines are something which it would be nice to avoid.
M.A. Young provided the information that udevd is started from
/etc/rc.d/rc.sysint and can be restarted with:
=== Fedora Bug-tracker Independent from Red Hat ? ===
Basil Mohamed Gohar asked for constructive criticism of a proposal
which would result in the Fedora Project community hosting its own
bugzilla instance. Basil attempted to provide some guidelines for the
Although several participants admitted that it would be nice if bugzilla
were faster Will Woods identified resource constraints which rendered
the discussion pointless: "This discussion is moot unless you can find
someone with the manpower, hardware, bandwidth, and expertise to
maintain such a bug tracker - 24/7/365 - for the entire Fedora
community. So far we've identified *one* organization willing to do that
- Red Hat's Bugzilla team. Unless you've got someone else who can commit
to that, there's really nothing else to discuss."
A practical disadvantage pointed out by Mike McGrath of implementing
Basil's scheme was that currently users of Fedora, Red Hat and CentOS
only need to go to a single place to file bugs.
Matēj Cepl ranted a little when Basil approved of the "FOSS
Needs a Central Bugtracker?" thread (see this same FWN#173). Matej
quoted Alan Cox's essay advising how to "Beware `We should', extend a
hand to `How do I?'".
=== FOSS Needs a Central Bugtracker ? ===
Markg85 started a longish thread in which he proposed to start a
single FOSS bugtracker for "[the] top 10 major foss distributions for
now i think[.]"
David Woodhouse thought that OpenID might be simpler, but wondered
what sort of bugs would be filed by people without the attention-span to
register for an account with each bug tracker. Colin Walters also
suggested on focusing on less universal solutions and proposed "[...]
more tractable, incremental problem to take on that would get us closer
to what you want, consolidating project hosting would be a good start.
For example, I'm very much against developers hosting projects on e.g.
some old Trac instance on their personal vserver, for many reasons,
among them that if at some later time they get bored or whatever, the
server goes down and with it a lot of useful data."
== Translation ==
This section covers the news surrounding the Fedora Translation (L10n)
Contributing Writer: Runa Bhattacharjee
=== Fedora 11 Preview Release Notes Proof-reading ===
John J. McDonough announced the availability of the built version of
the Fedora 11 Preview Release Notes for proof-reading. These notes would
be available until Fedora 11 GA.
=== Fedora 11 User Guide f11-tx Branch Available ===
The f11-tx branch of the Fedora 11 User Guide is now available at
for translation submissions.
=== New Members in FLP ===
JoseRoberto (Brazilian Portuguese), Pavel Lobach (Russian), Sergey
Danilov (Russian), and Martin Zehetmayer (German) joined the
Fedora Localization Project this week.
== Artwork ==
In this section, we cover the Fedora Artwork Project.
Contributing Writer: Nicu Buculei
=== Cleaning the Queue ===
This week some fresh blood started to help in cleaning the requests
queue of the Art team, with Israel Rodríguez Alonso proposing a
design for "4foundations Flags", Daniel Martinez Sarta trying a
T-shirt and some other newcomers still trying to get heir feet wet.
=== Graphic Tablets ===
Israel Rodríguez Alonso's efforts to configure a Wacom graphic
tabled, solved with Martin Sourada advice of using the pre-built
binaries "why do you try to install the linuxwacom software (and from
prebuilt binaries instead of recompiling them first) when there is
linuxwacom package available" drove Paul W. Frields to ask for a
recommendation "I want to buy a drawing tablet, preferably something
very well supported in Fedora and using USB. I'm assuming Wacom is the
way to go, but I'm not sure which model to get, and I'm open minded as
long as I know it's solid and works well with Fedora" and Máirín Duffy
shared her experience "I've always had luck with the Wacom graphire
series. They're quite affordable, [...]. For years now they just work
out-of-the-box, and if you want pressure-sensitivity, it's just a little
== Fedora Weekly Webcomic ==
This week something unbreakable is prophesied.
== Security Advisories ==
In this section, we cover Security Advisories from
Contributing Writer: David Nalley
=== Fedora 10 Security Advisories ===
* cups-1.3.10-1.fc10 -
* xpdf-3.02-13.fc10 -
* moin-1.6.4-1.fc10 -
* epiphany-2.24.3-5.fc10 -
* firefox-3.0.9-1.fc10 -
* epiphany-extensions-2.24.0-7.fc10 -
* xulrunner-184.108.40.206-1.fc10 -
* blam-1.8.5-9.fc10 -
* devhelp-0.22-7.fc10 -
* gecko-sharp2-0.13-7.fc10 -
* galeon-2.0.7-9.fc10 -
* gnome-web-photo-0.3-17.fc10 -
* gnome-python2-extras-2.19.1-29.fc10 -
* mozvoikko-0.9.5-9.fc10 -
* Miro-2.0.3-3.fc10 -
* google-gadgets-0.10.5-5.fc10 -
* kazehakase-0.5.6-4.fc10.1 -
* perl-Gtk2-MozEmbed-0.08-5.fc10.2 -
* mugshot-1.2.2-8.fc10 -
* pcmanx-gtk2-0.3.8-8.fc10 -
* ruby-gnome2-0.18.1-5.fc10.1 -
* yelp-2.24.0-8.fc10 -
* glib2-2.18.4-2.fc10 -
=== Fedora 9 Security Advisories ===
* cups-1.3.10-1.fc9 -
* xpdf-3.02-13.fc9 -
* moin-1.6.4-1.fc9 -
* firefox-3.0.9-1.fc9 -
* xulrunner-220.127.116.11-1.fc9 -
* chmsee-1.0.1-11.fc9 -
* epiphany-2.22.2-10.fc9 -
* epiphany-extensions-2.22.1-10.fc9 -
* blam-1.8.5-8.fc9.1 -
* devhelp-0.19.1-11.fc9 -
* gnome-python2-extras-2.19.1-26.fc9 -
* google-gadgets-0.10.5-5.fc9 -
* galeon-2.0.7-9.fc9 -
* gnome-web-photo-0.3-20.fc9 -
* evolution-rss-0.1.0-10.fc9 -
* mugshot-1.2.2-8.fc9 -
* Miro-2.0.3-3.fc9 -
* ruby-gnome2-0.17.0-8.fc9 -
* gtkmozembedmm-1.4.2.cvs20060817-28.fc9 -
* mozvoikko-0.9.5-9.fc9 -
* kazehakase-0.5.6-4.fc9.1 -
* totem-2.23.2-14.fc9 -
* yelp-2.22.1-11.fc9 -
== Virtualization ==
In this section, we cover discussion on the @et-mgmnt-tools-list,
@fedora-xen-list, and @libvirt-list of Fedora virtualization
Contributing Writer: Dale Bewley
=== Fedora Virtualization List ===
This section contains the discussion happening on the fedora-virt list.
==== New Release libguestfs 1.0.10 ====
Richard Jones announced release 1.0.10 of libguestfs.
Born only a couple of weeks ago(FWN#171), libguestfs has progressed
very far very fast. The package is currently being reviewed for
inclusion the Fedora repo.
"libguestfs is a library for accessing and modifying guest disk images.
Amongst the things this is good for: making batch configuration changes
to guests, getting disk used/free statistics (see also: virt-df),
migrating between virtualization systems (see also: virt-p2v),
performing partial backups, performing partial guest clones, cloning
guests and changing registry/UUID/hostname info, and much else besides."
Features in 1.0.10 include:
* bindings for: C, C++, Perl, Python, OCaml, Ruby, Java and shell
* KVM support
* QEMU binary is completely configurable at compile & runtime
* ext4 support
* support for uploading and downloading arbitrary-sized files
* support for uploading and downloading tar and tar.gz content
* support for querying size of block devices, setting r/o
* support for reading ext2/3 superblocks
* stat, lstat, statvfs commands
* commands to mount filesystems read-only
* run arbitrary commands from the guest
* file(1) command
* readline in guestfish with history and tab completion
* guestfish 'edit' command
* big documentation improvements, including more on the internals
* pkgconfig file
Richard posted some example uses of the libguestfs command line tool
==== Only libvirt Bug Fixes in updates-testing ====
Daniel Berrange described "introducing major new features into the
stable release stream" as a problem and switch to "a pretty strong
bugfix only policy..." Mark McLoughlin announced that this has now
* libvirt 0.6.1 has been unpushed from F9 and F10 updates-testing
* The latest version available in F9 and F10 updates is 0.5.1
* We do not expect to push new versions to F9 and F10, only bug fix
updates for 0.5.1
The rapid speed of Fedora releases every 6 months can not keep up with
the lightning fast libvirt releases happening every month. To gain
access to the new features and technologies offered by these new
releases, Mark offers "We are still planning on setting up a 'preview'
repository where the latest versions of virt packages from rawhide will
be available to Fedora stable release users".
In the meantime Daniel Veillard posts a src rpm with each release
and "I also build binaries rpms for the flavour of the day I run on my
workstation which is why you will find signed binaries too for F9
==== Fedora Virtualization Status Report ====
Mark McLoughlin provided another excellent round up of the latest
bugs and developments with virtualization in Fedora.
=== Fedora Xen List ===
This section contains the discussion happening on the fedora-xen list.
==== Dom0 Kernel Not Before 2.6.31 ====
The upstream Xen dom0 work done by Jeremy Fitzhardinge was recently
cleaned up and reorganized into two branches:
* Known-working - xen-tip/master
* Bleeding edge - xen-tip/next
Michael Young builta new experimental dom0 kernel version
2.6.30-0.1.2.21.rc3 "based on the Fedora devel kernel branch and [the]
xen-tip/next branch from the pvops kernel repository." An RPM of this
kernel may be found in Michael's yum repo.
Michael also drew attention to the fact that "very few xen patches made
it into 2.6.30, just bugfixes and tidy ups, so we are waiting at least
until 2.6.31 for mainline dom0 support."
=== Libvirt List ===
This section contains the discussion happening on the libvir-list.
==== New Release libvirt 0.6.3 ====
Daniel Veillard announced a new libvirt release, version 0.6.3.
"The main points are the VirtualBox driver and a number of bug fixes."
Read the post for details of other changes.
* VirtualBox driver support (Pritesh Kothari)
* virt-xml-validate new command (Daniel Berrange)
* add SCSI storage rescan (David Allan)
* rootless LXC containers support improvements (Serge Hallyn)
* getHostname support for LXC (Dan Smith)
* cleanup and logging output of some domain functions (Guido
* drop pool lock when allocating volumes (Cole Robinson)
* LXC handle kernel without CLONE_NEWUSER support (Serge Hallyn)
* cpu pinning on defined Xen domains (Takahashi Tomohiro)
* dynamic bridge names support (Soren Hansen)
* LXC use of private /dev/pts when available (Daniel Berrange)
* virNodeDeviceCreateXML and virNodeDeviceDestroy entry points (Dave
Daniel Veillard followed the announcement with a roadmap  suggesting
"a new release around May 25, which would mean entering code feature
freeze around May 18". Version 0.6.2 was released April 3rd
==== KVM Migration Support in F11 ====
Abhishek Jha  "needed to know if libvirt supports migration via the
QEMU/KVM driver. ( virDomainMigrate)".
Daniel Berrange answered "Yes it is supported in KVM >= 79, or QEMU
= 0.10.0 and libvirt 0.6.0 IIRC." With the latest version of
available for Fedora 10 being 0.5.1, this means migration of KVM guests
will not be supported in Fedora until F11 comes out next month.
"ALso note that successful migration depends on the hardware config of
your guest. In theory any config should work, but in practice there have
been bugs in the device state save/restore process of various types of
device. So test your particular VM config successfully migrates before
relying on it in production."