I use the following qmp commands (file cmds.txt) for testing:
- 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
On Thu, 22 Nov 2012 12:41:31 +
Dietmar Maurer diet...@proxmox.com wrote:
I use the following qmp commands (file cmds.txt) for testing:
- cmds.txt start
{execute:qmp_capabilities, arguments:{}}
{execute:migrate, arguments:{ uri:exec:cat /dev/null}}
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 am unable to apply that patch?
patching file vl.c
Hunk #1 FAILED at 3551.
Hunk #2 succeeded at 3729 with
On Thu, 22 Nov 2012 13:44:24 +
Dietmar Maurer diet...@proxmox.com wrote:
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 am unable to apply
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
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
Il 22/11/2012 16:53, Dietmar Maurer ha scritto:
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
Ok, in any case Jan's patch was for a QEMU that didn't start at all with --
enable-kvm -monitor stdio, i.e. really unrelated.
In any case, I cannot reproduce it here.
Any idea what can cause such behaviour?
Il 22/11/2012 17:04, Dietmar Maurer ha scritto:
Ok, in any case Jan's patch was for a QEMU that didn't start at all with --
enable-kvm -monitor stdio, i.e. really unrelated.
In any case, I cannot reproduce it here.
Any idea what can cause such behaviour?
It seems like mon-mc-command_mode
On Thu, 22 Nov 2012 17:09:24 +0100
Paolo Bonzini pbonz...@redhat.com wrote:
Il 22/11/2012 17:04, Dietmar Maurer ha scritto:
Ok, in any case Jan's patch was for a QEMU that didn't start at all with --
enable-kvm -monitor stdio, i.e. really unrelated.
Right. When I saw qmp and --enable-kvm
On Thu, 22 Nov 2012 14:24:14 -0200
Luiz Capitulino lcapitul...@redhat.com wrote:
It seems like mon-mc-command_mode is set wrong, looking at
qmp_cmd_mode and its callers. Luiz may have more ideas.
Checking. What I've just found is that qmp_capabilites will fail if the
VM is stopped (!?).
On Thu, 22 Nov 2012 14:33:24 -0200
Luiz Capitulino lcapitul...@redhat.com wrote:
On Thu, 22 Nov 2012 14:24:14 -0200
Luiz Capitulino lcapitul...@redhat.com wrote:
It seems like mon-mc-command_mode is set wrong, looking at
qmp_cmd_mode and its callers. Luiz may have more ideas.
Il 22/11/2012 17:58, Luiz Capitulino ha scritto:
It seems like mon-mc-command_mode is set wrong, looking at
qmp_cmd_mode and its callers. Luiz may have more ideas.
Checking. What I've just found is that qmp_capabilites will fail if the
VM is stopped (!?).
It's a regression somewhere. I
On 2012-11-22 18:07, Paolo Bonzini wrote:
Il 22/11/2012 17:58, Luiz Capitulino ha scritto:
It seems like mon-mc-command_mode is set wrong, looking at
qmp_cmd_mode and its callers. Luiz may have more ideas.
Checking. What I've just found is that qmp_capabilites will fail if the
VM is stopped
On Thu, 22 Nov 2012 18:09:44 +0100
Jan Kiszka jan.kis...@siemens.com wrote:
On 2012-11-22 18:07, Paolo Bonzini wrote:
Il 22/11/2012 17:58, Luiz Capitulino ha scritto:
It seems like mon-mc-command_mode is set wrong, looking at
qmp_cmd_mode and its callers. Luiz may have more ideas.
We have more timers than the one based on vm_clock. Does this help?
Yes, that patch fixes the problem for me.
diff --git a/qemu-char.c b/qemu-char.c
index 88f4025..242b799 100644
--- a/qemu-char.c
+++ b/qemu-char.c
@@ -134,9 +134,9 @@ static void qemu_chr_fire_open_event(void
*opaque)
16 matches
Mail list logo
