Re: xen/stable-2.6.32.x xen-4.1.1 live migration fails with kernels 2.6.39, 3.0.3 and 3.1-rc2

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Wed, Aug 31, 2011 at 03:07:22PM +0200, Andreas Olsowski wrote:
> A little update, i now have all machines running on xen-4.1-testing
> with xen/stable-2.6.32.x
> That gave me the possiblity for additional tests.
> 
> (I also tested xm/xend in addtion to xl/libxl, to make sure its not
> a xl/libxl problem.)
> 
> I took the liberty to create a new test result matrix that should
> provide a better overview (in case someone else wants to get the
> whole picture):

So.. I don't think the issue I am seeing is exactly the same. This is
what 'xl' gives me:

 :~/
> xl migrate 3 tst010
root@tst010's password:
migration target: Ready to receive domain.
Saving to migration stream new xl format (info 0x0/0x0/326)
Loading new save file incoming migration stream (new xl fmt info 0x0/0x0/326)
 Savefile contains xl domain config
xc: Saving memory: iter 0 (last sent 0 skipped 0): 262400/262400  100%
xc: Saving memory: iter 2 (last sent 1105 skipped 23): 262400/262400  100%
xc: Saving memory: iter 3 (last sent 74 skipped 0): 262400/262400  100%
xc: Saving memory: iter 4 (last sent 0 skipped 0): 262400/262400  100%
xc: error: unexpected PFN mapping failure pfn 19d0 map_mfn 4e7e04 p2m_mfn 4e7e04: Internal error
libxl: error: libxl_dom.c:363:libxl__domain_restore_common: restoring domain: Resource temporarily unavailable
libxl: error: libxl_create.c:483:do_domain_create: cannot (re-)build domain: -3
libxl: error: libxl.c:733:libxl_domain_destroy: non-existant domain 4
migration target: Domain creation failed (code -3).
libxl: error: libxl_utils.c:410:libxl_read_exactly: file/stream truncated reading ready message from migration receiver stream
libxl: info: libxl_exec.c:125:libxl_report_child_exitstatus: migration target process [5810] exited with error status 3
Migration failed, resuming at sender.


And on the receiving side (tst010) I get a monster off:

(XEN) mm.c:945:d0 Error getting mfn 4e7e04 (pfn ffffffffffffffff) from L1 entry 80000004e7e04627 for l1e_owner=0, pg_owner=4
XEN) mm.c:945:d0 Error getting mfn 36fd19 (pfn ffffffffffffffff) from L1 entry 800000036fd19627 for l1e_owner=0, pg_owner=4
(XEN) mm.c:945:d0 Error getting mfn 36f583 (pfn ffffffffffffffff) from L1 entry 800000036f583627 for l1e_owner=0, pg_owner=4
..
(XEN) mm.c:945:d0 Error getting mfn 4e7d09 (pfn ffffffffffffffff) from L1 entry 80000004e7d09627 for l1e_owner=0, pg_owner=4
(XEN) event_channel.c:250:d3 EVTCHNOP failure: error -17


The migration is from a 4GB box to a 32GB box (worked), then back to the 4GB( worked)
and then back to the 32GB (boom!).

anyhow, let me try this with 4.1-testing branch. Running on the bleeding
edge might not be the best idea sometimes.

> 
> ####################################################################
> ##### xen 4.1 live migration fails between different platforms #####
> ####################################################################
> XEN: xen-4.1-testing.hg
> dom0: xen/stable-2.6.32.x
> domU: linux-2.6.39 vanilla (also 3.0.3 and 3.1)
> 
> toolstack: xl/libxl
> (at least FAIL type1 also occurs with xm/xend)
> 
> # create means the guest has been created by this host
> # received means the guest has been migrate-received by this host
> 
> XEN: xen-4.1-testing.hg
> dom0: xen/stable-2.6.32.x
> domU: linux-2.6.39 vanilla (also 3.0.3 and 3.1)
> 
> toolstack: xl/libxl
> (at least FAIL type1 also occurs with xm/xend)
> 
> 
> # Dell PE 2950 and Dell PE 2950
> create pe2950-1 -> pe2950-2  OK
> received pe2950-2 -> pe2950-1 OK
> create pe2950-2 -> pe2950-1  OK
> received pe2950-1 -> pe2950-2 OK
> 
> # Dell PE 2950 and Dell R710
> create pe2950-1 -> r710  OK
> received r710 -> pe2950-1 OK
> create r710 -> pe2950-1 FAIL (type 1): http://pastebin.com/iUeNPQyY
> 
> # Dell PE 2950 and Dell R610
> create pe2950-1 -> r610-1 FAIL (type 2): http://pastebin.com/fzMkuS5s
> create r610-1 -> pe2950-1 FAIL (type 1): http://pastebin.com/Lq6SGVPj
> 
> # Dell R610 and Dell R610
> create r610-1 -> r610-2 OK
> received r610-2 -> r610-1 OK
> 
> create r610-2 -> r610-1 OK
> received r610-1 -> r610-2 OK
> 
> # Dell R610 and Dell R710
> create r610-1 -> r710 OK
> received r710 -> r610-1 OK
> 
> create r710 -> r610-1 FAIL (type 2): http://pastebin.com/eff5Yx0C
> 
> # Dell PE 2950 and Dell R710 and Dell R610
> create pe2950-2 -> r710 OK
> received r710 -> r610 FAIL (type 2): http://pastebin.com/it7QPsJk
> 
> create r610 -> r710 OK
> received r710 -> pe2950-2 FAIL (type 1 derived?):
> http://pastebin.com/R6pXSJpU
> 
> #EOF
> 
> with best regards
> 
> Andreas
> 



> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel