That's unfortunate, but I don't think many people will care. Pretty much everyone in virt uses ntp religiously and am yet to hear complains about clock performance in VMs.
Having said that, could the feature be enforceable through agent.properties if desired? Something like Rohit is suggesting with kvmclock.disable=false? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Marcus" <shadow...@gmail.com> > To: dev@cloudstack.apache.org > Sent: Friday, 6 February, 2015 06:45:14 > Subject: Re: [VOTE] Apache CloudStack 4.5.0 RC1 > I think we can wrap this in a version check as we have many other > things, that way Ubuntu 12.04 users who leverage newer libvirt > packages (as I'm temped to believe the majority of actual deployments > do) can still see the benefit, and we don't have to worry about > targeting a specific release. This will have the negative side effect > of not allowing centos 6.x people from leveraging their backported > support since their version numbers are deceptive, but it's probably > the smartest, most compatible way to indroduce it.
