From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM call minutes for June 8
Date: Thu, 10 Jun 2010 11:43:11 +0200
Message-ID: <4C10B3AF.5000201@redhat.com>
References: <20100608150500.GA28492@x200.localdomain>	<4C0E694F.8040607@codemonkey.ws>	<20100608175952.5f43ea8f@redhat.com> <4C0EB281.80907@codemonkey.ws>	<20100609121820.1f3bb47a@redhat.com>	<20100609153107.GE28326@redhat.com> <4C0FBFDF.5050009@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
	Chris Wright <chrisw@redhat.com>,
	kvm-devel <kvm@vger.kernel.org>, armbru@redhat.com,
	qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:8090 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1758693Ab0FJJnb (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 10 Jun 2010 05:43:31 -0400
In-Reply-To: <4C0FBFDF.5050009@codemonkey.ws>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Am 09.06.2010 18:22, schrieb Anthony Liguori:
> On 06/09/2010 10:31 AM, Daniel P. Berrange wrote:
>>>   However, libvirt was counting on this feature and on the snapshot commands
>>> to switch from the text Monitor. We have two options:
>>>
>>>   1. Ask them to wait one more release (not so good for us)
>>>   2. Try to find a way to have those features in for 0.13
>>>
>>>   Daniel has commented to me that making the snapshot commands synchronous
>>> for 0.13 wouldn't be that bad, what do you think?
>>>      
>> The thought is that changing a command from synchronous to asynchronous is
>> not an ABI incompatible change. An existing app simply won't know to take
>> advantage of the new possibilities that async commands offer.
>>    
> 
> It's not QMP that's the major issue with savevm.  The major issue is 
> actually the way snapshots are saved in qcow2.  You need to know the 
> size of the snapshot prior to creating the snapshot

Huh, why this? Seems I still haven't understood all of qcow2 then... I
always thought that there's just a specific offset where VM state
starts, but no explicit end.

Kevin