From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] KVM call minutes for Oct 19 Date: Wed, 20 Oct 2010 08:02:07 -0500 Message-ID: <4CBEE84F.7060207@codemonkey.ws> References: <20101019151441.GA24673@x200.localdomain> <4DE00079-05FA-40DF-9EA5-9573AD745117@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Chris Wright , kvm@vger.kernel.org, qemu-devel@nongnu.org To: Alexander Graf Return-path: Received: from mail-qw0-f46.google.com ([209.85.216.46]:56130 "EHLO mail-qw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750875Ab0JTNCK (ORCPT ); Wed, 20 Oct 2010 09:02:10 -0400 Received: by qwa26 with SMTP id 26so2304092qwa.19 for ; Wed, 20 Oct 2010 06:02:09 -0700 (PDT) In-Reply-To: <4DE00079-05FA-40DF-9EA5-9573AD745117@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: On 10/20/2010 03:21 AM, Alexander Graf wrote: >> Live snapshots >> - merge snapshot? >> - already supported, question about mgmt of snapshot chain >> - integrate with fsfreeze (and windows alternative) >> >> Guest Agent >> - have one coming RSN (poke Anthony for details) >> > Would there be a chance to have a single agent for everyone, so that we actually form a Qemu agent instead of a dozen individual ones? I'm mainly thinking Spice here. > Our main design points are to keep the code simple with few dependencies and to provide interfaces that have the maximum amount of flexibility. Having a single agent (not an agent framework) is important if we want these interfaces to be ubiquitous. This really means that the guest agent should be part of the QEMU source tree IMHO so that there is always a standard version of the agent. Regards, Anthony Liguori > Alex > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >