From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NuNOp-0003g0-TO for qemu-devel@nongnu.org; Wed, 24 Mar 2010 06:01:19 -0400 Received: from [140.186.70.92] (port=52766 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NuNNK-0003GD-Nv for qemu-devel@nongnu.org; Wed, 24 Mar 2010 06:01:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NuNM9-0004a5-FI for qemu-devel@nongnu.org; Wed, 24 Mar 2010 05:58:34 -0400 Received: from mail-px0-f173.google.com ([209.85.216.173]:34534) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NuNM9-0004Zz-8t for qemu-devel@nongnu.org; Wed, 24 Mar 2010 05:58:33 -0400 Received: by pxi3 with SMTP id 3so3206038pxi.28 for ; Wed, 24 Mar 2010 02:58:32 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Jun Koi Date: Wed, 24 Mar 2010 18:58:12 +0900 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] Re: Exposing monitor on socket interface? List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Juan Quintela Cc: qemu-devel@nongnu.org Thanks a lot, Juan! Jun On Wed, Mar 24, 2010 at 6:41 PM, Juan Quintela wrote: > Jun Koi wrote: >> Hi, >> >> Is it possible to use -monitor option to expose the monitor on socket >> interface, such as TCP or Unix domain port, so I can access the >> monitor using non-stdio way? > > man qemu > > search -monitor > > =A0 =A0 =A0 -monitor dev > =A0 =A0 =A0 =A0 =A0 Redirect the monitor to host device dev (same devices= as the serial > =A0 =A0 =A0 =A0 =A0 port). =A0The default device is "vc" in graphical mod= e and "stdio" in > =A0 =A0 =A0 =A0 =A0 non graphical mode. > > search -serial > > =A0 =A0 =A0-serial dev > =A0 =A0 =A0 =A0 =A0 Redirect the virtual serial port to host character de= vice dev. The > =A0 =A0 =A0 =A0 =A0 default device is "vc" in graphical mode and "stdio" = in non > =A0 =A0 =A0 =A0 =A0 graphical mode. > > =A0 =A0 =A0 =A0 =A0 This option can be used several times to simulate up = to 4 serial > =A0 =A0 =A0 =A0 =A0 ports. > > =A0 =A0 =A0 =A0 =A0 Use "-serial none" to disable all serial ports. > > =A0 =A0 =A0 =A0 =A0 Available character devices are: > > .... > =A0 =A0 =A0 =A0 =A0"tcp:[host]:port[,server][,nowait][,nodelay]" > =A0 =A0 =A0 =A0 =A0 =A0 =A0 The TCP Net Console has two modes of operatio= n. =A0It can send > =A0 =A0 =A0 =A0 =A0 =A0 =A0 the serial I/O to a location or wait for a co= nnection from a > =A0 =A0 =A0 =A0 =A0 =A0 =A0 location. =A0By default the TCP Net Console i= s sent to host at > =A0 =A0 =A0 =A0 =A0 =A0 =A0 the port. =A0If you use the server option QEM= U will wait for a > =A0 =A0 =A0 =A0 =A0 =A0 =A0 client socket application to connect to the p= ort before > =A0 =A0 =A0 =A0 =A0 =A0 =A0 continuing, unless the "nowait" option was sp= ecified. =A0The > =A0 =A0 =A0 =A0 =A0 =A0 =A0 "nodelay" option disables the Nagle buffering= algorithm. =A0If > =A0 =A0 =A0 =A0 =A0 =A0 =A0 host is omitted, 0.0.0.0 is assumed. Only one= TCP connection at > =A0 =A0 =A0 =A0 =A0 =A0 =A0 a time is accepted. You can use "telnet" to c= onnect to the > =A0 =A0 =A0 =A0 =A0 =A0 =A0 corresponding character device. > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 "Example to send tcp console to 192.168.0.2 p= ort 4444" > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -serial tcp:192.168.0.2:4444 > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 "Example to listen and wait on port 4444 for = connection" > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -serial tcp::4444,server > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 "Example to not wait and listen on ip 192.168= .0.100 port 4444" > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -serial tcp:192.168.0.100:4444,server= ,nowait > > =A0 =A0 =A0 =A0 =A0 "telnet:host:port[,server][,nowait][,nodelay]" > =A0 =A0 =A0 =A0 =A0 =A0 =A0 The telnet protocol is used instead of raw tc= p sockets. =A0The > =A0 =A0 =A0 =A0 =A0 =A0 =A0 options work the same as if you had specified= "-serial tcp". > =A0 =A0 =A0 =A0 =A0 =A0 =A0 The difference is that the port acts like a t= elnet server or > =A0 =A0 =A0 =A0 =A0 =A0 =A0 client using telnet option negotiation. =A0Th= is will also allow > =A0 =A0 =A0 =A0 =A0 =A0 =A0 you to send the MAGIC_SYSRQ sequence if you u= se a telnet that > =A0 =A0 =A0 =A0 =A0 =A0 =A0 supports sending the break sequence. =A0Typic= ally in unix telnet > =A0 =A0 =A0 =A0 =A0 =A0 =A0 you do it with Control-] and then type "send = break" followed by > =A0 =A0 =A0 =A0 =A0 =A0 =A0 pressing the enter key. > > > I think that it is difficult to get more options that qemu in that > department :-) > > Later, Juan. >