Are you using the latest systemm vm template or the one from 3.0.x? Try with the new template and let us know if this is still a problem.
On Fri, Jul 12, 2013 at 08:11:24AM +0000, Sailaja Mada wrote: > Hi, > > I have RHEL 6.2 KVM host with libvirt (0.9.4-23.el6). This is added to 4.2 > Cloudstack Management server. > > With this KVM host, system VM's are failed to start with error as: > > 2013-07-11 14:22:45,946 WARN [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-1:null) LibvirtException > 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.startVM(LibvirtComputingResource.java:1126) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3293) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1222) > 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:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > > > ASF Dev list there is a suggestion to upgrade Libvirt version to 1.0.2 to > resolve this issue. I am getting into lot of dependency failures to upgrade > the libvirt version. > > Has any one tried this workaround? Will it cause for any issues to existing > environments(4.x /3.0.x with KVM 6.2) after upgrade to 4.2 ? > > Thanks, > Sailaja.M -- Prasanna., ------------------------ Powered by BigRock.com
