All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "dlaor@redhat.com" <dlaor@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	Chris Wright <chrisw@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call minutes for Oct 19
Date: Thu, 21 Oct 2010 09:45:25 +0200	[thread overview]
Message-ID: <4CBFEF95.9060703@redhat.com> (raw)
In-Reply-To: <9DABD2D4-389E-4D05-8A4C-2DE1E20D3B5C@suse.de>

On 10/21/2010 03:14 AM, Alexander Graf wrote:
>> I agree that some agent code for basic stuff like live snapshot
>> sync with the filesystem is small enough and worth to host within
>> qemu. Maybe we do need more than one project?
>
> No, please. That's exactly what I don't want to see. The
> libvirt/qemu/virt-man split is killing us already. How is this going
> to become with 20 driver packs for the guest?

Agreed.  Not relying on Mata Hari and reinventing a dbus/WMI interface 
would be yet another case of QEMU NIH.  The same argument also works on 
the backend BTW, it can be virtio serial but also a Xen pvconsole and 
that wheel should not be reinvented either.

The guest agent should be a pluggable architecture, and QEMU can provide 
plugins for sync, spice, "info balloon" and everything else it needs.

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Chris Wright <chrisw@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"dlaor@redhat.com" <dlaor@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] KVM call minutes for Oct 19
Date: Thu, 21 Oct 2010 09:45:25 +0200	[thread overview]
Message-ID: <4CBFEF95.9060703@redhat.com> (raw)
In-Reply-To: <9DABD2D4-389E-4D05-8A4C-2DE1E20D3B5C@suse.de>

On 10/21/2010 03:14 AM, Alexander Graf wrote:
>> I agree that some agent code for basic stuff like live snapshot
>> sync with the filesystem is small enough and worth to host within
>> qemu. Maybe we do need more than one project?
>
> No, please. That's exactly what I don't want to see. The
> libvirt/qemu/virt-man split is killing us already. How is this going
> to become with 20 driver packs for the guest?

Agreed.  Not relying on Mata Hari and reinventing a dbus/WMI interface 
would be yet another case of QEMU NIH.  The same argument also works on 
the backend BTW, it can be virtio serial but also a Xen pvconsole and 
that wheel should not be reinvented either.

The guest agent should be a pluggable architecture, and QEMU can provide 
plugins for sync, spice, "info balloon" and everything else it needs.

Paolo

  reply	other threads:[~2010-10-21  7:45 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 15:14 KVM call minutes for Oct 19 Chris Wright
2010-10-19 15:14 ` [Qemu-devel] " Chris Wright
2010-10-20  8:21 ` Alexander Graf
2010-10-20  8:21   ` Alexander Graf
2010-10-20  8:25   ` Paolo Bonzini
2010-10-20  8:25     ` Paolo Bonzini
2010-10-20  8:30     ` Alexander Graf
2010-10-20  8:30       ` Alexander Graf
2010-10-20 10:47   ` Avi Kivity
2010-10-20 10:47     ` Avi Kivity
2010-10-20 12:16   ` Dor Laor
2010-10-20 12:16     ` Dor Laor
2010-10-21 10:22     ` Andrew Beekhof
2010-10-21 10:22       ` Andrew Beekhof
2010-10-21 10:26       ` Dor Laor
2010-10-21 10:26         ` Dor Laor
2010-10-21 13:09       ` Anthony Liguori
2010-10-21 13:09         ` Anthony Liguori
2010-10-21 13:18         ` Daniel P. Berrange
2010-10-21 13:18           ` Daniel P. Berrange
2010-10-21 13:32           ` Anthony Liguori
2010-10-21 13:32             ` Anthony Liguori
2010-10-21 15:43             ` Andrew Beekhof
2010-10-21 15:43               ` Andrew Beekhof
2010-10-21 16:25               ` Anthony Liguori
2010-10-21 16:25                 ` Anthony Liguori
2010-10-21 16:37                 ` Chris Wright
2010-10-21 16:37                   ` Chris Wright
2010-10-21 19:47                 ` Andrew Beekhof
2010-10-20 13:02   ` Anthony Liguori
2010-10-20 13:02     ` Anthony Liguori
2010-10-20 13:19     ` Daniel P. Berrange
2010-10-20 13:19       ` Daniel P. Berrange
2010-10-20 13:21       ` Anthony Liguori
2010-10-20 13:21         ` Anthony Liguori
2010-10-20 22:46         ` Dor Laor
2010-10-20 22:46           ` Dor Laor
2010-10-21  1:14           ` Alexander Graf
2010-10-21  1:14             ` Alexander Graf
2010-10-21  7:45             ` Paolo Bonzini [this message]
2010-10-21  7:45               ` Paolo Bonzini
2010-10-21 13:02               ` Anthony Liguori
2010-10-21 13:02                 ` Anthony Liguori
2010-10-21 13:05                 ` Dor Laor
2010-10-21 13:05                   ` Dor Laor
2010-10-22 17:29                 ` Chris Wright
2010-10-22 17:29                   ` Chris Wright
2010-10-22 17:39                   ` Anthony Liguori
2010-10-22 17:39                     ` Anthony Liguori
2010-10-22 18:20                     ` Chris Wright
2010-10-22 18:20                       ` Chris Wright
2010-10-22 18:53                       ` Anthony Liguori
2010-10-22 18:53                         ` Anthony Liguori
2010-10-23  0:06                         ` Chris Wright
2010-10-23  0:06                           ` Chris Wright

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=4CBFEF95.9060703@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=berrange@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=dlaor@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 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.