Re: [libvirt-users] Xen via libvirt

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