From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=33824 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PcHuN-0003nb-Ie
	for qemu-devel@nongnu.org; Mon, 10 Jan 2011 08:35:41 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <quintela@redhat.com>) id 1PcHsU-0003JC-0k
	for qemu-devel@nongnu.org; Mon, 10 Jan 2011 08:33:42 -0500
Received: from mx1.redhat.com ([209.132.183.28]:19587)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <quintela@redhat.com>) id 1PcHsT-0003Iy-PL
	for qemu-devel@nongnu.org; Mon, 10 Jan 2011 08:33:41 -0500
From: Juan Quintela <quintela@redhat.com>
In-Reply-To: <m3ipxxezqd.fsf@trasno.org> (Juan Quintela's message of "Mon, 10
	Jan 2011 12:59:22 +0100")
References: <m3pqs5gj17.fsf@trasno.org> <m3ipxxezqd.fsf@trasno.org>
Date: Mon, 10 Jan 2011 14:32:40 +0100
Message-ID: <m3lj2sevev.fsf@trasno.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Qemu-devel] Re: KVM call agenda for Jan 11
Reply-To: quintela@redhat.com
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Chris Wright <chrisw@redhat.com>, kvm-devel <kvm@vger.kernel.org>

Juan Quintela <quintela@redhat.com> wrote:
> Juan Quintela <quintela@redhat.com> wrote:
>
> Now sent it to the right kvm list.  Sorry for the second sent.
>
>> Please send any agenda items you are interested in covering.
>>
>> - KVM Forum 2011 (Jes).
>>
>> thanks, Juan.

- migration and block devices: a mess.
  * patches I sent last week: only work for root (for some definition of
    work)
  * qemu is used as non-root user.
  * forcing to have cache=none solves the issue
  * we use migrate not only for live migration, but also for
    save/resume.

At this point only 4 ideas remaining:

* -incoming-this-is-a-live-migration
  (or the opposite -incoming-this-is-a-restore-operation)
* just forche cache=none if you want to call migration code.
* let management app to do the right thing (it can check for cache=none)
* do nothing and pray?

Later, Juan.