public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Onkar Mahajan <kern.devel@gmail.com>, kvm@vger.kernel.org
Subject: Re: qemu-kvm monitor
Date: Tue, 12 Apr 2011 14:25:16 +0200	[thread overview]
Message-ID: <4DA444AC.5020501@siemens.com> (raw)
In-Reply-To: <BANLkTi=_b1qWO-2L8r55B=yjYAZ5JksRmw@mail.gmail.com>

On 2011-04-12 14:08, Stefan Hajnoczi wrote:
> On Tue, Apr 12, 2011 at 12:26 PM, Onkar Mahajan <kern.devel@gmail.com> wrote:
>> Hi All,
>>
>> I have following command line options to qemu-kvm ( apart from others
>> - irrelevant here !! )
>>
>> -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vm00-SMP.monitor,server,nowait
>> -mon chardev=charmonitor,id=monitor,mode=control
>>
>> How do I now start the qemu-kvm monitor control session ??
> 
> It looks like you're using libvirt.  Here are two methods of getting
> at the QEMU monitor through libvirt:
> 
> http://blog.vmsplice.net/2011/03/how-to-access-qemu-monitor-through.html
> 
> Basically, libvirt is already connected to the vm00-SMP.monitor UNIX
> domain socket.  You need to either use the qemu-monitor-command virsh
> command or you need to stop libvirtd and connect to the socket
> manually (e.g. using netcat).

...or pass another -mon command line switch set via the config
pass-though feature of libvirt. The warning related to
qemu-monitor-command applies to that approach as well of course.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

      reply	other threads:[~2011-04-12 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 11:26 qemu-kvm monitor Onkar Mahajan
2011-04-12 12:08 ` Stefan Hajnoczi
2011-04-12 12:25   ` Jan Kiszka [this message]

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=4DA444AC.5020501@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=kern.devel@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=stefanha@gmail.com \
    /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