From Fedora Project Wiki

< FWN‎ | Beats
 
(474 intermediate revisions by 4 users not shown)
Line 1: Line 1:
[[Category:Virtualization]] <!-- do not copy into FWN issue -->
{{Anchor|Virtualization}}
{{Anchor|Virtualization}}


== 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]]
 
=== Enterprise Management Tools List ===
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
 
=== Fedora Xen List ===
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
 
=== Libvirt List ===
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
 
==== Libvirt vs XenAPI ====
Atif Bajwa asked[1] about the advantages of using libvirt over [http://wiki.xensource.com/xenwiki/XenApi XenAPI] and what platforms libvirt supports.  [[AtsushiSakai|Atsushi Sakai]] pointed to a list[2] of which libvirt calls work on which drivers / hypervisors. [[DanielBerrange|Daniel P. Berrange]] replied[3] that libvirt is available for every major Linux distro, and listed several benefits such as:
 
* avoids locking applications to a particular hypervisor
* provides a guaranteed stable API that can be used both locally and remotely
* remote security options include SSL + x509 certificates, SSH tunnel, Kerberos GSSAPI single sign on, and username + password
* works with every version of Xen 3.0.x or later while XenAPI is only usable in Xen 3.1.0 and later


[[RichardJones|Richard W.M. Jones]] mentioned[4] that although there are no binaries [[SIGs/MinGW|yet]], libvirt client code can be compiled on windows.
Contributing Writer: [[User:Dale | Dale Bewley]]


[1] https://www.redhat.com/archives/libvir-list/2008-September/msg00002.html
=== Fedora Virtualization List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].


[2] http://libvirt.org/hvsupport.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.


[3] https://www.redhat.com/archives/libvir-list/2008-September/msg00008.html
<references />


[4] https://www.redhat.com/archives/libvir-list/2008-September/msg00016.html
==== RHEL and Fedora Virtualization Feature Parity ====
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.


=== oVirt Devel List ===
[[DanielBerrange|Daniel Berrange]]
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].
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."


==== Renaming oVirt RPMs ====
<references />
[[AlanPevec|Alan Pevec]] proposed[1] renaming the oVirt packages which turned into a discussion with [[DanielBerrange|Daniel P. Berrange]] about how to organize the git repos and how to continue support build-all  after such a change.


[1] https://www.redhat.com/archives/ovirt-devel/2008-September/msg00029.html


==== WUI Management of Underlying Hardware ====
==== ====
[[ChrisLalancette|Chris Lalancette]] posted[1] a series of patches to allow the Web User Interface to manage the underlying hardware it is running on.
<references />


[1] https://www.redhat.com/archives/ovirt-devel/2008-September/msg00081.html
====  ====
<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.

  1. ↑ http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html
  2. ↑ http://fedoraproject.org/wiki/Virtualization_bugs

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."

  1. ↑ http://www.redhat.com/virtualization/rhev/
  2. ↑ http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html



Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/Virtualization&oldid=142485"