From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: libvirt vs. in-qemu management
Date: Tue, 06 Apr 2010 15:41:02 +0300 [thread overview]
Message-ID: <4BBB2BDE.4040500@redhat.com> (raw)
In-Reply-To: <4BBB2900.9010309@suse.de>
On 04/06/2010 03:28 PM, Alexander Graf wrote:
>> Note things like network setup are a bottomless pit. Pretty soon you
>> need to setup vlans and bonding etc. If a user needs one of these and
>> qemud doesn't provide it, then qemud becomes useless to them. But the
>> same problem applies to libvirt.
>>
> If they are a bottomless pit then they are a bottomless pit. There's
> nothing we can do about it. This pit needs to be dug either way, whether
> it's in libvirt or in qemud.
>
Agreed. The only difference is who's doing the digging.
One way to avoid it is to have a rich plugin API so if some needs some
to, say, set up traffic control on the interface, they can write a
plugin to do that.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-04-06 12:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 21:11 [Qemu-devel] libvirt vs. in-qemu management Alexander Graf
2010-04-05 22:14 ` [Qemu-devel] " Avi Kivity
2010-04-05 22:29 ` Alexander Graf
2010-04-06 12:09 ` Avi Kivity
2010-04-06 12:28 ` Alexander Graf
2010-04-06 12:41 ` Avi Kivity [this message]
2010-04-06 12:51 ` Alexander Graf
2010-04-06 20:15 ` Jamie Lokier
2010-04-06 11:06 ` Daniel P. Berrange
2010-04-06 12:49 ` Alexander Graf
2010-04-06 13:00 ` Daniel P. Berrange
2010-04-06 13:20 ` Alexander Graf
2010-04-06 20:08 ` Jamie Lokier
2010-04-06 10:47 ` Daniel P. Berrange
2010-04-06 12:43 ` Alexander Graf
2010-04-06 12:58 ` Avi Kivity
2010-04-06 13:39 ` Daniel P. Berrange
2010-04-06 13:53 ` Alexander Graf
2010-04-06 14:06 ` Daniel P. Berrange
2010-04-06 15:06 ` Alexander Graf
2010-04-06 19:43 ` Jamie Lokier
2010-04-06 14:14 ` Richard W.M. Jones
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=4BBB2BDE.4040500@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.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.