From Fedora Project Wiki


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


Fedora Virtualization List

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

KVM and QEMU Merge Feature Stays in Fedora 11

After missing the previous round (FWN #165[1]) and some development delay, the KVM and QEMU package merge feature[2] of Fedora 11 has been marked as accepted by the Fedora Engineering Steering Committee[3].

"Currently, there is both a Package-x-generic-16.pngqemu package and Package-x-generic-16.pngkvm package. The KVM package's source is a fork of the QEMU source, but KVM regularily re-bases to the latest QEMU source and merging of KVM support into the QEMU code base is actively under-way."

  1. ↑ http://fedoraproject.org/wiki/FWN/Issue165#Approved_F11_Virtualization_Features
  2. ↑ http://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge
  3. ↑ http://fedoraproject.org/wiki/FESCO

Fedora Virtualization Status Report

After a few weeks off, Mark McLoughlin reached back into the future and produced an exhaustive status report[1] covering all the developments in fedora Virtualization for the last month. Grab a bowl of popcorn and dig in!

  1. ↑ http://www.redhat.com/archives/fedora-virt/2009-March/msg00068.html

Fedora Xen List

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

Success with Experimental Fedora 10 pv_ops dom0

Users are continuing to build experimental kernels with pv_ops dom0[1] support. Pasi Kärkkäinen was happy to report[2] success getting a "custom Xen pv_ops dom0 kernel working with virt-install and/or Package-x-generic-16.pngvirt-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 virt-install and custom kickstart to force PAE kernel installation to avoid the anaconda BUG[3])

Pasi was successful by using:

  • pv_ops dom0 kernel (2.6.29-rc8 or newer) "Compile with CONFIG_HIGHPTE=n since it seems to be broken still"
  • Package-x-generic-16.pnglibvirt 0.6.1 and related packages from Fedora 10 updates-testing
  • Package-x-generic-16.pngxen 3.3.1-9 packages from rawhide/F11 rebuilt for F10
  • LVM volumes for domU disks (tap:aio is not yet supported by pv_ops dom0 kernel)
  1. ↑ http://fedoraproject.org/wiki/Features/XenPvopsDom0
  2. ↑ http://www.redhat.com/archives/fedora-xen/2009-March/msg00071.html
  3. ↑ https://bugzilla.redhat.com/show_bug.cgi?id=470905

Yum Repository for Experimental Dom0 Kernels

Since Koji removes scratch builds after some time, Michael Young created[1] a repository[2] for the experimental Dom0 capable[3] kernels he's experimenting with.

  1. ↑ http://www.redhat.com/archives/fedora-xen/2009-March/msg00078.html
  2. ↑ http://fedorapeople.org/~myoung/dom0/
  3. ↑ http://fedoraproject.org/wiki/Features/XenPvopsDom0

Libvirt List

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

More Formal libvirt Release Scheduling

After Daniel Veillard proposed a Package-x-generic-16.pnglibvirt 0.6.2 release next week, Daniel Berrange thought [1] the "release schedule has become a little too variable in timeframe and quality in recent times." (FWN #155[2]) 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.

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."

Daniel Veillard tended[3] "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
  1. ↑ http://www.redhat.com/archives/libvir-list/2009-March/msg00435.html
  2. ↑ http://fedoraproject.org/wiki/FWN/Issue155#Release_of_libvirt_0.5.0_and_0.5.1
  3. ↑ http://www.redhat.com/archives/libvir-list/2009-March/msg00446.html

New Release perl-Sys-Virt 0.2.0

Daniel Berrange announced[1] an update of the Perl binding for libvirt, Package-x-generic-16.pngperl-Sys-Virt[2].

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
  1. ↑ http://www.redhat.com/archives/libvir-list/2009-March/msg00449.html
  2. ↑ http://search.cpan.org/dist/Sys-Virt/

SCSI Host Pools Patch

David Allan has been working[1] on a reworked SCSI host storage pool[2] patch for some time, and appears to be close to ironing out all the bugs.

  1. ↑ http://www.redhat.com/archives/libvir-list/2009-March/msg00420.html
  2. ↑ http://www.libvirt.org/storage.html

API for Host Interface Configuration

The Shared Network Interface feature[1] was deferred to Fedora 12 while David Lutterkort continues to work on netcf[2] (FWN #164[3]).

Now Laine Stump has posted[4] "a first attempt at the public API that will hook up to libnetcf on the libvirtd side."

  1. ↑ http://fedoraproject.org/wiki/Features/Shared_Network_Interface
  2. ↑ http://people.redhat.com/dlutter/netcf/
  3. ↑ http://fedoraproject.org/wiki/FWN/Issue164#netcf_Network_Interface_Configuration_Library
  4. ↑ http://www.redhat.com/archives/libvir-list/2009-March/msg00397.html

Web Based libvirt Management

Radek Hladik is developing[1] "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 virsh command. Radik sought advice on picking from a list of approaches.

Daniel Berrange picked[2] 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."

Russell Haering mentioned[3] a Django (python) WebApp he's working on, called virtadmin[4]. To bridge the stateless to stateful gap, the "system consists of a python daemon used for actual libvirt interaction and a separate django web interface that interacts with the daemon via AMF over https."

Although more of an appliance, it is also worth mentioning oVirt[5]. "oVirt is a small host image that provides libvirt service and hosts virtual machines and a web-based virtual machine management console."

  1. ↑ http://www.redhat.com/archives/libvir-list/2009-March/msg00402.html
  2. ↑ http://www.redhat.com/archives/libvir-list/2009-March/msg00407.html
  3. ↑ http://www.redhat.com/archives/libvir-list/2009-March/msg00409.html
  4. ↑ http://trac.osuosl.org/trac/virtadmin
  5. ↑ http://ovirt.org/

oVirt Devel List

This section contains the discussion happening on the ovirt-devel list.

Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/Virtualization&oldid=93229"