From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [ANNOUNCE] Native Linux KVM tool v2 Date: Sun, 19 Jun 2011 11:15:06 +0300 Message-ID: <20110619081506.GA8744@redhat.com> References: <1308153214.7566.6.camel@jaguar> <20110616142859.GA18356@redhat.com> <4DFA1AC2.20605@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Pekka Enberg , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Avi Kivity , Andrew Morton , Linus Torvalds , Ingo Molnar , Prasad Joshi , Sasha Levin , Cyrill Gorcunov To: Asias He Return-path: Received: from mx1.redhat.com ([209.132.183.28]:22919 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751408Ab1FSIPN (ORCPT ); Sun, 19 Jun 2011 04:15:13 -0400 Content-Disposition: inline In-Reply-To: <4DFA1AC2.20605@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Jun 16, 2011 at 11:01:22PM +0800, Asias He wrote: > On 06/16/2011 10:28 PM, Michael S. Tsirkin wrote: > > On Wed, Jun 15, 2011 at 06:53:34PM +0300, Pekka Enberg wrote: > >> Hi all, > >> > >> We=E2=80=99re proud to announce the second version of the Native L= inux KVM tool! We=E2=80=99re > >> now officially aiming for merging to mainline in 3.1. > >> > >> Highlights: > >> > >> - Experimental GUI support using SDL and VNC > >> > >> - SMP support. tools/kvm/ now has a highly scalable, largely lockl= ess driver > >> interface and the individual drivers are using finegrained locks= =2E > >> > >> - TAP-based virtio networking > >=20 > > Wanted to ask for a while: would it make sense to use vhost-net? > > Or maybe use that exclusively? > > Less hypervisor code to support would help the focus. > >=20 >=20 > Sure. We are planning to use vhost-net. Just out of time right now, w= e > are currently working on simple user model network support which allo= ws > plain user to use network without root privilege. Yes, qemu does this by implementing NAT and the TCP stack in userspace. What always made me unhappy about this solution is that we have a perfectly fine NAT and TCP in kernel, we just lack APIs to make an unpriveledged user make use of it the way we want. I hope you can avoid this duplication. Another question is whether you want to implement a dhcp server. --=20 MST