From Fedora Project Wiki

< FWN‎ | Beats

m (→‎Secure Guest Migration Between Hosts: s/concensus/consensus/)
(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]
  
==== Managing Guest OS Types ====
+
==== ====
Cole Robinson created<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00023.html</ref> a patch to provide a <code>--list-os-options</code> option to <code>virt-install</code> and <code>virt-convert</code>. Output from this option would be used to help users determine the appropriate argument for <code>--os-type</code>.
 
The <code>--os-type</code> option is used to
 
"Optimize the guest configuration for a type of operating system. This will
 
attempt to pick the most suitable ACPI & APIC settings, optimally supported
 
mouse drivers and generally accommodate other operating system quirks."
 
 
 
This touched off a discussion<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00028.html</ref> of how such information is managed.
 
Daniel P. Berrange pointed out shortcomings in the current approach and
 
perscribed the following fixes, and supplied an example XML file.
 
 
 
* An XML schema for defining all the information wrt to guest OS distros that is relevant to virt management tools.
 
* A C library for querying the information in the XML file(s).
 
* Bindings of the C library into Python/Ruby etc as needed
 
* Ability for local admins to extend / override the information either by editing the XML files directly, or a pretty GUI
 
 
 
Cole later dropped<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00034.html</ref> his patch and automated<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00033.html</ref> the creation of the OS list in the <code>virt-install</code> man page instead.
 
 
 
<references />
 
 
 
==== virt-manager Storage Removal ====
 
A patch<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00042.html</ref> from Cole Robinson "adds a storage aware delete dialog to virt-manager.
 
When deleting a VM, we are presented with a list of storage attached to
 
it, with an option to remove individual disks as part of the delete process."
 
 
 
<references />
 
 
 
==== virt-install Host Device Assignment Support ====
 
Cole Robinson added<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00003.html</ref> "support for host device assignment to <code>virtinst</code> and <code>virt-install</code>.
 
This adds a <code>--host-device</code><ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00006.html</ref> command to
 
"Attach a physical host device to the guest. HOSTDEV is a node device name
 
as used by libvirt (as shown by 'virsh nodedev-list')."
 
 
 
Daniel P. Berrange described<ref>http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00007.html</ref> the management options for host devices.
 
* "If 'managed=yes' then libvirt will automatically detach the device from the host driver."
 
* "If 'managed=no' then libvirt expects that the caller has already ensured the device is detached from the host before *ALL* attempts to start the guest, now & in the future."
 
 
 
This change supports the KVM PCI Device Assignment feature<ref>http://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment</ref> in Fedora 11.
 
 
 
 
<references />
 
<references />
  
Line 57: Line 19:
 
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
 
[http://www.redhat.com/mailman/listinfo/fedora-virt fedora-virt list].
  
==== User Interface Makeover for virt-manager ====
+
==== ====
Daniel P. Berrange pointed<ref>http://www.redhat.com/archives/fedora-virt/2009-March/msg00001.html</ref> out
 
"there's a significant redesign of {{package|virt-manager}} in progress" and brought
 
attention to Cole Robinson's 'New VM' wizard makeover<ref>http://blog.wikichoon.com/2009/02/virt-manager-in-fedora-11-new-vm-wizard.html</ref>.
 
Daniel added
 
"Many more design improvements are targetted for the next few virt-manager
 
releases, impacting nearly every area of the UI, so keep an eye out for
 
more UI review postings during F12 timeframe too."
 
 
 
<references />
 
 
 
==== New Release virtinst 0.4.2 ====
 
[[ColeRobinson|Cole Robinson]] announced<ref>http://www.redhat.com/archives/fedora-virt/2009-March/msg00002.html</ref> a new <code>virtinst</code> release, version 0.400.2.
 
 
 
{{package|python-virtinst}} 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 <code>virt-clone</code> option <code>--original-xml</code>, allows cloning a guest from an xml file, rather than require an existing, defined guest.
 
* New <code>virt-install</code> option <code>--import</code>, allows creating a guest from an existing disk image, bypassing any OS install phase.
 
* New <code>virt-install</code> option <code>--host-device</code>, for connecting a physical host device to the guest.
 
* Allow specifying 'cache' value via <code>virt-install</code>'s <code>--disk</code> options (Ben Kochie)
 
* New <code>virt-install</code> option <code>--nonetworks</code> (John Levon)
 
* Lots of backend cleanups and documentation improvements.
 
 
 
 
<references />
 
<references />
  
Line 90: 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 Inches Closer ====
+
==== ====
Pasi Kärkkäinen walked<ref>http://www.redhat.com/archives/fedora-xen/2009-March/msg00017.html</ref> the bleeding edge while testing Xen dom0 host support. Using Fedora 10 with Xen 3.3.1-9 from [[Releases/Rawhide|Rawhide]] and a custom built 2.6.29-rc7 pv_ops dom0 kernel the system boots, but <code>virt-install</code> and <code>virt-manager</code> fail with the error "<code>Unsupported virtualization type 'xen'</code>".
 
 
 
It seems<ref>http://www.redhat.com/archives/fedora-xen/2009-March/msg00023.html</ref> that <code>/sys/hypervisor/properties/capabilities</code> is not present for some unknown reason.
 
 
 
 
<references />
 
<references />
  
Line 101: Line 33:
 
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
 
[http://www.redhat.com/mailman/listinfo/libvir-list libvir-list].
  
==== New Release libvirt 0.6.1 ====
+
==== ====
[[DanielVeillard|Daniel Veillard]] announced<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00144.html</ref> a new {{package|libvirt}} release, version 0.6.1.
 
 
 
<code>Libvirt</code> is a <code>C</code> toolkit to interact with the virtualization capabilities of recent versions of Linux (and other OSes).
 
 
 
'''New features:'''
 
* new APIs for Node device detach reattach and reset (Mark McLoughlin)
 
* <code>sVirt</code><ref>http://fedoraproject.org/wiki/Features/SVirt_Mandatory_Access_Control</ref> mandatory access control support (James Morris and Dan Walsh)
 
 
 
'''Improvements:'''
 
* don't hardcode ssh port (Guido Gunther)
 
* new test cases and testing infrastructure (Jim Meyering)
 
* improve the SExpr parser (John Levon)
 
* proper error reporting on <code>xend</code> shutdown command (John Levon)
 
* proper handling of errors when saving <code>QEmu</code> domains state (Guido Gunther)
 
* revamp of the internal error memory APIs (John Levon)
 
* better <code>virsh</code> error reporting (John Levon)
 
* more daemon options to allow running multiple daemons (Jim Meyering)
 
* error handling when creating a <code>QEmu</code> domain (Guido Gunther)
 
* fix timeouts in <code>QEmu</code> log reading (Guido Gunther)
 
* migration with <code>xend</code> 3.3 fixes (John Levon)
 
* <code>virsh</code> XML dump flags cleanup (Cole Robinson)
 
* fix build with loadable drivers (Maximilian Wilhelm)
 
* internal XML APIs to read long long and hexa values (Mark McLoughlin)
 
* function to parse node device XML descriptions and associated test (Mark McLoughlin)
 
* generate network bridge names if not provided (Cole Robinson)
 
* recognize ejectable media in hostdev hal driver (Cole Robinson)
 
* integration of <code>sVirt</code> (Daniel Berrange)
 
 
 
There were also dozens of cleanups, documentation enhancements, portability and bug fixes.
 
 
 
With about five weeks since the release of 0.6.0<ref>http://fedoraproject.org/wiki/FWN/Issue161#New_Release_libvirt_0.6.0</ref>, Daniel added
 
"So quite a bit of changes happened in one month of development,
 
so it's getting clear we aren't really slowing down and keeping a
 
relatively fast release cycle is needed. So expect 0.6.2 in a month
 
or so."
 
 
 
<references />
 
 
 
==== sVirt Support Committed ====
 
Daniel P. Berrange applied<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00092.html</ref> the <code>sVirt</code><ref>http://fedoraproject.org/wiki/Features/SVirt_Mandatory_Access_Control</ref> patches to enable <code>selinux</code> support in <code>libvirt</code>.
 
 
 
<references />
 
 
 
==== Secure Guest Migration Between Hosts ====
 
Chris Lalancette posted<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00094.html</ref> a request for comments on secure migration with an initial focus on <code>Qemu</code>. The proposal included two options. One leveraged existing RPC while the second created a new well known port to handle the migration. Using RPC adds a layer of authenitcation which may possibly be avoided in the second option by simply opening a new port in a firewall.
 
 
 
Sticking with existing RPC and enhancing<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00148.html</ref> the authentication system for migration seemed to be the consensus.
 
 
 
<references />
 
 
 
==== Hynesim Project Interest in Libvirt ====
 
Florian Vichot of the Hynesim<ref>http://www.hynesim.org</ref> project was
 
interested<ref>http://www.redhat.com/archives/libvir-list/2009-March/msg00115.html</ref> in replacing their wrappers around <code>KVM</code>, VirtualBox, and OpenVZ with <code>libvirt</code>, and so asked about support for a number of features including auxiliary TAP devices in the host to correspond with ethernet devices in the guest.
 
 
 
 
<references />
 
<references />

Revision as of 16:06, 14 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.