[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571549#comment-15571549
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9397:
--------------------------------------------

GitHub user wido opened a pull request:

    https://github.com/apache/cloudstack/pull/1707

    CLOUDSTACK-9397: Add Watchdog timer to KVM Instance

    The watchdog timer adds functionality where the Hypervisor can detect if an
    instance has crashed or stopped functioning.
    
    When the Instance has the 'watchdog' daemon running it will send heartbeats
    to the /dev/watchdog device.
    
    If these heartbeats are no longer received by the HV it will reset the 
Instance.
    
    If the Instance never sends the heartbeats the HV does not take action. It 
only
    takes action if it stops sending heartbeats.
    
    This is supported since Libvirt 0.7.3 and can be defined in the XML format 
as
    described in the docs: 
https://libvirt.org/formatdomain.html#elementsWatchdog
    
    To the 'devices' section this will be added:
    
      <watchdog model='i6300esb' action='reset'/>
    
    In the agent.properties the action to be taken can be defined:
    
      vm.watchdog.action=reset
    
    The same goes for the model. The Intel i6300esb is however the most 
commonly used.
    
      vm.watchdog.model=i6300esb

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/wido/cloudstack watchdog-timer

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1707.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1707
    
----
commit 8046ba679be53abd7a70657d7f8ed00f2225cf46
Author: Wido den Hollander <w...@widodh.nl>
Date:   2016-05-31T09:31:27Z

    CLOUDSTACK-9397: Add Watchdog timer to KVM Instance
    
    The watchdog timer adds functionality where the Hypervisor can detect if an
    instance has crashed or stopped functioning.
    
    When the Instance has the 'watchdog' daemon running it will send heartbeats
    to the /dev/watchdog device.
    
    If these heartbeats are no longer received by the HV it will reset the 
Instance.
    
    If the Instance never sends the heartbeats the HV does not take action. It 
only
    takes action if it stops sending heartbeats.
    
    This is supported since Libvirt 0.7.3 and can be defined in the XML format 
as
    described in the docs: 
https://libvirt.org/formatdomain.html#elementsWatchdog
    
    To the 'devices' section this will be added:
    
      <watchdog model='i6300esb' action='reset'/>
    
    In the agent.properties the action to be taken can be defined:
    
      vm.watchdog.action=reset
    
    The same goes for the model. The Intel i6300esb is however the most 
commonly used.
    
      vm.watchdog.model=i6300esb

----


> Add Watchdog timer to KVM Instances
> -----------------------------------
>
>                 Key: CLOUDSTACK-9397
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9397
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: KVM
>            Reporter: Wido den Hollander
>            Assignee: Wido den Hollander
>              Labels: kvm, libvirt, watchdog
>
> A Watchdog timer can be used by the hypervisor to verify if an Instance is 
> still alive. If not, for example due to a kernel panic the HV can reset the 
> Instance so that it boots again.
> Inside the Instance the 'watchdog' daemon has to run to provide this. If the 
> Watchdog is not running the HV can't verify if the Instance has crashed.
> This is supported by Libvirt and Qemu and can be configured in the XML: 
> https://libvirt.org/formatdomain.html#elementsWatchdog



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to