cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus Sorensen <shadow...@gmail.com>
Subject Re: [jira] [Commented] (CLOUDSTACK-4012) [UPGRADE]System VMs and VRs failed to start using KVM host after upgrading from 3.0.6 to 4.2.
Date Mon, 05 Aug 2013 18:08:19 GMT
org.libvirt.LibvirtException: internal error unknown timer name 'kvmclock'

I've been waiting to hear what platforms will be supported in 4.2
before committing '0fa108f03895e83ccc5d4c81e058ea8f424663b9' to 4.2.
We eventually want this code, as it's a critical fix for system vm
clocks, but specifically the now long-in-tooth Ubuntu 12.04 doesn't
support this libvirt feature. I assume we will continue to support
12.04 until 14.04 comes out, so we should probably revert it in 4.2 as
well.

On Mon, Aug 5, 2013 at 12:04 PM, Kishan Kavala (JIRA) <jira@apache.org> wrote:
>
>     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729733#comment-13729733
]
>
> Kishan Kavala commented on CLOUDSTACK-4012:
> -------------------------------------------
>
> Could be a system Vm template issue.
>
> Related discussion:
> http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201307.mbox/%3C2AC317E9E0682749A5A8A3C9939AE003064152CC@SINPEX01CL02.citrite.net%3E
>
> Related bugs:
> CLOUDSTACK-2871
> CLOUDSTACK-2823
>
>> [UPGRADE]System VMs  and VRs failed to start using KVM host after upgrading  from
3.0.6 to 4.2.
>> -----------------------------------------------------------------------------------------------
>>
>>                 Key: CLOUDSTACK-4012
>>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4012
>>             Project: CloudStack
>>          Issue Type: Bug
>>      Security Level: Public(Anyone can view this level - this is the default.)
>>          Components: KVM, Upgrade
>>    Affects Versions: 4.2.0
>>         Environment: KVM host--Upgrade from 3.0.6 to 4.2
>>            Reporter: manasaveloori
>>            Assignee: Kishan Kavala
>>            Priority: Blocker
>>             Fix For: 4.2.0
>>
>>         Attachments: agent.log, management-server.log, mysqldump1.dmp, mysqldumpafterUpgrade.dmp,
mysqldumpusage1.dmp
>>
>>
>> Steps:
>> 1.    Have a CS 3.0.6 patchE with KVM and Xen hypervisors(both Advanced zones).
>> 2.    Add the external devices F5,SRX,Netscaler to CS.
>> 3.    Delpoy VMs and create firewall,LB rules  using the external devices.
>> 4.    Upgrade to 4.2 build.
>> Observed that the system VMs failed to start with KVM host.
>> After running the cloudstack-sysvmadm script the System VMs and VRs failed to start.
>> Observing the agent logs,it show following exception
>> 013-08-01 17:41:02,158 WARN  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2: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:1128)
>>         at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3295)
>>         at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1224)
>>         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)
>> Attaching the Ms logs,Db dumps and agent logs.
>
> --
> 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

Mime
View raw message