[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen HVM Guest fails (errors) to launch on Opensuse 12.2's Xen 4.2 + 'xl' toolstack



hoping to provide some form of useful debug info, per

        3.2. Debugging your program using Valgrind gdbserver and GDB
        
http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver

i've attached, below, the output of:

        valgrind -v --vgdb=yes --vgdb-error=0 --track-origins=yes
        --trace-children=yes --leak-check=full --show-reachable=yes xl
        create -c /home/ar/test.cfg

& the corresponding gdb session:

        gdb xl
        (gdb) target remote | /usr/lib64/valgrind/../../bin/vgdb
        --pid=7667
        ...
        (gdb) continue
        ...
        (gdb) bt
        ...

which appears to get a SIGTRAP at

        101     libxl_utils.h: No such file or directory.

although,

        ls -al /usr/include/libxl_utils.h
                -rw-r--r-- 1 root root 5.7K Sep 18 14:42
                /usr/include/libxl_utils.h


======================================================================
valgrind -v --vgdb=yes --vgdb-error=0 --track-origins=yes
--trace-children=yes --leak-check=full --show-reachable=yes xl create -c
/home/ar/test.cfg
==7667== Memcheck, a memory error detector
==7667== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==7667== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright
info
==7667== Command: xl create -c /home/ar/test.cfg
==7667==
--7667-- Valgrind options:
--7667--    -v
--7667--    --vgdb=yes
--7667--    --vgdb-error=0
--7667--    --track-origins=yes
--7667--    --trace-children=yes
--7667--    --leak-check=full
--7667--    --show-reachable=yes
--7667-- Contents of /proc/version:
--7667--   Linux version 3.4.6-2.10-xen (geeko@buildhost) (gcc version
4.7.1 20120723 [gcc-4_7-branch revision 189773] (SUSE Linux) ) #1 SMP
Thu Jul 26 09:36:26 UTC 2012 (641c197)
--7667-- Arch and hwcaps: AMD64, amd64-sse3-cx16-lzcnt
--7667-- Page sizes: currently 4096, max supported 4096
--7667-- Valgrind library directory: /usr/lib64/valgrind
--7667-- Reading syms from /usr/sbin/xl
--7667--   Considering
/usr/lib/debug/.build-id/30/a64409d9dfee58a099b01b8e833b012f11f0bd.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /lib64/ld-2.15.so
--7667--   Considering
/usr/lib/debug/.build-id/e4/2d5feaef8b50f76c5d9011480021d8c76be03a.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /usr/lib64/valgrind/memcheck-amd64-linux
--7667--   Considering
/usr/lib/debug/usr/lib64/valgrind/memcheck-amd64-linux.debug ..
--7667--   .. CRC is valid
--7667--    object doesn't have a dynamic symbol table
--7667-- Scheduler: using generic scheduler lock implementation.
--7667-- Reading suppressions file: /usr/lib64/valgrind/default.supp
==7667== (action at startup) vgdb me ...
==7667== embedded gdbserver: reading from
/tmp/vgdb-pipe-from-vgdb-to-7667-by-root-on-server
==7667== embedded gdbserver: writing to  
/tmp/vgdb-pipe-to-vgdb-from-7667-by-root-on-server
==7667== embedded gdbserver: shared mem  
/tmp/vgdb-pipe-shared-mem-vgdb-7667-by-root-on-server
==7667==
==7667== TO CONTROL THIS PROCESS USING vgdb (which you probably
==7667== don't want to do, unless you know exactly what you're doing,
==7667== or are doing some strange experiment):
==7667==   /usr/lib64/valgrind/../../bin/vgdb --pid=7667 ...command...
==7667==
==7667== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==7667==   /path/to/gdb xl
==7667== and then give GDB the following command
==7667==   target remote | /usr/lib64/valgrind/../../bin/vgdb --pid=7667
==7667== --pid is optional if only one valgrind process is running
==7667==
--7667-- REDIR: 0x4017980 (strlen) redirected to 0x3806c751
(vgPlain_amd64_linux_REDIR_FOR_strlen)
--7667-- Reading syms from
/usr/lib64/valgrind/vgpreload_core-amd64-linux.so
--7667--   Considering
/usr/lib/debug/.build-id/58/fafcae89b15a60beb5a94f5cebe506d63adbe2.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so
--7667--   Considering
/usr/lib/debug/.build-id/19/a54751b3d366463830a2dcab6372e03b1cba14.debug
..
--7667--   .. build-id is valid
--7667-- REDIR: 0x40177f0 (index) redirected to 0x4c2c930 (index)
--7667-- REDIR: 0x4017870 (strcmp) redirected to 0x4c2d940 (strcmp)
--7667-- Reading syms from /usr/lib64/libxlutil.so.1.0.0
--7667--   Considering
/usr/lib/debug/.build-id/57/db42dff0f5c8eaf2270b9b2c1749372e7a43eb.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /usr/lib64/libxenlight.so.2.0.0
--7667--   Considering
/usr/lib/debug/.build-id/c5/612d35a8a81737c65c7373b51b513aae115ead.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /usr/lib64/libxenctrl.so.4.2.0
--7667--   Considering
/usr/lib/debug/.build-id/b2/95761d280c399a5a6fcad017488f114c9eb134.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /usr/lib64/libyajl.so.2.0.1
--7667--   Considering
/usr/lib/debug/.build-id/99/9a0d33091222f1538223325db7f5e243dd63c9.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /lib64/libpthread-2.15.so
--7667--   Considering
/usr/lib/debug/.build-id/d5/a497713b5ae7d06971fb34530b63d89a42e0af.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /lib64/libc-2.15.so
--7667--   Considering
/usr/lib/debug/.build-id/74/a39090ae55f5852f5051263d722588db13bf55.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /usr/lib64/libxenguest.so.4.2.0
--7667--   Considering
/usr/lib/debug/.build-id/f0/4b4f86cb8506da6a8bfe4d5294c9f7708f8ddb.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /usr/lib64/libxenstore.so.3.0.1
--7667--   Considering
/usr/lib/debug/.build-id/82/5de7c92321f509c1f56f5c82de84f1391d5b16.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /usr/local/lib64/libblktapctl.so.1.0.0
--7667-- Reading syms from /lib64/libutil-2.15.so
--7667--   Considering
/usr/lib/debug/.build-id/ff/73a066c7363459b2c6a83f8530333bacea5b53.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /usr/lib64/libuuid.so.1.3.0
--7667--   Considering
/usr/lib/debug/.build-id/6b/2300887663497904f5bd17e51e0f6e04849058.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /lib64/libdl-2.15.so
--7667--   Considering
/usr/lib/debug/.build-id/d0/ec4dbdb0d7b15bb7a6454fefa923d5de1daf40.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /usr/lib64/libbz2.so.1.0.6
--7667--   Considering
/usr/lib/debug/.build-id/ec/1a7cb75fb00b3027653c7e44ab2ae5e1bdc323.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /usr/lib64/liblzma.so.5.0.3
--7667--   Considering
/usr/lib/debug/.build-id/40/ab1743eda0b177bfd7097de713d3842973ef98.debug
..
--7667--   .. build-id is valid
--7667-- Reading syms from /lib64/libz.so.1.2.7
--7667--   Considering
/usr/lib/debug/.build-id/07/c94c65d4108bb9372f7943566cc01c54f161ca.debug
..
--7667--   .. build-id is valid
--7667-- REDIR: 0x596e4d0 (strncasecmp) redirected to 0x4a24750
(_vgnU_ifunc_wrapper)
--7667-- REDIR: 0x5968590 (strnlen) redirected to 0x4a24750
(_vgnU_ifunc_wrapper)
--7667-- REDIR: 0x596c200 (strcasecmp) redirected to 0x4a24750
(_vgnU_ifunc_wrapper)
--7667-- REDIR: 0x5967e00 (strcpy) redirected to 0x4a24750
(_vgnU_ifunc_wrapper)
--7667-- REDIR: 0x5968460 (strlen) redirected to 0x4a24750
(_vgnU_ifunc_wrapper)
--7667-- REDIR: 0x596afe0 (memset) redirected to 0x4a24750
(_vgnU_ifunc_wrapper)
--7667-- REDIR: 0x5970bb0 (memcpy@@GLIBC_2.14) redirected to 0x4a24750
(_vgnU_ifunc_wrapper)
--7667-- REDIR: 0x59666b0 (strcat) redirected to 0x4a24750
(_vgnU_ifunc_wrapper)
--7667-- REDIR: 0x5969f80 (__GI_strrchr) redirected to 0x4c2c750
(__GI_strrchr)
--7667-- REDIR: 0x59684b0 (__GI_strlen) redirected to 0x4c2ccb0
(__GI_strlen)
--7667-- REDIR: 0x5962bb0 (malloc) redirected to 0x4c2c200 (malloc)
--7667-- REDIR: 0x59720f0 (strchrnul) redirected to 0x4c2f2c0
(strchrnul)
--7667-- REDIR: 0x59630d0 (free) redirected to 0x4c2aef0 (free)
--7667-- REDIR: 0x59dca60 (__strcpy_chk) redirected to 0x4c2f330
(__strcpy_chk)
--7667-- REDIR: 0x5970c00 (__GI_memcpy) redirected to 0x4c2dc70
(memcpy@@GLIBC_2.14)
--7667-- REDIR: 0x5968670 (strncmp) redirected to 0x4a24750
(_vgnU_ifunc_wrapper)
--7667-- REDIR: 0x59686b0 (__GI_strncmp) redirected to 0x4c2d180
(__GI_strncmp)
--7667-- REDIR: 0x59668f0 (__GI_strchr) redirected to 0x4c2c830
(__GI_strchr)
--7667-- REDIR: 0x59668b0 (index) redirected to 0x4a24750
(_vgnU_ifunc_wrapper)
Parsing config from /home/ar/test.cfg
--7667-- REDIR: 0x5963160 (realloc) redirected to 0x4c2c400 (realloc)
--7667-- REDIR: 0x5966970 (strcmp) redirected to 0x4a24750
(_vgnU_ifunc_wrapper)
--7667-- REDIR: 0x59669b0 (__GI_strcmp) redirected to 0x4c2d8f0
(__GI_strcmp)
--7667-- REDIR: 0xffffffffff600000 (???) redirected to 0x3806c733
(vgPlain_amd64_linux_REDIR_FOR_vgettimeofday)
--7667-- REDIR: 0x5963c30 (calloc) redirected to 0x4c2a020 (calloc)
--7667-- REDIR: 0x5975870 (__memset_x86_64) redirected to 0x4c2ed70
(memset)
--7667-- REDIR: 0x5969f40 (rindex) redirected to 0x4a24750
(_vgnU_ifunc_wrapper)
==7667== Warning: noted but unhandled ioctl 0x305000 with no
size/direction hints
==7667==    This could cause spurious value errors to appear.
==7667==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing
a proper wrapper.
==7667== Conditional jump or move depends on uninitialised value(s)
==7667==    at 0x505FBC4: libxl__domain_build_info_setdefault
(libxl_utils.h:101)
==7667==    by 0x505B404: libxl_domain_need_memory (libxl.c:3514)
==7667==    by 0x40CB8C: create_domain (xl_cmdimpl.c:1591)
==7667==    by 0x410A60: main_create (xl_cmdimpl.c:3905)
==7667==    by 0x406FFF: main (xl.c:267)
==7667==  Uninitialised value was created by a stack allocation
==7667==    at 0x4014225: _dl_runtime_resolve (dl-trampoline.S:43)
==7667==
==7667== (action on error) vgdb me ...
======================================================================
gdb xl
GNU gdb (GDB) SUSE (7.4.50.20120603-78.5)
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/sbin/xl...Reading symbols from
/usr/lib/debug/usr/sbin/xl.debug...done.
done.
(gdb) target remote | /usr/lib64/valgrind/../../bin/vgdb --pid=7667
Remote debugging using | /usr/lib64/valgrind/../../bin/vgdb --pid=7667
relaying data between gdb and process 7667
Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from
/usr/lib/debug/lib64/ld-2.15.so.debug...done.
done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
[Switching to Thread 7667]
0x00000000040014e0 in _start () from /lib64/ld-linux-x86-64.so.2
(gdb) continue
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
0x000000000505fbc4 in libxl_cpu_bitmap_alloc (max_cpus=6,
cpumap=0x7fefff238, ctx=0x6f1e0b0) at libxl_utils.h:101
101     libxl_utils.h: No such file or directory.
(gdb) bt
#0  0x000000000505fbc4 in libxl_cpu_bitmap_alloc (max_cpus=6,
cpumap=0x7fefff238, ctx=0x6f1e0b0) at libxl_utils.h:101
#1  libxl__domain_build_info_setdefault (gc=gc@entry=0x7fefff060,
b_info=b_info@entry=0x7fefff220) at libxl_create.c:215
#2  0x000000000505b405 in libxl_domain_need_memory (ctx=<optimized out>,
b_info=b_info@entry=0x7fefff220,
need_memkb=need_memkb@entry=0x7fefff0f0) at libxl.c:3514
#3  0x000000000040cb8d in freemem (b_info=0x7fefff220) at
xl_cmdimpl.c:1591
#4  create_domain (dom_info=dom_info@entry=0x7fefff4d0) at
xl_cmdimpl.c:1874
#5  0x0000000000410a61 in main_create (argc=3, argv=0x7fefffac0) at
xl_cmdimpl.c:3905
#6  0x0000000000407000 in main (argc=3, argv=0x7fefffac0) at xl.c:267
(gdb)
======================================================================

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.