Re: libxl and libvirt in Fedora (rawhide)

[Jim Fehlig <jfehlig@suse.com>]

Dario Faggioli wrote:
> On Thu, 2013-01-17 at 09:00 -0700, Jim Fehlig wrote: 
>   
>> Dario Faggioli wrote:
>>     
>>> Hi Jim,
>>>
>>> I'm having some problems with the libvirt libxl driver you're working
>>> on. More specifically, it does not seem to be working for me, at least
>>> not in the form in which it comes out of the related Fedora package.
>>>
>>> If/When you have a minute, would it be possible to you to have a look
>>> here:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=893699
>>> https://bugzilla.redhat.com/show_bug.cgi?id=893699#c10 ?
>>>   
>>>       
>> Thanks for the bug ref, I've made a comment there.
>>
>>     
> Thanks. I replied myself, trying to provide some more information about
> what's going on...
>
>   
>> As mentioned in the bug, the libxl driver will not load if xend is
>> running.  It appears xend is not running on your system, so hopefully
>> there is something in your libvirtd logs telling why the driver did not
>> load.
>>
>>     
> I'm not even sure whether xend is running or not! :-( As I wrote there,
> even when I only see the xend status check, I have xm working, which
> shouldn't happen without a proper xend running, right?
>   

For those not following in the bug, the libxl driver executes
'/usr/sbin/xend status' and refuses to load it xend is running.  The
problem here is that the status check causes xend to start!  I can't
reproduce the issue, so perhaps it is specific to the fedora packages.

> Moreover, independently from whether I install the package or not, or
> whether I kill/start xend manually, it looks indeed like the libxl
> driver is not able to load itself.
>   

Since checking xend status starts the service and returns that it is
running, the driver won't load :).

> Where should I look for the libvirtd logs you're mentioning? I've
> checked in /var/log/libvirt/* and in /var/log/messages, without finding
> anything interesting. Should I look somewhere else? Should I pass
> additional parameter to any of the involved components?
>   

See /etc/libvirt/libvirtd.conf for a nice set of logging controls.

Regards,
Jim