All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Dietmar Maurer <dietmar@proxmox.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qmp problems with --enable-kvm
Date: Thu, 22 Nov 2012 16:35:28 +0100	[thread overview]
Message-ID: <50AE4640.3000604@redhat.com> (raw)
In-Reply-To: <20121122112026.405709d8@doriath.home>

Il 22/11/2012 14:20, Luiz Capitulino ha scritto:
>> > --------- cmds.txt start--------
>> > {"execute":"qmp_capabilities", "arguments":{}}
>> > {"execute":"migrate", "arguments":{ "uri":"exec:cat >/dev/null"}}
>> > {"execute":"query-migrate", "arguments":{}}
>> > --------- cmds.txt end--------
>> > 
>> > and the following command line to start qemu:
>> > 
>> > #  ./x86_64-softmmu/qemu-system-x86_64 -chardev socket,id=qmp,path=/tmp/test.qmp,server,nowait -mon chardev=qmp,mode=control  --enable-kvm
>> > 
>> > I then execute the qmp commands with:
>> > 
>> > # cat cmds.txt | socat - /tmp/test.qmp 
>> > {"QMP": {"version": {"qemu": {"micro": 90, "minor": 2, "major": 1}, "package": ""}, "capabilities": []}}
>> > {"return": {}}
>> > {"return": {}}
>> > {"timestamp": {"seconds": 1353587785, "microseconds": 134907}, "event": "STOP"}
>> > {"return": {"status": "completed", "downtime": 8, "ram": {"total": 143065088, "remaining": 0, "transferred": 772035, "duplicate": 34755, "dirty-pages-rate": 0, "normal-bytes": 737280, "normal": 180}}}
>> > 
>> > so far so good.
>> > 
>> > But if I execute that again I get an error:
>> > 
>> > # cat cmds.txt | socat - /tmp/test.qmp 
>> > {"error": {"class": "CommandNotFound", "desc": "The command qmp_capabilities has not been found"}}
>> > {"return": {}}
>> > {"return": {"expected-downtime": 0, "status": "active", "total-time": 33, "ram": {"total": 143065088, "remaining": 8937472, "transferred": 495481, "duplicate": 67388, "dirty-pages-rate": 0, "normal-bytes": 1200128, "normal": 293}}}
>> > 
>> > 
>> > The interesting thing is that it works perfectly without --enable-kvm. 
> Can you please try the following patch?
> 
>  https://lists.gnu.org/archive/html/qemu-devel/2012-11/msg00174.html

I don't think that's related.  The only problem I see here, is that
"qmp_capabilities" can only be executed once.  That's by design, as I
understand it.

What do you get without --enable-kvm?

Paolo

  parent reply	other threads:[~2012-11-22 15:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 12:41 [Qemu-devel] qmp problems with --enable-kvm Dietmar Maurer
2012-11-22 13:20 ` Luiz Capitulino
2012-11-22 13:44   ` Dietmar Maurer
2012-11-22 15:07     ` Luiz Capitulino
2012-11-22 15:35   ` Paolo Bonzini [this message]
2012-11-22 15:53     ` Dietmar Maurer
2012-11-22 16:00       ` Paolo Bonzini
2012-11-22 16:04         ` Dietmar Maurer
2012-11-22 16:09           ` Paolo Bonzini
2012-11-22 16:24             ` Luiz Capitulino
2012-11-22 16:33               ` Luiz Capitulino
2012-11-22 16:58                 ` Luiz Capitulino
2012-11-22 17:07                   ` Paolo Bonzini
2012-11-22 17:09                     ` Jan Kiszka
2012-11-22 17:24                       ` Luiz Capitulino
2012-11-23  6:29                       ` Dietmar Maurer

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=50AE4640.3000604@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dietmar@proxmox.com \
    --cc=lcapitulino@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.