Bug 1299876
| Summary: | system_reset should clear pending request for error (IDE) | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ademar Reis <areis> | |
| Component: | qemu-kvm-rhev | Assignee: | John Snow <jsnow> | |
| Status: | CLOSED ERRATA | QA Contact: | aihua liang <aliang> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | high | |||
| Version: | 7.2 | CC: | ailan, aliang, armbru, coli, huding, jsnow, juzhang, michen, mkenneth, qzhang, rbalakri, virt-bugs, virt-maint, xuwei, zhguo | |
| Target Milestone: | rc | Keywords: | ZStream | |
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Windows | |||
| Whiteboard: | ||||
| Fixed In Version: | QEMU 2.9 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1299875 | |||
| : | 1393043 (view as bug list) | Environment: | ||
| Last Closed: | 2017-08-01 23:29:42 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: | ||||
| Bug Depends On: | 1281713, 1299875 | |||
| Bug Blocks: | 1393043 | |||
|
Description
Ademar Reis
2016-01-19 13:07:34 UTC
The backtrace is similar to the one in bug 1346237 (thanks to Stefan Hajnoczi for bringing it to my attention). Can you still reproduce it with qemu-kvm-rhev-2.6.0-11.el7? Thanks to Laszlo's simple reproduce steps, I can reproduce this issue against qemu-kvm-rhev-2.6.0-15.el7.x86_64
Steps:
1. #qemu-img create -f qcow2 test.qcow2 8G
2. #ulimit -f 256
3. #gdb /usr/libexec/qemu-kvm
(gdb) run -m 2048 -smp 2 -drive file=test.qcow2,werror=stop,rerror=stop,cache=writeback,id=hd0,if=none -device ide-hd,drive=hd0 -drive id=cd0,readonly,media=cdrom,cache=writeback,if=none,file=Fedora-Server-dvd-x86_64-24-1.2.iso -device ide-cd,drive=cd0 -vnc :0 -monitor stdio
4. Install fedora from vnc and guest will hang very soon during installation.
5. Do system_reset from qmp and qemu will crash.
Backtrace:
(qemu)
Program received signal SIGSEGV, Segmentation fault.
0x0000555556b750f0 in ?? ()
(gdb) bt
#0 0x0000555556b750f0 in ?? ()
#1 0x000055555593cc4a in bdrv_aio_cancel_async (acb=0x555556b75570)
at block/io.c:2060
#2 bdrv_aio_cancel (acb=0x555556b75570) at block/io.c:2041
#3 0x0000555555931ce5 in blk_aio_cancel (acb=<optimized out>)
at block/block-backend.c:1044
#4 0x000055555584133a in ide_bus_reset (bus=bus@entry=0x5555597bf0d8)
at hw/ide/core.c:2326
#5 0x0000555555844674 in piix3_reset (opaque=0x5555597be000)
at hw/ide/piix.c:115
#6 0x00005555557d1abd in qemu_devices_reset () at vl.c:1738
#7 0x000055555574d166 in pc_machine_reset ()
at /usr/src/debug/qemu-2.6.0/hw/i386/pc.c:1936
#8 0x00005555557d1b26 in qemu_system_reset (report=report@entry=true)
at vl.c:1751
#9 0x00005555556c795b in main_loop_should_exit () at vl.c:1898
#10 main_loop () at vl.c:1938
#11 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>)
at vl.c:4664
Moving back from POST to ASSIGNED as the 7.4 tree isn't open for submissions yet, and we decided not to include this for 7.3 as of 2016-09-19. There is another bug proposed for Z-stream (BZ#1375520) which MAY require the same fix as this bug, so it is possible we may change our minds again in the near future based on analysis of that bug. (While you're here reading bugzilla comments: The two bugs currently trigger the same exact stack trace, but the triggering mechanism appears to be different between the two BZs, hence the separate entries.) --js For reference, this is the cluster of BZ related to this issue: bug 1281713, bug 1299876, bug 1299875, bug 1361487, bug 1361490, bug 1361488, bug 1375520 Hi, John
Test on RHEV7.4+qemu-kvm-rhev 2.9, the problem has been resolved, so please help to handle the bug, change its status to the correct one, thanks
*******Test Detail**************
Test Version:
kernel version:3.10.0-623.el7.x86_64
qemu-kvm-rhev version:qemu-kvm-rhev-2.9.0-0.el7.mrezanin201703210848.x86_64
Test Steps:
1.Install a guest, ex, win2012
2.Full write host disk.
3.Start guest with qemu cmds, then start some apps on guest until guest hang
/usr/libexec/qemu-kvm \
-name 'avocado-vt-vm1' \
-sandbox off \
-machine pc \
-nodefaults \
-vga std \
-chardev socket,id=qmp_id_qmpmonitor1,path=/var/tmp/monitor-qmpmonitor1-20161227-001116-PD2k1uXB,server,nowait \
-mon chardev=qmp_id_qmpmonitor1,mode=control \
-chardev socket,id=qmp_id_catch_monitor,path=/var/tmp/monitor-catch_monitor-20161227-001116-PD2k1uXB,server,nowait \
-mon chardev=qmp_id_catch_monitor,mode=control \
-device pvpanic,ioport=0x505,id=id95e1vw \
-chardev socket,id=serial_id_serial0,path=/var/tmp/serial-serial0-20161227-001116-PD2k1uXB,server,nowait \
-device isa-serial,chardev=serial_id_serial0 \
-chardev socket,id=seabioslog_id_20161227-001116-PD2k1uXB,path=/var/tmp/seabios-20161227-001116-PD2k1uXB,server,nowait \
-device isa-debugcon,chardev=seabioslog_id_20161227-001116-PD2k1uXB,iobase=0x402 \
-device ich9-usb-ehci1,id=usb1,addr=1d.7,multifunction=on,bus=pci.0 \
-device ich9-usb-uhci1,id=usb1.0,multifunction=on,masterbus=usb1.0,addr=1d.0,firstport=0,bus=pci.0 \
-device ich9-usb-uhci2,id=usb1.1,multifunction=on,masterbus=usb1.0,addr=1d.2,firstport=2,bus=pci.0 \
-device ich9-usb-uhci3,id=usb1.2,multifunction=on,masterbus=usb1.0,addr=1d.4,firstport=4,bus=pci.0 \
-drive id=drive_image1,if=none,snapshot=off,aio=native,cache=none,format=qcow2,file=/home/win2012-64-virtio.qcow2 \
-device ide-hd,id=image1,drive=drive_image1,bus=ide.0,unit=0 \
-device virtio-net-pci,mac=9a:d7:d8:d9:da:db,id=idoYMY7R,vectors=4,netdev=iddvjhTd,bus=pci.0,addr=03 \
-netdev tap,id=iddvjhTd,vhost=on \
-m 4096 \
-smp 8,maxcpus=8,cores=4,threads=1,sockets=2 \
-cpu host \
-vnc :0 \
-rtc base=localtime,clock=host,driftfix=slew \
-boot order=cdn,menu=off,strict=off \
-enable-kvm \
-monitor stdio \
-spice port=3000,ipv4,disable-ticketing \
4.Check vm status
(qemu)info status -------> vm status:paused(io-error)
5. Reset vm
(qemu)system_reset
(qemu)c ------->vm restart
6. Release some host space, then reset vm
(qemu)system_reset
(qemu)c -------> vm restart and work normally
Hi, John The problem has been resolved on RHEV7.4+qemu-kvm-rhev 2.9, please help to handle it to the correct status, thanks. OK, I think it's up to QE to mark it as ON_QA or VERIFIED, so from the Dev perspective I'll mark it as MODIFIED to signify that the fix is in the tree. Hopefully this moves the BZ back into the normal flow of things. As the fix has been in the tree and verified as "pass", we change bug's status to "Verified", thanks... Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 |