No edit summary |
|||
Line 13: | Line 13: | ||
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]. | ||
==== 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. | |||
<references /> | |||
==== RHEL and Fedora Virtualization Feature Parity ==== | ==== RHEL and Fedora Virtualization Feature Parity ==== | ||
Line 28: | Line 35: | ||
<references /> | <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 libvirt
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."