You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Sailaja Mada <sa...@citrix.com> on 2013/07/12 10:11:24 UTC
[ACS 4.2 with KVM 6.2]System VM's are failed to start with
'LibvirtException: internal error unknown timer name 'kvmclock'
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
RE: [ACS 4.2 with KVM 6.2]System VM's are failed to start with
'LibvirtException: internal error unknown timer name 'kvmclock'
Posted by Sailaja Mada <sa...@citrix.com>.
[root@rhel19 ~]# cat /etc/issue
Red Hat Enterprise Linux Server release 6.2 (Santiago)
Kernel \r on an \m
[root@rhel19 ~]# virsh --version
0.9.4
[root@rhel19 ~]# rpm -qa | grep qemu
qemu-img-0.12.1.2-3.209.el6.4.x86_64
gpxe-roms-qemu-0.9.7-6.9.el6.noarch
qemu-kvm-0.12.1.2-3.209.el6.4.x86_64
[root@rhel19 ~]#
Thanks,
Sailaja.M
-----Original Message-----
From: Prasanna Santhanam [mailto:tsp@apache.org]
Sent: Friday, July 12, 2013 2:24 PM
To: dev@cloudstack.apache.org
Subject: Re: [ACS 4.2 with KVM 6.2]System VM's are failed to start with 'LibvirtException: internal error unknown timer name 'kvmclock'
On Fri, Jul 12, 2013 at 08:45:43AM +0000, Sailaja Mada wrote:
> I tried with 4.2 new template.
> (systemvmtemplate-2013-06-25-master-kvm.qcow2.bz2)
Output of the following?
[root@apache-83-1 ~]# cat /etc/issue
[root@apache-83-1 ~]# virsh --version
0.10.2
[root@apache-83-1 ~]# rpm -qa | grep qemu
qemu-img-0.12.1.2-2.355.0.1.el6.centos.5.x86_64
qemu-kvm-0.12.1.2-2.355.0.1.el6.centos.5.x86_64
gpxe-roms-qemu-0.9.7-6.9.el6.noarch
[root@apache-83-1 ~]# rpm -qa | grep agent
cloudstack-agent-4.2.0-SNAPSHOT.el6.x86_64
--
Prasanna.,
------------------------
Powered by BigRock.com
Re: [ACS 4.2 with KVM 6.2]System VM's are failed to start with
'LibvirtException: internal error unknown timer name 'kvmclock'
Posted by Prasanna Santhanam <ts...@apache.org>.
On Fri, Jul 12, 2013 at 08:45:43AM +0000, Sailaja Mada wrote:
> I tried with 4.2 new template.
> (systemvmtemplate-2013-06-25-master-kvm.qcow2.bz2)
Output of the following?
[root@apache-83-1 ~]# cat /etc/issue
[root@apache-83-1 ~]# virsh --version
0.10.2
[root@apache-83-1 ~]# rpm -qa | grep qemu
qemu-img-0.12.1.2-2.355.0.1.el6.centos.5.x86_64
qemu-kvm-0.12.1.2-2.355.0.1.el6.centos.5.x86_64
gpxe-roms-qemu-0.9.7-6.9.el6.noarch
[root@apache-83-1 ~]# rpm -qa | grep agent
cloudstack-agent-4.2.0-SNAPSHOT.el6.x86_64
--
Prasanna.,
------------------------
Powered by BigRock.com
RE: [ACS 4.2 with KVM 6.2]System VM's are failed to start with
'LibvirtException: internal error unknown timer name 'kvmclock'
Posted by Sailaja Mada <sa...@citrix.com>.
Hi,
Edison applied the patch provided by you today to use as a temporary workaround .
I will try with latest builds and update the details .
Thanks,
Sailaja.M
-----Original Message-----
From: Wei ZHOU [mailto:ustcweizhou@gmail.com]
Sent: Friday, July 12, 2013 2:26 PM
To: dev@cloudstack.apache.org
Subject: Re: [ACS 4.2 with KVM 6.2]System VM's are failed to start with 'LibvirtException: internal error unknown timer name 'kvmclock'
Sailaja,
I think libvirt 0.10.2 is enough. You can get the RPMS from CentOS 6.4 repositories http://isoredirect.centos.org/centos/6.4/os/x86_64/Packages/
Please tell us whether systemvms start successfully.
I changed something for CLOUDSTACK-2823 today.
-Wei
2013/7/12 Sailaja Mada <sa...@citrix.com>
> I tried with 4.2 new template.
> (systemvmtemplate-2013-06-25-master-kvm.qcow2.bz2)
>
> -----Original Message-----
> From: Prasanna Santhanam [mailto:tsp@apache.org]
> Sent: Friday, July 12, 2013 2:02 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [ACS 4.2 with KVM 6.2]System VM's are failed to start
> with
> 'LibvirtException: internal error unknown timer name 'kvmclock'
>
> 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(Lib
> virtComputingResource.java:1126)
> > at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(Lib
> virtComputingResource.java:3293)
> > at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequ
> est(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.j
> ava: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
>
>
Re: [ACS 4.2 with KVM 6.2]System VM's are failed to start with
'LibvirtException: internal error unknown timer name 'kvmclock'
Posted by Wei ZHOU <us...@gmail.com>.
Sailaja,
I think libvirt 0.10.2 is enough. You can get the RPMS from CentOS 6.4
repositories
http://isoredirect.centos.org/centos/6.4/os/x86_64/Packages/
Please tell us whether systemvms start successfully.
I changed something for CLOUDSTACK-2823 today.
-Wei
2013/7/12 Sailaja Mada <sa...@citrix.com>
> I tried with 4.2 new template.
> (systemvmtemplate-2013-06-25-master-kvm.qcow2.bz2)
>
> -----Original Message-----
> From: Prasanna Santhanam [mailto:tsp@apache.org]
> Sent: Friday, July 12, 2013 2:02 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [ACS 4.2 with KVM 6.2]System VM's are failed to start with
> 'LibvirtException: internal error unknown timer name 'kvmclock'
>
> 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
>
>
RE: [ACS 4.2 with KVM 6.2]System VM's are failed to start with
'LibvirtException: internal error unknown timer name 'kvmclock'
Posted by Sailaja Mada <sa...@citrix.com>.
I tried with 4.2 new template. (systemvmtemplate-2013-06-25-master-kvm.qcow2.bz2)
-----Original Message-----
From: Prasanna Santhanam [mailto:tsp@apache.org]
Sent: Friday, July 12, 2013 2:02 PM
To: dev@cloudstack.apache.org
Subject: Re: [ACS 4.2 with KVM 6.2]System VM's are failed to start with 'LibvirtException: internal error unknown timer name 'kvmclock'
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
Re: [ACS 4.2 with KVM 6.2]System VM's are failed to start with
'LibvirtException: internal error unknown timer name 'kvmclock'
Posted by Prasanna Santhanam <ts...@apache.org>.
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