[Bug 501756] New: When live migrating two domUs simultaneously in the opposite direction, one of them will freeze
http://bugzilla.novell.com/show_bug.cgi?id=501756 Summary: When live migrating two domUs simultaneously in the opposite direction, one of them will freeze Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: jdouglas@novell.com ReportedBy: nice@titanic.nyme.hu QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; hu-HU; rv:1.9.0.9) Gecko/2009041500 SUSE/3.0.9-0.1.1 Firefox/3.0.9 I have two 64 bit openSUSE 11.1 dom0s (carrier4 and carrier5), and two fibrechannel backed openSUSE 11.1 domUs on top of these dom0s (openSUSE111-32 and openSUSE111-64). Migrating seems to be rock solid now. I can even live migrate them simultaneously in the same direction. But when migration takes place in the opposite direction one of the dom0s will freeze, namely always the one which started migrating LATER. Freezing means that when I'm watching the virtual machine manager at the receiving dom0, I will see that in spite of the fact that the sending dom0 finished migration (xm migrate --live command exited in bash without error message and domU disappeared from virtual machine manager), the arrived domU will stay in paused state. This paused state is normal during domU reception, but it should be immediately unpaused on migration finish. When I try to resume it in virtual machine manager, it seem to be started, but I cannot connect to it neither via network (ping also doesn't work) nor by xen virtual framebuffer vnc console. This frozen domU cannot even be shutdown, it has to be destroyed instead. I will attach two tar/gzipped xen log directories, one from the dom0 carrier4 and one from carrier5. The last action was (I hope I can remember correctly) that openSUSE111-64 travelled from carrier4 to carrier5, and during this migration openSUSE111-32 started to travel in the opposite direction and finally hung on carrier4. Reproducible: Always Steps to Reproduce: 1. Migrate two domUs between two dom0s simultaneously in the opposite direction Actual Results: The domU which started the migration later, will hang Expected Results: Both domUs should function properly afterwards, too -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=501756
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=501756#c1
--- Comment #1 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=501756
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=501756#c2
--- Comment #2 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=501756
Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=501756
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=501756#c3
--- Comment #3 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=501756
User jdouglas@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=501756#c4
Jason Douglas
participants (1)
-
bugzilla_noreply@novell.com