From Fedora Project Wiki

< FWN‎ | Beats
 
(323 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]
 
==== Enabling Builds of libvirt for Windows ====
[[RichardJones|Richard W.M. Jones]] sought[1] help in enabling builds of
Windows <code>libvirt</code> binaries under Fedora. "It seems like we should have the base MinGW (Windows cross-compiler)
packages in Fedora 11 by the end of this week.  This email is to
document the additional packages we need to get approved, in order to
get the cross-compiled <code>libvirt</code> and virt tools into (or buildable by)
Fedora 11.
 
If you want to help out, please start reviewing by following the
Bugzilla links, and looking at the approved packaging guidelines[2]"
 
[1] http://www.redhat.com/archives/et-mgmt-tools/2008-November/msg00073.html
 
[2] http://fedoraproject.org/wiki/Packaging/MinGW.
 
==== Solaris Support in virtinst ====
[[JohnLevon|John Levon]] submitted several patches to improve Solaris support
in {{package|python-virtinst}} including and not limited to the following:
 
* Add an option for passing Solaris JumpStart information.[1]
* Various utility functions[2].
* "Make 'solaris' a first-class OS type, and select USB tablet support for the appropriate variants."[3]
* Add support for Solaris PV.[4]
* Support for the vdisk format[5]. John explained "<code>vdisk</code> is basically " Sun's " tap implementation and disk management tool.
 
[1] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00062.html
 
[2] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00063.html
 
[3] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00064.html
 
[4] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00065.html


[5] http://www.redhat.com/archives/et-mgmt-tools/2008-December/msg00067.html
Contributing Writer: [[User:Dale | Dale Bewley]]


=== Fedora Xen List ===
=== Fedora Virtualization List ===
This section contains the discussion happening on the
This section contains the discussion happening on the
[https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
 
==== Support for Fedora 10 DomU on F8 Dom0 ====
The changes[1] made to the {{package|kernel}} which obviated
{{package|kernel-xen}} caused {{package|python-virtinst}} to fail[2] during the
creation of a Fedora 10 Xen guest on a Fedora 8 Xen host.
 
[[ColeRobinson|Cole Robinson]] announced[3] a test build[4] which fixes this
problem. Readers are encouraged to test the release and provide positive karma
points in bodhi[5] to make the build an official update.
 
[1] http://docs.fedoraproject.org/release-notes/f10/en_US/What_Do_System_Adminstrators_Care_About.html#sn-Unified_kernel_image
 
[2] {{bz|458164}}
 
[3] http://www.redhat.com/archives/fedora-xen/2008-November/msg00036.html
 
[4] http://koji.fedoraproject.org/koji/buildinfo?buildID=71125
 
[5] https://admin.fedoraproject.org/updates/F8/FEDORA-2008-10394
 
==== Paravirt Ops Dom0 Feature Update ====
After some prompting[1] from [[PasiKärkkäinen|Pasi Kärkkäinen]]
the dom0 support feature page[2] was updated to better clarify where the work
to bring dom0 support back to Fedora is being done, and to more accurately represent the current status.
 
The patches[3] are being written by Jeremy Fitzhardinge and others at Citrix/XenSource are being submitted to the mainline <code>kernel</code>. Once accepted in the upstream <code>kernel</code>, efforts will resume within Fedora to make the changes necessary to support dom0. These efforts include[4] ensuring the hypervisor supports <code>bzImage</code> kernels.


[1] http://www.redhat.com/archives/fedora-xen/2008-November/msg00021.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] http://fedoraproject.org/wiki/Features/XenPvopsDom0
<references />
 
[3] http://xenbits.xen.org/paravirt_ops/patches.hg/
 
[4] http://www.redhat.com/archives/fedora-xen/2008-November/msg00025.html
 
=== Libvirt List ===
This section contains the discussion happening on the
[https://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
 
==== Release of libvirt 0.5.0 and 0.5.1 ====
[[DanielVeillard|Daniel Veillard]] announced[1][2] the releases of
{{package|libvirt}} 0.5.0 and 0.5.1. "This is a long expected release, with a lot of new features, as a result the small version number is increased." Tarballs and signed RPMs available upstream[3] and in Bodhi[4].
 
"As stated there is a huge amount of new features and improvement in this release, as well as a lot of bug fixes, the list is quite long". See the post[1] for the full list including the numerous improvments, documentation updates, bug fixes, and cleanups omitted below.
 
'''New features:'''
* CPU and scheduler support for LXC (Dan Smith)
* SDL display configuration (Daniel Berrange)
* domain lifecycle event support for QEmu and Xen with python bindings (Ben Guthro and Daniel Berrange)
* KVM/QEmu migration support (Rich Jones and Chris Lalancette)
* User Mode Linux driver (Daniel Berrange)
* API for node device enumeration using HAL and DeviceKit with python bindings (David Lively)
 
"Thanks a lot to everybody who contributed to this release, it is
really great to see new people providing significant patches, and the
amount of feedback received on the list."
 
[1] http://www.redhat.com/archives/libvir-list/2008-November/msg00387.html
 
[2] http://www.redhat.com/archives/libvir-list/2008-December/msg00148.html
 
[3] ftp://libvirt.org/libvirt/
 
[4] https://admin.fedoraproject.org/updates/libvirt
 
==== Allow Automatic Driver Probe for Remote TCP Connections ====
Later described by the release of {{package|libvirt}} 0.5.1 as an improvement, [[DanielBerrange|Daniel P. Berrange]] posted[1] the patch to implement a more general method for connecting to remote[2] hypervisor drivers.
 
"When connecting to a local <code>libvirt</code> you can let it automatically probe
the hypervisor URI if you don't know it ahead of time. This doesn't
work with remote URIs because you need to have something to put in
the URI scheme before the hostname:
* qemu+ssh://somehost/system
* xen+tcp://somehost/system
 
This is then translated into the URI:
* qemu:///system
* xen:///
 
...
 
This patch adds a 'remote' URI scheme, usable like this:
* remote+ssh://somehost/
* remote+tcp://somehost/
 
...
 
This finally makes the Avahi[3] broadcasts useful - they only include
info on the hostname + data transport (SSH, TCP, TLS), not the HV
type. So letting us use auto-probing remotely is the missing link."
 
[1] http://www.redhat.com/archives/libvir-list/2008-November/msg00420.html
 
[2] http://libvirt.org/remote.html
 
[3] http://www.avahi.org
 
==== Thread Safety for libvirtd Daemon and Drivers ====
[[DanielBerrange|Daniel P. Berrange]] posted[1] a huge series of 28 patches
which add "thread safety for the
<code>libvirtd</code>
daemon and drivers, and makes the daemon multi-threaded in processing
RPC calls. This enables multiple clients to be processed in parallel,
without blocking each other. It does not change the thread rules for the
virConnectPtr object though, so each individual client is still serialized."
...
"This touches a huge amount of code, so I'd like to get this all merged
ASAP as it'll be really hard to keep it synced with ongoing changes."
 
[1] http://www.redhat.com/archives/libvir-list/2008-November/msg00453.html
 
[2] http://fedoraproject.org/wiki/FWN/Issue148#Experimental_Driver_Thread_Safety
 
==== libvirt 0.5.0 and KVM Migration Support ====
Mickaël Canévet wondered[1] if {{package|kvm}} guest migration was expected to be functional.
"I just installed {{package|libvirt}} 0.5.0 on Debian Lenny with <code>kvm</code> 0.72 to try <code>kvm</code>
migration support." Tests failed with "libvir: error : this function is not supported by the hypervisor: virDomainMigrate."
 
[[ChrisLalancette|Chris Lalancette]] confirmed[2]
"Yes, it is supposed to work, but yes, you need a very, very new <code>kvm</code>.  In particular, you need at least kvm-77, and it won't really work right until you get to kvm-79."
 
[1] http://www.redhat.com/archives/libvir-list/2008-December/msg00025.html
 
[2] http://www.redhat.com/archives/libvir-list/2008-December/msg00027.html
 
=== oVirt Devel List ===
This section contains the discussion happening on the
[https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].


==== Some Architecture Diagrams ====
==== RHEL and Fedora Virtualization Feature Parity ====
[[DanielBerrange|Daniel P. Berrange]] said[1]
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
"I felt I wanted some additional more technically detailed/ focused diagrams
compared to Fedora 12.
to illustrate what we're doing to developers actually writing code
for the project." And pointed to <code>oVirt</code> architecure diagrams he
created.[2]


[1] http://www.redhat.com/archives/ovirt-devel/2008-November/msg00357.html
[[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."


[2] http://ovirt.org/page/ArchDiagrams
<references />


==== Standalone Console Viewer for oVirt ====
Continuing work on a executable console solution[1] for <code>oVirt</code>, with a fork of {{package|virt-viewer}},
[[RichardJones|Richard W.M. Jones]] created[2] <code>ovirt-viewer</code>.


[1] https://fedoraproject.org/wiki/FWN/Issue151#oVirt_Console_Conundrum
====  ====
<references />


[2] http://www.redhat.com/archives/ovirt-devel/2008-November/msg00412.html
====  ====
<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"