From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
Line 9: Line 9:


Contributing Writer: [[User:Dale | Dale Bewley]]
Contributing Writer: [[User:Dale | Dale Bewley]]
=== Events ===
==== Red Hat Virtual Experience ====
On December 9th 9am EST to 6pm EST, Red Hat will be holding an online "event focused on Red Hat Enterprise Linux solutions, including virtualization and cloud computing."
Titled "Red Hat Virtual Experience 2009"<ref>http://www-2.virtualevents365.com/rhexp/about.php</ref>
Attendees can participate in keynote sessions and "chats with business leaders, executives, key developers, customers, and strategic partners", and
"learn what's on the horizon from Red Hat and industry partners—innovations in Red Hat Enterprise Linux, tools, security, and deployment in the cloud."
<references />


=== Fedora Virtualization List ===
=== Fedora Virtualization List ===
Line 23: Line 14:
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].


==== KSM Tuning Daemon and the KSM Kernel Thread Process ====
==== RHEL and Fedora Virtualization Feature Parity ====
[[GianlucaCecchi|Gianluca Cecchi]]
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
was<ref>http://www.redhat.com/archives/fedora-virt/2009-November/msg00061.html</ref>
compared to Fedora 12.
surprised to find that <code>ksm</code> was not running even though it was
enabled with chkconfig. After starting more guests, <code>ksm</code> was found to be
running.  


[[DanKenigsberg|Dan Kenigsberg]]
[[DanielBerrange|Daniel Berrange]]  
added the follwing explaination to the KSM feature page<ref>http://fedoraproject.org/wiki/Features/KSM</ref>
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
"Fedora's kvm comes with 2 services controlling the behavior of <code>ksm</code>. One,
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
simply called <code>ksm</code>, is just a nice means to start and stop ksm's kernel thread.
Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was
The other, called <code>ksmtuned</code>, controls the first service and tunes its
rebased to be near parity with [[Releases/11|Fedora 11]], and KVM in RHEL-5.4 is
parameters according to the memory stress that is generated by KVM virtual
also pretty close to that using what's best described as a hybrid of
machines. <code>ksmtuned</code> may stop <code>ksm</code> service alltogether, if memory is not in need.
kvm-83 and kvm-84."
Later, if <code>ksmtuned</code> senses that memory stress has risen, it will fire up <code>ksm</code> again."


Soon after the explaination, Dan posted a patch<ref>http://www.redhat.com/archives/fedora-virt/2009-November/msg00068.html</ref>
<references />
which will cause <code>ksmtuned</code> to log any <code>ksm</code> state changes. This patch will soon be available in an update.


KSM was also recently covered in FWN 200<ref>http://fedoraproject.org/wiki/FWN/Issue200#KSM_Tuning_in_Fedora_12</ref>.
====  ====
<references />


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


==== New Release virt-manager 0.8.1 ====
====  ====
[[ColeRobinson|Cole Robinson]]
announced<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00003.html</ref> new releases of {{package|virt-manager}} 0.8.1 and {{package|python-virtinst|virtinst}} 0.500.1.
 
Virtual Machine Manager<ref>http://www.virt-manager.org/</ref> provides a graphical tool for administering virtual machines, using {{package|libvirt}} as the backend management API.
 
<code>Virtinst</code> is a python module that helps build and install <code>libvirt</code> based virtual
machines. Currently supports KVM, QEmu and Xen virtual machines. Package
includes several command line utilities, including {{command|virt-install}} (build
and install new VMs) and {{command|virt-clone}} (clone an existing virtual machine).
 
'''New virt-manager Features:'''
* VM Migration wizard, exposing various migration options
* Enumerate CDROM and bridge devices on remote connections
* Can once again list multiple graphs in the manager window (Jon Nordby)
* Support disabling dhcp (Michal Novotny), and specifying 'routed' type for new virtual networks
* Support storage pool source enumeration for LVM, NFS, and SCSI
* Allow changing VM ACPI, APIC, clock offset, individual vcpu pinning, and video model (vga, cirrus, etc.)
* Many improvements and bugfixes
 
'''New virtinst Features:'''
* virt-install now attempts --os-variant detection by default. This can be disabled with '--os-variant none' (distro detection currently only works for URL installs)
* New --disk option 'format', for creating image disks formats such as qcow2 or vmdk
* Many improvements and bugfixes
 
"Thanks to everyone who has contributed to this release through testing,
bug reporting, submitting patches, and otherwise sending in feedback!"
 
Also see coverage of the release on linux-kvm.com<ref>http://www.linux-kvm.com/content/virt-manager-081-released</ref>.
Version 0.8.0 of <code>virt-manager</code> was announced<ref>http://fedoraproject.org/wiki/FWN/Issue187#New_Release_virt-manager_0.8.0</ref> on July 28th, 2009.
 
<references />
<references />

Revision as of 17:45, 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.

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