From Fedora Project Wiki

< FWN‎ | Beats

(reset)
Line 12: Line 12:
 
[http://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
 
[http://www.redhat.com/mailman/listinfo/et-mgmt-tools et-mgmt-tools list]
  
==== New Release virt-manager 0.7.0 ====
+
==== ====
[[ColeRobinson|Cole Robinson]] announce<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00058.html</ref>
 
a new {{package|virt-manager}}<ref>http://virt-manager.org/</ref> release, version 0.7.0.
 
 
 
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.
 
 
 
'''New features:'''
 
* Redesigned 'New Virtual Machine' wizard (Jeremy Perry, Tim Allen, Cole Robinson)
 
* Option to remove storage when deleting a virtual machine.
 
* File browser<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00045.html</ref> for libvirt storage pools and volumes, for use when attaching storage to a new or existing guest.
 
* Physical device assignment (PCI, USB) for existing virtual machines.
 
* Bug fixes and minor improvements.
 
 
 
 
<references />
 
<references />
  
==== New Release virtinst 0.4.3 ====
+
=== Fedora Virtualization List ===
[[ColeRobinson|Cole Robinson]] announce<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00057.html</ref>
+
This section contains the discussion happening on the
a new {{package|python-virtinst}} release, version 0.400.3.
+
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
 
 
<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).
 
 
 
This is largely a bug fix release.
 
  
 +
====  ====
 
<references />
 
<references />
  
Line 48: Line 26:
 
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
 
[http://www.redhat.com/mailman/listinfo/fedora-xen fedora-xen list].
  
==== dom0 Kernel: Better, Still Not Ready ====
+
==== ====
Itamar Reis Peixoto reported<ref>http://www.redhat.com/archives/fedora-xen/2009-March/msg00046.html</ref>
 
success with [[MichaelYoung|Michael Young]]'s latest {{package|kernel}} build<ref>http://koji.fedoraproject.org/koji/taskinfo?taskID=1238587</ref> and wondered when it could be released.
 
 
 
Michael explained, "The current plan is to wait until basic <code>dom0</code> support makes it into the vanilla <code>kernel</code>, which should happen for 2.6.30, and then decide if <code>dom0</code> can be enabled and if the patches for full <code>dom0</code> support can safely be added without affecting ordinary operation."
 
 
 
"At the moment there are still things that are broken such as <code>X</code> support in some cases, and there are also Fedora patches that have been omitted because they were tricky to merge, so it is too early to start adding <code>dom0</code> support to official Fedora kernels."
 
 
 
<references />
 
 
 
==== Missing Hypervisor Capabilities Restored ====
 
There was progress on a bug discovered<ref>http://fedoraproject.org/wiki/FWN/Issue166#dom0_Kernel_Inches_Closer</ref> last week. This missing file
 
<code>/sys/hypervisor/properties/capabilities</code> has been
 
restored<ref>http://www.redhat.com/archives/fedora-xen/2009-March/msg00039.html</ref>,
 
however a bug<ref>https://bugzilla.redhat.com/show_bug.cgi?id=489799</ref> remained<ref>http://www.redhat.com/archives/fedora-xen/2009-March/msg00040.html</ref> in <code>libvirt</code> or <code>virt-install</code>.
 
 
 
 
<references />
 
<references />
  
Line 70: Line 33:
 
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
 
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
  
==== Snapshot Support Discussed ====
+
====  ====
In an attempt to make it easier to backup <code>KVM</code> windows guests,
 
[[MattMcCowan| Matt McCowan]]
 
created<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00177.html</ref>
 
a checkpoint <code>virsh</code> function. "Modelled on the <code>virDomainSave</code><ref>http://libvirt.org/html/libvirt-libvirt.html#virDomainSave</ref> function it takes
 
an optional script which it will execute (and pass the name of the
 
domain as an argument) while the domain is paused, then resume the
 
domain." Within this script, a backup of the guest domain could be created.
 
 
 
The patch was seen as too ad-hoc, and not accepted as-is.
 
[[DanielVeillard|Daniel Veillard]]
 
commented<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00199.html</ref>
 
"I think this can help administrators in a controlled situation,
 
but I'm hoping a real snapshotting API will be possible at some point
 
where {{package|libvirt}} goes though the list of storage resources used by the
 
domain and properly make a snapshot using a storage API or return
 
an error if that's not possible."
 
 
 
[[DanielBerrange|Daniel P. Berrange]]
 
described<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00205.html</ref>
 
what he would like to see.
 
"In terms of API I think I'd like to see
 
snapshotting<ref>http://wiki.libvirt.org/page/TodoVMSnapshots</ref> available as part
 
of a more generic save/restore API.  I tend to think of the current API
 
as providing 'unmanaged save/restore'". Libvirt does not track saved images,
 
so does not know if a snapshot is available to be started at the restart of
 
<code>libvirtd</code>."
 
 
 
"Thus I think the first step towards a general snapshot facility would
 
be to provide an API for 'managed save/restore' where we explicitly
 
track saved images."
 
"With this, you could configure <code>libvirtd</code>, so that when starting up, it"
 
would "see if the guest was suspended before
 
the previous host shutdown, and if so, then restore from that saved
 
image automatically.<ref>http://wiki.libvirt.org/page/TodoDaemonRestart</ref> Or make it skip autostart completely, if any save
 
images exist, and allow an admin defined initscript to do auto restore
 
from the save image."
 
 
 
<references />
 
 
 
==== Memory Ballooning Support for QEMU ====
 
[[DanielBerrange|Daniel Berrange]]
 
patched<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00200.html</ref>
 
the <code>libvirt</code> QEMU driver to fully support memory ballooning.
 
"Memory ballooning allows you to have your guest dynamically change it’s memory usage by evicting unused memory during runtime. This is a useful feature because it reduces the impact your guest can have on memory usage of your host by giving up unused memory back to the host."<ref>http://www.linux-kvm.com/content/memory-ballooning-feature-coming-soon-kvm</ref>
 
 
 
 
<references />
 
<references />

Revision as of 00:53, 22 March 2009


Virtualization

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

Contributing Writer: Dale Bewley

Enterprise Management Tools List

This section contains the discussion happening on the et-mgmt-tools list


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.


Libvirt List

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