FWN/Beats/Virtualization

From FedoraProject

< FWN | Beats(Difference between revisions)
Jump to: navigation, search
(starting next ed)
Line 5: Line 5:
 
== 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, @fedora-xen-list, and @libvirt-list lists.
  
 
Contributing Writer: [[User:Dale | Dale Bewley]]
 
Contributing Writer: [[User:Dale | Dale Bewley]]
Line 24: Line 24:
 
<references />
 
<references />
  
=== Libvirt List ===
+
=== Fedora Xen List ===
 
This section contains the discussion happening on the
 
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
+
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
  
==== Node device enumeration with udev ====
+
==== No Xen dom0 in Fedora 12 Hopefully 13 ====
[[DaveAllan|Dave Allan]]
+
Zhang Enming
posted<ref>http://www.redhat.com/archives/libvir-list/2009-October/msg00731.html</ref>
+
was disappointed<ref>http://www.redhat.com/archives/fedora-xen/2009-November/msg00019.html</ref> to learn the support for hosting Xen guests, dropped in Fedora 9, is still not present in Fedora 12.
"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."
+
  
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.
+
Zhang referenced numerous videos documenting success with Xen dom0 on Fedora
 +
11. While there are experimental patches which may be applied<ref>http://fedoraproject.org/wiki/FWN/Issue190#Dom0_Kernel_Status</ref> to the kernel to enable support
 +
for dom0, they are not yet in the upstream kernel which forms the basis the
 +
Fedora kernel package.  
  
<references />
+
It was decided<ref>http://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html</ref> two years ago this month that
 
+
Fedora "simply cannot spend more time forward porting Xen kernels" and
==== Rewrite of QEMU monitor handling ====
+
"the plan is to re-focus 100% of all Xen kernel efforts onto paravirt_ops."
[[DanielBerrange|Daniel Berrange]]
+
See FWN#137.<ref>http://fedoraproject.org/wiki/FWN/Issue137#kernel-xen_is_Dead</ref>
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 ====
+
=== Libvirt List ===
In a characteristically long and detailed post [[DanielBerrange|Daniel Berrange]]
+
This section contains the discussion happening on the
laid<ref>http://www.redhat.com/archives/libvir-list/2009-October/msg00815.html</ref>
+
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
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 />

Revision as of 19:21, 11 November 2009


Contents

Virtualization

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

Contributing Writer: Dale Bewley

Fedora Virtualization List

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

Bridges

Andrés García asked[1]

[2]

[3] [4]

  1. http://www.redhat.com/archives/fedora-virt/2009-November/msg00002.html
  2. http://wiki.libvirt.org/page/Networking#Bridged_networking_.28aka_.22shared_physical_device.22.29
  3. https://fedorahosted.org/netcf/
  4. http://linux-kvm.com/content/netcf-silver-bullet-network-configuration

Fedora Xen List

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

No Xen dom0 in Fedora 12 Hopefully 13

Zhang Enming was disappointed[1] to learn the support for hosting Xen guests, dropped in Fedora 9, is still not present in Fedora 12.

Zhang referenced numerous videos documenting success with Xen dom0 on Fedora 11. While there are experimental patches which may be applied[2] to the kernel to enable support for dom0, they are not yet in the upstream kernel which forms the basis the Fedora kernel package.

It was decided[3] two years ago this month that Fedora "simply cannot spend more time forward porting Xen kernels" and "the plan is to re-focus 100% of all Xen kernel efforts onto paravirt_ops." See FWN#137.[4]

  1. http://www.redhat.com/archives/fedora-xen/2009-November/msg00019.html
  2. http://fedoraproject.org/wiki/FWN/Issue190#Dom0_Kernel_Status
  3. http://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html
  4. http://fedoraproject.org/wiki/FWN/Issue137#kernel-xen_is_Dead

Libvirt List

This section contains the discussion happening on the libvir-list.