Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1720181

Summary: sometimes system_powerdown cause RHEL.8.1 guest kernel panic
Product: Red Hat Enterprise Linux Advanced Virtualization Reporter: FuXiangChun <xfu>
Component: qemu-kvmAssignee: Bandan Das <bdas>
Status: CLOSED DUPLICATE QA Contact: FuXiangChun <xfu>
Severity: high Docs Contact:
Priority: high    
Version: 8.1CC: bdas, chayang, jinzhao, juzhang, lijin, pezhang, ribarry, virt-maint, yfu
Target Milestone: rc   
Target Release: 8.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-29 08:34:27 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:
Embargoed:
Attachments:
Description Flags
vmcore-dmesg none

Description FuXiangChun 2019-06-13 10:29:19 UTC 
Description of problem:
Boot RHEL8.1.0 guest. Then switch runlevel 5 to 3.  Executed system_powerdown command. Sometimes RHEL8.1 guest kernel panic

Version-Release number of selected component (if applicable):
guest kernel:4.18.0-104.el8.x86_64
host kernel:4.18.0-100.el8.x86_64
qemu-kvm-4.0.0-4.module+el8.1.0+3356+cda7f1ee.x86_64


How reproducible:
1/10

Steps to Reproduce:
1.
/usr/libexec/qemu-kvm \
-name 'avocado-vt-vm1' \
-machine pc  \
-nodefaults \
-device qxl-vga,bus=pci.0,addr=0x2 \
-device pci-bridge,id=pci_bridge,bus=pci.0,addr=0x3,chassis_nr=1 \
-device intel-hda,bus=pci.0,addr=0x4 \
-device hda-duplex  \
-chardev socket,id=qmp_id_qmpmonitor1,path=/var/tmp/avocado_gkcvu_p_/monitor-qmpmonitor1-20190612-173229-PgpDZMcq,server,nowait \
-mon chardev=qmp_id_qmpmonitor1,mode=control  \
-chardev socket,id=qmp_id_catch_monitor,path=/var/tmp/avocado_gkcvu_p_/monitor-catch_monitor-20190612-173229-PgpDZMcq,server,nowait \
-mon chardev=qmp_id_catch_monitor,mode=control \
-device pvpanic,ioport=0x505,id=idobJiO3  \
-chardev socket,id=serial_id_serial0,path=/var/tmp/avocado_gkcvu_p_/serial-serial0-20190612-173229-PgpDZMcq,server,nowait \
-device isa-serial,chardev=serial_id_serial0 \
-device virtio-serial-pci,id=virtio_serial_pci0,bus=pci.0,addr=0x5 \
-chardev socket,server,id=id3JksuC,path=/var/tmp/avocado_gkcvu_p_/virtio_port-vs-20190612-173229-PgpDZMcq,nowait \
-device virtserialport,id=idz4ZbQX,name=vs,bus=virtio_serial_pci0.0,chardev=id3JksuC \
-object rng-random,filename=/dev/random,id=passthrough-u5l6QO8M \
-device virtio-rng-pci,id=virtio-rng-pci-zD2CVg1F,rng=passthrough-u5l6QO8M,bus=pci.0,addr=0x6  \
-chardev socket,id=seabioslog_id_20190612-173229-PgpDZMcq,path=/var/tmp/avocado_gkcvu_p_/seabios-20190612-173229-PgpDZMcq,server,nowait \
-device isa-debugcon,chardev=seabioslog_id_20190612-173229-PgpDZMcq,iobase=0x402 \
-device ich9-usb-ehci1,id=usb1,addr=0x1d.7,multifunction=on,bus=pci.0 \
-device ich9-usb-uhci1,id=usb1.0,multifunction=on,masterbus=usb1.0,addr=0x1d.0,firstport=0,bus=pci.0 \
-device ich9-usb-uhci2,id=usb1.1,multifunction=on,masterbus=usb1.0,addr=0x1d.2,firstport=2,bus=pci.0 \
-device ich9-usb-uhci3,id=usb1.2,multifunction=on,masterbus=usb1.0,addr=0x1d.4,firstport=4,bus=pci.0 \
-device qemu-xhci,id=usb2,bus=pci.0,addr=0x7 \
-device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x8 \
-drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/home/kvm_autotest_root/images/rhel810-64-virtio-scsi.qcow2 \
-device scsi-hd,id=image1,drive=drive_image1 \
-device virtio-net-pci,mac=9a:3c:3d:3e:3f:40,id=idTMbze9,vectors=4,netdev=idRYIwi0,bus=pci.0,addr=0x9  \
-netdev tap,id=idRYIwi0,vhost=on \
-m 7168  \
-smp 8,maxcpus=8,cores=4,threads=1,sockets=2  \
-cpu 'Skylake-Server',+kvm_pv_unhalt \
-device usb-tablet,id=usb-tablet1,bus=usb2.0,port=1  \
-rtc base=utc,clock=host,driftfix=slew  \
-boot order=cdn,once=c,menu=off,strict=off  \
-no-hpet \
-enable-kvm  \
-watchdog i6300esb \
-watchdog-action reset \
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xa \
-monitor stdio \
-vnc :2 \


2.switch runlevel 5 to 3
#init 3
3.

Actual results:
someitmes guest kernel panic

Expected results:

works
Additional info:
Comment 1 FuXiangChun 2019-06-13 10:30:46 UTC 
Created attachment 1580207 [details]
vmcore-dmesg
Comment 2 FuXiangChun 2019-06-13 10:31:32 UTC 
I will test more kernel version later. and update test result to bz asap.
Comment 3 Yanan Fu 2019-06-13 10:56:34 UTC 
dmesg show :
[  141.691881] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

[  141.693560] CPU: 1 PID: 1 Comm: shutdown Kdump: loaded Not tainted 4.18.0-104.el8.x86_64 #1
[  141.695041] Hardware name: Red Hat KVM, BIOS 1.12.0-1.module+el8.1.0+3258+4c45705b 04/01/2014
[  141.696555] Call Trace:
[  141.697046]  dump_stack+0x5c/0x80
[  141.697658]  panic+0xe7/0x247
[  141.698214]  do_exit.cold.22+0x26/0x81
[  141.698893]  do_group_exit+0x3a/0xa0
[  141.699601]  __x64_sys_exit_group+0x14/0x20
[  141.700364]  do_syscall_64+0x5b/0x1b0
[  141.700842]  entry_SYSCALL_64_after_hwframe+0x65/0xca
[  141.701401] RIP: 0033:0x7f37ba0b2e4e
[  141.701800] Code: Bad RIP value.
[  141.702158] RSP: 002b:00007fff611d4d18 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7
[  141.702972] RAX: ffffffffffffffda RBX: 00007f37ba0bb530 RCX: 00007f37ba0b2e4e
[  141.703726] RDX: 000000000000007f RSI: 000000000000003c RDI: 000000000000007f
[  141.704449] RBP: 00007f37ba2c1e00 R08: 00000000000000e7 R09: 00007fff611d4c28
[  141.705173] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000002
[  141.705912] R13: 0000000000000001 R14: 00007f37ba2c1e30 R15: 0000000000000000


I guess, duplicate with bz 1717323.