Domain not found while running examples in libvmi folder

[Irfan]

I am running debian-6.0.3-i386 and getting the following error when
trying to run the examples in libvmi folder. I have also enabled the
debug in libvmi.h by uncommenting the following line.
#define VMI_DEBUG


ERROR
----------------------------------------------------------------
root@debian:/opt/libvmi-0.6/examples# ./process-list centos
libvir: QEMU error : Domain not found: no domain with matching name
'centos'
[ 0]
[ 0] (null)
[ 0] (null)
[ 0] (null)
[ 0] (null)
[ 0] (null)
[ 0] (null)
.
.
.
-----------------------

Following are some of the information about libvmi.conf, xm list
output and configure output.


/etc/libvmi.conf
---------------------------------------
centos {
ostype = "Linux";
sysmap = "/boot/System.map-2.6.32-5-xen-686";
}


Output of # xm list
--------------------------------------------------------------
root@debian:/opt/libvmi-0.6# xm list
Name ID Mem VCPUs
State Time(s)
Domain-0 0 1742 1
r----- 244.2
centos 1 256 1 --
p--- 10.7


Configure script
----------------------------

root@debian:/opt/libvmi-0.6# ./configure --prefix=/usr/local
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether build environment is sane... yes
checking for xs_read in -lxenstore... yes
checking for xc_interface_open in -lxenctrl... yes
checking for vcpu_guest_context_any_t... yes
checking for virConnectOpen in -lvirt... yes
checking for bison... bison
Found yacc as bison.
checking for bison... (cached) bison
checking for lex... lex
Found lex as lex.
checking for flex... (cached) lex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GLIB... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating libvmi.pc
config.status: creating libvmi/Makefile
config.status: creating libvmi/config/Makefile
config.status: creating examples/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
-------------------------------------------------------------------------------
LibVMI is configured as follows. Please verify that this configuration
matches your expectations.

Host system type: i686-pc-linux-gnu
Build system type: i686-pc-linux-gnu
Installation prefix: /usr/local

Feature | Option | Reason
-------------|--------------------|-----------------------
Xen Support | --enable-xen=yes | yes
KVM Support | --enable-kvm=yes | yes
File Support | --enable-file=yes | yes

If everything is correct, you can now run 'make' and (optionally)
'make install'. Otherwise, you can run './configure' again.
___________________________________________________________________


Any idea how to resolve it?

[Bryan Payne]

This is because you have KVM support enabled, but you are connecting
with a Xen domain. The message comes from the KVM libraries and can
be safely ignored in your case.

-Bryan

> --
> You received this message because you are subscribed to the Google Groups "vmitools" group.
> To post to this group, send email to vmit...@googlegroups.com.
> To unsubscribe from this group, send email to vmitools+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/vmitools?hl=en.
>