Created attachment 360068 [details]
strace log

what should be done to ensure this?

Hi gleb

for the NMI filtering. any other expected testing besides restarting ?


Thanks 
Lijun Huang

(In reply to comment #15)
> Hi gleb
> 
> for the NMI filtering. any other expected testing besides restarting ?
AFAIK kdump uses nmi. You can try that.

Test this problem with kvm-83-105.el5_4.4 in AMD host:

1. 
1)Start windows guest by:
/usr/libexec/qemu-kvm -rtc-td-hack -no-hpet -usbdevice tablet -cpu qemu64,+sse2 -drive file=win08-r2.raw,if=virtio,boot=on -smp 2 -m 2G -name win08-r2 -net nic,macaddr=20:20:20:11:42:77,model=e1000,vlan=0 -net tap,script=/etc/qemu-ifup,vlan=0 -vnc :2
2)type nmi 0 in the monitor

Actual result:
windows guest got BSOD.

2.
1)Start linux guest by:
/usr/libexec/qemu-kvm -rtc-td-hack -no-hpet -usbdevice tablet -cpu qemu64,+sse2 -drive file=RHEL-Server-5.4-64-virtio.qcow2,if=ide -smp 2 -m 2G -name rhel54-64 -net nic,macaddr=20:20:20:11:42:66,model=e1000,vlan=0 -net tap,script=/etc/qemu-ifup,vlan=0 -vnc :2
2)type nmi 0 in the monitor

Actual result:
grep NMI /cat/interrupts
NMI:      1        0

3.
Restart win2008R2 DC guest for 10 times, all restart sucess.
cmd:
/usr/libexec/qemu-kvm -rtc-td-hack -no-hpet -usbdevice tablet -cpu qemu64,+sse2 -drive file=win28k-r2-virtio.raw,if=virtio,boot=on -smp 2 -m 2G -name win28k-r2-virtio -net nic,macaddr=20:20:20:11:42:77,model=e1000,vlan=0 -net tap,script=/etc/qemu-ifup,vlan=0 -vnc :2

Base on above test, NMI can be received by guest in AMD host.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2009-1465.html

*** Bug 552531 has been marked as a duplicate of this bug. ***