You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "edison su (JIRA)" <ji...@apache.org> on 2014/01/03 20:47:50 UTC

[jira] [Resolved] (CLOUDSTACK-5574) KVM - HA - one of the Vms failed to start on another host when the host that it was running on was shutdown.

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

edison su resolved CLOUDSTACK-5574.
-----------------------------------

    Resolution: Won't Fix

KVM itself reports error that can't start the vm, seems nothing we can do for it. Maybe we can reproduce it and grab more kvm logs, to future identify the issue.

> KVM - HA - one of the Vms failed to start on another host when the host that it was running on was shutdown.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5574
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5574
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>         Environment: Build from 4.3
>            Reporter: Sangeetha Hariharan
>            Assignee: edison su
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> KVM - HA - one of the Vms failed to start on another host when the host that it was running on was shutdown.
> Set up:
> Advanced zone with 2 KVM hosts (RHEL 6.3).
> Had 5 user Vms running on each host.
> Shutdown host1 ( execute  echo o > /proc/sysrq-trigger on host)
> All VMs from host1 , get HA-ed to host2.
> Bring host1 up.
> Shutdown host2. (  execute  echo o > /proc/sysrq-trigger on host)
> All VMs from host2 get HA-ed to host2 , except for 1 user Vm.
> It encounters the following exception in the agent logs when management server tries to start this Vm as part of HA process.
> 2013-12-19 13:32:56,997 WARN  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) LibvirtException
> org.libvirt.LibvirtException: internal error Process exited while reading console log output:
>         at org.libvirt.ErrorHandler.processError(Unknown Source)
>         at org.libvirt.Connect.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:1188)
>         at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3594)
>         at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1282)
>         at com.cloud.agent.Agent.processRequest(Agent.java:498)
>         at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:806)
>         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)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)