July 2008 - Devel - libvirt List Archives

[libvirt] ruby-libvirt on debian based systems
by Tom Verhaeghe 21 Jul '08

21 Jul '08

Hello I don't know if ruby-libvirt can work in a debian-based environment. I installed kvm, libvirt, RoR, etc on Ubuntu and it all works fine. I pasted the output when installing the gem below. I think the problem could be that libvirt is called differently in Ubuntu or stored on a different location. Is there a way to get around? Thanks in advance Tom Building native extensions. This could take a while... ERROR: While executing gem ... (RuntimeError) Error instaling ruby-libvirt-0.0.7.gem: ERROR: Failed to build gem native extension. ruby extconf.rb install ruby-libvirt-0.0.7.gem *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/usr/bin/ruby1.8 --with-_libvirt-dir --without-_libvirt-dir --with-_libvirt-include --without-_libvirt-include=${_libvirt-dir}/include --with-_libvirt-lib --without-_libvirt-lib=${_libvirt-dir}/lib --with-libvirt-config --without-libvirt-config --with-pkg-config --without-pkg-config extconf.rb:16: libvirt not found (RuntimeError) Gem files will remain installed in /var/lib/gems/1.8/gems/ruby-libvirt-0.0.7 for inspection. Results logged to /var/lib/gems/1.8/gems/ruby-libvirt-0.0.7/ext/libvirt/gem_make.out

2 2

[libvirt] Problem building RPM on x86_64
by Darryl L. Pierce 21 Jul '08

21 Jul '08

I'm hitting the following problem while building an RPM for x86_64: (mcpierce@dpierce-dev:libvirt)$ make rpm Making clean in po make[1]: Entering directory `/home/mcpierce/Programming/libvirt/po' rm -f *.insert-header rm -f remove-potcdate.sed rm -f stamp-poT rm -f core core.* libvirt.po libvirt.1po libvirt.2po *.new.po rm -fr *.o ... make[2]: Leaving directory `/home/mcpierce/Programming/libvirt/gnulib/tests' make[2]: Entering directory `/home/mcpierce/Programming/libvirt/python' make[2]: *** No rule to make target `libvirt-py.c', needed by `distdir'. Stop. make[2]: Leaving directory `/home/mcpierce/Programming/libvirt/python' make[1]: *** [distdir] Error 1 make[1]: Leaving directory `/home/mcpierce/Programming/libvirt' make: *** [rpm] Error 2 However, on i386 the build works just fine. -- Darryl L. Pierce, Sr. Software Engineer Red Hat, Inc. - http://www.redhat.com/ oVirt - Virtual Machine Management - http://www.ovirt.org/ "What do you care what other people think, Mr. Feynman?"

3 7

[libvirt] [PATCH] parse container id in separate function
by Evgeniy Sokolov 21 Jul '08

21 Jul '08

There were several places with parsing container id from code. Separate function is used now.

3 8

[libvirt] Re: make fails (Kenneth Nagin)
by Kenneth Nagin 21 Jul '08

21 Jul '08

>I downloaded the latest libvirt and tried to make it but received this >error message: >make: *** No rule to make target `gnulib/m4/onceonly_2_57.m4', needed by >`Makefile.in'. Stop. The problem was related to running ./autogen.sh --prefix=$HOME/usr. I didn't notice that it did not run correctly. It requires the install gettext-devel which does not come automatically with fedora. But now the make fails due to an i386 / i386:x86-64 incompatibility. These are the error messages: /usr/bin/ld: i386 architecture of input file `.libs/libvirt_la-openvz_conf.o' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `.libs/libvirt_la-openvz_driver.o' is incompatible with i386:x86-64 output collect2: ld returned 1 exit status make[2]: *** [libvirt.la] Error 1 make[2]: Leaving directory `/home/nagin/workspace/libvirt/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/nagin/workspace/libvirt' make: *** [all] Error 2 -- Kenneth Nagin

3 4

[libvirt] leak? xenUnifiedOpen
by Stefan de Konink 21 Jul '08

21 Jul '08

==5486== 184 bytes in 1 blocks are definitely lost in loss record 5 of 18 ==5486== at 0x4C20111: calloc (vg_replace_malloc.c:397) ==5486== by 0x4E3ADFD: __virAlloc (memory.c:100) ==5486== by 0x4E4AF21: xenUnifiedOpen (xen_unified.c:264) ==5486== by 0x4E3A005: do_open (libvirt.c:777) ==5486== by 0x4009D7: main (in /home/skinkie/development/htdocs/cherokee/experiment) Maybe valgrind is over active, because I see the free code at the close connection, and my own code is closing it... Stefan

3 5

[libvirt] [PATCH] cpu usage in OpenVZ
by Evgeniy Sokolov 21 Jul '08

21 Jul '08

OpenVZ calculate statistics and allow to get them . Added function for getting cpu usage of container.

3 3

[libvirt] [PATCH] configure.in: make --with-xen-distdir work for 64bit xen too
by David Lively 21 Jul '08

21 Jul '08

Currently running autogen.sh with --with-xen-distdir=something fails to find libxenstore if there's only a 64-bit version, and subsequently fails to enable xen support (i.e., ends up with WITH_XEN=0). This one-line patch fixes that by telling it to search both lib and lib64. I guess it would be better to search only the appropriate directory (lib OR lib64) rather than both, but I'm not sure (being an autoconf-dummy) how to ask about the target architecture. Dave configure.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

2 1

[libvirt] [PATCH] fix lookup
by Evgeniy Sokolov 21 Jul '08

21 Jul '08

I am often catching error related with that stoped VM has ID = -1. 1. If I create/define VM with existing ID of stoped VM. Creation failed, but error message is wrong. Detection is fixed. 2. Dominfo command may show info about some another VM. And report error that can't get autostart state. Current patch shoud fix problems.

3 2

[libvirt] make fails
by Kenneth Nagin 20 Jul '08

20 Jul '08

I downloaded the latest libvirt and tried to make it but received this error message: make: *** No rule to make target `gnulib/m4/onceonly_2_57.m4', needed by `Makefile.in'. Stop. Kenneth Nagin

1 0

[libvirt] Inconsistency with documentation virDomainGetMaxMemory(NULL)
by Stefan de Konink 19 Jul '08

19 Jul '08

I was making a some test code to checkout some code before I start on my brand new Invite/Tender cluster distribution engine(tm ;) From docs: Retrieve the maximum amount of physical memory allocated to a domain. If domain is NULL, then this get the amount of memory reserved to Domain0 i.e. the domain where the application runs. skinkie@xenapi ~/development/htdocs/cherokee $ ./experiment libvir: Domain error : invalid domain pointer in virDomainGetMaxMemory 0 262144 Code: printf("%ld\n", virDomainGetMaxMemory(NULL)); virDomainPtr domu = virDomainLookupByName(conn, "klant1_gentoo"); printf("%ld\n", virDomainGetMaxMemory(domu)); virDomainFree(domu); Stefan

1 3