Bug 1012270
Summary: | resume S4 cause qemu-kvm core dump after hot-plug block device | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | zhonglinzhang <zhzhang> |
Component: | qemu-kvm | Assignee: | Virtualization Maintenance <virt-maint> |
Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.5 | CC: | acathrow, bsarathy, juzhang, michen, mkenneth, qzhang, virt-maint, xfu |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-05 22:15:08 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: | |||
Bug Blocks: | 912287 |
Description
zhonglinzhang
2013-09-26 07:19:57 UTC
resume S4 cause qemu-kvm core dump after hot-plug network: win8 guest Steps to Reproduce: 1. Boot a win8 guest /usr/libexec/qemu-kvm -M pc -cpu SandyBridge -enable-kvm -m 4G -smp 4,sockets=1,cores=4,threads=1 -name test \ -rtc base=localtime,clock=host,driftfix=slew -k en-us -boot menu=on \ -vnc :3 -vga cirrus -usb -device usb-tablet -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -monitor stdio \ -drive file=/home/win8-32.raw,if=none,id=drive-system-disk,media=disk,format=raw,aio=native,werror=stop,rerror=stop \ -device virtio-blk-pci,drive=drive-system-disk,id=system-disk,addr=0x5 2. Hotplug rtl8139 (qemu) netdev_add tap,id=virtio2,script=/etc/qemu-ifup (qemu) device_add driver=rtl8139,netdev=virtio2,mac=00:22:15:27:54:8d,id=test2,addr=0xa 3. Do s4 4. Resume from s4 /usr/libexec/qemu-kvm ... \ -netdev tap,id=virtio2,script=/etc/qemu-ifup -device rtl8139,netdev=virtio2,id=test2,mac=00:22:15:27:54:8d,addr=0xa Actual Results: qemu-kvm core dump (qemu) qemu-kvm: virtio_pci_set_host_notifier_internal: unable to unmap ioeventfd: -2 qemu-kvm: /builddir/build/BUILD/qemu-kvm-0.12.1.2/hw/virtio-pci.c:310: virtio_pci_stop_ioeventfd: Assertion `r >= 0' failed. Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fffef4ce700 (LWP 6193)] 0x00007ffff4c9c925 in raise () from /lib64/libc.so.6 (gdb) (gdb) (gdb) bt #0 0x00007ffff4c9c925 in raise () from /lib64/libc.so.6 #1 0x00007ffff4c9e105 in abort () from /lib64/libc.so.6 #2 0x00007ffff4c95a4e in __assert_fail_base () from /lib64/libc.so.6 #3 0x00007ffff4c95b10 in __assert_fail () from /lib64/libc.so.6 #4 0x00007ffff7ddfe15 in virtio_pci_stop_ioeventfd (proxy=0x7ffff877b2b0) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/virtio-pci.c:310 #5 0x00007ffff7de0b65 in virtio_ioport_write (opaque=0x7ffff877b2b0, addr=<value optimized out>, val=0) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/virtio-pci.c:364 #6 0x00007ffff7dece4f in kvm_handle_io (env=0x7ffff86fc230) at /usr/src/debug/qemu-kvm-0.12.1.2/kvm-all.c:145 #7 kvm_run (env=0x7ffff86fc230) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:1049 #8 0x00007ffff7ded089 in kvm_cpu_exec (env=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:1744 #9 0x00007ffff7dedf6d in kvm_main_loop_cpu (_env=0x7ffff86fc230) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:2005 #10 ap_main_loop (_env=0x7ffff86fc230) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:2061 #11 0x00007ffff77009d1 in start_thread () from /lib64/libpthread.so.0 #12 0x00007ffff4d52a8d in clone () from /lib64/libc.so.6 (gdb) Additional info: qemu-kvm can not core dump for RHEL6.5 guest(First: hotplug network. Second: s4, Third: resume from s4) S3/S4 support is tech-preview in RHEL6 and it'll be promoted to fully supported at some point, but only in RHEL7. Therefore we're closing all S3/S4 related bugs in RHEL6. New bugs will be considered only if they're regressions or break some important use-case or certification. RHEL7 is being more extensively tested and effort from QE is underway in certifying that this particular bug is not present there. Please reopen with a justification if you believe this bug should not be closed. We'll consider them on a case-by-case basis following a best effort approach. Thank you. |