From Fedora Project Wiki

< FWN‎ | Beats

 
(194 intermediate revisions by 2 users not shown)
Line 2: Line 2:
  
 
{{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: [[User:Dale | Dale Bewley]]
 
Contributing Writer: [[User:Dale | Dale Bewley]]
 
 
  
 
=== Fedora Virtualization List ===
 
=== Fedora Virtualization List ===
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].
  
==== Fedora Virtualization Status Report ====
+
==== Virt Status Report ====
[[MarkMcLoughlin|Mark McLoughlin]]'s
+
[[JustinForbes|Justin Forbes]]
status report<ref>http://www.redhat.com/archives/fedora-virt/2009-April/msg00006.html</ref>
+
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report.
this week reminds us that the final development freeze<ref>http://fedoraproject.org/wiki/ReleaseEngineering/DevelFreezePolicy</ref>
+
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.
for
 
[[Releases/11/Schedule|Fedora 11]] is coming up on April
 
14, 2009, and "there's a huge pile of bug-fixing and polish work to do".
 
 
 
"If you're looking to help out, there's no better place to start
 
than the
 
F11VirtBlocker<ref>https://bugzilla.redhat.com/showdependencytree.cgi?id=F11VirtBlocker&hide_resolved=1</ref>
 
and
 
F11VirtTarget<ref>https://bugzilla.redhat.com/showdependencytree.cgi?id=F11VirtTarget&hide_resolved=1</ref>
 
tracker bugs."
 
 
 
Read on for more coverage of virtualization developments in the past week.
 
  
 
<references />
 
<references />
  
==== Using kvm-autotest to test Fedora KVM ====
+
==== 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
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-April/msg00007.html</ref>
+
compared to Fedora 12.
"upstream <code>KVM</code> developers are working hard on a suite of regression tests for <code>KVM</code>. It would be hugely helpful if people could run
 
<code>kvm-autotest</code><ref>http://www.linux-kvm.org/page/KVM-Autotest</ref>
 
on their own machines to try and catch as many <code>KVM</code> issues as possible."
 
Mark also provided
 
a howto<ref>http://fedoraproject.org/wiki/Testing_KVM_with_kvm_autotest</ref>.
 
  
<references />
+
[[DanielBerrange|Daniel Berrange]]  
 
+
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
=== Fedora Xen List ===
+
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
This section contains the discussion happening on the
+
Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
+
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
==== Experimental Dom0 Kernel Update ====
+
kvm-83 and kvm-84."
[[MichaelYoung|Michael Young]]
 
announced<ref>http://www.redhat.com/archives/fedora-xen/2009-March/msg00084.html</ref>
 
his repository<ref>http://fedorapeople.org/~myoung/dom0/</ref>
 
"is up to kernel 2.6.29-1.2.18.fc11. This one is based on push2/xen/dom0/master<ref>http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary</ref>
 
rather than xen/dom0/hackery which should be closer to what is proposed for the 2.6.30 merge. It also has CONFIG_HIGHPTE=n (for x86), but my attempts to add squashfs 3 in addition to squashfs 4 didn't work as it seems you can't build both."
 
  
 
<references />
 
<references />
  
=== Libvirt List ===
 
This section contains the discussion happening on the
 
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
 
 
==== New Release libvirt 0.6.2 ====
 
[[DanielVeillard|Daniel Veillard]]
 
announced<ref>http://www.redhat.com/archives/libvir-list/2009-April/msg00084.html</ref>
 
a new {{package|libvirt}} release, version 0.6.2.
 
 
"This is mostly a bug fix release, though it also includes a few new
 
features and some improvements:"
 
 
'''New features:'''
 
* support SASL auth for VNC server (Daniel Berrange)
 
* memory ballooning in QEMU (Daniel Berrange)
 
* SCSI HBA storage pool support (Dave Allan)
 
* PCI passthrough in Xen driver (Daniel Berrange)
 
 
'''Improvements:'''
 
* get CPU usage info for LXC (Ryota Ozaki)
 
* fix domain RNG to add ac97 and tests (Pritesh Kothari)
 
* OpenVZ support for non-template filesystem root (Florian Vichot)
 
* improve arch capabilities generation (Daniel Berrange)
 
* modularization of spec file (Ryota Ozaki)
 
* better error reports in SEXPR generation (Daniel Berrange)
 
* support for vifname parameter in VIF config (Daniel Berrange)
 
* localtime handling for new xen (Daniel Berrange)
 
* error reporting/ verification of security labels (Dan Walsh)
 
* add --console arg for create and start virsh commands (Daniel Berrange)
 
* refresh volume alloc/capacity when dumping XML (Cole Robinson)
 
 
This release comes one month after the release of
 
0.6.1<ref>http://fedoraproject.org/wiki/FWN/Issue166#New_Release_libvirt_0.6.1</ref>.
 
 
[[DanielVeillard|Daniel Veillard]]
 
referred<ref>http://www.redhat.com/archives/libvir-list/2009-April/msg00085.html</ref>
 
to the scheduling conversation last week
 
(FWN#169<ref>http://fedoraproject.org/wiki/FWN/Issue169#More_Formal_libvirt_Release_Scheduling</ref>) when reitterating the plan for a feature freeze around April 17th and a release of 0.6.3 around April 24th.
 
 
"Plannned so far for 0.6.3 are:
 
* API for physical host interface
 
* the VirtualBox driver if in shape and in time
 
 
but that's not an exhaustive list and there is a couple of drivers
 
submitted I need to look at (OpenNebula for example)."
 
  
 +
====  ====
 
<references />
 
<references />
  
==== First Release netcf 0.0.1 ====
+
==== ====
Less that 3 months since compsing the RFC(FWN#159<ref>http://fedoraproject.org/wiki/FWN/Issue159#Configuring_Host_Interfaces_RFC</ref>)
 
[[DavidLutterkort|David Lutterkort]]
 
announced<ref>http://www.redhat.com/archives/libvir-list/2009-April/msg00068.html</ref>, the release of {{package|netcf}}<ref>http://fedorahosted.org/netcf/</ref> 0.0.1. This is
 
"the initial
 
release of a library for managing network configuration in a platform
 
agnostic manner. If I were into code names, this would be the 'what have
 
you been waiting for' release."
 
 
 
"<code>Netcf</code> does its work by directly modifying the 'native' configuration files
 
of the host it is running on; this avoids a whole class of problems caused
 
by similar approaches that do network configuration behind the back of the
 
native mechanisms. The API allows listing of configured interfaces,
 
defining the configuration of an interface, retrieving the same (regardless
 
of whether the interface was initially configured with netcf or not), and
 
bringing interfaces up and down. This functionality is needed both by
 
{{package|libvirt}} and {{package|NetworkManager}}, so it seemed only logical to move their common
 
needs into a separate library."
 
 
 
[[LaineStump|Laine Stump]] is already working on patches<ref>http://www.redhat.com/archives/libvir-list/2009-April/msg00050.html</ref> to add the <code>netcf</code> calls in the <code>libvirt</code> API.
 
 
 
Read the announcement for more information such as the new mailing list for
 
<code>netcf</code> development discussion and where to find the test builds for
 
Fedora 10.
 
 
 
 
<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."