From Fedora Project Wiki

< FWN‎ | Beats

(reset for fwn 170)
Line 8: Line 8:
 
Contributing Writer: [[User:Dale | Dale Bewley]]
 
Contributing Writer: [[User:Dale | Dale Bewley]]
  
 +
=== Enterprise Management Tools List ===
 +
This section contains the discussion happening on the
 +
[http://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
  
 +
====  ====
 +
<references />
  
 
=== Fedora Virtualization List ===
 
=== Fedora Virtualization List ===
Line 14: Line 19:
 
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
 
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
  
==== KVM and QEMU Merge Feature Stays in Fedora 11====
+
==== ====
After missing the previous
 
round (FWN #165<ref>http://fedoraproject.org/wiki/FWN/Issue165#Approved_F11_Virtualization_Features</ref>)
 
and some development delay, the <code>KVM</code> and <code>QEMU</code> package merge
 
feature<ref>http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge</ref>
 
of Fedora 11 has been marked as
 
accepted by the Fedora Engineering Steering Committee<ref>http://fedoraproject.org/wiki/FESCO</ref>.
 
 
 
"Currently, there is both a {{package|qemu}} package and {{package|kvm}} package. The <code>KVM</code> package's source is a fork of the <code>QEMU</code> source, but <code>KVM</code> regularily re-bases to the latest <code>QEMU</code> source and merging of <code>KVM</code> support into the <code>QEMU</code> code base is actively under-way."
 
 
 
<references />
 
 
 
==== Fedora Virtualization Status Report ====
 
After a few weeks off,
 
[[MarkMcLoughlin|Mark McLoughlin]]
 
reached back into the future and produced an exhaustive status
 
report<ref>http://www.redhat.com/archives/fedora-virt/2009-March/msg00068.html</ref>
 
covering all the developments in fedora Virtualization for the last month.
 
Grab a bowl of popcorn and dig in!
 
 
 
 
<references />
 
<references />
  
Line 40: Line 26:
 
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
 
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
  
==== Success with Experimental Fedora 10 pv_ops dom0 ====
+
==== ====
Users are continuing to build experimental kernels with <code>pv_ops</code> dom0<ref>http://fedoraproject.org/wiki/Features/XenPvopsDom0</ref> support.
 
[[PasiKärkkäinen|Pasi Kärkkäinen]]
 
was happy to
 
report<ref>http://www.redhat.com/archives/fedora-xen/2009-March/msg00071.html</ref>
 
success getting a
 
"custom Xen <code>pv_ops</code> dom0 <code>kernel</code> working with
 
<code>virt-install</code> and/or {{package|virt-manager}} on Fedora 10".
 
 
 
"I was able to run the following on Fedora 10 32bit PAE pv_ops dom0:"
 
* CentOS 5.3 32bit PAE PV domU
 
* Fedora 10 32bit PAE PV domU (using <code>virt-install</code> and custom kickstart to force PAE kernel installation to avoid the anaconda BUG<ref>https://bugzilla.redhat.com/show_bug.cgi?id=470905</ref>)
 
 
 
Pasi was successful by using:
 
* pv_ops dom0 kernel (2.6.29-rc8 or newer) "Compile with <code>CONFIG_HIGHPTE=n</code> since it seems to be broken still"
 
* {{package|libvirt}} 0.6.1 and related packages from Fedora 10 updates-testing
 
* {{package|xen}} 3.3.1-9 packages from rawhide/F11 rebuilt for F10
 
* LVM volumes for domU disks (<code>tap:aio</code> is not yet supported by <code>pv_ops</code> dom0 kernel)
 
 
 
<references />
 
 
 
==== Yum Repository for Experimental Dom0 Kernels ====
 
Since [[Koji]] removes scratch builds after some time,
 
[[MichaelYoung|Michael Young]]
 
created<ref>http://www.redhat.com/archives/fedora-xen/2009-March/msg00078.html</ref>
 
a repository<ref>http://fedorapeople.org/~myoung/dom0/</ref>
 
for the experimental Dom0 capable<ref>http://fedoraproject.org/wiki/Features/XenPvopsDom0</ref> <code>kernels</code> he's experimenting with.
 
 
 
 
<references />
 
<references />
  
Line 74: Line 33:
 
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
 
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
  
==== More Formal libvirt Release Scheduling ====
+
====  ====
After
 
[[DanielVeillard|Daniel Veillard]]
 
proposed a {{package|libvirt}} 0.6.2 release next week,
 
[[DanielBerrange|Daniel Berrange]]
 
thought
 
<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00435.html</ref>
 
the "release schedule has become a little too variable in timeframe and
 
quality in recent times."
 
(FWN #155<ref>http://fedoraproject.org/wiki/FWN/Issue155#Release_of_libvirt_0.5.0_and_0.5.1</ref>) and suggested
 
* Monthly releases aiming for the 1st of the month.
 
* Any non-trivial new feature for release must be reviewed, approved and committed at least 1 week before the release.
 
 
 
[[DanielBerrange|Daniel Berrange]] is also
 
"working on an integration test suite, which will
 
enable us to run automated tests against individual hypervisor drivers.
 
This will help us detect regressions in hypervisor drivers, and more
 
importantly let us ensure that all drivers are implementing consistent
 
semantics for their APIs."
 
 
 
[[DanielVeillard|Daniel Veillard]]
 
tended<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00446.html</ref>
 
"to agree on the approximate rule of one release every months [sic]
 
but I would like to keep this flexible" and offered this schedule for the
 
next 2 releases:
 
 
 
* 0.6.2:
 
: commit feature freeze: Tuesday 31 Mar
 
: expected release date: Friday 3 Apr
 
 
 
* 0.6.3:
 
: commit feature freeze: Friday 17 Apr
 
: expected release date: Friday 24 Apr
 
 
 
<references />
 
 
 
==== New Release perl-Sys-Virt 0.2.0 ====
 
[[DanielBerrange|Daniel Berrange]]
 
announced<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00449.html</ref>
 
an update of the Perl binding for <code>libvirt</code>, {{package|perl-Sys-Virt}}<ref>http://search.cpan.org/dist/Sys-Virt/</ref>.
 
 
 
'''New features:'''
 
* Fix network create API, and UUID lookups
 
* Implement storage pool, storage vol, node device, security model, domain events and event loop APIs
 
* Improve way constants are exposed to Perl layer
 
* Fix horrible memory leak in methods returning a hash
 
* Fix integer overflow in APIs using 64-bit ints (aka 'long long')
 
* Minimum required libvirt C library for building is 0.6.1
 
 
 
<references />
 
 
 
==== SCSI Host Pools Patch ====
 
[[DavidAllan|David Allan]]
 
has been working<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00420.html</ref>
 
on a reworked SCSI host storage pool<ref>http://www.libvirt.org/storage.html</ref>
 
patch for some time, and appears to be close to ironing out all the bugs.
 
 
 
<references />
 
 
 
==== API for Host Interface Configuration ====
 
The Shared Network Interface
 
feature<ref>http://fedoraproject.org/wiki/Features/Shared_Network_Interface</ref>
 
was deferred to Fedora 12 while
 
[[DavidLutterkort|David Lutterkort]]
 
continues to work on <code>netcf</code><ref>http://people.redhat.com/dlutter/netcf/</ref>
 
(FWN #164<ref>http://fedoraproject.org/wiki/FWN/Issue164#netcf_Network_Interface_Configuration_Library</ref>).
 
 
 
Now [[LaineStump|Laine Stump]]
 
has posted<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00397.html</ref>
 
"a first attempt at the public API that will hook up to <code>libnetcf</code> on the <code>libvirtd</code> side."
 
 
 
<references />
 
 
 
==== Web Based libvirt Management ====
 
[[RadekHladik|Radek Hladik]] is
 
developing<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00402.html</ref>
 
"a simple web application in PHP to monitor and control VMs using libvirt."
 
The stateless nature of the web presents efficiency problems when each action
 
must call out to the <code>virsh</code> command. Radik sought advice on
 
picking from a list of approaches.
 
 
 
[[DanielBerrange|Daniel Berrange]]
 
picked<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00407.html</ref>
 
door number two, which is to create a libvirt-aware Zend extension in C.
 
"A few people have expressed interest in
 
this idea in the past, but unforatuntely I'm not aware of anyone having
 
written any code for this yet. We'd very much like to see a PHP binding
 
for libvirt developed & happy to give advice/support to anyone attempting
 
this."
 
 
 
[[RussellHaering|Russell Haering]]
 
mentioned<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00409.html</ref>
 
a Django (python) WebApp he's working on, called virtadmin<ref>http://trac.osuosl.org/trac/virtadmin</ref>. To bridge the stateless to stateful gap, the
 
"system consists of a <code>python</code> daemon used for actual <code>libvirt</code>
 
interaction and a separate <code>django</code> web interface that interacts with the
 
daemon via <code>AMF</code> over https."
 
 
 
Although more of an appliance, it is also worth mentioning
 
oVirt<ref>http://ovirt.org/</ref>.
 
"oVirt is a small host image that provides libvirt service and hosts virtual
 
machines and a web-based virtual machine management console."
 
 
 
 
<references />
 
<references />

Revision as of 00:42, 5 April 2009


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.

Contributing Writer: Dale Bewley

Enterprise Management Tools List

This section contains the discussion happening on the et-mgmt-tools list


Fedora Virtualization List

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


Fedora Xen List

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


Libvirt List

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