From Fedora Project Wiki

< FWN‎ | Beats

(→‎Libvirt List: API for Host Interface Configuration)
 
(204 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].


==== KVM and QEMU Merge Feature Stays in Fedora 11====
==== Virt Status Report ====
After missing the previous
[[JustinForbes|Justin Forbes]]
round (FWN #165<ref>http://fedoraproject.org/wiki/FWN/Issue165#Approved_F11_Virtualization_Features</ref>)
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report.  
and some development delay, the <code>KVM</code> and <code>QEMU</code> package merge
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.
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 />
 
=== Fedora Xen List ===
This section contains the discussion happening on the
[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 />


=== Libvirt List ===
==== RHEL and Fedora Virtualization Feature Parity ====
This section contains the discussion happening on the
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
compared to Fedora 12.
 
==== 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
[[DanielBerrange|Daniel Berrange]]  
"working on an integration test suite, which will
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
enable us to run automated tests against individual hypervisor drivers.
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
This will help us detect regressions in hypervisor drivers, and more
Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was
importantly let us ensure that all drivers are implementing consistent
rebased to be near parity with [[Releases/11|Fedora 11]], and KVM in RHEL-5.4 is
semantics for their APIs."
also pretty close to that using what's best described as a hybrid of
 
kvm-83 and kvm-84."
[[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 />
<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 />
<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 />
==== ====
<references />
=== oVirt Devel List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].


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