From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
 
(77 intermediate revisions by 2 users not shown)
Line 6: Line 6:
== Virtualization ==
== Virtualization ==
In this section, we cover discussion of Fedora virtualization technologies on the
In this section, we cover discussion of Fedora virtualization technologies on the
@fedora-virt, @fedora-xen-list, @libguestfs, @libvirt-list,
@fedora-virt list.
@virt-tools-list, and @ovirt-devel-list lists.


Contributing Writer: [[User:Dale | Dale Bewley]]
Contributing Writer: [[User:Dale | Dale Bewley]]
Line 15: Line 14:
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].


==== Distributing I/O Load Among Guests ====
==== Virt Status Report ====
Dennis J.
[[JustinForbes|Justin Forbes]]
asked<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00183.html</ref>
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report.
"What is the best way to deal with I/O load when running several VMs on a
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.
physical machine with local or remote storage?" "What I'm primarily worried about is the case when several VMs cause disk I/O at the same time." "What is the best way to soften the impact of such a situation?"


[[PasiKärkkäinen|Pasi Kärkkäinen]]
suggested "If the IOS are not split evenly between VMs, you could use some tool like
dm-ioband<ref>http://sourceforge.net/apps/trac/ioband/wiki/dm-ioband</ref> to make sure IOs are split fairly between VMs. Or then get faster disks. Single 15k rpm SAS disk will give you up to 350
IOPS, so it's 2-3x faster than 7200 rpm SATA."
[[RichardJones|Richard Jones]]
concurred<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00188.html</ref>
"For KVM, each VM isn't really any different from a host process, so
you have to deal with them the same way that you'd deal with having
lots of host processes doing I/O.  So: lots of spindles, expensive I/O
hardware, etc."
<references />
=== Fedora Xen List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
====  ====
<references />
<references />


=== Virtualization Tools 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/virt-tools-list virt-tools-list list].
compared to Fedora 12.


==== New Release virt-manager 0.8.0 ====
[[DanielBerrange|Daniel Berrange]]  
[[ColeRobinson|Cole Robinson]]
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
<ref>http://www.redhat.com/archives/virt-tools-list/2009-July/msg00054.html</ref>
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
a new {{package|virt-manager}}<ref>http://virt-manager.org/</ref> release, version 0.8.0.
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
Virtual Machine Manager provides a graphical tool for administering virtual machines for <code>KVM</code>, <code>Xen</code>, and <code>QEmu</code>. Start, stop, add or remove virtual devices, connect to a graphical or serial console, and see resource usage statistics for existing VMs on local or remote machines. Uses {{package|libvirt}} as the backend management API.
also pretty close to that using what's best described as a hybrid of
 
kvm-83 and kvm-84."
'''New features:'''
* New 'Clone VM' Wizard
* Improved UI, including an overhaul of the main 'manager' view
* System tray icon for easy VM access (start, stop, view console/details)
* Wizard for adding serial, parallel, and video devices to existing VMs.
* CPU pinning support (Michal Novotny)
* Ability to view and change VM security (sVirt) settings (Dan Walsh)
* Many bug fixes and improvements
 
The newest releases of virt packages can be found in the [[Virtualization Preview Repository]].


<references />
<references />


=== Libguestfs List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/libguestfs libguestfs list].


====  ====
====  ====
<references />
<references />
=== Libvirt List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
====  ====
<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."