From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=43058 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PepWV-0001O3-OH
	for qemu-devel@nongnu.org; Mon, 17 Jan 2011 08:53:33 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1PepWR-0007K7-Pj
	for qemu-devel@nongnu.org; Mon, 17 Jan 2011 08:53:28 -0500
Received: from mx1.redhat.com ([209.132.183.28]:34003)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1PepWR-0007JQ-Fg
	for qemu-devel@nongnu.org; Mon, 17 Jan 2011 08:53:27 -0500
Message-ID: <4D3449C5.1030006@redhat.com>
Date: Mon, 17 Jan 2011 14:53:09 +0100
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [RFC][PATCH v6 00/23] virtagent: host/guest RPC
	communication agent
References: <1295270117-24760-1-git-send-email-mdroth@linux.vnet.ibm.com>
In-Reply-To: <1295270117-24760-1-git-send-email-mdroth@linux.vnet.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: agl@linux.vnet.ibm.com, stefanha@linux.vnet.ibm.com, markus_mueller@de.ibm.com, marcel.mittelstaedt@de.ibm.com, qemu-devel@nongnu.org, abeekhof@redhat.com, aliguori@linux.vnet.ibm.com, ryanh@us.ibm.com, Jes.Sorensen@redhat.com

   Hi,

> OVERVIEW:
>
> There are a wide range of use cases motivating the need for a guest
> agent of some sort to extend the functionality/usability/control
> offered by QEMU. Some examples include graceful guest shutdown/reboot
> and notifications thereof, copy/paste syncing between host/guest,
> guest statistics gathering, file access, etc.

What is your plan to handle system-level queries+actions (such as 
reboot) vs. per-user stuff (such as cut+paste)?

cheers,
   Gerd