[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [POC] colo-proxy in qemu

From: zhanghailiang
Subject: Re: [Qemu-devel] [POC] colo-proxy in qemu
Date: Mon, 27 Jul 2015 19:24:53 +0800
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0

On 2015/7/27 18:13, Stefan Hajnoczi wrote:
On Tue, Jul 21, 2015 at 10:49:29AM +0100, Stefan Hajnoczi wrote:
On Tue, Jul 21, 2015 at 08:13:42AM +0200, Jan Kiszka wrote:
On 2015-07-20 17:01, Stefan Hajnoczi wrote:
On Mon, Jul 20, 2015 at 2:12 PM, Vasiliy Tolstov <address@hidden> wrote:
2015-07-20 14:55 GMT+03:00 zhanghailiang <address@hidden>:
Agreed, besides, it is seemed that slirp is not supporting ipv6, we also
have to supplement it.

patch for ipv6 slirp support some times ago sended to qemu list, but i
don't know why in not accepted.

I think no one reviewed it but there was no objection against IPv6
support in principle.

Jan: Can we merge slirp IPv6 support for QEMU 2.5?

Sorry, as I pointed out some time back, I don't have the bandwidth to
look into slirp. Someone need to do a review, then send a pull request.

Do you want to remove yourself from the slirp section of the MAINTAINERS

Going forward we'll need to find someone familiar with the QEMU
development process and with enough time to review slirp patches.


I hoped this would raise some discussion and that maybe we could find a
new maintainer or co-maintainer to get slirp moving.

Yes, please, this is important, we need slirp's maintainer to help reviewing 
the COLO proxy
patches that will be implemented based on slirp. (If we finally come to an 
agreement on realizing it in qemu)

We also need to support ipv6 for slirp, i have emailed Samuel who have sent 
ipv6 patches for slirp before,
but got no response. (I would like to respin and test Samuel's ipv6 slirp patch 
if he don't have time to do this,
but firstly, i need to get his permission :) )

Cc: Samuel Thibault <address@hidden> <address@hidden>.


Any thoughts?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]