From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=46040 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1P9Ldt-0006wV-Vs
	for qemu-devel@nongnu.org; Fri, 22 Oct 2010 13:43:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <chrisw@redhat.com>) id 1P9LQh-0002em-IW
	for qemu-devel@nongnu.org; Fri, 22 Oct 2010 13:29:24 -0400
Received: from mx1.redhat.com ([209.132.183.28]:20597)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chrisw@redhat.com>) id 1P9LQh-0002dT-Bj
	for qemu-devel@nongnu.org; Fri, 22 Oct 2010 13:29:23 -0400
Date: Fri, 22 Oct 2010 10:29:16 -0700
From: Chris Wright <chrisw@redhat.com>
Subject: Re: [Qemu-devel] KVM call minutes for Oct 19
Message-ID: <20101022172916.GF27794@x200.localdomain>
References: <20101019151441.GA24673@x200.localdomain>
	<4DE00079-05FA-40DF-9EA5-9573AD745117@suse.de>
	<4CBEE84F.7060207@codemonkey.ws>
	<20101020131925.GH15143@redhat.com>
	<4CBEECE6.8030605@codemonkey.ws> <4CBF7154.2070304@redhat.com>
	<9DABD2D4-389E-4D05-8A4C-2DE1E20D3B5C@suse.de>
	<4CBFEF95.9060703@redhat.com> <4CC039DA.5090607@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4CC039DA.5090607@codemonkey.ws>
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: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@redhat.com>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>, "dlaor@redhat.com" <dlaor@redhat.com>, Alexander Graf <agraf@suse.de>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Paolo Bonzini <pbonzini@redhat.com>

* Anthony Liguori (anthony@codemonkey.ws) wrote:
> The first step is just identifying what interfaces we need in a
> guest agent.  So far, I think we can get away with a very small
> number of interfaces (mainly read/write files, execute command).

Could you elaborate here?  I can't imagine you mean:

vm_system(target_vm, "shutdown -r now")

But from other post, it does seem you want complexity in the host side
not guest side of agent.

Seems vm_reboot(target_vm) as the RPC makes more sense with the guest
side implementing that in whatever guest-specific appropriate way.

thanks,
-chris