similar to: [PATCH] virtio: a new vcpu watchdog driver

On Mon, 31 Jul 2023 09:25:12 +0800, "zhanghao1" <zhanghao1 at kylinos.cn> wrote: > A new virtio pci driver is added for listening to vcpus > inside guest. Each vcpu creates a corresponding thread to > periodically send data to qemu's back-end watchdog device. > If a vCPU is in the stall state, data cannot be sent to > back-end virtio device. As a result, the

Hi, i''m not sure if i understood the new acpi xen cpufreq driver - here''s the output when loading xen_acpi_processor module in linux 3.4: dom0 dmesg: [ 32.728151] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU8 [ 32.728156] xen-acpi-processor: (CX): Hypervisor error (-22) for ACPI CPU9 [ 32.728160] xen-acpi-processor: (CX): Hypervisor error (-22) for

Hi all, I've got a Portwell NANO-6060 board I am testing out for potential use in a project of ours. One of the nice features of this board, beyond nice NICs, is that it has a hardware watchdog timer. The problem is that I don't get a /dev/watchdog device file. I know the hardware works, because when I enable it in BIOS, the box will reboot after the timer expires. However,

Dom0 uses this hypercall to pass ACPI information to Xen. It is not very uncommon for more cpus to be listed in the ACPI tables than are present on the system, particularly on systems with a common BIOS for a 2 and 4 socket server varients. As Dom0 does not control the number of entries in the ACPI tables, and is required to pass everything it finds to Xen, reduce the ERR to an INFO.

Good morning! On a CentOS 6.4 / 64 bit server I have installed the watchdog 5.5 package. The rpm -qi watchdog states: The watchdog program can be used as a powerful software watchdog daemon or may be alternately used with a hardware watchdog device such as the IPMI hardware watchdog driver interface to a resident Baseboard Management Controller (BMC). ... This configuration file is also used to

All, I have an GigaByte motherboard GA-M61P-S3 and I was wondering if any kernel watchdog processes will work with that? Jerry ----------------------------- /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/softdog.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/ibmasr.ko

Hello everybody, I''m implementing a qdisc for my MSc thesis and I''ve experienced some issue maybe you can help me with. The discipline is simply a slotted max-weight in which any user has a Ceil Rate they mustn''t trespass on. Being such a discipline non-work-conserving, I''ve to set a watchdog timer in order to allow further call of the dequeue function.

Hello all, In app_fax WATCHDOG_TOTAL_TIMEOUT is set to 30 minutes to kill a fax channel regardless of whether or not it completes. In my case I have a fax that really would take longer than 30 minutes to complete. Is there any way to disable the WATCHDOG_TOTAL_TIMEOUT so that it runs to completion? Thanks, Eric -------------- next part -------------- An HTML attachment was

> > Are you sure you are > > putting the apic= line on the *Xen* grub line, not Linux? > > > The contrary - I am sure that I put the acpi=off in the Linux > Kernel grub line and never even tried to use this on the xen > grub line! > > Does that make everything said in this thread invalid? Yes. The acpi= line must go on the *xen* command line, which will

Hi, Just for your information I had the tinc daemon dying on the main machine I use as a hub, so I looked for a script to restart the daemon it if dies. Here is tinc.sh: ========================================================== #!/bin/bash # Tinc Process Monitor # Restart Tinc daemon When It Goes Down # Source: http://bash.cyberciti.biz/web-server/restart-apache2-httpd-shell-script/

Author: wentaoy Repository: /hg/zfs-crypto/gate Revision: 30bcd690ede94fe16dd95b03178e85b537d48602 Log message: FWARC 2005/367 sun4v watchdog service API FWARC 2006/093 sun4v watchdog API update 6354584 Add watchdog timer support in sun4v Files: create: usr/src/uts/sparc/sys/wdt.h create: usr/src/uts/sun4v/os/wdt.c update: usr/src/uts/common/os/clock.c update: usr/src/uts/sun4/os/cpu_states.c

Yes, acpi=off seems to have decided my problem of instability. Soon, then I will be returning the HD in the machine in production and I dispatched by post the result. -- Leonardo Pinto listas#openlogic dot com br > The troubles went away when adding kernel options "noapic > acpi=off" to > the modules grub line. > > Both noapic and acpi=off make big difference to the

> Like I just mentioned in a different thread, I need to use > the ''noapic'' > options on both the PowerEdge models I''ve tried.. I''ll try to > build up a Xen vs. non-Xen kernel tomorrow or Tuesday and > grab a diff for you. Which PE models are they? We have quite a few different Dell PowerEdge models running 24x7 in the test lab, and

Hi, I have been trying to figure out why my Supermicro X7DWA-N with dual Xeon E5420''s locks up occasionally when running Xen, I''ve tried 3.2.1 and 3.3 with the Xensource 2.6.18 kernel, with gentoo 2.6.21, and 2.6.25 and 2.6.27 kernels patched with suse xen patches, every single combination suffers from occasional lockups :(, I am reasonably confident that the hardware is ok

Dear Developers, I've released a patch against openssh-2.5.2p2. The patch adds heartbeat (keepalive) function to ssh(1), and watchdog timeout function to sshd(8). The watchdog timeout is intended to terminate user's processes as soon as possible after the link has been lost. http://www.ecip.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html The combination of the heartbeat and the

The old CPU_CLK_UNHALTED performance counter no longer runs on Core or Core2 CPUs. Use the new CPU_CLK_UNHALTED.CORE_P one. Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

CentOS 6 Hi all, I am working on setting up sanlock + watchdog on a 2 node KVM pair. Sanlock is working beautifully and is preventing access to the VM disks by more than one process as it should across both boxes. I am attempting to test failure scenarios involving watchdog, but I am having a hard time getting it to actually reset the server. I am running wdmd with -D so I can see the

Apologies if this is posted on the wrong list, but when I try to get pci passthrough to work on a Wheezy Xen box I get NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out and then not much else works at all. The same hardware works just fine with Xen and Squeeze. It seemed to me that the problem I am seeing is very similar to

Hello, Hideaki Goto has written a patch for OpenSSH that adds heartbeat and watchdog functions to OpenSSH: http://www.sc.isc.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html The heartbeat function sends an SSH_MSG_IGNORE packet every <n> seconds to the server, and the watchdog function checks incoming packets only to see if the connection has been interrupted. Where I work, all Internet

I'm behind a watchdog firebox, which has recently blocked ssh out. I have it to where i can use port 21(the server forwards 21 to 22 that i am trying to connect to), but somehow the watchdog firewall is also blocking by protocol type? the only way i can connect is if i choose raw protocol in putty... and this is what i get SSH-1.99-OpenSSH_3.5p1 test Protocol