FWN/Beats/Virtualization

From FedoraProject

< FWN | Beats(Difference between revisions)
Jump to: navigation, search
(starting next ed)
(Fedora Virtualization List)
 
(23 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 and @libvirt-list lists.
+
@fedora-virt list.
  
 
Contributing Writer: [[User:Dale | Dale Bewley]]
 
Contributing Writer: [[User:Dale | Dale Bewley]]
Line 13: Line 14:
 
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
 
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
  
==== Bridges ====
+
==== Virt Status Report ====
[[AndrésGarcía|Andrés García]]
+
[[JustinForbes|Justin Forbes]]
asked<ref>http://www.redhat.com/archives/fedora-virt/2009-November/msg00002.html</ref>
+
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.
<ref>http://wiki.libvirt.org/page/Networking#Bridged_networking_.28aka_.22shared_physical_device.22.29</ref>
+
 
+
<ref>https://fedorahosted.org/netcf/</ref>
+
<ref>http://linux-kvm.com/content/netcf-silver-bullet-network-configuration</ref>
+
  
 
<references />
 
<references />
  
=== Libvirt List ===
+
==== RHEL and Fedora Virtualization Feature Parity ====
This section contains the discussion happening on the
+
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
+
compared to Fedora 12.
  
==== Node device enumeration with udev ====
+
[[DanielBerrange|Daniel Berrange]]  
[[DaveAllan|Dave Allan]]
+
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
posted<ref>http://www.redhat.com/archives/libvir-list/2009-October/msg00731.html</ref>
+
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
"a fully functional version of the node device udev<ref>http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html</ref> based backend, incorporating all the feedback from earlier revisions." "...I have also included a patch removing the DevKit backend."
+
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 see FWN#146 "Host Device Enumeration API"<ref>http://fedoraproject.org/wiki/FWN/Issue146#Host_Device_Enumeration_API</ref> for some coverage of the host device enumeration API.
+
also pretty close to that using what's best described as a hybrid of
 +
kvm-83 and kvm-84."
  
 
<references />
 
<references />
  
==== Rewrite of QEMU monitor handling ====
 
[[DanielBerrange|Daniel Berrange]]
 
posted<ref>http://www.redhat.com/archives/libvir-list/2009-October/msg00644.html</ref> a
 
"patch series [which] rewrites the QEMU monitor handling almost completely.
 
 
The key theme here is to move from a totally synchronous way of
 
interacting with the monitor, to a totally asynchronous way. This
 
allows " {{package|libvirt}} " to handle receipt & dispatch of asychronous events from
 
QEMU. For example a notification of a disk-full error, or VM state
 
change.  In the process of doing this re-factoring I have also
 
dropped in basic support/infrastructure for the JSON based monitor."
 
  
 +
====  ====
 
<references />
 
<references />
  
==== Libvirt QEMU driver thread safety rules ====
+
==== ====
In a characteristically long and detailed post [[DanielBerrange|Daniel Berrange]]
+
laid<ref>http://www.redhat.com/archives/libvir-list/2009-October/msg00815.html</ref>
+
donw the law on thread safety rules for the Qemu driver<ref>http://www.libvirt.org/drvqemu.html</ref>.
+
 
+
"This document describes how thread safety is ensured throughout
+
the QEMU driver. The criteria for this model are:
+
 
+
* Objects must never be exclusively locked for any pro-longed time
+
* Code which sleeps must be able to time out after suitable period
+
* Must be safe against dispatch asynchronous events from monitor"
+
 
+
Also see FWN#155 "Thread Safety for libvirtd Daemon and Drivers"<ref>http://fedoraproject.org/wiki/FWN/Issue155#Thread_Safety_for_libvirtd_Daemon_and_Drivers</ref>
+
 
+
 
<references />
 
<references />

Latest revision as of 18:09, 18 December 2009



Contents

[edit] Virtualization

In this section, we cover discussion of Fedora virtualization technologies on the @fedora-virt list.

Contributing Writer: Dale Bewley

[edit] Fedora Virtualization List

This section contains the discussion happening on the fedora-virt list.

[edit] 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

[edit] 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


[edit]


[edit]