On Tue, Jul 28, 2009 at 09:48:00AM -0500, Anthony Liguori wrote: > Richard W.M. Jones wrote: >> On Mon, Jul 27, 2009 at 06:44:28PM -0500, Anthony Liguori wrote: >> >>> It really suggests that you need _one_ vmchannel that's exposed to >>> userspace with a single userspace daemon that consumes it. >>> >> >> ... or a more flexible API. I don't like having fixed /dev/vmch* >> devices either. >> > > Indeed. > >> A long time ago (on a mailing list not so far away) there was a much >> better userspace API proposed, which had a separate AF_VMCHANNEL >> address family. >> >> That API works much more like TCP sockets, except without requiring >> network devices: >> > > Dave Miller nacked that approach with a sledgehammer instead preferring > that we just use standard TCP/IP which is what led to the current > implementation using slirp. I'm aware of that - I just don't think it was a good choice. [BTW the qemu-devel mailing list seems to be bouncing messages] Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://et.redhat.com/~rjones/libguestfs/ See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
