Re: [Xen-users] 1000 Domains: Not able to access Domu via xm console from Dom0

[Paul Harvey <jhebus@xxxxxxxxxxxxxx>]

On 14 December 2012 14:57, Wei Liu <Wei.Liu2@xxxxxxxxxx> wrote:

On Fri, 2012-12-14 at 13:06 +0000, Paul Harvey wrote:
> SO
>
> #with 341 domains
> ./lsevntchn 0 | wc -l
> 724
>
> Attaching gdb to xenconsoled,
>
> Program received signal SIGABRT, Aborted.
> 0x00007fe588ca8425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
> (gdb) bt
> #0  0x00007fe588ca8425 in raise ()
> from /lib/x86_64-linux-gnu/libc.so.6
> #1  0x00007fe588cabb8b in abort ()
> from /lib/x86_64-linux-gnu/libc.so.6
> #2  0x00007fe588ce639e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #3  0x00007fe588d7c807 in __fortify_fail ()
> from /lib/x86_64-linux-gnu/libc.so.6
> #4  0x00007fe588d7b700 in __chk_fail ()
> from /lib/x86_64-linux-gnu/libc.so.6
> #5  0x00007fe588d7c7be in __fdelt_warn ()
> from /lib/x86_64-linux-gnu/libc.so.6
> #6  0x0000000000403ca8 in handle_io () at daemon/io.c:1059
> #7  0x00000000004021c5 in main (argc=2, argv=0x7fff58691d48) at
> daemon/main.c:166
>

libc raises exception when it detects memory violation.

You can probably try to use valgrind to identify memory leak in
xenconsoled.


Wei.

Feeling in a little over my head now,

I have run valgrind and include the file with the output. As before xenconsoled crashes, but i am not really sure how to read what i am seeing from valgrind. I am not really sure if it is telling me that these errors happen as it goes along, or if it is as a result of the crash that there are lost blocks around.

Valgrind was run with:

valgrind --tool=memcheck --leak-check=yes --show-reachable=yes --num-callers=20 --log-file="valgrind_output.txt" --track-fds=yes ./xenconsoled --pid-file=/var/run/xenconsoled.pid

If the attached file doesn't show, could you tell where it should go?

Paul

Attachment: valgrind_output.txt
Description: Text document

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