From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
 
(127 intermediate revisions by 2 users not shown)
Line 2: Line 2:


{{Anchor|Virtualization}}
{{Anchor|Virtualization}}


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


Contributing Writer: [[User:Dale | Dale Bewley]]
Contributing Writer: [[User:Dale | Dale Bewley]]
=== Enterprise Management Tools List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
====  ====
<references />


=== Fedora Virtualization List ===
=== Fedora Virtualization List ===
Line 19: Line 14:
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].


==== F12 Feature: Host Information ====
==== Virt Status Report ====
[[RichardJones|Richard Jones]]
[[JustinForbes|Justin Forbes]]
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00123.html</ref>
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report.
an RFC for a feature<ref>http://fedoraproject.org/wiki/Features/Hostinfo</ref> he's working on for [[Releases/12|Fedora 12]]. 
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.
The feature will "Allow a virtual machine to see information and statistics from the
host operating system."
 
For example, it will "Allow a virtual machine to look at host information (such as number of
physical, not just virtual CPUs), and statistics like the load on the
host."
 
[[DanielBerrange|Daniel Berrange]]
noted<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00130.html</ref>
that "a core goal of this
hostinfo service is to avoid any use of networking. We don't want to
presume that a guest has a NIC, nor that the host has a configured
NIC on the same LAN as the guest." So this feature will make use of serial
ports to pass queries and responses between the guest and the host.


<references />
<references />


==== libguestfs Super-minimized Appliance ====
==== RHEL and Fedora Virtualization Feature Parity ====
[[RichardJones|Richard Jones]]
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
created<ref>http://www.redhat.com/archives/fedora-virt/2009-June/msg00118.html</ref>
compared to Fedora 12.
a set of "very experimental" patches to {{package|libguestfs}}
"which allow you to build a so-called 'supermin (super-minimized) appliance'."
 
Within <code>libguestfs</code>, "The normal appliance is a self-contained Linux operating system, based
on the Fedora/RHEL/CentOS Linux distro.  So it contains a complete
copy of all the libraries and programs needed, like kernel, libc,
bash, coreutils etc etc."
 
"The supermin appliance removes the kernel and all the executable
libraries and programs from the appliance.  That just leaves a
skeleton of config files and some data files, which is obviously
massively smaller than the normal appliance.  At runtime we rebuild
the appliance on-the-fly from the libraries and programs on the host
(eg. pulling in the real /lib/libc.so, the real /bin/bash etc.)"
 
"The new appliance is a mere 500K, so <code>libguestfs</code> RPMs will be a lot
smaller.  Of course that just means they will have many more
dependencies, so the amount pulled down will be the same or greater."


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


<references />
<references />


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


====  ====
====  ====
<references />
<references />
=== Libvirt List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
====  ====
<references />
=== oVirt Devel List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].


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