From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
 
(53 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
In this section, we cover discussion of Fedora virtualization technologies on the
@fedora-virt, @fedora-xen-list, @libguestfs, @libvirt-list,
@fedora-virt list.
and @virt-tools-list lists.


Contributing Writer: [[User:Dale | Dale Bewley]]
Contributing Writer: [[User:Dale | Dale Bewley]]
Line 14: Line 14:
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].


==== KSM Tuning Service  ====
==== Virt Status Report ====
A new feature for [[Releases/12 | Fedora 12]], Kernel Samepage Merging<ref>http://fedoraproject.org/wiki/Features/KSM</ref>,
[[JustinForbes|Justin Forbes]]
enables KVM guest virtual machines to share identical memory pages. This is especially useful when running multiple guests from the same or similar base operating system image. Because memory is shared, the combined memory usage of the guests is reduced. KSM works by scanning memory, looking for identical pages.
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.
[[DanKenigsberg |Dan Kenigsberg ]]
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-September/msg00023.html</ref>
a KSM control daemon in a  
"simple script that controls whether (and with what vigor) should ksm search duplicated memory pages."
 
"An unattended host running a variable number of qemu-kvm's needs to tune
ksm automatically, since when memory is tight, it's better to spend more
cpu on merging pages. In more relaxed cases, it's just a waste of time."


<references />
<references />


==== Host Iptables Settings for Bridged Guests ====
==== RHEL and Fedora Virtualization Feature Parity ====
[[MarkMcLoughlin|Mark McLoughlin]]
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
pointed<ref>http://www.redhat.com/archives/fedora-virt/2009-September/msg00014.html</ref>
compared to Fedora 12.
out that the recommended<ref>http://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging</ref>
configuration for configuring iptables on the host to allow traffic to pass to
a bridged guest to disable netfilter on the bridge altogether.
 
<pre>
# cat >> /etc/sysctl.conf <<EOF
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
EOF
# sysctl -p /etc/sysctl.conf
</pre>
 
This "will be the default with Fedora 12."
 
<references />
 
=== Fedora Xen List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
 
==== Xen Domain0 Kernels ====
Until support for pv_ops<ref>http://fedoraproject.org/wiki/Features/XenPvopsDom0</ref> is added to the upstream kernel (F13?), it takes some twiddling to host Xen guests on Fedora.
More adventurous users are reporting some success with experimental kernels and running a Xen dom0.<ref>http://www.redhat.com/archives/fedora-xen/2009-September/msg00000.html</ref>
<ref>http://www.redhat.com/archives/fedora-xen/2009-September/msg00025.html</ref>
<ref>http://bderzhavets.wordpress.com/2009/09/05/setup-xen-3-4-1-libvirt-on-top-f12-alpha-rawhide/</ref>


Current dom0 kernel options include
[[DanielBerrange|Daniel Berrange]]
building<ref>http://www.redhat.com/archives/fedora-xen/2009-September/msg00019.html</ref>
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
one from Jeremy Fitzhardinge's git repository or
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
installing<ref>http://www.redhat.com/archives/fedora-xen/2009-August/msg00083.html</ref>
Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was
Brian Young's RPM.  
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 />


=== Virtualization Tools List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/virt-tools-list virt-tools-list list].


====  ====
====  ====
<references />
<references />
=== Libguestfs List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/libguestfs libguestfs list].
====  ====
<references />
=== Libvirt List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-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."