search for: test_driver

Hi All, For some testing purpose I've changed some content in src/test/test_driver.c and then used "make" command to compile and build the code. Then I copied the "libvirt.so.0.9.10.so" file to the target machine and restart the libvirtd daemon, but the changes I made in test_driver.c is nothing reflected. I'm not sure whether I'm missing something. Is...

Hi All, I'm need to simulate libvirt API's say to mock the libvirt API responses. (Actually I need to simulate qemu API's response). Because of my project needs I need to write this simulated libvirt server in Java. I believe the simulated libvirt can be written as java RPC which should capable to receive the client RPC request calls and by dispatcher we can dispatch to the

...sts as this function is quite > a core one and it's implementation is a bit confusing (maybe a > refactoring would simplify its logic). > Unfortunately the function is not exposed, therefore unittests are a bit > challenging. Higher level tests seem to mock the driver > (src/test/test_driver.c) as well. > > Here's the patch fixing the issue. I set the correct uid and gid only if > the file is being created and dynamic ownership is set. > > diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c > index a2cc002..1b47dc6 100644 > --- a/src/qemu/qemu_driver...

...l drivers are), then libvirt.so passes it to src/remote/remote_driver.c to be bundled up into RPC calls which mirror the semantics of the public API. If you want to install your own mock driver, it may be easier to build a new URI and implement the same C interface as the test driver (see src/test/test_driver.c) than it is to implement your own RPC parser. > > Also I'm not sure how to implement the ssl layer support for the > libvirt server in java. I need to write a java server in such a way that > python client should capable to create a connection with uri > "qemu+t...

Hi, Excuse me, I have watched qemu_driver.c where most of the libvirt API is overrided in order to connect qemu. But I am confused which functions then call those qemu_driver API? I mean where is the qemu_driver implementation? Libvirt.c? But how does the qemu_driver connect and control qemu? Thanks a lot! Regards, Corey -------------- next part -------------- An HTML

Trying to build the virtualbox-4.2 branch from git://pipo.sk/pipo/libvirt.git under OSX 10.7, I get the following build error: ... CC timegm.lo CC vasnprintf.lo CCLD libgnu.la /usr/bin/ranlib: file: .libs/libgnu.a(fd-hook.o) has no symbols /usr/bin/ranlib: file: .libs/libgnu.a(threadlib.o) has no symbols ranlib: file: .libs/libgnu.a(fd-hook.o) has no symbols ranlib: file:

...libvirt.so > passes it to src/remote/remote_driver.c to be bundled up into RPC calls > which mirror the semantics of the public API. If you want to install > your own mock driver, it may be easier to build a new URI and implement > the same C interface as the test driver (see src/test/test_driver.c) > than it is to implement your own RPC parser. > > > > > Also I'm not sure how to implement the ssl layer support for the > > libvirt server in java. I need to write a java server in such a way that > > python client should capable to create a connectio...

For future reference, it looks like we should avoid DONT_RESOLVE_DLL_REFERENCES in any extensions. http://weblogs.asp.net/oldnewthing/archive/2005/02/14/372266.aspx Regards, Dan