From: Philipp Hahn <hahn@univention.de>
To: lejeczek <peljasz@yahoo.co.uk>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] how to setup a watchdog?
Date: Wed, 20 Jan 2016 07:37:53 +0100 [thread overview]
Message-ID: <569F2B41.1080109@univention.de> (raw)
In-Reply-To: <569CCFC6.60909@yahoo.co.uk>
Hi,
Am 18.01.2016 um 12:43 schrieb lejeczek:
> I'm trying Qemu's watchdog.
> My understanding was that hardware (here qemu's watchdog) would take
> action, eg. cold 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, right?
>
> I have this in the guest:
>
> <watchdog model='i6300esb' action='reset'>
> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
> </watchdog>
>
> and I see /dev/watchdog in my guest. Yet nothing happens, guest(linux)
> runs uninterrupted.
> I must be missing something, an expert said it's config problem, is it
> really is?
Probably reading linux/Documentation/watchdog/watchdog-api.txt should
give you some extra hints.
AFAIK you need to open that device file at least once, either with the
sample program included in the Linux source tree, or by another program
like (Debian) watchdog or systemd (man 5 systemd-system.conf ->
RuntimeWatchdogSec)
cat /dev/watchdog # will print an error about the read(), but the
important thing (opening the file) has been done
dmesg | grep watchdog # will print "i6300esb: Unexpected close, not
stopping watchdog!" to show you that the watchdog is still running and
will trigger the reboot, as it has gone through the shutdown protocol,
which can be used to disable the watchdog again
After ~1m my test VM rebooted.
Philipp
next prev parent reply other threads:[~2016-01-20 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 11:43 [Qemu-devel] how to setup a watchdog? lejeczek
2016-01-20 6:37 ` Philipp Hahn [this message]
2016-01-30 11:42 ` Richard W.M. Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=569F2B41.1080109@univention.de \
--to=hahn@univention.de \
--cc=peljasz@yahoo.co.uk \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).