You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "terryye (JIRA)" <ji...@apache.org> on 2013/06/13 04:17:20 UTC
[jira] [Closed] (CLOUDSTACK-2871) internal error unknown timer name
'kvmclock'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
terryye closed CLOUDSTACK-2871.
-------------------------------
Resolution: Won't Fix
other bug report
> internal error unknown timer name 'kvmclock'
> --------------------------------------------
>
> Key: CLOUDSTACK-2871
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2871
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: KVM
> Affects Versions: 4.1.0
> Environment: ubuntu12.04
> Reporter: terryye
>
> 2013-06-06 09:23:16,766 WARN [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null) Exception
> org.libvirt.LibvirtException: internal error unknown timer name 'kvmclock'
> at org.libvirt.ErrorHandler.processError(Unknown Source)
> at org.libvirt.Connect.processError(Unknown Source)
> at org.libvirt.Connect.domainCreateXML(Unknown Source)
> at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startDomain(LibvirtComputingResource.java:986)
> at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3114)
> at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1102)
> at com.cloud.agent.Agent.processRequest(Agent.java:525)
> at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
> at com.cloud.utils.nio.Task.run(Task.java:83)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira