Hide Forgot
Description of problem: I have this in my guest: <watchdog model='i6300esb' action='reset'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </watchdog> and even though watchdog.service(with plain-vanilla config) is stopped the guess is fine, up & running. Is this expected? Version-Release number of selected component (if applicable): qemu-kvm-common-ev-2.3.0-29.1.el7.x86_64 qemu-kvm-ev-2.3.0-29.1.el7.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Since you are using centos, and this is really more of a config question than a bug, please take this to an upstream mailing list like libvirt-users But you say that watchdog.service is _stopped_ inside the VM... it needs to be running. There's some more info here: https://rwmj.wordpress.com/2010/03/03/what-is-a-watchdog/
sorry, my understanding was that hardware (here qemu's watchdog) would take action(reboot) the system if there is no ping from the OS watchdog, so I thought stopping watchdog service in VM should be a quick test. I'll check mailing list. Many thanks