[jira] [Commented] (CLOUDSTACK-8177) Fix kvmclock for libvirt update

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696665#comment-14696665 ] 

ASF subversion and git services commented on CLOUDSTACK-8177:
-------------------------------------------------------------

Commit f54d266c8b6c6e0333eeaa0021861b28e1ea2360 in cloudstack's branch refs/heads/4.5 from [~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f54d266 ]

BUG-ID:CLOUDSTACK-7472: kvmclock fix for LXC is not required after fixing CLOUDSTACK-8177

This closes #557

(cherry picked from commit 3a19a8916eb7840302882cddd8465ac56150d32d)
Signed-off-by: Rohit Yadav <ro...@shapeblue.com>

Conflicts:
	plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java


> Fix kvmclock for libvirt update
> -------------------------------
>
>                 Key: CLOUDSTACK-8177
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8177
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.5.0
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>             Fix For: 4.5.0
>
>
> Newer libvirt builds disallow a tickpolicy parameter with the kvmclock timer. Previously it was allowed but apparently didn't do anything. We need to remove tickpolicy for kvmclock timer to be compatible with libvirt change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)