From Fedora Project Wiki

< FWN‎ | Beats

(→‎Libvirt List: didn't have time this week)
(reset)
Line 2: Line 2:
  
 
{{Anchor|Virtualization}}
 
{{Anchor|Virtualization}}
 +
  
 
== Virtualization ==
 
== Virtualization ==
Line 14: Line 15:
 
[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 ====
+
==== ====
[[RichardJones|Richard Jones]]
 
announced
 
<ref>http://www.redhat.com/archives/libguestfs/2009-July/msg00059.html</ref>
 
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 ====
+
=== Fedora Xen List ===
[[RichMahn|Rich Mahn]]
+
This section contains the discussion happening on the
asked<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00173.html</ref>
+
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
"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]]
 
added<ref>http://www.redhat.com/archives/fedora-virt/2009-July/msg00182.html</ref>
 
"Guest swapping is a reasonable scenario that should be allowed and
 
supported." On the question of oversubscribing host memory to guests, Dor said
 
"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."
 
 
 
<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 />
  
Line 83: Line 29:
 
[http://www.redhat.com/mailman/listinfo/virt-tools-list virt-tools-list list].
 
[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 />
 
<references />
  
==== Virt Manager UI Rework ====
+
=== Libguestfs List ===
[[ColeRobinson|Cole Robinson]]
+
This section contains the discussion happening on the
has "been reworking the main manager view in <code>virt-manager</code>"
+
[http://www.redhat.com/mailman/listinfo/libguestfs libguestfs list].
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 />
  
<references />
+
=== Libvirt List ===
 +
This section contains the discussion happening on the
 +
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
  
==== 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 />
 
<references />
  
==== Virt What? ====
+
=== oVirt Devel List ===
Another week, another release<ref>http://www.redhat.com/archives/virt-tools-list/2009-July/msg00034.html</ref> from [[RichardJones|Richard Jones]].  
+
This section contains the discussion happening on the
 
+
[http://www.redhat.com/mailman/listinfo/ovirt-devel ovirt-devel list].
<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 />
 
<references />

Revision as of 23:16, 2 August 2009



Virtualization

In this section, we cover discussion of Fedora virtualization technologies on the @fedora-virt, @fedora-xen-list, @libguestfs, @libvirt-list, @virt-tools-list, and @ovirt-devel-list lists.

Contributing Writer: Dale Bewley

Fedora Virtualization List

This section contains the discussion happening on the fedora-virt list.


Fedora Xen List

This section contains the discussion happening on the fedora-xen list.


Virtualization Tools List

This section contains the discussion happening on the virt-tools-list list.


Libguestfs List

This section contains the discussion happening on the libguestfs list.


Libvirt List

This section contains the discussion happening on the libvir-list.


oVirt Devel List

This section contains the discussion happening on the ovirt-devel list.