<div dir="ltr">You might want to send these questions to the user mailing list instead, which is libvirt-users. This mailing list is for libvirt development discussions related as well as patches.</div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Fri, Dec 13, 2013 at 1:21 PM, Joaquim Barrera <span dir="ltr"><<a href="mailto:jbarrera@ac.upc.edu" target="_blank">jbarrera@ac.upc.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hello everybody!<br>
<br>
I would like to introduce myself, as this is my first contact with
libvirt mailing list (although I've been reading quite a lot of
documentation).<br>
<br>
My name is Joaquim Barrera, from Barcelona, Catalonia. I am a
computer engineer and recently I joined a research group here in the
university. My task is related to VM migration and management, and
since then (a couple of months) I've been trying to figure some
things up.<br>
<br>
Now I need to go one step forward, and I would like to set up a nice
dev environment to try some modifications we want to make to
libvirt, such as new API or migration-related-stuff.<br>
<br>
Although I am familiar with linux environrment and programming, I am
not really quite familiar with this kind of, may I say, professional
development, and there are some issues I need to solve before start
writting code. Some of this issues you'll find not relevant or
newbie stuff, but I assure you I tried lots of times before coming
here. :-)<br>
<br>
Here is what I got following the instructions in
<a href="http://libvirt.org/compiling.html" target="_blank">http://libvirt.org/compiling.html</a><br>
<br>
<pre style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;background-color:rgb(238,238,238);font-weight:normal;padding:1em;line-height:normal;text-transform:none;border:1px solid rgb(153,153,153);background-repeat:initial initial;word-spacing:0px">
$ ./autogen.sh --system
$ make</pre>
<br>
After make finishes I have compiled 1.2.0 libvirt in the source
tree, and if I execute 'sudo ./run tools/virsh version' I get a this
answer:<br>
<br>
<i>Compiled against library: libvirt 1.2.0</i><i><br>
</i><i>Using library: libvirt 1.2.0</i><i><br>
</i><i>Using API: QEMU 1.2.0</i><i><br>
</i><i>Running hypervisor: QEMU 1.5.0</i><br>
<br>
(note that now I need to run virsh with sudo, I don't know exactly
why)<br>
<br>
So far, so good. I guess that, with --system flag, 1.2.0 custom
libvirt uses config files from standard directories such as
/etc/libvirt/libvirtd.conf, and if I used a custom directory
instead, I would have to redefine my VMs, am I right?<br>
<br>
Problems come when I want to use custom 1.2.0 daemon. If I execute
"sudo service libvirt-bin stop" followed by "./daemon/libvirtd -d",
then custom virsh gives me this error:<br>
<br>
<i>error: failed to connect to the hypervisor</i><i><br>
</i><i>error: no valid connection</i><i><br>
</i><i>error: Failed to connect socket to
'/var/run/libvirt/libvirt-sock': No such file or directory</i><br>
<br>
And I need to kill custom daemon and restart 1.1.1 libvirtd to
recover from this. Any advice?<br>
<br>
Finally (sorry about this large mail), there is one thing that does
bother me quite a lot.<br>
<br>
Using custom virsh, command history seems to vanish, as I press
Arrow-UP and I get "^[[A" in the screen, instead of last command
used. Tell me, please, that this is just some silly config I need to
adjust... :_(<br>
<br>
The final comment is, am I following the right direction to be able
to develop something with libvirt? ^^<br>
<br>
Ok, that's all for now, thank you A LOT for your time.<span class="HOEnZb"><font color="#888888"><br>
<br>
Joaquim.<br>
<br>
<br>
</font></span></div>
<br>--<br>
libvir-list mailing list<br>
<a href="mailto:libvir-list@redhat.com">libvir-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/libvir-list" target="_blank">https://www.redhat.com/mailman/listinfo/libvir-list</a><br></blockquote></div><br></div>