|
From: | Avi Kivity |
Subject: | [Qemu-devel] Re: libvirt vs. in-qemu management |
Date: | Tue, 06 Apr 2010 15:41:02 +0300 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Thunderbird/3.0.4 |
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
[Prev in Thread] | Current Thread | [Next in Thread] |