From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N12Se-0005y3-SB for qemu-devel@nongnu.org; Thu, 22 Oct 2009 14:32:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N12Sa-0005rZ-Or for qemu-devel@nongnu.org; Thu, 22 Oct 2009 14:32:32 -0400 Received: from [199.232.76.173] (port=44169 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N12Sa-0005r9-Eg for qemu-devel@nongnu.org; Thu, 22 Oct 2009 14:32:28 -0400 Received: from mail-ew0-f221.google.com ([209.85.219.221]:60878) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N12Sa-0003zI-BW for qemu-devel@nongnu.org; Thu, 22 Oct 2009 14:32:28 -0400 Received: by ewy21 with SMTP id 21so6783674ewy.8 for ; Thu, 22 Oct 2009 11:32:27 -0700 (PDT) Message-ID: <4AE0A535.3000607@codemonkey.ws> Date: Thu, 22 Oct 2009 13:32:21 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] new SDL keyboard shortcuts to start and stop VM References: <4ADCE635.4060604@codemonkey.ws> <4ADD9388.8040206@redhat.com> <20091020170800.GG32538@redhat.com> <4ADEB7EF.3060800@redhat.com> <5d6222a80910210652q3b005ca6ub950a2014bfbaa41@mail.gmail.com> <5d6222a80910210924j62505b7dtf298754ce65f1c99@mail.gmail.com> <20091021183503.GA27677@shareable.org> <20091022124036.5df991f3@doriath> <4AE07D06.4080205@codemonkey.ws> <20091022143833.51c48260@doriath> In-Reply-To: <20091022143833.51c48260@doriath> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: Kevin Wolf , Glauber Costa , Mulyadi Santosa , qemu-devel@nongnu.org Luiz Capitulino wrote: > On Thu, 22 Oct 2009 10:40:54 -0500 > Anthony Liguori wrote: > > >> Luiz Capitulino wrote: >> >>> Yeah, I agree. >>> >>> When testing migration, for example, I have to type 'migrate -d tcp:0:4444' >>> several times... Maybe there's a smarter way to do this, but the monitor >>> macros idea seems interesting to me. >>> >>> >> When we have QMP, we can create a QMP socket at a well known location >> based on the -name parameter. We could also introduce a qm command that >> allowed one to execute monitor commands from the shell. That allows >> people to write whatever crazy shell scripts they want. >> > > Yes. > > What about the macros idea? Are you against it? > I'm concerned that it's a snowball of complexity waiting to happen for very little benefit. I think we're trying to solve a non-existent problem. Regards, Anthony Liguori