From Fedora Project Wiki

< FWN‎ | Beats

 
(405 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]
 
==== Starting Guests from a Desktop Icon ====
[[OrionPoplawski|Orion Poplawski]] said[1]
"I'd like to provide an icon that would startup the virtual machine and connect to it."
[[ColeRobinson|Cole Robinson]] posted[2] a couple of ways to accomplish this.
 
* With <code>virt-manager</code> and support for CDROM and USB devices
<pre>
UUID=`virsh --connect qemu:///system domuuid vm-name`
virsh --connect qemu:///system start $UUID
virt-manager --connect qemu:///system \
            --show-domain-console=$UUID
</pre>
 
* With <code>virt-viewer</code> which won't support CDROM and USB access
<pre>
UUID=`virsh --connect qemu:///system domuuid vm-name`
virsh --connect qemu:///system start $UUID
virt-viewer --connect qemu:///system $UUID
</pre>
 
Each solution requires adequate user permissions to work.
 
[1] https://www.redhat.com/archives/et-mgmt-tools/2008-October/msg00100.html
 
[2] https://www.redhat.com/archives/et-mgmt-tools/2008-October/msg00103.html
 
==== libvirt Plugins for Performance Monitoring Applications ====
[[GuidoGünther|Guido Günther]] announced[1] the creation
of plugins[2] for net and block I/O monitoring in Munin[3].
 
[[DanielVeillard|Daniel Veillard]] posted[4] a patch to add this and
similar plugins for collectd[5] and Nagios[6] to the libvirt
applications page[7].
 
 
[1] https://www.redhat.com/archives/et-mgmt-tools/2008-October/msg00118.html
 
[2] http://munin.projects.linpro.no/
 
[3] http://honk.sigxcpu.org/projects/libvirt/monitor/
 
[4] https://www.redhat.com/archives/et-mgmt-tools/2008-October/msg00121.html
 
[5] http://collectd.org/plugins/libvirt.shtml
 
[6] http://et.redhat.com/~rjones/nagios-virt/
 
[7] http://libvirt.org/apps.html"
 
=== Fedora Xen List ===
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
 
=== Libvirt List ===
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
 
==== Openvz Bridge Support and Related Patches ====
[[DanielBerrange|Daniel Berrange]] posted[1] a
patch series "derived from [[AntonProtopopov|Anton Protopopov]] / [[EvgeniySokolov|Evgeniy Sokolov]] bridge device patches. It first does some generic refactoring of MAC
address handler in all drivers, then adds code to extract OpenVZ[2] version
number, then does network config, and finally does filesystem config."
 
[1] https://www.redhat.com/archives/libvir-list/2008-October/msg00323.html
 
[2] http://wiki.openvz.org/
 
==== Guest Image Locking ====
[[ItamarHeim|Itamar Heim]] asked[1]
"how libvirt envisions image locking. i.e., how do we make sure multiple nodes are not trying to access the same storage volume".
 
[[DanielBerrange|Daniel Berrange]] said[2]
in the domain XML format "the semantics are that every <disk> section
added to a guest config is read-write, with an exclusive lock. To allow
multiple guests to use the same disk, is intended that you add either
<readonly/> or <sharable/> element within the <disk>."
 
Adding, "we only implement this for the Xen driver, handing off
the actuall logic to XenD to perform. That we don't implement this in
the QEMU driver is a clear shortcoming that needs addressing. "


The problem on a single host is relatively simple, but more complex among multiple host nodes.
Contributing Writer: [[User:Dale | Dale Bewley]]
[[GuidoGünther|Guido Günther]] has been toying[3] "with the idea of using
DLM[4] for libvirt".


[1] https://www.redhat.com/archives/libvir-list/2008-October/msg00334.html
=== Fedora Virtualization List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].


[2] https://www.redhat.com/archives/libvir-list/2008-October/msg00336.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.


[3] https://www.redhat.com/archives/libvir-list/2008-October/msg00342.html
<references />


[4] http://sources.redhat.com/cluster/dlm/
==== RHEL and Fedora Virtualization Feature Parity ====
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
compared to Fedora 12.


==== Exporting the Label on Block Devices ====
[[DanielBerrange|Daniel Berrange]]  
[[ChrisLalancette|Chris Lalancette]] described[1] his patch
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
"To support LVM partitioning in oVirt, one of the things we need is the ability
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
to tell what kind of label is currently on a block device. Here, a 'label' is
Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was
used in the same sense that it is used in parted; namely, it defines which kind
rebased to be near parity with [[Releases/11|Fedora 11]], and KVM in RHEL-5.4 is
of partition table is on the disk, whether it be DOS, LVM2, SUN, BSD, etc." Not
also pretty close to that using what's best described as a hybrid of
the partition type.
kvm-83 and kvm-84."


[1] https://www.redhat.com/archives/libvir-list/2008-October/msg00341.html
<references />


==== Experimental User Mode Linux Driver ====
[[DanielBerrange|Daniel P. Berrange]] [1]
"This patch implements a driver supporting User Mode Linux guests. User mode
linux is a kind of paravirtualized kernel which runs on a plain Linux host.
It requires no elevated privileges at all, except for some of the network
integration. It is a pretty straightforward thing to invoke, so I figured
it would be easy to write a driver to support it. I was right :-)"...


[1] https://www.redhat.com/archives/libvir-list/2008-October/msg00355.html
====  ====
<references />


=== oVirt Devel List ===
====  ====
This section contains the discussion happening on the [https://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].
<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."