Re: [Users] usage of swap on host server
Markus Hardiyanto a écrit : the problem is i'm starting to get error: fork: cannot allocate memory, and when it happens apache will show 500 internal server error and wont fix if i'm not stopping and starting it manually. any way to prevent this? I want the RAM allocation for the VE remains the same. Just to be sure, don't you have some resource limits hit for your VZ (have a look to /proc/user_beancounters)? If so, raising the faulty limit should help. -- Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve. ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
AW: AW: [Users] problems with vzctl init logging patch
Attached is the new patch. - Dietmar vzctl.diff Description: vzctl.diff ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] Mainstream progress?
Pavel, Please correct/enlarge me if there's anything missing/incorrect. Carl-Daniel Hailfinger wrote: Hi, the ongoing merge of OpenVZ-based lightweight virtualization into mainline Linux seems to be progressing nicely and I have a few questions about it: - How usable will net namespaces be in 2.6.25? I'm especially interested in assigning a real hardware ethernet device to a VE. I guess some network namespace stuff is NOT completed in upcoming 2.6.25 (a lot of stuff done, but not finished) For 2.6.26, it will be more-or-less working, with just a few exceptions such as conntracks and IPv6 -- maybe. - Will there be an OpenVZ patch or against 2.6.25? As of now we do not plan to have one. Porting to each mainstream version is too much work to do -- instead we concentrate on (1) merging stuff to mainstream (2) supporting our stable kernels (3) stabilizing 2.6.24 (for now) - Do you expect net namespace/virtualization work to be completely merged in 2.6.26? As said before, we guess that network namespaces will be more or less useable in 2.6.26. - Which OpenVZ features will not make it to mainline in the 2.6.26 timeframe? A lot. Network namespaces is just one piece of a pie. To paint in big strokes: resource management and live migration are still on our todo list. Resource management: some stuff is in -mm kernel, need to add much more. Will work on that after finishing with net namespaces. Live migration: this is much more far perspective, we haven't even started to discuss that seriously on containers@ list. Some of the questions above probably can't be answered without guessing, but a good guess is better than no information and I'd appreciate any status update newer than the OpenVZ blog entry from 2008-01-26. Thanks, Carl-Daniel ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
[Users] State of 2.6.24
Hi all, I just tested 2.6.24 with the new fairsched. Everything seems to works like expected - great. I wonder if openvz-2.6.24 is now feature complete, or is there still something missing? - Dietmar ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] Mainstream progress?
Kir Kolyshkin wrote: Pavel, Please correct/enlarge me if there's anything missing/incorrect. Carl-Daniel Hailfinger wrote: Hi, the ongoing merge of OpenVZ-based lightweight virtualization into mainline Linux seems to be progressing nicely and I have a few questions about it: - How usable will net namespaces be in 2.6.25? I'm especially interested in assigning a real hardware ethernet device to a VE. I guess some network namespace stuff is NOT completed in upcoming 2.6.25 (a lot of stuff done, but not finished) For 2.6.26, it will be more-or-less working, with just a few exceptions such as conntracks and IPv6 -- maybe. - Will there be an OpenVZ patch or against 2.6.25? As of now we do not plan to have one. Porting to each mainstream version is too much work to do -- instead we concentrate on (1) merging stuff to mainstream (2) supporting our stable kernels (3) stabilizing 2.6.24 (for now) 2.6.26 will be the next kernel we will port on. - Do you expect net namespace/virtualization work to be completely merged in 2.6.26? As said before, we guess that network namespaces will be more or less useable in 2.6.26. - Which OpenVZ features will not make it to mainline in the 2.6.26 timeframe? A lot. Network namespaces is just one piece of a pie. To paint in big strokes: resource management and live migration are still on our todo list. Resource management: some stuff is in -mm kernel, need to add much more. Will work on that after finishing with net namespaces. Memory management will change with 2.6.26. API will be kept, but we'll have a per-ve swapout and (probably) drop privvmpages accounting. Live migration: this is much more far perspective, we haven't even started to discuss that seriously on containers@ list. Some of the questions above probably can't be answered without guessing, but a good guess is better than no information and I'd appreciate any status update newer than the OpenVZ blog entry from 2008-01-26. Thanks, Carl-Daniel ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
