On 06/30/2011 11:32 PM, Anthony Liguori wrote:
> On 06/30/2011 03:56 AM, Stefan Hajnoczi wrote:
>> On Thu, Jun 30, 2011 at 9:40 AM, Asias He<asias.hejun@xxxxxxxxx> wrote:
>>> uip stands for user mode {TCP,UDP}/IP. Currently, uip supports ARP,
>>> ICMP,
>>> IPV4, UDP, TCP. So any network protocols above UDP/TCP should work as
>>> well,
>>> e.g., HTTP, FTP, SSH, DNS.
>>
>> There is an existing uIP which might cause confusion, not sure if
>> you've seen it. First I thought you were using that :).
>>
>> http://en.wikipedia.org/wiki/UIP_(micro_IP)
>
> Is the primary motivation here to allow unprivileged guests with
> networking without providing unprivileged access to raw networking or
> just to make networking Just Work?
>
> We've explored various things in the past like using a fscap based
> helper to open tap devices which can help with the Just Works parts.
Does qemu use fscap?
>
> Usermode TCP/IP can be quite cumbersome for users as things like ping
> and ip6 won't work properly.
Yes, usermode TCP/IP do have limits. But it's more cumbersome for user
to setup bridge/nat thing with privileged networking. The network setup
is a headache for some users.
This patchset implements things like 'qemu -net user' without the slirp.
I just took at a look the LOC in qemu and uip.
qemu.git$ cat slirp/*.{c,h} net/slirp.{c,h}| wc -l
11514
kernel.git/tools/kvm$ cat uip/*.{c,h} include/kvm/uip.h | wc -l
1312
--
Best Regards,
Asias He
--
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
