WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] xen-wdt questions

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] xen-wdt questions
From: Laszlo Ersek <lersek@xxxxxxxxxx>
Date: Wed, 05 Oct 2011 15:08:40 +0200
Cc: Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Wed, 05 Oct 2011 06:08:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110817 Fedora/3.1.12-1.fc14 Lightning/1.0b3pre Mnenhy/0.8.4 Thunderbird/3.1.12
Hi,

I tried to test xen-wdt (as of 066d6c7) with
Documentation/watchdog/src/watchdog-test.c:

(1) when the test tool is invoked as "./watchdog-test -d", it exercises
WDIOC_SETOPTIONS/WDIOS_DISABLECARD, prints "Watchdog card disabled.",
and then closes /dev/watchdog.

That ioctl stops the watchdog alright via the hypercall and zeroes out
the guets's "wdt", but in repsonse to the closure (since
"expect_release" is not set) the xen_wdt_release() function prints a
critical message to the console ("unexpected close, not stopping
watchdog!"), and tries to kick it again. (At this time the guest's
wdt.id is 0, and so xen_wdt_kick() returns -ENXIO, but xen_wdt_release()
ignorese it.) The watchdog is stopped for real and the domain is not
killed, but the KERN_CRIT message could be misleading.

(2) Additionally, the WDIOC_SETOPTIONS/WDIOS_DISABLECARD ioctl manages
to turn off the watchdog, even if nowayout=1 was passed to the xen-wdt
module. Is that intentional?

Thanks
Laszlo

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>