Hi Volker, yes, of course we do. They are, however, part of the company QA framework. Are you interested in testing these kernels on regular basis? I can check with the QA team how difficult it would be to extract them and use independently
-----Original Message----- From: users-boun...@openvz.org [mailto:users-boun...@openvz.org] On Behalf Of Volker Janzen Sent: Friday, November 04, 2016 2:31 AM To: OpenVZ users <users@openvz.org> Subject: Re: [Users] I've noticed a new 'readykernel' package Hi Andre, do you have test plans for kernels? Regards Volker Am 03.11.2016 um 22:17 schrieb Andre Moruga <amor...@virtuozzo.com>: >> Thanks for your instructions to get the latest patched vzkernel. >> Generally I don't want to run nightly kernel builds in production. >> Will the Dirty COW and future security patches make their way into >> stable OpenVZ 7 kernels soon after testing in nightly builds? (Same >> as with OpenVZ 6 stable kernel series?) > > Hi Frank, > I understand your concern; not yet sure if we can offer an immediate solution > though. > > Virtuozzo team uploads stable kernels for OpenVZ version 7, tested for our > commercial customers, approximately once a quarter. In between, we do not > test or release any kernels - all the intermediate updates are delivered to > our commercial customers in rebootless (kpatch) format without building full > kernel updates. Again, this is a part of our commercial offering. > > As for the contributions to the community product, we still build > these kernels for the "factory" repository. However, we are not equipped to > test them on regular basis, between these quarterly updates We do however > invite anyone from the OpenVZ community to contribute resources into testing > of these intermediate kernel updates - we will be more than happy to > cooperate and publish these kernels appropriately tagged as stable/community > tested. > > This time, due to the severity of the Dirty COW issue, we'll try to allocate > our own QA resources to test a kernel with that vulnerability fixed > specifically for OpenVZ. However, moving forward we definitely need a better > solution. > > So please consider it as open invitation and volunteering opportunity > to contribute into the project > > Thanks > Andre Moruga @ Virtuozzo Team > > > > _______________________________________________ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
