From: Avi Kivity <avi@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Re: RFC: blockdev_add & friends, brief rationale, QMP docs
Date: Sun, 30 May 2010 12:11:39 +0300 [thread overview]
Message-ID: <4C022BCB.5000907@redhat.com> (raw)
In-Reply-To: <20100528162451.2d10859d@redhat.com>
On 05/28/2010 10:24 PM, Luiz Capitulino wrote:
>
>> If a password is needed, we should throw an error and let the QMP client
>> set the password and try again.
>>
> It's what we do today, a password should be set with block_passwd before
> issuing the change command. Otherwise an error is throw.
>
Is the password some kind of global or per-monitor property? In that
case it doesn't work with parallel execution of commands; better to have
a password field (or assign IDs to passwords and require a
passwordid=... argument).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-05-30 9:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 18:21 [Qemu-devel] RFC: blockdev_add & friends, brief rationale, QMP docs Markus Armbruster
2010-05-28 19:13 ` [Qemu-devel] " Kevin Wolf
2010-05-28 19:17 ` Anthony Liguori
2010-05-28 19:24 ` Luiz Capitulino
2010-05-30 9:11 ` Avi Kivity [this message]
2010-05-31 11:05 ` Markus Armbruster
2010-05-31 13:48 ` Luiz Capitulino
2010-05-31 14:04 ` Kevin Wolf
2010-05-30 9:09 ` Avi Kivity
2010-05-31 10:54 ` Markus Armbruster
2010-05-31 11:23 ` Avi Kivity
2010-05-31 11:50 ` Markus Armbruster
2010-06-04 14:16 ` Markus Armbruster
2010-06-04 14:32 ` Kevin Wolf
2010-06-04 15:53 ` Markus Armbruster
2010-06-04 16:20 ` Kevin Wolf
2010-06-06 8:23 ` Avi Kivity
2010-06-08 9:41 ` Markus Armbruster
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=4C022BCB.5000907@redhat.com \
--to=avi@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@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 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.