From Fedora Project Wiki

< FWN‎ | Beats

(→‎Libvirt List: add Libvirt and Persistent Iptables Rules)
 
(491 intermediate revisions by 4 users not shown)
Line 1: Line 1:
[[Category:Virtualization]] <!-- do not copy into FWN issue -->
{{Anchor|Virtualization}}
{{Anchor|Virtualization}}


= INCOMPLETE =


== Virtualization ==
== 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.  
In this section, we cover discussion of Fedora virtualization technologies on the
@fedora-virt list.


Contributing Writer: [[DaleBewley | Dale Bewley]]
Contributing Writer: [[User:Dale | Dale Bewley]]


=== Enterprise Management Tools List ===
=== Fedora Virtualization List ===
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
This section contains the discussion happening on the
 
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
==== Virt-mem Tools 0.2.8 Released ====
[[RichardJones|Richard W.M. Jones]] announced[1] the release of [http://et.redhat.com/~rjones/virt-mem/ virt-mem] 0.2.8. Virt-mem provides a set of dom0 or host tools which leverage [http://www.libvirt.org libvirt] to facilitate the inspection of domU or guest kernel information. Commands include 'virt-uname', 'virt-ps', and 'virt-dmesg' for example.
 
This latest version has been reworked to have direct access to basically any kernel structure. This will allow a more rapid fullfillment of outstanding feature requests such as memory usage information, network interface listings, etc.


[1] https://www.redhat.com/archives/et-mgmt-tools/2008-August/msg00033.html
==== Virt Status Report ====
[[JustinForbes|Justin Forbes]]
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report.
Justin pointed out F13 bugs<ref>http://fedoraproject.org/wiki/Virtualization_bugs</ref> now include Important and Pony classifications in addition to Blocker and Target.


=== Fedora Xen List ===
<references />
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].


==== Installing Fedora 9 Guest on Centos 5 Fails ====
==== RHEL and Fedora Virtualization Feature Parity ====
[[KennethTanzer|Kenneth Tanzer]] had trouble[1] installing a Fedora 9 paravirtualized guest on a CentOs 5 host. Eventually the install hung on installing openoffice.org-writer2latex. David Hláčik reported[2] a kernel panic during the same scenario. He stated it was due to the Fedora 9 kernel-xen having newer features which the CentOs dom0 did not support. However, [[MarkMcLoughlin|Mark McLoughlin]] said[3] RHEL5/CentOS Xen is expected to be able to run pv_ops kernels, and a bug should be filed if this isn't the case.
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
compared to Fedora 12.


[1] https://www.redhat.com/archives/fedora-xen/2008-August/msg00011.html
[[DanielBerrange|Daniel Berrange]]
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was
rebased to be near parity with [[Releases/11|Fedora 11]], and KVM in RHEL-5.4 is
also pretty close to that using what's best described as a hybrid of
kvm-83 and kvm-84."


[2] https://www.redhat.com/archives/fedora-xen/2008-August/msg00013.html
<references />


[3] https://www.redhat.com/archives/fedora-xen/2008-August/msg00018.html


=== Libvirt List ===
==== ====
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
<references />
 
==== Libvirt and Persistent Iptables Rules ====
[[DanielBerrange|Daniel Berrange]] responded[1] to a networking problem by pointing out that libvirt will automatically setup the correct iptables rules to allow outbound NAT based connectivity for guest VMs and that restarting the iptables service will erase these rules.
 
[1] https://www.redhat.com/archives/libvir-list/2008-July/msg00508.html
 
[[DavidLutterkort|David Lutterkort]] hoped[2] this was a temporary situation
due to the confusion it can cause. [[MarkMcLoughlin|Mark McLoughlin]] confirmed[3] there is a RFE ([https://bugzilla.redhat.com/show_bug.cgi?id=227011 bug 227011]) to enable libvirt to persistently register iptables rules, but was depressed that a resulting fix would be Fedora specific.
 
[2] https://www.redhat.com/archives/libvir-list/2008-August/msg00098.html
 
[3] https://www.redhat.com/archives/libvir-list/2008-August/msg00193.html
 
=== oVirt Devel List ===
This section contains the discussion happening on the
[https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].


==== Thread ====
==== ====
[1] ref
<references />

Latest revision as of 18:09, 18 December 2009



Virtualization

In this section, we cover discussion of Fedora virtualization technologies on the @fedora-virt list.

Contributing Writer: Dale Bewley

Fedora Virtualization List

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

Virt Status Report

Justin Forbes posted[1] a Fedora virtualization status report. Justin pointed out F13 bugs[2] now include Important and Pony classifications in addition to Blocker and Target.

RHEL and Fedora Virtualization Feature Parity

Robert Day wondered how the virtualization features[1] of Red Hat Enterprise Linux 5.4 compared to Fedora 12.

Daniel Berrange explained[2] "The KVM based virtualization in RHEL-5.4 is not nearly so far behind Fedora as you might think. The Package-x-generic-16.pnglibvirt mgmt stack in RHEL-5.4 was rebased to be near parity with Fedora 11, and KVM in RHEL-5.4 is also pretty close to that using what's best described as a hybrid of kvm-83 and kvm-84."