Description of problem: Based on specification on: http://www.ovirt.org/Features/Watchdog_engine_support VM after triggering watchdog (kill -9 `pgrep watchdog`) with action 'dump' should go to status pause. However VM stay in up status. This is officialy supported by libvirt based on: http://libvirt.org/formatdomain.html Version-Release number of selected component (if applicable): is10 How reproducible: 100% Steps to Reproduce: 1. Add Vm with watchdog 2. Set action to dump 3. Install Linux OS In VM run: 4. yum -y install watchdog 5. sed -i 's/#w/w/' /etc/watchdog.conf 6. service watchdog start 7. kill -9 `pgrep watchdog` Actual results: Vm stays in status up and dump file located in specified by: # grep ^auto_dump_path < /etc/libvirt/qemu.conf is created Aditional info: It is unclear if RHEVM should pause the VM by specification on ovirt wiki or go with the libvirt version.
Lukas, the paused mode is set by the device. Can you check what vdsm reports on this VM and also what libvirt reports?
Reproduced on upstream, the engine kicks it back to running state. Try it like this: - start a VM with i6300esb and pause - kill the watchdog process - immediately kill the engine - ssh to host - virsh (vdsm@ovirt shibboleth) - list - and see the Vm as paused
After some test, it turned out that it was not the engine that kicked back the VM to running state. Even when the engine is down, the VM goes back to running state. So if this is a bug, then it belongs to libvirt. Also, the default dump directory (/var/lib/libvirt/qemu/dump/) does not exist after fresh installation of libvirt, therfore the dumps are not created.
Created attachment 792259 [details] vdsm.log of actions adding VDSM.log of action starting the VM + 5 mins waiting for watchdog action to be triggered
Created attachment 792260 [details] engine.log of start VM action
Created attachment 792261 [details] engine.log of start VM action
Created attachment 792264 [details] vdsm.log of action dump
Created attachment 792265 [details] engine.log of action dumb sorry for so many reuploads got mixed logs from two bugs this should be fine now... nothing special appeared in engine.log so this might be an libvirt issue as laszlo suggested
https://bugzilla.redhat.com/show_bug.cgi?id=1004400 - the related libvirt bug
This behavior originates from libvirt. Re-open if there is engine-specific issues.