FWN/Issue158

= Fedora Weekly News Issue 158 =

Welcome to Fedora Weekly News Issue 158 for the week ending January 11th, 2009.

http://fedoraproject.org/wiki/FWN/Issue158

In this first FWN issue of 2009, we bring you several announcements of the outcomes of recent Fedora-related elections. Fedora 8 reaches its end of life (time to upgrade!), and FUDCon 11 reports abound. Much news coverage of the Fedora Planet, including Fedora 10 vs. OpenSuSE, explanations on some of the recent security items now in the latest (2.6.28) Linux Kernel, and Fedora and OLPC goodness. From the development realm, useful coverage of the state of Intel graphics under Fedora 10 and debates on disabling staging drivers. Release notes and packaging guide areas need volunteers in the documentation project, and the translation team welcomes new members and suggests new language teams. In artwork, announcement of a new November/December issue of Echo Monthly News, another great sister Fedora publication. Security advisories for Fedora 9 and 10 are brought to light and the issue round out with more virtualization coverage, including announcement of Xen 3.3.1 in Rawhide and a new Fedora virtualization list, "everything concerning Fedora and virtualization, including Xen." Read on!

If you are interested in contributing to Fedora Weekly News, please see our 'join' page[1]. We welcome reader feedback: fedora-news-list@redhat.com

FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala

[1] http://fedoraproject.org/wiki/NewsProject/Join

Announcements
In this section, we cover announcements from the Fedora Project.

http://www.redhat.com/archives/fedora-announce-list/

http://www.redhat.com/archives/fedora-devel-announce/

Contributing Writer: Max Spevack

Election Results
Bill Nottingham and Matt Domsch were re-elected to the Fedora Board for two-release terms[1].

Josh Boyer, Dan Horák, Jarod Wilson, and Jon Stanley were elected to the Fedora Engineering Steering Committee for two-release terms[2].

Max Spevack, Joerg Simon, Francesco Ugolini, Thomas Canniot, Rodrigo Padula, David Nalley, and Susmit Shannigrahi were elected to the Fedora Ambassadors Steering Committee for two-release terms[3].

Paul Frields announced that Dimitris Glezos has been appointed to fill the final seat on the Fedora Board[4].

[1] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00019.html

[2] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00017.html

[3] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00018.html

[4] http://www.redhat.com/archives/fedora-announce-list/2009-January/msg00007.html

FUDCon Boston 2009
Hopefully, some of you were able to attend FUDCon Boston, January 9-11[1]. If you weren't, keep reading below for coverage!

[1] https://fedoraproject.org/wiki/FUDCon/FUDConF11

Fedora 8 End of Life
The end-of-life for Fedora 8 is Wednesday, January 7[1]. No further updates will be issued, no new builds will be allowed in the build system, and all open bugs against Fedora 8 will be closed WONTFIX[2].

[1] http://www.redhat.com/archives/fedora-announce-list/2008-December/msg00018.html

[2] https://fedoraproject.org/wiki/End_of_life

Planet Fedora
In this section, we cover the highlights of Planet Fedora - an aggregation of blogs from Fedora contributors worldwide.

http://planet.fedoraproject.org

Contributing Writer: Adam Batkin

General
Michael DeHaan wrote[1] an essay entitled Academics, Innovation, Patents, And a Path Beyond? about FOSS, cross-organizational collaboration and encouraging innovation.

Jef Spaleta had some ideas[2] about "how to do more focused new contributor recruitment and training in Fedora" and using the  online service to gather statistics and create personalized notifications (invitations) to its users.

Máirín Duffy created[3] a list of questions (and provoked a healthy discussion) that could be used to develop a set of guidelines for notifications ("Chatty Applications").

Greg DeKoenigsberg wrote[4] about some of the work going in to synchronizing Fedora and OLPC efforts.

James Morris explained[5] some of the security changes that have gone in to the latest (2.6.28) Linux Kernel.

Karsten Wade asked "why aren’t you publishing on the Fedora wiki?"[6] and followed up with a set of thoughts to encourage documentation contributions.

After a few Fedora 10 frustrations, Scott Williams tried-out[7] OpenSuSE and found some good bits and some not-so-good bits.

The latest Red Hat Magazine included[8] a video interview of Michael DeHann discussing Cobbler "and how it simplifies network installations for datacenters and other large-scale linux environments".

James Laska continued[9] his tutorial on Creating a virtual test lab (using tools such as Cobbler, Koan and SNAKE).

David Nalley thanked[10] HP for providing Mini-notes (with Linux preinstalled!) for Fedora Ambassadors.

Jef Spaleta wrote[11] an open letter to Mark Shuttleworth questioning the openness (or lack thereof) of Canonical's Launchpad.

[1] http://www.michaeldehaan.net/?p=820

[2] http://jspaleta.livejournal.com/31456.html

[3] http://mihmo.livejournal.com/66637.html

[4] http://gregdek.livejournal.com/43404.html

[5] http://james-morris.livejournal.com/37583.html

[6] http://iquaid.org/2009/01/06/the-outside-and-inside-of-documentation-or-why-arent-you-publishing-on-the-fedora-wiki/

[7] http://vwbusguy.wordpress.com/2009/01/07/review-opensuse-111/

[8] http://www.redhatmagazine.com/2009/01/07/video-spotlight-on-cobbler/

[9] http://jlaska.livejournal.com/3910.html

[10] http://www.nalley.sc/david/?p=171

[11] http://jspaleta.livejournal.com/31829.html

FUDCon 11
A small selection of FUDCon-related posts:

[1] http://sexysexypenguins.com/2009/01/10/fudcon-f11-not-in-boston-listen-live-watch-videos-after/ ("Not in Boston? Listen Live, Watch Videos After!")

[2] Photos: http://mihmo.livejournal.com/67003.html

[3] More photos: http://mihmo.livejournal.com/67287.html

[4] Even more photos: http://mihmo.livejournal.com/67388.html

Developments
In this section the people, personalities and debates on the @fedora-devel mailing list are summarized.

Contributing Writer: Oisin Feeley

Default ssh-agent Dialog Pop-up
Confusion abounded when user "nodata" reported[1] that running  from the command-line popped up a gnome dialog requesting his private SSH key. "nodata" disliked handing out his private key in such a manner. The confusion resulted from the availability of at least two possible [2] and also a change in configuration between   and   which presents the authentication dialog by default.

Ricky Zhou was among those who suggested (with a manpage quote) that the  environment variable determined whether the passphrase was read from a terminal or by an   dialog. Separately Jesse Keating[3] and Nalin Dahyabhai explained[4] that the dialog was presented by  and not.

"nodata" questioned[5] whether the behavior had changed between  and   and expressed irritation that a "[...] GUI is popping up when I am using a command line app." Jesse Keating responded[6]: "You're using a command line app from a graphical terminal. Also, cli apps aren't the only use for ssh and ssh keys." This did not appeal to many respondents including John Linville who questioned[7] the benefit of changing focus to a new window to type a passphrase. Callum Lerwick rather tartly outlined[8] some benefits including preventing key logging attacks.

Matthias Clasen suggested[9] using gconftool-2 -s -t bool /apps/gnome-keyring/daemon-components/ssh false to turn off the behavior for those who dislike it and this led to several requests to make this the default. Andrew Haley put[10] the case that "[t]he key argument against a pop-up dialog box that asks for the passphrase is that we're training people to type secrets into pop-up dialog boxes. Bad psychology, bad security."

Matthias Clasen and Tomas Mraz with Jerry Amundson explored[11] the use of  as an alternate method to disable the GUI dialog.

[1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00486.html

[2] Private keys are stored by ssh agents so that they may handle all key related operations requested by clients. The passphrase to decrypt the key thus need only be typed into the agent once instead of per-operation.

[3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00487.html

[4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00536.html

[5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00492.html

[6] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00495.html

[7] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00523.html

[8] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00533.html

[9] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00498.html

[10] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00517.html

[11] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00540.html

Intel Graphics Installation Woes
"Mike" requested[1] information on when a working  driver for Intel graphics chipsets had a chance of appearing. He was disappointed that it was non-trivial to get two machines with  and   chipsets installed and had needed to fall back to using the   driver instead of the intel one.

Others listed outstanding bugzilla entries for a wide range of Intel chipsets. Dan Williams asked[2] if using  as a workaround for problems with the   chipsets was succesfull and received mixed reports. It seemed that he was making some progress with resolving some of the issues.

MAYoung suggested[3] that setting "NoAccel true" in  might work for some people but that "[...] intel graphics are highly flaky on Fedora 10."

Robert Arendt laid[4] the blame at the door of upstream merges of  into the kernel and noted that other distributions were suffering identical problems. "Mike" later confirmed[5] this with a list of bugzilla entries from upstream : "It would be nice if Intel would help to get this fixed, and there are indeed problems with Suse, Ubuntu and Mandriva also with newer drivers and Intel graphics chipsets of various flavors - this is really bad!"

[1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00435.html

[2] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00475.html

[3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00443.html

[4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00445.html

[5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00467.html

KPackageKit Auto-update Bug
Michael B Allen reported[1] that his system had performed an update without his permission and asked how to completely disable such behavior.

It appeared[2] that this was due to a bug in  which has been unfixable[3] for over a month due in part to the complexity of the code.

[1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00461.html

[2] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00504.html

[3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00510.html

Enabling Staging Drivers ?
Rahul Sundaram asked[1] if enabling the many new drivers in the staging tree[2] would make sense in  in order to support a wider range of hardware such as the  's   wireless chipset.

Opinion was roughly split between those who were completely against the idea and those who suggested avoiding codifying a rigid policy. Matthew Garrett believed[3] that it would be "somewhat user-hostile" to, for example enable the  drivers in   but possibly remove them for a general release. He argued that the  drivers were a dead-end[4] which would never merge upstream. On the other hand Dave Jones preferred[5] to take a case-by-case approach as long as "[...] we have someone responsible for working on it, with the goal of getting it out of staging, and dealing with bugs etc. Not unlike the same reasoning for us adding various not-yet-upstream drivers to the Fedora kernel really."

While preferring to completely disable the staging drivers Thorsten Leemhuis expressed[6] the intention to provide    in that case. Dan Williams made[7] a strong argument that "-staging" itself was a bad idea as it gave "legitimacy to drivers of questionable quality" and John Linville limned[8] the tortured history of the  driver.

[1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00459.html

[2] "linux-staging" is a kernel tree whose purpose is to test drivers and filesystems for later inclusion in mainline http://lkml.org/lkml/2008/6/10/329

[3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00462.html

[4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00474.html

[5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00472.html

[6] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00465.html

[7] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00473.html

[8] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00476.html

git-* Commands Moved to /usr/libexec/git-core/
Adam Tkac worried[1] that scripts would break due to the latest git branch in rawhide which had moved all the  binaries to   in order to comply with upstream practice. The issue was previously discussed (see FWN#141[2)] with the resolution that updating to  would be a flag day for this change. Adam suggested that the new location could be added to the  environment variable but this received no support.

Karel Zak advocated[3] that such scripts should be fixed as the change had been coming since 2006.

Bryn Reeves wondered[4] if compatibility symlinks and a release note would ease the transition over a couple of releases. Although the symlinks were generally felt to be a non-effective strategy Todd Zulinger was encouraged[5] by Paul W. Frields to open a bugzilla entry against the Release Notes to ensure that the documentation team take care of highlighting the issue for.

[1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00404.html

[2] http://fedoraproject.org/wiki/FWN/Issue141#Git-1.6.0_Commands_to_be_Moved_Out_of_PATH

[3] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00408.html

[4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00410.html

[5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00460.html

Mandatory FHS Adherence
Jason L. Tibbitts III posted[1] a summary and links to the 2009-01-06 FPC meeting deliberations. Interest on @fedora-devel was mostly sparked by the item which declared that the FPC would "Make adherence to the FHS a MUST [.]" Jason encouraged reading of the full minutes in order to understand this item.

Doug Ledford discussed[2] the problem his MPI[3] implementations experienced with the FHS and Richard W. M. Jones expressed [4] concern that the FHS was a moribund standard and adhering to it would block projects such as MinGW without any method to evolve the standard. Toshio Kuratomi responded in detail in both threads and pointed out[5] that the MinGW case had been addressed in the meeting and also that there were problems with changing the FHS.

[1] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00362.html

[2] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00424.html

[3] http://www.open-mpi.org/papers/ipdps-2006/

[4] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00469.html

[5] https://www.redhat.com/archives/fedora-devel-list/2009-January/msg00483.html

Documentation
In this section, we cover the Fedora Documentation Project.

http://fedoraproject.org/wiki/DocsProject

Contributing Writer: Jason Taylor

Docs Project and FUDCon
At FUDCon the Documentation Project tasks[0] were discussed and some headway was made. There is still work to be done and the information contained here[0] can be used to pickup where tasks were left off.

[0] https://fedoraproject.org/wiki/Your_Docs_Project_BarCamp_session_FUDConF11

Documentation Team Ownership Deadline
The Docs Project has divided the published documentation into teams[0]. The teams consist of a Lead who manages the overall direction of the document and writers who write and/or edit various pieces of the published document. There are two publications that need a lead, the release notes[1] and the packaging guide[2]. The packaging guide needs a rewrite and the release notes will start the update/publication process for F11. The deadline for claiming a publication is the week of 11-Jan-2009.

[0] https://fedoraproject.org/wiki/Docs_Project_content_tasks_for_experienced_contributors

[1] https://fedorahosted.org/release-notes/

[2] https://fedoraproject.org/wiki/PackagingGuidelines

Translation
This section covers the news surrounding the Fedora Translation (L10n) Project.

http://fedoraproject.org/wiki/L10N

Contributing Writer: Runa Bhattacharjee

cvsl10n Sponsorship and Listing of Sponsors
As a follow-up to the ongoing discussion about the "cvsl10n" sponsorship procedure, NorikoMizumoto and IgorSoares have put together a page[1][2] with the name of the Administrators and Sponsors of the "cvsl10n" group. IgorSoares suggested the formation of language groups to ease the sponsorship and an aging policy for unattended requests[3]. RunaBhattacharjee suggested if a patch to the existing FAS interface as possible, that would allow addition of the language name when a new member sends a request to join the FLP[4]. ChristianRose also suggested a patch for damned-lies that would allow addition of the "sponsor" information directly on the team's page[5].

[1] https://fedoraproject.org/wiki/L10N/GroupSponsors

[2] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00091.html

[3] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00086.html

[4] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00085.html

[5] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00024.html

New Administrators for cvsl10n
The FLSCo members were upgraded to "Administrators" of the "cvsl10n" group by KarstenWade[6].

[6] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00108.html

TQSG upgraded
NorikoMizumoto announced[7] the availability of the updated .pot and .po files of the Translation Quick Start Guide (TQSG). FLP members can also join the TQSG project to help in its maintenance.

[7] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00008.html

New Members in the FLP Project
ChristopheAlladoum (French)[8], Luís Gomes (Portugeuse)[9], Mieszko Ślusarczyk (Polish)[10], Mario Jalsovec (Croatian)[11], Kris Thomsen (Danish)[12], David Kjær (Danish)[13], Wes Freeman (Spanish)[14] join the FLP teams.

[8] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00014.html

[9] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00113.html

[10] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00112.html

[11] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00109.html

[12] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00107.html

[13] https://www.redhat.com/archives/fedora-trans-list/2008-December/msg00094.html

[14] https://www.redhat.com/archives/fedora-trans-list/2009-January/msg00009.html

Artwork
In this section, we cover the Fedora Artwork Project.

http://fedoraproject.org/wiki/Artwork

Contributing Writer: Nicu Buculei

Echo News and Development
After a month of absence, Martin Sourada announced[1] on @fedora-art a new issue[2] of Echo Monthly News "We've just published latest Echo Monthly News Issue. Due too lack of enough content, it is joint of November's and December's happenings"

[1] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00021.html

[2] https://fedorahosted.org/echo-icon-theme/wiki/MonthlyNews/Issue4-5

[3] https://fedorahosted.org/echo-icon-theme/wiki/MonthlyNews

In other Echo related news, Martin announced[4] a poll[5] regarding the future development of the theme "I've just posted a poll about Echo Perspective on Fedora Forum to see our user base opinion and I'd like to hear the opinions of the Art Team members as well"

[4] https://www.redhat.com/archives/fedora-art-list/2009-January/msg00030.html

[5] http://forums.fedoraforum.org/showthread.php?t=210159

Security Advisories
In this section, we cover Security Advisories from fedora-package-announce.

https://www.redhat.com/mailman/listinfo/fedora-package-announce

Contributing Writer: David Nalley

Fedora 10 Security Advisories

 * proftpd-1.3.1-8.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00106.html
 * xterm-238-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00109.html
 * samba-3.2.7-0.25.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00189.html
 * zoneminder-1.23.3-2.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00204.html
 * thunderbird-2.0.0.19-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00232.html
 * p7zip-4.61-1.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00242.html
 * avahi-0.6.22-12.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00267.html
 * openssl-0.9.8g-12.fc10 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00374.html

Fedora 9 Security Advisories

 * xterm-238-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00072.html
 * proftpd-1.3.1-8.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00078.html
 * thunderbird-2.0.0.19-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00239.html
 * p7zip-4.61-1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00243.html
 * am-utils-6.1.5-8.1.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00273.html
 * samba-3.2.7-0.23.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00309.html
 * openssl-0.9.8g-9.12.fc9 - https://www.redhat.com/archives/fedora-package-announce/2009-January/msg00369.html

Virtualization
In this section, we cover discussion on the @et-mgmnt-tools-list, @fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora virtualization technologies.

Contributing Writer: Dale Bewley

Enterprise Management Tools List
This section contains the discussion happening on the et-mgmt-tools list

Help Perfect Cobbler SELinux Policy
Dominick Grift posted[1] "instructions on how to install a bare SELinux policy for . Feedback in the form of AVC denials would be appreciated so that we can perfect this bare policy."

Michael DeHaan asked[2] "Would someone like to take a shot at refining this policy some or at least running Cobbler with that for a while (in permissive mode) to identify what else needs to be allowed?" and added the policy to the cobbler wiki[3].

[1] http://www.redhat.com/archives/et-mgmt-tools/2009-January/msg00003.html

[2] http://www.redhat.com/archives/et-mgmt-tools/2009-January/msg00004.html

[3] http://fedorahosted.org/cobbler/wiki/SeLinuxPolicy

Fedora Virtualization List
This section contains the discussion happening on the fedora-virt list.

New Fedora Virtualization List
On @fedora-xen, Daniel Veillard announced[1] the creation of the new @fedora-virt list.

"As the initiator for [the fedora-xen] list, I must admit I made a mistake 3 years ago, I should have picked a list name agnostic from the hypervisor name. With the current state of Xen in Fedora recent releases it really make sense to try to correct that mistake ... it's never too late ! So http://www.redhat.com/mailman/listinfo/fedora-virt is born, I don't want to mass-subscribe people, especially as I think the current list should survive with its Xen centric focus. You can subscribe directly to the new URL above.

The topic is everything concerning Fedora and virtualization including Xen.

I think the [fedora-xen] list would be a good place for people still using Fedora <= 8 with Xen, but it's just a suggestion :-)"

And on @et-mgt-tools Richard W.M. Jones suggested[2] "we should fold et-mgmt-tools into fedora-virt too."

[1] http://www.redhat.com/archives/fedora-xen/2009-January/msg00014.html

[2] http://www.redhat.com/archives/et-mgmt-tools/2009-January/msg00010.html

Fedora Xen List
This section contains the discussion happening on the fedora-xen list.

Xen 3.3.1 in Rawhide
Pasi Kärkkäinen pointed[1] out the release of 3.3.1. A few days later it was made available[2] in Rawhide.

[1] http://www.redhat.com/archives/fedora-xen/2009-January/msg00008.html

[2] http://koji.fedoraproject.org/koji/packageinfo?packageID=7

Manage Shutdowns of KVM Xenner Guests
Felix Schwarz used[1] and to migrate a Fedora 8 Xen dom0 host to Fedora 10.

"So far this was easier than expected. :-) Of course there are some smaller issues (Xenner does not work with SElinux, NetworkManager does not support bridges) but now there is only one real issue left:

How can I automatically shut down all running VMs when my host machine goes down? All VMs do poweroff if I press the 'shutdown' button in virt-manager. So I guess it's just a matter of sending this signal to all running VMs and waiting a bit."

[1] http://www.redhat.com/archives/fedora-xen/2009-January/msg00001.html

Test Dom0 Kernel For Fedora 10
Michael Young has[1] "succeeded in getting a fedora based to build with Dom0 patches added." ... "If anyone wants to inspect it, the source rpm generated is at http://compsoc.dur.ac.uk/~may/xen/kernel-2.6.28-0.106.rc6.fc10.src.rpm It is completely untested beyond the fact that it compiles for me, so I have no idea if a kernel built from it will actually boot."

See also Xen[2] and Fedora[3] wikis.

[1] http://www.redhat.com/archives/fedora-xen/2008-December/msg00028.html

[2] http://wiki.xensource.com/xenwiki/XenParavirtOps

[3] http://fedoraproject.org/wiki/Features/XenPvopsDom0

Libvirt List
This section contains the discussion happening on the libvir-list.

Interface Bandwidth Controls
Max Zhen described[1] a goal of enabling to configure bandwidth rate limits for the network interface of virtual machines, and asked for comments on implementation ideas.

[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00644.html

RHEL 5 Support
Markus Armbruster posted[1] a "patch series attempts to make just work on RHEL-5.  Right now it doesn't, mostly because   relies on version number checks in a couple of places, and RHEL-5's version numbers aren't the whole truth due to various backports of later stuff." Adding "I'm not proposing this for immediate commit, as I'm still testing. But I'd appreciate review: is this the right way to do it?"

[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00629.html

Choice of Private Network Range
Peter Anvin was[1] "kind of wondering why defaults to 192.168.122.0/24". Refering to RFCs 2544 and 3330. Peter suggested the following alternative ranges:


 * 192.0.2.0/24	- reserved as "test and example network"
 * 198.18.0.0/15	- reserved as "benchmark test network"

[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00545.html

Guest-Safe libvirtd Restarts
A restart of  will necessarily also restart   virtual machine guests. Guido Günther sought[1] to rectify this with a submission of several patches.

[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00346.html

[2] http://fedoraproject.org/wiki/FWN/Issue146#Maintaining_VM_State_While_Restarting_libvirtd_Needed