Xen users - Nov 2012 - Remus: Xen 4.2.1 with Debian 6.0 does not work

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Adding xen-devel since this is an xl segfault.

Please can you not send html mail. Plain text is just fine.

On Fri, 2012-11-02 at 12:32 +0000, D K wrote:
> Xen: Version 4.2.-testing from mercurial
Which version exactly ? There was a batch of backports recently which
included some fixes to the ao infrastructure, including a fix for
aoinprogress (which appears in your stack trace).

So please can you try the most recent tip of 4.2-testing.
> 
> 
> Guest:
> 
> Config: http://pgb.game-host.org/xen/debian.cfg
> 
> 
> Erroranalysis:
> 
> 


>      1. Getting the vm started on PC1 with the following command works
>         fine:
>         
>         xl create debian.cfg
>         
>      2. Remus does not:
>         
>         
>         xl remus <domid> 129.217.43.51
Does normal migration work?
>         
> Segmentation fault
> 
> xc: error: read_exact_timed failed (select returned 0): Internal error 
> xc: error: Error reading QEMU signature (110 = Connection timed out):
Internal error
> xc: error: error buffering image tail, finishing: Internal error 
> 
> migration target: Remus Failover for domain 3 
It seems like there might be more than one issue here, the original
failure and then a failure in the error path too.

[...snip, I don''t thin k w needed the whole story, just the resulting
stacktrace...]

Is this backtrace from the sending or the receiving xl?
> #0 0xb7e4bfea in malloc_consolidate (av=<value optimized out>) at
malloc.c:5145
> #1 0xb7e4e21d in _int_malloc (av=<value optimized out>,
bytes=<value optimized out>) at malloc.c:4373
> #2 0xb7e506f3 in *__GI___libc_malloc (bytes=1012) at malloc.c:3661 
> #3 0xb7f9e011 in datacopier_readable (egc=0xbffff2bc, ev=0x806a92c, fd=21,
events=1, revents=1) at libxl_aoutils.c:144
> #4 0xb7fa3072 in afterpoll_internal (egc=0xbffff2bc, poller=<value
optimized out>, nfds=6, fds=0x806bb10, now=...)
> at libxl_event.c:948 
> #5 0xb7fa3e1b in eventloop_iteration (egc=<value optimized out>,
poller=0x806a688) at libxl_event.c:1368
> #6 0xb7fa448f in libxl__ao_inprogress (ao=0x806a768, file=0xb7fb09cc
"libxl.c", line=728, func=0xb7fb2c4f
"libxl_domain_remus_start") at libxl_event.c:1614
> #7 0xb7f842bf in libxl_domain_remus_start (ctx=0x806a030, info=0xbffff3c4,
domid=2, send_fd=10, recv_fd=11, ao_how=0x0) at libxl.c:728
> #8 0x0805045e in main_remus (argc=3, argv=0xbffff4f8) at xl_cmdimpl.c:6776 
> #9 0x0804d2be in main (argc=4, argv=0xbffff4f4) at xl.c:267
>

Adding xen-devel since this is an xl segfault.

Please can you not send html mail. Plain text is just fine.

On Fri, 2012-11-02 at 12:32 +0000, D K wrote:
> Xen: Version 4.2.-testing from mercurial
Which version exactly ? There was a batch of backports recently which
included some fixes to the ao infrastructure, including a fix for
aoinprogress (which appears in your stack trace).

So please can you try the most recent tip of 4.2-testing.
> 
> 
> Guest:
> 
> Config: http://pgb.game-host.org/xen/debian.cfg
> 
> 
> Erroranalysis:
> 
> 


>      1. Getting the vm started on PC1 with the following command works
>         fine:
>         
>         xl create debian.cfg
>         
>      2. Remus does not:
>         
>         
>         xl remus <domid> 129.217.43.51
Does normal migration work?
>         
> Segmentation fault
> 
> xc: error: read_exact_timed failed (select returned 0): Internal error 
> xc: error: Error reading QEMU signature (110 = Connection timed out):
Internal error
> xc: error: error buffering image tail, finishing: Internal error 
> 
> migration target: Remus Failover for domain 3 
It seems like there might be more than one issue here, the original
failure and then a failure in the error path too.

[...snip, I don''t thin k w needed the whole story, just the resulting
stacktrace...]

Is this backtrace from the sending or the receiving xl?
> #0 0xb7e4bfea in malloc_consolidate (av=<value optimized out>) at
malloc.c:5145
> #1 0xb7e4e21d in _int_malloc (av=<value optimized out>,
bytes=<value optimized out>) at malloc.c:4373
> #2 0xb7e506f3 in *__GI___libc_malloc (bytes=1012) at malloc.c:3661 
> #3 0xb7f9e011 in datacopier_readable (egc=0xbffff2bc, ev=0x806a92c, fd=21,
events=1, revents=1) at libxl_aoutils.c:144
> #4 0xb7fa3072 in afterpoll_internal (egc=0xbffff2bc, poller=<value
optimized out>, nfds=6, fds=0x806bb10, now=...)
> at libxl_event.c:948 
> #5 0xb7fa3e1b in eventloop_iteration (egc=<value optimized out>,
poller=0x806a688) at libxl_event.c:1368
> #6 0xb7fa448f in libxl__ao_inprogress (ao=0x806a768, file=0xb7fb09cc
"libxl.c", line=728, func=0xb7fb2c4f
"libxl_domain_remus_start") at libxl_event.c:1614
> #7 0xb7f842bf in libxl_domain_remus_start (ctx=0x806a030, info=0xbffff3c4,
domid=2, send_fd=10, recv_fd=11, ao_how=0x0) at libxl.c:728
> #8 0x0805045e in main_remus (argc=3, argv=0xbffff4f8) at xl_cmdimpl.c:6776 
> #9 0x0804d2be in main (argc=4, argv=0xbffff4f4) at xl.c:267
>