From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
Eric Blake <eblake@redhat.com>,
quintela@trasno.org, KVM devel mailing list <kvm@vger.kernel.org>,
Developers qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 28th
Date: Tue, 28 Feb 2012 15:47:23 +0100 [thread overview]
Message-ID: <4F4CE8FB.8080404@redhat.com> (raw)
In-Reply-To: <CAJSP0QWW9OqQ3uDpE5wY9QDasM+7AiX5wLnoXpxQarLKwEOr4w@mail.gmail.com>
Il 28/02/2012 15:39, Stefan Hajnoczi ha scritto:
> I'm not a fan of transactions or freeze/thaw (if used to atomically
> perform other commands).
>
> We should not export low-level block device operations so that
> external software can micromanage via QMP. I don't think this is a
> good idea because it takes the block device offline and possibly
> blocks the VM. We're reaching a level comparable to an HTTP interface
> for acquiring pthread mutex, doing some operations, and then another
> HTTP request to unlock it. This is micromanagement it will create
> more problems because we will have to support lots of little API
> functions.
So you're for extending Jeff's patches to group mirroring etc.?
That's also my favorite one, assuming we can do it in time for 1.1.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Developers qemu-devel <qemu-devel@nongnu.org>,
Eric Blake <eblake@redhat.com>,
quintela@trasno.org, Anthony Liguori <anthony@codemonkey.ws>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 28th
Date: Tue, 28 Feb 2012 15:47:23 +0100 [thread overview]
Message-ID: <4F4CE8FB.8080404@redhat.com> (raw)
In-Reply-To: <CAJSP0QWW9OqQ3uDpE5wY9QDasM+7AiX5wLnoXpxQarLKwEOr4w@mail.gmail.com>
Il 28/02/2012 15:39, Stefan Hajnoczi ha scritto:
> I'm not a fan of transactions or freeze/thaw (if used to atomically
> perform other commands).
>
> We should not export low-level block device operations so that
> external software can micromanage via QMP. I don't think this is a
> good idea because it takes the block device offline and possibly
> blocks the VM. We're reaching a level comparable to an HTTP interface
> for acquiring pthread mutex, doing some operations, and then another
> HTTP request to unlock it. This is micromanagement it will create
> more problems because we will have to support lots of little API
> functions.
So you're for extending Jeff's patches to group mirroring etc.?
That's also my favorite one, assuming we can do it in time for 1.1.
Paolo
next prev parent reply other threads:[~2012-02-28 14:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 12:22 KVM call agenda for Tuesday 28th Juan Quintela
2012-02-27 12:22 ` [Qemu-devel] " Juan Quintela
2012-02-27 17:21 ` Eric Blake
2012-02-27 21:58 ` Paolo Bonzini
2012-02-27 21:58 ` Paolo Bonzini
2012-02-27 22:06 ` Anthony Liguori
2012-02-27 22:09 ` Paolo Bonzini
2012-02-27 22:09 ` [Qemu-devel] " Paolo Bonzini
2012-02-28 14:39 ` Stefan Hajnoczi
2012-02-28 14:47 ` Paolo Bonzini [this message]
2012-02-28 14:47 ` Paolo Bonzini
2012-02-28 14:58 ` Stefan Hajnoczi
2012-02-28 14:58 ` Stefan Hajnoczi
2012-02-28 16:07 ` blockdev operations [was: [Qemu-devel] KVM call agenda for Tuesday 28th] Eric Blake
2012-02-28 16:07 ` [Qemu-devel] blockdev operations [was: " Eric Blake
2012-02-28 16:12 ` blockdev operations [was: [Qemu-devel] " Paolo Bonzini
2012-02-28 16:12 ` [Qemu-devel] blockdev operations [was: " Paolo Bonzini
2012-02-29 10:16 ` Kevin Wolf
2012-02-29 10:16 ` Kevin Wolf
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=4F4CE8FB.8080404@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=eblake@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.org \
--cc=stefanha@gmail.com \
/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.