From Fedora Project Wiki

< FWN‎ | Beats
 
(310 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 ===
Contributing Writer: [[User:Dale | Dale Bewley]]
This section contains the discussion happening on the
[https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].


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


==== Interface Bandwidth Controls ====
==== Virt Status Report ====
[[MaxZhen|Max Zhen]] described[1] a goal of enabling {{package|libvirt}} to configure bandwidth rate limits for the network interface of virtual machines, and asked for comments on implementation ideas.
[[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.


[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00644.html
<references />


==== RHEL 5 Support ====
==== RHEL and Fedora Virtualization Feature Parity ====
[[MarkusArmbruster|Markus Armbruster]] posted[1] a
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
"patch series attempts to make {{package|libvirt}} just work on RHEL-5.  Right
compared to Fedora 12.
now it doesn't, mostly because <code>libvirt</code> relies on version number checks
in a couple of places, and RHEL-5's version numbers aren't the whole
truth due to various backports of later stuff." Adding
"I'm not proposing this for immediate commit, as I'm still testing.
But I'd appreciate review: is this the right way to do it?"


[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00629.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."


==== Choice of Private Network Range ====
<references />
[[PeterAnvin|Peter Anvin]] was[1] "kind of wondering why {{package|libvirt}} defaults to
192.168.122.0/24". Refering to RFCs [http://www.faqs.org/rfcs/rfc2544.html 2544] and [http://www.faqs.org/rfcs/rfc3330.html 3330]. Peter suggested the following alternative ranges:


* 192.0.2.0/24 - reserved as "test and example network"
* 198.18.0.0/15 - reserved as "benchmark test network"


[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00545.html
====  ====
<references />


==== Guest-Safe libvirtd Restarts ====
==== ====
{{Admon/warning|Stub|Come back and finish me.}}
<references />
"
attached is a new version of the "let kvm/qemu survive libvirt restart"
patches. Since we have the VIR_DOMAIN_XML_INACTIVE changes already
applied we now only need to persist the monitor path, pid and current
domain state (running, paused, ...).
"
 
[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00346.html
 
[2] http://fedoraproject.org/wiki/FWN/Issue146#Maintaining_VM_State_While_Restarting_libvirtd_Needed
 
=== oVirt Devel List ===
This section contains the discussion happening on the
[https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].

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"