qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kashyap Chamarthy <kchamart@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/4] scripts: qmp-shell: add transaction support
Date: Wed, 29 Apr 2015 17:20:16 +0200	[thread overview]
Message-ID: <20150429152016.GE2764@tesla.redhat.com> (raw)
In-Reply-To: <20150428161732.GD11726@tesla.redhat.com>

On Tue, Apr 28, 2015 at 06:17:32PM +0200, Kashyap Chamarthy wrote:

[. . .]

> > Seems like a regression from your v2.
> > 
> > It fails here, even for a non-transaction command, with your patch series
> > applied:
> > 
> >   (QEMU) blockdev-snapshot-internal-sync device=drive-ide0-0-0 name=snapshot0
> >   Error while parsing command line: global name '_QMPShell__parse_value' is not defined
> >   command format: <command-name>  [arg-name1=arg1] ... [arg-nameN=argN]
> 
> I now tested again with your qmp-shell-plus branch:
> 
>   $ git describe
>   v2.3.0-rc4-4-g994af97
> 
>   $ git log --oneline | head -4
>   994af97 scripts: qmp-shell: Add verbose flag
>   1009369 scripts: qmp-shell: add transaction subshell
>   0ae65ff scripts: qmp-shell: Expand support for QMP expressions
>   5f367d9 scripts: qmp-shell: refactor helpers
> 
> Result:
> 
>   - The non-transaction commands work just fine; so that regression is
>     fixed in your qmp-shell-plus branch.
>   - The transaction command (same commands as tested previously,
>     retained it below) still fails.

Tested with your newer branch[1], this time, good news -- from my
minimal testing, no regressions found while running transactional/
non-transactional commands. 

As a transactional subshell test, I ran a three-combination command like
below:

  (QEMU) transaction(
  TRANS> blockdev-snapshot-sync device=drive-ide0-0-0 snapshot-file=./ext-snap2.qcow2 format=qcow2
  TRANS> blockdev-snapshot-internal-sync device=drive-ide0-0-0 name=snapshot1
  TRANS> drive-backup device=drive-ide0-0-0 sync=full target=./backup-copy.qcow2 mode=absolute-paths format=qcow2
  TRANS> )
  {"return": {}}
  (QEMU)

When you submit a new version to the list, FWIW, you can carry my
'Tested-by'.

[1] https://github.com/jnsnow/qemu/tree/qmp-shell%2B%2B

-- 
/kashyap

      parent reply	other threads:[~2015-04-29 15:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 14:34 [Qemu-devel] [PATCH v3 0/4] scripts: qmp-shell: add transaction support John Snow
2015-04-23 14:34 ` [Qemu-devel] [PATCH v3 1/4] scripts: qmp-shell: refactor helpers John Snow
2015-04-23 14:34 ` [Qemu-devel] [PATCH v3 2/4] scripts: qmp-shell: Expand support for QMP expressions John Snow
2015-04-23 14:35 ` [Qemu-devel] [PATCH v3 3/4] scripts: qmp-shell: add transaction subshell John Snow
2015-04-23 14:35 ` [Qemu-devel] [PATCH v3 4/4] scripts: qmp-shell: Add verbose flag John Snow
2015-04-23 16:23 ` [Qemu-devel] [PATCH v3 0/4] scripts: qmp-shell: add transaction support John Snow
2015-04-23 16:23 ` Kashyap Chamarthy
2015-04-28 16:17   ` Kashyap Chamarthy
2015-04-28 16:19     ` John Snow
2015-04-29 15:20     ` Kashyap Chamarthy [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=20150429152016.GE2764@tesla.redhat.com \
    --to=kchamart@redhat.com \
    --cc=jsnow@redhat.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 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).