From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM call agenda for May 18
Date: Tue, 18 May 2010 11:25:23 -0500 [thread overview]
Message-ID: <4BF2BF73.5070901@codemonkey.ws> (raw)
In-Reply-To: <20100518161654.GU8328@redhat.com>
On 05/18/2010 11:16 AM, Daniel P. Berrange wrote:
> The must haves are blockdev_add, and the commit/delvm/loadvm/savevm
> stuff, since they're already in use.
>
> The problem I fear is that we're aiming for a moving target here.
>
> eg, by the time QEMU 0.13 comes out libvirt may have received patches
> using yet more QEMU monitor commands.
libvirt could just stop taking patches that use monitor commands.
There's no way we're going to break the deadlock if we don't work
together here.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-05-18 16:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 3:23 [Qemu-devel] KVM call agenda for May 18 Chris Wright
2010-05-18 6:59 ` [Qemu-devel] " Brian Jackson
2010-05-18 13:52 ` Anthony Liguori
2010-05-18 19:46 ` Brian Jackson
2010-05-18 19:51 ` Chris Wright
2010-05-19 8:20 ` Christoph Hellwig
2010-05-19 19:47 ` Anthony Liguori
2010-05-25 9:51 ` Avi Kivity
2010-05-18 13:53 ` Anthony Liguori
2010-05-18 14:09 ` Daniel P. Berrange
2010-05-18 14:34 ` Anthony Liguori
2010-05-18 14:55 ` Daniel P. Berrange
2010-05-18 15:26 ` Anthony Liguori
2010-05-18 15:44 ` Markus Armbruster
2010-05-18 15:48 ` Markus Armbruster
2010-05-18 16:00 ` Luiz Capitulino
2010-05-18 16:16 ` Daniel P. Berrange
2010-05-18 16:25 ` Anthony Liguori [this message]
2010-05-18 17:46 ` Luiz Capitulino
2010-05-18 17:31 ` Avi Kivity
2010-05-18 21:50 ` Anthony Liguori
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=4BF2BF73.5070901@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=berrange@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--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).