From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GnjMd-00015p-85 for qemu-devel@nongnu.org; Fri, 24 Nov 2006 17:17:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GnjMb-00015B-Mb for qemu-devel@nongnu.org; Fri, 24 Nov 2006 17:17:42 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GnjMb-000150-Gt for qemu-devel@nongnu.org; Fri, 24 Nov 2006 17:17:41 -0500 Received: from [64.233.182.191] (helo=nf-out-0910.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GnjMa-0000kf-WA for qemu-devel@nongnu.org; Fri, 24 Nov 2006 17:17:41 -0500 Received: by nf-out-0910.google.com with SMTP id c31so2081016nfb for ; Fri, 24 Nov 2006 14:17:39 -0800 (PST) Message-ID: <4c5e54ba0611241417m42754694i42c9ab520ed49b61@mail.gmail.com> Date: Fri, 24 Nov 2006 23:17:39 +0100 From: "Eric Bellard" Sender: eric.bellard@gmail.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5770_10810730.1164406659167" Subject: [Qemu-devel] Re: Problem with windows qemu port Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_5770_10810730.1164406659167 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Eduardo, The ",server" option is not a good choice for me: - I prefer to start a server socket from my gui and plug qemu into it. It's less error prone (when it works :-) : => I was using ",server" before and I needed to sleep my gui process an *enough* amount of time to wait for qemu start before connecting on its socket... Anyway if I don't have the choice I will do it. Regards, eric Eduardo Felipe gmail.com> writes: > > > > > -monitor option is not supported. > > > > The server variants of the command work for me on Windows, though. Try: > > -monitor tcp:127.0.0.1:9100,server > > or just > > -monitor tcp::9100,server > > to start qemu in server mode listening to port 9100. Then make your > GUI connect to qemu, instead of the other way around. > > Regards, > Eduardo Felipe > -- Eric BELLARD bellard@supagro.inra.fr 04-99-61-30-08 ------=_Part_5770_10810730.1164406659167 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Eduardo,

The ",server" option is not a good choice for me:
- I prefer to start a server socket from my gui and plug qemu into it. It's less error prone (when it works :-) :
   => I was using ",server" before and I needed to sleep my gui process an *enough* amount of time  to wait for qemu start before connecting on its socket...

Anyway if I don't have the choice I will do it.

Regards,

eric

Eduardo Felipe <edusaper <at> gmail.com> writes:

>
> >
> > -monitor option is not supported.
> >
>
> The server variants of the command work for me on Windows, though. Try:
>
>  -monitor tcp:127.0.0.1:9100,server
>
> or just
>
>  -monitor tcp::9100,server
>
> to start qemu in server mode listening to port 9100. Then make your
> GUI connect to qemu, instead of the other way around.
>
> Regards,
> Eduardo Felipe
>




--
Eric BELLARD
bellard@supagro.inra.fr
04-99-61-30-08 ------=_Part_5770_10810730.1164406659167--