Hello all.

I'm wondering here I can obtain or generate OpenVZ specific patches,
especially for 2.6.22, that don't include bug fixes to main kernel. I
would like to test it on Ubuntu Gutsy, and use it. It would be very
appreciate if there is way to get it from OpenVZ git tree. Thanks.

-- 
Regards
Dulmandakh

> Hello all.
> 
> I'm wondering here I can obtain or generate OpenVZ specific patches,
> especially for 2.6.22, that don't include bug fixes to main kernel. I
> would like to test it on Ubuntu Gutsy, and use it. It would be very
> appreciate if there is way to get it from OpenVZ git tree. Thanks.

You can try to apply ignoring hunks which patch reports to be already applied.
After that save that patch and apply incremental OVZ patches on top after that
(interdiff -p1 patch-ovz003 patch-ovz005 > incremental-ovz-003-005-patch).

Also please note that this is a development branch kernel, so it can be
not that stable for production use. Our main target now is 2.6.24 kernel for coming 
Ubuntu server (TLS).

Thanks,
Kirill

Hi Kirill

> Also please note that this is a development branch kernel, so it can be
> not that stable for production use. Our main target now is 2.6.24 kernel
> for coming Ubuntu server (TLS).

http://git.openvz.org/?p=linux-2.6-netns;a=summary
^- git repro for that kernel ?

Regards,
 Thorsten

Thorsten Schifferdecker wrote:
> Hi Kirill
> 
> 
>>Also please note that this is a development branch kernel, so it can be
>>not that stable for production use. Our main target now is 2.6.24 kernel
>>for coming Ubuntu server (TLS).
> 
> 
> http://git.openvz.org/?p=linux-2.6-netns;a=summary
> ^- git repro for that kernel ?

no, thats a git for network namespace integration into mainstream.
2.6.24-OVZ will be published this week I hope by Alexey Dobriyan
after minimal stabilization.

Kirill

On 10.12.2007 13:07, Kirill Korotaev wrote:
> Thorsten Schifferdecker wrote:
>   
>> Hi Kirill
>>
>>
>>     
>>> Also please note that this is a development branch kernel, so it can be
>>> not that stable for production use. Our main target now is 2.6.24 kernel
>>> for coming Ubuntu server (TLS).
>>>       
>> http://git.openvz.org/?p=linux-2.6-netns;a=summary
>> ^- git repro for that kernel ?
>>     
>
> no, thats a git for network namespace integration into mainstream.
> 2.6.24-OVZ will be published this week I hope by Alexey Dobriyan
> after minimal stabilization.
>   

Does 2.6.24-ovz use the namespace code parts merged in 2.6.24?
Is there any target for an OpenVZ merge into mainline (or at least a
merge of the network parts)?

Regards,
Carl-Daniel

> Does 2.6.24-ovz use the namespace code parts merged in 2.6.24?

Sure. We even backport these patches back to our branch to use and test it.

> Is there any target for an OpenVZ merge into mainline (or at least a
> merge of the network parts)?

I think it's hard to predict exactly...

Our current plan is to have IPv4/routing/rules virtualization in a 1-2 months,
IPv6 should go faster after that (~1 month).
Then vlan, tun/tap, netfilters and other features.

Thanks,
Kirill

On Dec 11, 2007 1:09 AM, Kirill Korotaev <dev@sw.ru> wrote:
> > Does 2.6.24-ovz use the namespace code parts merged in 2.6.24?
>
> Sure. We even backport these patches back to our branch to use and test it.

What will happen with 2.6.22? Will it become stable branch or will die
like 2.6.20?

> > Is there any target for an OpenVZ merge into mainline (or at least a
> > merge of the network parts)?
>
> I think it's hard to predict exactly...
>
> Our current plan is to have IPv4/routing/rules virtualization in a 1-2 months,
> IPv6 should go faster after that (~1 month).
> Then vlan, tun/tap, netfilters and other features.

>From Kir's mail we assume that 2.6.24 soon will be released and marked
as 'development'. And is there any plan about when it will be stable
or something like that?


-- 
Regards
Dulmandakh

DULMANDAKH Sukhbaatar wrote:
> On Dec 11, 2007 1:09 AM, Kirill Korotaev <dev@sw.ru> wrote:
> 
>>>Does 2.6.24-ovz use the namespace code parts merged in 2.6.24?
>>
>>Sure. We even backport these patches back to our branch to use and test it.
> 
> 
> What will happen with 2.6.22? Will it become stable branch or will die
> like 2.6.20?

will die.

>>>Is there any target for an OpenVZ merge into mainline (or at least a
>>>merge of the network parts)?
>>
>>I think it's hard to predict exactly...
>>
>>Our current plan is to have IPv4/routing/rules virtualization in a 1-2 months,
>>IPv6 should go faster after that (~1 month).
>>Then vlan, tun/tap, netfilters and other features.
> 
> 
>>From Kir's mail we assume that 2.6.24 soon will be released and marked
> as 'development'. And is there any plan about when it will be stable
> or something like that?

the goal is to have it stable for Ubuntu TLS release, so it's around Februrary 2008.

Thanks,
Kirill

> the goal is to have it stable for Ubuntu TLS release, so it's around Februrary 2008.

it would be great. Someone is already working on it. You can see it
from https://wiki.ubuntu.com/ServerTeam/HardyIdeaPool .

-- 
Regards
Dulmandakh

DULMANDAKH Sukhbaatar wrote:
>>the goal is to have it stable for Ubuntu TLS release, so it's around Februrary 2008.
> 
> 
> it would be great. Someone is already working on it. You can see it
> from https://wiki.ubuntu.com/ServerTeam/HardyIdeaPool .

thanks! will definetely contact him!

Kirill