Bug 1231600
Summary: | Guest can't be shutdown | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Yang Meng <meyang> | ||||
Component: | qemu-kvm | Assignee: | Laszlo Ersek <lersek> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.7 | CC: | chayang, juzhang, mkenneth, qzhang, rbalakri, virt-maint | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-07-07 20:06:43 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: |
|
I'm assuming this is not a regression and deferring it to 6.8. (In reply to Ademar Reis from comment #2) > I'm assuming this is not a regression and deferring it to 6.8. The reporter Yang Meng said that shutdown the rhel7 guest directly with "system_powerdown" instead with watchdog device, hit the same issue. The problem looks similar with the following bugs: Bug 980692 - gdm login screen in VMs: the ACPI power button should by default effect a shutdown Bug 907711 - fail to poweroff guest when do system_powerdown in HMP monitor after login guest Bug 1040307 - Qemu monitor "system_powerdown" command fail to power down guest Yes, this is a duplicate of bug 980692. I installed the exact host kernel and qemu-kvm-rhev versions noted in comment 0: - kernel: 2.6.32-565.el6.x86_64 - qemu-kvm-rhev-0.12.1.2-2.478.el6.x86_64 I also used the qemu command line from comment 0. The guest version is not specified in the bug report. From the qemu command line in comment 0, we can gather "RHEL-Server-7.2-64-virtio-scsi.raw" only. In any case, I reused an earlier RHEL-7 disk image of mine. I performed the following tests: (1) wait until the guest boots to the GDM login screen. Then, at the QEMU monitor, switch to a character console with "sendkey ctrl-alt-f2". Log in at the character console as root (in the guest window), and run the /dev/watchdog command stated in comment 0. Result: the guest shuts down all fine in 30 seconds. (30 seconds is the default heartbeat for i6300esb, see "Documentation/watchdog/watchdog-parameters.txt" in the kernel tree). (2) Same as test (1), but right after issuing the /dev/watchdog command in the guest root shell (and seeing the confirmation in the guest dmesg), switch back to the GDM GUI with the QEMU monitor command "sendkey ctrl-alt-f1". Result: shutdown never happens, guest continues running indefinitely. (3) Boot the guest afresh. Wait until the GDM login screen is shown. Issue "system_powerdown" at the QEMU console. Result: nothing happens. (4) Boot the guest afresh. Wait until the GDM login screen is shown. Enter the following two commands at the QEMU console (with a few seconds in between): sendkey ctrl-alt-f2 system_powerdown Results: after the first command, the character console (VT2) is shown. After the second command, the guest is shut down immediately, successfully. So yes, GDM inhibits shutdown. *** This bug has been marked as a duplicate of bug 980692 *** |
Created attachment 1038740 [details] screendump Description of problem: boot guest with watchdog device ,in guest issue "echo c > /dev/watchdog",guest will not shutdown Version-Release number of selected component (if applicable): kernel: kernel-2.6.32-565.el6.x86_64 qemu : qemu-kvm-rhev-0.12.1.2-2.478.el6.x86_64 How reproducible: easy to reproduce in my env 100% Steps to Reproduce: 1.boot guest with the cmdline: /usr/bin/qemu-kvm \ -S \ -name 'virt-tests-vm1' \ -M rhel6.6.0 \ -nodefaults \ -vga qxl \ -device AC97,bus=pci.0,addr=03 \ -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20150609-153354-uy9GdXPd,server,nowait \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ -chardev socket,id=qmp_id_catch_monitor,path=/tmp/monitor-catch_monitor-20150609-153354-uy9GdXPd,server,nowait \ -mon chardev=qmp_id_catch_monitor,mode=control \ -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20150609-153354-uy9GdXPd,server,nowait \ -device isa-serial,chardev=serial_id_serial0 \ -chardev socket,id=seabioslog_id_20150609-153354-uy9GdXPd,path=/tmp/seabios-20150609-153354-uy9GdXPd,server,nowait \ -device isa-debugcon,chardev=seabioslog_id_20150609-153354-uy9GdXPd,iobase=0x402 \ -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=04 \ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=05 \ -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,format=raw,file=/home/autotest/autotest-devel/client/tests/virt/shared/data/images/RHEL-Server-7.2-64-virtio-scsi.raw \ -device scsi-hd,id=image1,drive=drive_image1 \ -device virtio-net-pci,mac=9a:22:23:24:25:26,id=id2jGMKz,vectors=4,netdev=idvJ5GVe,bus=pci.0,addr=06 \ -netdev tap,id=idvJ5GVe,vhost=on \ -m 16384 \ -smp 16,maxcpus=16,cores=8,threads=1,sockets=2 \ -cpu 'Westmere' \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -spice port=3000,password=123456,addr=0,image-compression=auto_glz,zlib-glz-wan-compression=auto,streaming-video=all,agent-mouse=on,playback-compression=on,ipv4 \ -rtc base=utc,clock=host,driftfix=slew \ -boot order=cdn,once=c,menu=off,strict=off \ -enable-kvm \ -watchdog i6300esb \ -watchdog-action shutdown \ -monitor stdio \ 2. after guest boots up ,in guest ,issue: echo c > /dev/watchdog ,wait for some time, 3.you will see the guest didn't shutdown, check the status ,will see the guest is still running. 4)there is a screendump in the attachment Actual results: Expected results: Additional info: hostinfo: 1)cpu: processor : 23 vendor_id : GenuineIntel cpu family : 6 model : 44 model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz stepping : 2 microcode : 21 cpu MHz : 1596.000 cache size : 12288 KB physical id : 1 siblings : 12 core id : 10 cpu cores : 6 apicid : 53 initial apicid : 53 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm arat epb dts tpr_shadow vnmi flexpriority ept vpid