1192847 : NMI watchdog fails to increment the NMI counter in /proc/interrupts

All of lore.kernel.org
 help / color / mirror / Atom feed

From: chandrashekar shastri <cshastri@linux.vnet.ibm.com>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: 1192847 : NMI watchdog fails to increment the NMI counter in /proc/interrupts
Date: Thu, 20 Jun 2013 14:29:28 +0530	[thread overview]
Message-ID: <51C2C470.5080809@linux.vnet.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

Hi All,

I have filed the following bug for watchdog:

NMI watchdog fails to increment the NMI counter in /proc/interrupts

Kernel Version: 3.10.0-rc5+
Libvirt Version: 1.0.6
Qemu Version: 1.5.50

Steps to reproduce the issue:

1. Booted the VM with :
qemu-system-x86_64 VM1.qcow2 -enable-kvm -watchdog i6300esb 
-watchdog-action reset -smp 2 -m 2000
2. Edit the /boot/grub/grub/grub.conf with "nmi_watchdog = 1" before the 
initrd image.
3. Restart the guests, the NMI counter in /proc/interrupts was 0
4. Installed the watchdog rpm and ran chkconfig watchdog on
5. Restart the guest, even then the NMI counter did not increment
6. Changed the /boot/grub/grub/grub.conf with "nmi_watchdog = 1" to 
/boot/grub/grub/grub.conf with "nmi_watchdog = 2"
and restarted the guest. Even then NMI conuter did not increment (The 
NMI counter was showing 0 all the time for all the above steps).

Please let me know if I am missing some steps to test the NMI.

Thanks,
Shastri


[-- Attachment #2: Type: text/html, Size: 1472 bytes --]

WARNING: multiple messages have this Message-ID (diff)

From: chandrashekar shastri <cshastri@linux.vnet.ibm.com>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] 1192847 : NMI watchdog fails to increment the NMI counter in /proc/interrupts
Date: Thu, 20 Jun 2013 14:29:28 +0530	[thread overview]
Message-ID: <51C2C470.5080809@linux.vnet.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

Hi All,

I have filed the following bug for watchdog:

NMI watchdog fails to increment the NMI counter in /proc/interrupts

Kernel Version: 3.10.0-rc5+
Libvirt Version: 1.0.6
Qemu Version: 1.5.50

Steps to reproduce the issue:

1. Booted the VM with :
qemu-system-x86_64 VM1.qcow2 -enable-kvm -watchdog i6300esb 
-watchdog-action reset -smp 2 -m 2000
2. Edit the /boot/grub/grub/grub.conf with "nmi_watchdog = 1" before the 
initrd image.
3. Restart the guests, the NMI counter in /proc/interrupts was 0
4. Installed the watchdog rpm and ran chkconfig watchdog on
5. Restart the guest, even then the NMI counter did not increment
6. Changed the /boot/grub/grub/grub.conf with "nmi_watchdog = 1" to 
/boot/grub/grub/grub.conf with "nmi_watchdog = 2"
and restarted the guest. Even then NMI conuter did not increment (The 
NMI counter was showing 0 all the time for all the above steps).

Please let me know if I am missing some steps to test the NMI.

Thanks,
Shastri


[-- Attachment #2: Type: text/html, Size: 1472 bytes --]

next             reply	other threads:[~2013-06-20  8:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20  8:59 chandrashekar shastri [this message]
2013-06-20  8:59 ` [Qemu-devel] 1192847 : NMI watchdog fails to increment the NMI counter in /proc/interrupts chandrashekar shastri

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=51C2C470.5080809@linux.vnet.ibm.com \
    --to=cshastri@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.