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

ASF GitHub Bot commented on CLOUDSTACK-7472:
--------------------------------------------

GitHub user kishankavala opened a pull request:

    https://github.com/apache/cloudstack/pull/557

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

    kvmclock fix for LXC is not required after fixing CLOUDSTACK-8177

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kishankavala/cloudstack CLOUDSTACK-7472

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/557.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #557
    
----
commit 34e4e9a79cb90dd56bc89f59fcbd0ec0dee82287
Author: Kishan Kavala <kis...@apache.org>
Date:   2015-07-02T11:22:46Z

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

----


> Change cloudstack agent.properties file for rhel 7 to include 
> kvmclock.disable=true
> -----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7472
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7472
>             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: shweta agarwal
>            Assignee: Kishan Kavala
>            Priority: Critical
>             Fix For: 4.5.2
>
>
> We need to minimize manual steps that needs to be done after agent 
> installation so change cloudstack agent.properties file for rhel 7 to include 
> kvmclock.disable=true



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

Reply via email to