From Fedora Project Wiki

< FWN‎ | Beats

 
(70 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 and
@fedora-virt list.
@virt-tools-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.  
about [[Features/VirtStorage|virt storage]].
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.
"What is the best way to deal with I/O load when running several VMs on a
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 />
<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.
 
The very newest releases of virt packages are available (for testing purposes only) in the [[Virtualization Preview Repository]] before they become generally available.


==== 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, using {{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


<references />
<references />


==== New Release virtinst 0.500.0 ====
[[ColeRobinson|Cole Robinson]]
announced<ref>http://www.redhat.com/archives/virt-tools-list/2009-July/msg00055.html</ref>
a new {{package|python-virtinst}} release, version 0.500.0.
<code>virtinst</code>  is a module that helps build and install <code>libvirt</code> based virtual machines. It currently supports <code>KVM</code>, <code>QEmu</code> and <code>Xen</code> virtual machines. Package includes several command line utilities, including <code>virt-install</code> (build and install new VMs) and <code>virt-clone</code> (clone an existing virtual machine).
'''New features:'''
* New virt-install device options --serial, --parallel, and --video
* Allow various auth types for libvirt connections (PolicyKit, SASL, ...)
* New virt-clone option --auto-clone: generates all needed input.
* Option to specify network device model via virt-install --network (Guido Gunther)
* New virt-install option --virt-type for specifying hypervisor type (kvm, qemu). --accelerate is now the default behavior: To provision a plain qemu VM on a KVM enabled host, use '--virt-type qemu'
* OVF input support for virt-convert
* Many bug fixes and improvements


====  ====
<references />
<references />


==== New Release virt-viewer 0.2.0 ====
==== ====
[[DanielBerrange|Daniel Berrange]]
announced<ref>http://www.redhat.com/archives/virt-tools-list/2009-July/msg00059.html</ref>
a new {{package|python-virtinst|virtinst}}<ref>http://virt-manager.org/</ref> release, version 0.2.0.
 
'''New features:'''
* Switch UI over to use Glade
* Support graphical dialog for VNC and libvirt authentication
* Resize window to match VNC desktop size where possible
* Scale down VNC desktop if it cannot fit in host desktop space
* Allow user to resize window to arbitrary size, scaling VNC
* Fix blocking of accelerators
* Allow automatic reconnect to a VM via --reconnect
* Use libvirt events to detect when VM changes state
* Wait for VM to appear if it does not exist
* Fix plugin build with newer xulrunner
* Port & build for Mingw32 target
 
<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."