Bug 1383878

Summary: [ppc64le]when stress guest via stress tool,report:"kernel:NMI watchdog: BUG: soft lockup - CPU#5"
Product: Red Hat Enterprise Linux 7 Reporter: xianwang <xianwang>
Component: qemu-kvm-rhevAssignee: David Gibson <dgibson>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: dgibson, knoel, qzhang, virt-maint, xianwang, zhengtli
Target Milestone: rc   
Target Release: ---   
Hardware: ppc64le   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-12 21:34:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg none

Description xianwang 2016-10-12 03:36:42 UTC
Created attachment 1209425 [details]
dmesg

Description of problem:
Boot a guest, tress guest via stress tool with command"stress --cpu 1 --io 1 --vm 1 --vm-bytes 512M",then reports:"kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 119s! [stress:8110]"

Version-Release number of selected component (if applicable):
Host install tree: RHEL7.3-20161005.0
kernel: kernel-3.10.0-512.el7
qemu: qemu-kvm-rhev-2.6.0-27.el7
SLOF: SLOF-20160223-6.gitdbbfda4.el7

Guest: RHEL7.3 BE guest with RHEL7.3-20161005.0 tree
driveformat: virtio_scsi
nicmodel: virtio_net
mem: 16G
vcpu: 16

How reproducible:
3/3

Steps to Reproduce:
1.boot a guest with qcow2 disk
2.ssh guest, then stress guest via stress tool with command"stress --cpu 1 --io 1 --vm 1 --vm-bytes 512M"

Actual results:
report message on terminal:
[root@dhcp112-232 ~]# stress --cpu 1 --io 1 --vm 1 --vm-bytes 512M
stress: info: [8109] dispatching hogs: 1 cpu, 1 io, 1 vm, 0 hdd
Message from syslogd@dhcp112-232 at Oct 11 22:54:21 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 119s! [stress:8110]
Message from syslogd@dhcp112-232 at Oct 11 23:02:09 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 134s! [stress:8110]
Message from syslogd@dhcp112-232 at Oct 11 23:02:49 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#6 stuck for 355s! [stress:8112]
Message from syslogd@dhcp112-232 at Oct 11 23:03:01 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#15 stuck for 354s! [swapper/15:0]
Message from syslogd@dhcp112-232 at Oct 11 23:06:05 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#6 stuck for 338s! [stress:8112]

Expected results:
it should not report the bug message above

Additional info:
the full qemu command is as follows:
/usr/libexec/qemu-kvm \
    -name 'avocado-vt-vm1'  \
    -sandbox off  \
    -nodefaults  \
    -machine pseries-rhel7.3.0 \
    -vga std  \
    -device virtio-serial-pci,id=virtio_serial_pci0,bus=pci.0,addr=03 \
    -device virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x4 \
    -chardev socket,id=devorg.qemu.guest_agent.0,path=/tmp/virtio_port-org.qemu.guest_agent.0-20160516-164929-dHQ00mMM,server,nowait \
    -device virtserialport,chardev=devorg.qemu.guest_agent.0,name=org.qemu.guest_agent.0,id=org.qemu.guest_agent.0,bus=virtio_serial_pci0.0  \
    -chardev socket,id=console0,path=/tmp/console0,server,nowait \
    -device spapr-vty,chardev=console0 \
    -device ich9-usb-ehci1,id=usb1,addr=1d.7,multifunction=on,bus=pci.0 \
    -drive file=/root/RHEL7.3.qcow2,if=none,id=blk1,cache=writethrough \
    -device virtio-blk-pci,scsi=off,drive=blk1,id=blk-disk1,bootindex=1 \
    -drive id=drive_cd1,if=none,snapshot=off,aio=native,cache=none,media=cdrom,file=/root/RHEL7.3.iso \
    -device scsi-cd,id=cd1,drive=drive_cd1,bootindex=2 \
    -device virtio-net-pci,mac=9a:7b:7c:7d:7e:71,id=idtlLxAk,vectors=4,netdev=idlkwV8e,bus=pci.0,addr=05 \
    -netdev tap,id=idlkwV8e,vhost=on,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown \
    -m 16G \
    -smp 16 \
    -cpu host \
    -device usb-kbd \
    -device usb-mouse \
    -qmp tcp:0:8881,server,nowait \
    -vnc :1  \
    -msg timestamp=on \
    -rtc base=localtime,clock=vm,driftfix=slew  \
    -boot order=cdn,once=c,menu=off,strict=off \
    -monitor stdio \
    -enable-kvm

Comment 2 Qunfang Zhang 2016-10-12 05:12:09 UTC
Xianxian,

What's the guest dmesg or console log? Is it similar with https://bugzilla.redhat.com/show_bug.cgi?id=1350719#c53?

Comment 3 Qunfang Zhang 2016-10-12 05:33:21 UTC
(In reply to Qunfang Zhang from comment #2)
> Xianxian,
> 
> What's the guest dmesg or console log? Is it similar with
> https://bugzilla.redhat.com/show_bug.cgi?id=1350719#c53?

Ignore it, attachment is there already.

Comment 4 David Gibson 2016-10-12 21:33:25 UTC
Looks like another dupe of bug 1350719.

Comment 5 David Gibson 2016-10-12 21:34:09 UTC

*** This bug has been marked as a duplicate of bug 1350719 ***