From Fedora Project Wiki

< FWN‎ | Beats

 
(81 intermediate revisions by 2 users not shown)
Line 2: Line 2:


{{Anchor|Virtualization}}
{{Anchor|Virtualization}}


== 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 14: Line 14:
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].


==== New Release libguestfs 1.0.64 ====
==== Virt Status Report ====
[[RichardJones|Richard Jones]]
[[JustinForbes|Justin Forbes]]
announced
posted<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00056.html</ref> a Fedora virtualization status report.  
<ref>http://www.redhat.com/archives/libguestfs/2009-July/msg00059.html</ref>
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.
the release of {{package|libguestfs}} 1.0.64.
 
'''New Features:'''
* New tool: virt-cat.  This tool lets you copy out files from a guest.<ref>http://libguestfs.org/virt-cat.1.html#examples</ref>
* Added libguestfs-test-tool which is a tool you can use to diagnose qemu / kernel booting problems, and also make bug reports more useful.
* [Sys::Guestfs::Lib] split $os->{version} into $os->{major_version} and $os->{minor_version}.  Add feature tags. (Matt Booth).
* Allow TMPDIR to be used to override the location of temporary files.
* Implement the guestfs_read_file call.
* New calls guestfs_mkmountpoint and guestfs_rmmountpoint to allow some specialized read-only or nested filesystems to be mounted, particularly for examining live CDs.<ref>http://rwmj.wordpress.com/2009/07/15/unpack-the-russian-doll-of-a-f11-live-cd/</ref>
* New call guestfs_mountpoints to return a hash of device -> mountpoint.
* Many documentation fixes, including an "API Overview"<ref>http://libguestfs.org/guestfs.3.html#api_overview</ref> section which will help developers navigate parts of the now very large libguestfs API.
* Add ~ and ~username expansion in guestfish ({{bz|511372}}).
* Add kernel modules for reading DOS filesystems (Guido Gunther).
* Add i18n support for Perl strings.


<references />
<references />


==== Swap Use in Guests ====
==== RHEL and Fedora Virtualization Feature Parity ====
[[RichMahn|Rich Mahn]]
Robert Day wondered how the virtualization features<ref>http://www.redhat.com/virtualization/rhev/</ref> of Red Hat Enterprise Linux 5.4
asked<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00173.html</ref>
compared to Fedora 12.
"How big should the swap parititons be on virtual machines
under qemu, qemu/kvm?" "It seems to me that if the VM actually needs swap space, it would be more efficient to allocate more virual[sic] memory to it."
 
[[RichardJones|Richard Jones]]
found<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00178.html</ref> this to be an interesting question, but argued
"One place I think you're wrong is the assumption that adding more
memory to a VM is better than having the VM use a swap disk.  The
reason would be that the VM's memory manager will assume that the
[from its point of view] physical memory will be much faster than
swap, and so will arrange memory vs swap use accordingly. But this
assumption isn't true, this so-called physical memory is really just
as slow as swap!" Richared pointed out Kernel Shared Memory<ref>http://lwn.net/Articles/306704/</ref> further complicates things.


[[DorLaor|Dor Laor]]
[[DanielBerrange|Daniel Berrange]]  
added<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00182.html</ref>
explained<ref>http://www.redhat.com/archives/fedora-virt/2009-December/msg00040.html</ref>
"Guest swapping is a reasonable scenario that should be allowed and
"The KVM based virtualization in RHEL-5.4 is not nearly so far behind
supported." On the question of oversubscribing host memory to guests, Dor said
Fedora as you might think. The {{package|libvirt}} mgmt stack in RHEL-5.4 was
"You can overcommit VM memory and it might be good if you have many VMs that have low memory foot print. If it is not the case, you better not do it."
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."


<references />
<references />


==== Clustering libvirt Hosts ====
[[GianlucaCecchi|Gianluca Cecchi]]
asked<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00161.html</ref> "is there any pointer about how to set up a cluster of Qemu/KVM hosts?"
"What are the uuid tags into the xml for? Do they have to be identical
for clusters or do they have to be absolutely different for a sort of
"identification" of host (as the term seems to suggest)?"
[[RichardJones|Richard Jones]]
pointed out oVirt<ref>http://ovirt.org/</ref> "which is an
open source management tool designed precisely for looking after
networks of virt hosts.  It is based on libvirt, and they have looked
at and solved many of the issues you raise."
[[GuidoGünther|Guido Günther]] answered<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00177.html</ref>
"In principle they don't have to be the same across hosts since you can
identify the network by name and the volumes by their path but I prefer
to keep them in sync (using shared nfs in my case)."


====  ====
<references />
<references />
=== Virtualization Tools List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/virt-tools-list virt-tools-list list].
==== Virtual Machine Cloning ====
[[ColeRobinson|Cole Robinson]]
with some UI designs from
[[JeremyPerry|Jeremy Perry]]
patched<ref>http://www.redhat.com/archives/virt-tools-list/2009-July/msg00017.html</ref> {{package|virt-manager}} to include a virtual machine cloning wizard.
<references />
==== Virt Manager UI Rework ====
[[ColeRobinson|Cole Robinson]]
has "been reworking the main manager view in <code>virt-manager</code>"
and asked<ref>http://www.redhat.com/archives/virt-tools-list/2009-July/msg00035.html</ref>
for comments.
In another UI tweak, Cole created<ref>http://www.redhat.com/archives/virt-tools-list/2009-July/msg00042.html</ref> a system tray icon that "can be used to quit the app, or start, stop, pause, or open a VM."
<references />
==== Support for Processor Affinity ====
[[MichalNovotny|Michal Novotny]]
submitted<ref>http://www.redhat.com/archives/virt-tools-list/2009-July/msg00031.html</ref> a patch to <code>virt-manager</code> which enables pinning a guest to a select physical CPU.
<references />
==== Virt What? ====
Another week, another release<ref>http://www.redhat.com/archives/virt-tools-list/2009-July/msg00034.html</ref> from [[RichardJones|Richard Jones]].
<code>virt-what</code><ref>http://et.redhat.com/~rjones/virt-what/</ref> "is a collection of code
snippets to allow you to determine what sort of virtualization you are
running inside."
"The new version can tell the difference between QEMU and KVM, and can
tell if you are running inside a Xen fullvirt guest."
<references />
=== Libvirt List ===
This section contains the discussion happening on the
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-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."