Much of this developer documentation provides historical context but may not reflect the current state of the project.
If you see outdated content please navigate to the page footer and click "Report an issue on GitHub".

It is not user documentation and should not be treated as such.

User Documentation is available here.

Watchdog Device

VDSM side

1) support watchdog device

A virtual hardware watchdog device can be added to the guest via the the “devices” configuration. And only one watchdog device is supported for each VM.

When a watchdog device is active and take action, the vdsm will log this event.

The watchdog device requires an additional driver and management daemon in the guest. Just enabling the watchdog in the vdsm “devices” configuration does not do anything useful on its own.

model of watchdog:

The required model attribute specifies what real watchdog device is emulated. Valid values are specific to the underlying hypervisor.

  'i6300esb'    default model, emulating a PCI Intel 6300ESB
  'ib700'       emulating an ISA iBase IB700

action of watchdog timeout:

The optional action attribute describes what action to take when the watchdog expires. Valid values are specific to the underlying hypervisor.

  'reset'          forcefully reset the guest 
  'shutdown'       gracefully shutdown the guest (not recommended)
  'poweroff'       forcefully power off the guest
  'pause'          pause the guest
  'none'           default, do nothing
  'dump'           automatically dump the guest

The watchdog device can be used to detect guest crash or hang, and if ‘dump’ is chosen for the action of watchdog timeout, libvirt will dump guest’s memory on timeout automatically. And the directory to save dump files can be configured by auto_dump_path in file /etc/libvirt/qemu.conf.

you can add the watchdog to the vm parameter when create a vm as follow:

  import vdscli
  s = vdscli.connect()
  # add a wathdog device parameter
  dev_list = [{'device': 'watchdog', 'type': 'watchdog', 'specParams': {'model': 'i6300esb', 'action': "none"}}
               drives=[dict(poolID=spUUID, domainID=sdUUID, imageID=imgUUID, volumeID=volUUID)],
               memSize=256, display="vnc", vmName="vm1", devices = dev_list,)

This is aready implemented in vdsm.

2) report the watchdog event

There will be another patch to resolve that.

1. In the host level, vdsm should get the notification from libvirt, and report it in the vm stats.

A flag in vm stats indicate the event happened and what action was taken. Then engine could find it by polling vm’s stats.

Maybe this is not a good way for a watchdog event. But simple.

The problem is that when and how to clean this flag shoule be clean? if clean this flag once it is read, only one rpc client can get the watchdog event.

  import vdscli
  s = vdscli.connect()
  # poll vm's stats to check a wathdog event 
  while True:
      stat = getVmStats(vmId)
      # stats = getAllVmStats()
      # watchdogEvent is opptional.  It depends on watchdog device was added.  
      if hasattr(stat, 'watchdogEvent'):
          print stat['watchdogEvent']


There is not a event channel in vdsm.

If add an event register mechanism. This is a big work.

Engine side

See: Watchdog engine support feature