Guest is destroyed after live migration

Bug #1293975 reported by Robert Hu
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QEMU
Fix Released
Undecided
Unassigned

Bug Description

Environment:
------------
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:8fbb1daf3e8254afc17fc4490b69db00920197ae
qemu.git Commit: 6fffa26244737f8fd8641a21fee29bd6aa9fdff5
Host Kernel Version:3.14.0-rc3
Hardware:Romley_EP, Ivytown_EP

Bug detailed description:
--------------------------
after live migration, the guest will be destroyed

note:
after save restore, the guest will be destroyed.

Reproduce steps:
----------------
1.Start a TCP daemon for migration
qemu-system-x86_64 -enable-kvm -m 2048 -smp 2 -net none /root/rhel6u4.qcow -incoming tcp:localhost:4444
2. create guest
qemu-system-x86_64 -enable-kvm -m 2048 -smp 2 -net none /root/rhel6u4.qcow
3. ctrl+alt+2 to switch to qemu monitor
4. migrate tcp:localhost:4444

Current result:
----------------
the guest will be destroyed

Expected result:
----------------
the guest works fine

Basic root-causing log:
----------------------
qemu-system-x86[15027]: segfault at 698 ip 00007f94be628166 sp 00007f94bb820c58 error 6 in libc-2.12.so[7f94be5a5000+189000]

Bisect result
the first bad commit:
commit 00c8cb0a36f51a6866a83c08962d12a0eb21864b
Author: Andreas Färber <email address hidden>
Date: Wed Sep 4 02:19:44 2013 +0200

    cputlb: Change tlb_flush() argument to CPUState

    Signed-off-by: Andreas Färber <email address hidden>

Revision history for this message
Dr. David Alan Gilbert (dgilbert-h) wrote :

Can you capture a backtrace for the failure? Is the seg happening in the source or destination qemu?

Revision history for this message
Dr. David Alan Gilbert (dgilbert-h) wrote :
Revision history for this message
Robert Hu (robert-hu) wrote :

kvm.git + qemu.git: 94b3ffcd_f71e769d
after live migration, the guest works fine.

Changed in qemu:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.