From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: qemu-kvm monitor Date: Tue, 12 Apr 2011 14:25:16 +0200 Message-ID: <4DA444AC.5020501@siemens.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Onkar Mahajan , kvm@vger.kernel.org To: Stefan Hajnoczi Return-path: Received: from thoth.sbs.de ([192.35.17.2]:19663 "EHLO thoth.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755272Ab1DLMZX (ORCPT ); Tue, 12 Apr 2011 08:25:23 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 2011-04-12 14:08, Stefan Hajnoczi wrote: > On Tue, Apr 12, 2011 at 12:26 PM, Onkar Mahajan 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