From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
eblake <eblake@redhat.com>
Subject: [Qemu-devel] KVM call minutes for 2013-04-23
Date: Tue, 23 Apr 2013 16:45:05 +0200 [thread overview]
Message-ID: <87ppxluwzy.fsf@elfo.elfo> (raw)
* 1.5 pending patches (paolo)
anthony thinks nothing big is outstanding
rdma: not probably for this release, too big change on migration
cpu-hotplug: andreas expect to get it for 1.5
* What can libvirt expect in 1.5 for introspection of command-line support?
command extensions? libvirt want then
* What are the rules for adding optional parameters to existing QMP
commands? Would it help if we had introspection of QMP commands?
what are the options that each command support.
command line could work for 1.5
if we got patches on the next 2 days we can get it.
rest of introspection need 1.6
it is "challenging"
we are interesting into feature introspection
and comand extensions?
one command to return the schema?
if we change a command, how we change the interface without
changing the c-api?
we can change "drive_mirror" to use a new command to see if there
are the new features.
if we have a stable c-api we can do test cases that work.
Eric will complete this with his undrestanding from libvirt point of
view.
Later, Juan.
next reply other threads:[~2013-04-23 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 14:45 Juan Quintela [this message]
2013-04-23 16:06 ` [Qemu-devel] KVM call minutes for 2013-04-23 Eric Blake
2013-04-24 8:03 ` Stefan Hajnoczi
2013-04-24 15:43 ` Luiz Capitulino
2013-04-24 15:21 ` Anthony Liguori
2013-04-24 15:30 ` Luiz Capitulino
2013-04-24 21:37 ` Eric Blake
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=87ppxluwzy.fsf@elfo.elfo \
--to=quintela@redhat.com \
--cc=eblake@redhat.com \
--cc=kvm@vger.kernel.org \
--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).