Hide Forgot
Description of problem: kvm core dumps when offline migrate guest Version-Release number of selected component (if applicable): kvm-83-242.el5 kmod-kvm-83-242.el5 qspice-0.3.0-54.el5_5.2 qspice-libs-0.3.0-54.el5_5.2 How reproducible: 1 / 10 Steps to Reproduce: 1. boot a guest (I am using rhel6.1-64 release when I met this issue) 2. migrate guest by offline method (migrate -d "exec:gzip -c > /tmp/rhel61.gz") 3. repeatly connect to guest using spicec... Actual results: kvm core dumps Expected results: guest offline migrate done and can migrate back , both host and guest work well. Additional info: gdb bt full attached, rpm-list.txt attached. Core was generated by `/usr/local/staf/test/RHEV/kvm-new/autotest/client/tests/kvm/qemu -name vm1 -mon'. Program terminated with signal 11, Segmentation fault. #0 0x0000003ed2953a38 in main_arena () from /lib64/libc.so.6 (gdb) bt #0 0x0000003ed2953a38 in main_arena () from /lib64/libc.so.6 #1 0x0000003edee2de1d in red_worker_main (arg=<value optimized out>) at red_worker.c:8801 #2 0x0000003ed2e0673d in start_thread () from /lib64/libpthread.so.0 #3 0x0000003ed26d44bd in clone () from /lib64/libc.so.6 (gdb)
Created attachment 529172 [details] bt full
Hi Backtrace points to spice thread. Gerd, can you take a look?
Yes, looks like a spice bug. /me goes reassign ...
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).