From: Asias He <asias.hejun@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Pekka Enberg <penberg@kernel.org>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Avi Kivity <avi@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Prasad Joshi <prasadjoshi124@gmail.com>,
Sasha Levin <levinsasha928@gmail.com>,
Cyrill Gorcunov <gorcunov@gmail.com>
Subject: Re: [ANNOUNCE] Native Linux KVM tool v2
Date: Thu, 16 Jun 2011 23:01:22 +0800 [thread overview]
Message-ID: <4DFA1AC2.20605@gmail.com> (raw)
In-Reply-To: <20110616142859.GA18356@redhat.com>
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’re proud to announce the second version of the Native Linux KVM tool! We’re
>> 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 lockless driver
>> interface and the individual drivers are using finegrained locks.
>>
>> - TAP-based virtio networking
>
> 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.
>
Sure. We are planning to use vhost-net. Just out of time right now, we
are currently working on simple user model network support which allows
plain user to use network without root privilege.
--
Best Regards,
Asias He
next prev parent reply other threads:[~2011-06-16 15:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 15:53 [ANNOUNCE] Native Linux KVM tool v2 Pekka Enberg
2011-06-15 16:30 ` Avi Kivity
2011-06-15 17:10 ` Pekka Enberg
2011-06-15 20:13 ` Prasad Joshi
2011-06-15 20:23 ` Sasha Levin
2011-06-15 20:49 ` Prasad Joshi
2011-06-15 21:53 ` Anthony Liguori
2011-06-15 22:04 ` Anthony Liguori
2011-06-15 22:07 ` Alexander Graf
2011-06-15 22:20 ` Anthony Liguori
2011-06-15 22:44 ` Anthony Liguori
2011-06-16 5:41 ` Pekka Enberg
2011-06-16 6:21 ` Pekka Enberg
2011-06-16 9:24 ` Christoph Hellwig
2011-06-16 9:34 ` Pekka Enberg
2011-06-16 9:48 ` Christoph Hellwig
2011-06-16 9:57 ` Ingo Molnar
2011-06-16 9:57 ` Pekka Enberg
2011-06-16 10:02 ` Christoph Hellwig
2011-06-16 11:22 ` Ingo Molnar
2011-06-16 11:25 ` Christoph Hellwig
2011-06-16 11:40 ` Ingo Molnar
2011-06-16 11:51 ` Christoph Hellwig
2011-06-17 7:21 ` Jeff Garzik
2011-06-16 5:45 ` Pekka Enberg
2011-06-16 7:24 ` Ingo Molnar
2011-06-16 7:33 ` Pekka Enberg
2011-06-16 8:07 ` Ingo Molnar
2011-06-16 9:09 ` Stefan Hajnoczi
2011-06-16 5:29 ` Stefan Hajnoczi
2011-06-16 5:42 ` Pekka Enberg
2011-06-15 21:41 ` Anthony Liguori
2011-06-16 14:28 ` Michael S. Tsirkin
2011-06-16 15:01 ` Asias He [this message]
2011-06-19 8:15 ` Michael S. Tsirkin
2011-06-16 14:48 ` Pekka Enberg
2011-06-16 22:50 ` Anthony Liguori
2011-06-17 1:03 ` Sasha Levin
2011-06-17 5:00 ` Stefan Hajnoczi
2011-06-17 13:41 ` Sasha Levin
2011-06-17 13:45 ` Anthony Liguori
2011-06-17 5:11 ` Stefan Hajnoczi
2011-06-17 7:31 ` justin
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=4DFA1AC2.20605@gmail.com \
--to=asias.hejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.com \
--cc=torvalds@linux-foundation.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.