<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Wed, Oct 31, 2018 at 2:58 AM Jim Fehlig <<a href="mailto:jfehlig@suse.com" target="_blank">jfehlig@suse.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 10/29/18 11:58 PM, Minjun Hong wrote:<br>
> On Tue, Oct 30, 2018 at 4:57 AM Jim Fehlig <<a href="mailto:jfehlig@suse.com" target="_blank">jfehlig@suse.com</a> <br>
> <mailto:<a href="mailto:jfehlig@suse.com" target="_blank">jfehlig@suse.com</a>>> wrote:<br>
> <br>
> On 10/29/18 12:26 PM, Minjun Hong wrote:<br>
> > Hello.<br>
> > I want to use libvirt for toolstack of Xen (not XenServer) to set up<br>
> Openstack<br>
> > system but,<br>
> > I'm new to libvirt so, I had some troubles on installing libvirt.<br>
> ><br>
> > I downloaded the source code, build and installed it, following here<br>
> > (<a href="https://libvirt.org/compiling.html" rel="noreferrer" target="_blank">https://libvirt.org/compiling.html</a>).<br>
> > However, when I type a command (# virsh 'xen:///system' list) to check if<br>
> > libvirt has been installed successfully,<br>
> > I can see an error message:<br>
> ><br>
> > error: failed to connect to the hypervisor<br>
> > error: internal error: libxenlight state driver is not active<br>
> <br>
> It sounds like the libvirt libxl driver failed to load. Are there any related<br>
> messages from libvirtd in your syslog or hints in<br>
> /var/log/libvirt/libxl/libxl-driver.log?<br>
> <br>
> Regards,<br>
> Jim<br>
> <br>
> <br>
> Thanks for your answer, Jim.<br>
> <br>
> I check the log file you mentioned, but it was empty.<br>
<br>
Hmm, are you sure you built the libxl driver when configuring/building libvirt? <br>
Did you explicitly specify it when invoking './configure'? E.g. './configure <br>
--with-libxl ...'?<br>
<br>
If not explicitly specified the default is to check for xen build requirements. <br>
Do you have the xen development package (e.g. xen-devel) installed? You can <br>
check the summary of the configure output (should also be in your config.log) to <br>
see if building the libxl driver is enabled. You should see 'libxl: yes' under <br>
the Drivers section of the configuration summary.<br>
<br>
> So, I lost my way how to, where to access this problem.<br>
> And, by chance, I checked the status of 'libvirtd':<br>
> <br>
> ● libvirtd.service - Virtualization daemon<br>
> Loaded: loaded (/usr/local/lib/systemd/system/libvirtd.service; enabled;<br>
> vendor preset: enabled)<br>
> Active: active (running) since 2018-10-30 14:47:58 KST; 9s ago<br>
> Docs: man:libvirtd(8)<br>
> <a href="https://libvirt.org" rel="noreferrer" target="_blank">https://libvirt.org</a><br>
> Process: 6029 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)<br>
> Main PID: 8940 (libvirtd)<br>
> Tasks: 20 (limit: 32768)<br>
> CGroup: /system.slice/libvirtd.service<br>
> ├─2217 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf<br>
> --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper<br>
> ├─2221 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf<br>
> --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper<br>
> └─8940 /usr/local/sbin/libvirtd<br>
> node1 systemd[1]: Starting Virtualization daemon...<br>
> node1 systemd[1]: Started Virtualization daemon.<br>
> node1 libvirtd[8940]: 2018-10-30 05:47:59.010+0000: 8956: info : libvirt<br>
> version: 4.9.0<br>
> node1 libvirtd[8940]: 2018-10-30 05:47:59.010+0000: 8956: info : hostname: node1<br>
> node1 libvirtd[8940]: 2018-10-30 05:47:59.010+0000: 8956: error :<br>
> virGetUserID:1041 : invalid argument: Failed to parse user 'tss'<br>
> node1 libvirtd[8940]: 2018-10-30 05:47:59.010+0000: 8956: error :<br>
> virGetGroupID:1124 : invalid argument: Failed to parse group 'tss'<br>
> node1 libvirtd[8940]: 2018-10-30 05:47:59.342+0000: 8956: error :<br>
> networkCheckRouteCollision:122 : internal error: Network is already in use<br>
> by interface virbr0<br>
> <br>
> <br>
> I found out a hint.<br>
> Actually, I have already done googling regarding this problem so much, but I do <br>
> not know what problem is about user 'tss'.<br>
<br>
The missing 'tss' user and group is actually not a problem. In fact, Martin <br>
committed a patch to squelch those errors<br>
<br>
<a href="https://libvirt.org/git/?p=libvirt.git;a=commit;h=b907fd75fa826a8285dc33fcf6117c7833e2853b" rel="noreferrer" target="_blank">https://libvirt.org/git/?p=libvirt.git;a=commit;h=b907fd75fa826a8285dc33fcf6117c7833e2853b</a><br>
<br>
Does the libvirt you're building include that patch?<br>
<br>
Regards,<br>
Jim<br></blockquote><div><br></div><div>Thanks for your advise.</div><div>I found the solution. Cause of the problem was additional install of libvirt-bin by apt.</div><div>I'm not sure what was wrong. But when I set up libvirt on an other server, there was no problem.</div><div>So I guess the additional install might be main reason.</div><div>I removed the package and built libvirt source code again. And finally, I could see it was working well.<br></div><div><br></div><div>And as you mentioned, the other bug about user 'tss' was not critical problem. That's why I'm just using the libvirt which does not include the patch.</div><div><br></div><div>Thank you so much, Jim</div></div></div>