qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Jun Koi <junkoi2004@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Multiple monitor interfaces?
Date: Tue, 27 Apr 2010 15:26:40 -0300	[thread overview]
Message-ID: <20100427152640.447f7390@redhat.com> (raw)
In-Reply-To: <i2lfdaac4d51004270723s3e69ad4fzfddcf20af0c74afc@mail.gmail.com>

On Tue, 27 Apr 2010 23:23:45 +0900
Jun Koi <junkoi2004@gmail.com> wrote:

> Hi,
> 
> I am wondering if is it possible to have multiple monitor interfaces
> at the same time? If so, how can we open more than one?

 The following command will create three monitors (stdio, vc and telnet
on port 4444):

# qemu [...] -chardev stdio,id=mon0 -mon chardev=mon0,mode=readline \
             -chardev socket,id=mon1,host=localhost,port=4444,server \
             -mon chardev=mon1,mode=readline \
             -chardev vc,id=mon2 -mon chardev=mon2,mode=readline

> This might be useful for something like libvirt, so while we leave one
> monitor port for libvirt, we can still access to another one to
> control Qemu?

 Historically, libvirt had support to only one monitor: the one it uses. But
now they're working on supporting custom command-line options, so adding
new monitors should be possible I think.

 Also, you can point libvirt to a script that opens an additional monitor
for you, some developers do this afaik.

  reply	other threads:[~2010-04-27 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 14:23 [Qemu-devel] Multiple monitor interfaces? Jun Koi
2010-04-27 18:26 ` Luiz Capitulino [this message]
2010-04-28  3:20   ` Jun Koi
2010-04-28 12:40     ` Luiz Capitulino
2010-04-27 18:39 ` [Qemu-devel] " Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100427152640.447f7390@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=junkoi2004@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).