|
|
| Line 9: |
Line 9: |
| This section contains the discussion happening on the | | This section contains the discussion happening on the |
| [http://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list] | | [http://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list] |
|
| |
| ==== Help Perfect Cobbler SELinux Policy ====
| |
| [[DominickGrift|Dominick Grift]] posted[1]
| |
| "instructions on how to install a bare SELinux policy for {{package|cobbler}}. Feedback in the form of AVC denials would be appreciated so that we can perfect this bare policy."
| |
|
| |
| [[MichaelDeHaan|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 === | | === Fedora Virtualization List === |
| This section contains the discussion happening on the | | This section contains the discussion happening on the |
| [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. | | [http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list]. |
|
| |
| ==== New Fedora Virtualization List ====
| |
| On @fedora-xen, [[DanielVeillard|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 [[RichardJones|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 === | | === Fedora Xen List === |
| This section contains the discussion happening on the | | This section contains the discussion happening on the |
| [http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list]. | | [http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list]. |
|
| |
| ==== Xen 3.3.1 in Rawhide ====
| |
| [[PasiKärkkäinen|Pasi Kärkkäinen]] pointed[1] out the release of
| |
| {{package|xen}} 3.3.1. A few days later it was made available[2] in
| |
| [[Releases/Rawhide|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 ====
| |
| [[FelixSchwarz|Felix Schwarz]] used[1] {{package|kvm}} and {{package|xenner}}
| |
| 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 ====
| |
| [[MichaelYoung|Michael Young]] has[1] "succeeded in getting a fedora based {{package|kernel}} 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 === | | === Libvirt List === |
| Line 93: |
Line 22: |
| [http://www.redhat.com/mailman/listinfo/libvir-list libvir-list]. | | [http://www.redhat.com/mailman/listinfo/libvir-list libvir-list]. |
|
| |
|
| ==== Interface Bandwidth Controls ==== | | === oVirt Devel List === |
| [[MaxZhen|Max Zhen]] described[1] a goal of enabling {{package|libvirt}} to configure bandwidth rate limits for the network interface of virtual machines, and asked for comments on implementation ideas.
| | This section contains the discussion happening on the |
| | | [http://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list]. |
| [1] http://www.redhat.com/archives/libvir-list/2008-December/msg00644.html
| |
| | |
| ==== RHEL 5 Support ====
| |
| [[MarkusArmbruster|Markus Armbruster]] posted[1] a
| |
| "patch series attempts to make {{package|libvirt}} just work on RHEL-5. Right
| |
| now it doesn't, mostly because <code>libvirt</code> 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 ====
| |
| [[PeterAnvin|Peter Anvin]] was[1] "kind of wondering why {{package|libvirt}} defaults to
| |
| 192.168.122.0/24". Refering to RFCs [http://www.faqs.org/rfcs/rfc2544.html 2544] and [http://www.faqs.org/rfcs/rfc3330.html 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 <code>libvirtd</code> will necessarily also restart <code>KVM</code> virtual machine guests.
| |
| [[GuidoGünther|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
| |
