From Fedora Project Wiki

< FWN‎ | Beats
 
(390 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 ===
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
 
==== DomU I/O Performance Sanity Check ====
[[AskHansen|Ask Bjørn Hansen]] asked[1] if the disk throughput he experienced matched what others see.
The dom0 host achieved 120MB/sec sequential write speed, and a domU only 22MB/sec.
 
[[TroelsArvin|Troels Arvin's]] experiences with paravirt Xen on raw devices were fine for normal I/O but bad for low-level operations like file system creation. Troel also posted[3] some benchmark results in 2007.
 
[1] https://www.redhat.com/archives/fedora-xen/2008-October/msg00012.html
 
[2] https://www.redhat.com/archives/fedora-xen/2008-October/msg00013.html
 
[3] http://article.gmane.org/gmane.comp.emulators.xen.user/29483
 
=== Libvirt List ===
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
 
==== sVirt Initial Prototype Release ====
[[JamesMorris|James Morris]] requested[1] comments on an initial prototype of <code>sVirt</code>[2] v0.10.
<code>sVirt</code> was first mentioned in FWN #138[3].
 
"The purpose of this release is to establish a proof of concept of applying
security labels to VMs, and for discussion of the underlying technical approach."
 
"With this release, it is possible to define a security label for a
<code>KVM</code>/<code>QEMU</code> domain in its XML configuration ('<code>virsh edit</code>'), launch the domain
and have it transition to the specified security label ('<code>virsh start</code>'),
then query the security label of the running domain ('<code>virsh dominfo</code>')."
 
[1] https://www.redhat.com/archives/libvir-list/2008-October/msg00478.html
 
[2] http://www.selinuxproject.org/page/SVirt


[3] http://fedoraproject.org/wiki/FWN/Issue138#sVirt_project_to_Integrate_SELinux_and_Linux-based_Virtualization
Contributing Writer: [[User:Dale | Dale Bewley]]


==== Hot-add SCSI/VirtIO Disks for KVM Guests ====
=== Fedora Virtualization List ===
[[GuidoGünther|Guido Günther]] supplied[1] a patch to add hot plugging and
This section contains the discussion happening on the
unplugging[2] of SCSI/VirtIO disks for <code>KVM</code> guests.  
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].


[1] https://www.redhat.com/archives/libvir-list/2008-October/msg00391.html
==== Virt Status Report ====
[[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.


[2] https://www.redhat.com/archives/libvir-list/2008-October/msg00427.html
<references />


==== Domain Events Support Completed ====
==== RHEL and Fedora Virtualization Feature Parity ====
After three[1] rounds, [[BenGuthro|Ben Guthro's]] domain events patches have been committed. This major API addition led[2] [[DanielVeillard|Daniel Veillard]] to speculate that the next release version number may jump to 0.5.0. Domain events are only emitted from <code>KVM</code> guests. The other hypervisor drivers will require more work to properly emit domain events.
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
compared to Fedora 12.


The <code>python</code> bindings are forthcoming. [3]
[[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."


[1] https://www.redhat.com/archives/libvir-list/2008-October/msg00537.html
<references />


[2] https://www.redhat.com/archives/libvir-list/2008-October/msg00594.html


[3] https://www.redhat.com/archives/libvir-list/2008-October/msg00598.html
====  ====
<references />


=== oVirt Devel List ===
====  ====
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].
<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.

  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"