From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juan Quintela Subject: Re: KVM call agenda for Mar 16 Date: Tue, 16 Mar 2010 10:18:03 +0100 Message-ID: References: <20100316070155.GK3732@x200.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org To: Chris Wright Return-path: Received: from mx1.redhat.com ([209.132.183.28]:43765 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932553Ab0CPJSH (ORCPT ); Tue, 16 Mar 2010 05:18:07 -0400 In-Reply-To: <20100316070155.GK3732@x200.localdomain> (Chris Wright's message of "Tue, 16 Mar 2010 00:01:55 -0700") Sender: kvm-owner@vger.kernel.org List-ID: Chris Wright wrote: > Please send in any agenda items you are interested in covering. Migration: - flexible migration: I hope to sent an RFC patch on time for the call. idea is to use subsections. - callbacks. block migration introduced several callbacks: * cancel() * get_status() * release() in spice we need now another to callbacks: on_start() and on_end(). * on_start(): tells spice that migration has started (it will then manage certificates, passwords, ... itself) * on_end(): it is called when migration ends. spice use it to transparently connect to the new host and user don't have to "reconnect" - what to do on migration error: - target side: libvirt folks want the program to print a message if it fails. Current code spent 100% cpu time doing select on a closed fd. (patches already on the list to make it wait without using cpu). - source side: current behaviour if migration fails is to stop the vm. We have requests to make it continue (remember that this is live migration). what to do? adding a paramenter like the block layer: migration_error=[stop|continue] any better ideas. - block migration: it added the set_params() callback, investigating why. I think that it can be done with inside block_save_live(), but I haven't investigated it fully yet. Later, Juan. > thanks, > -chris