Greetings - I'm happy to report that the feature "time:on" works exactly as hoped for in a CT
Jake On Tue, May 28, 2019 at 10:07 AM jjs - mainphrame <j...@mainphrame.com> wrote: > Thanks for this - > > I had a hardware failure and am down to one openvz server, so I don't want > to rock the boat. When the new box arrives this week, I'll migrate the CTs, > boot to the new kernel, try the sys_time capability and report back. > > Jake > > On Tue, May 28, 2019 at 2:57 AM Konstantin Khorenko < > khore...@virtuozzo.com> wrote: > >> On 05/21/2019 12:25 PM, Konstantin Khorenko wrote: >> > Hi Jake, Ming, >> > >> > i've created a feature request to reintroduce sys_time capability: >> > https://bugs.openvz.org/browse/OVZ-7096 >> > >> > It does not look too complicated, so hope it will be implemented. >> > >> > BTW, feel free to contribute. :) >> > IT worked in OpenVZ 6, need just to check the code of kernel and vzctl >> and port the patches. :) >> >> JFYI: the feature is ready (documentation is TBD), >> so you can use the feature, all you need is to update vzkernel and >> libvzctl from factory repo: >> vzkernel-3.10.0-957.12.2.vz7.96.6 >> libvzctl-7.0.521 >> >> https://download.openvz.org/virtuozzo/factory/x86_64/os/Packages/v/ >> https://download.openvz.org/virtuozzo/factory/x86_64/os/Packages/l/ >> >> Hope that helps. >> >> -- >> Best regards, >> >> Konstantin Khorenko, >> Virtuozzo Linux Kernel Team >> >> >> > On 05/20/2019 09:28 PM, jjs - mainphrame wrote: >> >> Hi Konstantin, >> >> >> >> Just wanted to follow up on the removal of capability sys_time - >> >> >> >> This change is rather disappointing, because it means that virtuozzo >> containers can no longer be used in the role they played in the past and >> the management will likely just order >> >> them replaced by VMware instances when it's time for hardware refresh. >> >> >> >> Sure, it's not optimal to have multiple containers potentially >> adjusting the system time, but even if its a kludge, it was a very useful >> one. >> >> >> >> Jake >> >> >> >> >> >> >> >> On Thu, May 16, 2019 at 8:59 AM jjs - mainphrame <j...@mainphrame.com >> <mailto:j...@mainphrame.com>> wrote: >> >> >> >> Hi Konstantin, >> >> >> >> With commercial Virtuozzo, we deployed containers to various lans, >> where each container served ntp, among other things.The host itself is >> isolated. >> >> Removal of this capability brings about a dead end scenario. Is >> there some other way to accomplish the ntp server duties moving forward? >> >> >> >> Jake >> >> >> >> >> >> On Thu, May 16, 2019 at 5:19 AM Konstantin Khorenko < >> khore...@virtuozzo.com <mailto:khore...@virtuozzo.com>> wrote: >> >> >> >> On 05/16/2019 02:29 PM, Nethub Online - Ming wrote: >> >> > Hi Konstantin, >> >> > >> >> > It is because we want to setup a NTP server in CT, and then >> let other servers to update their system time via ntpdate from this CT. >> However after install NTP server in >> >> this CT, it >> >> > is unable to start NTP service. >> >> >> >> Hi again, >> >> >> >> thank you, the usecase is understandable. >> >> We usually just run ntp clients on all hosts and don't face >> with time unsync in Containers, >> >> it's only a matter of one-time configuration of ntp service... >> >> >> >> -- >> >> Best regards, >> >> >> >> Konstantin Khorenko, >> >> Virtuozzo Linux Kernel Team >> >> >> >> > 於 2019年5月16日 下午5:25,"Konstantin Khorenko" < >> khore...@virtuozzo.com <mailto:khore...@virtuozzo.com> <mailto: >> khore...@virtuozzo.com <mailto:khore...@virtuozzo.com>>> >> >> 寫道: >> >> > >> >> > On 05/15/2019 05:11 AM, Nethub Online - Ming wrote: >> >> > > Hi all, >> >> > > >> >> > > In OpenVZ 6 users guide ( >> https://download.openvz.org/doc/OpenVZ-Users-Guide.pdf ), it allows me >> to change hardware node system time from container by command >> >> "vzctl set 101 >> >> > > --capability sys_time:on --save" >> >> > > >> >> > > However I found that there is no such parameter for >> vzctl or prlctl under OpenVZ 7, may I know how to change hardware node >> system time from CT under OpenVZ 7? >> >> > >> >> > Hi, >> >> > >> >> > no way at the moment and you are the first who ask for >> it. >> >> > Why do you need it? >> >> > What it your usecase? >> >> > >> >> > Thank you. >> >> > >> >> > -- >> >> > Best regards, >> >> > >> >> > Konstantin Khorenko, >> >> > Virtuozzo Linux Kernel Team >> >> > >> >> > _______________________________________________ >> >> > Users mailing list >> >> > Users@openvz.org <mailto:Users@openvz.org> <mailto: >> Users@openvz.org <mailto:Users@openvz.org>> >> >> > https://lists.openvz.org/mailman/listinfo/users >> >> > >> >> > >> >> > >> >> > _______________________________________________ >> >> > Users mailing list >> >> > Users@openvz.org <mailto:Users@openvz.org> >> >> > https://lists.openvz.org/mailman/listinfo/users >> >> > >> >> >> >> _______________________________________________ >> >> Users mailing list >> >> Users@openvz.org <mailto: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 >> > >> >> _______________________________________________ >> 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