I tried to fire up VirtManager today for the first time since the recent round of updates but libvirtd is looking for libhal ( which no longer exists? )

Any ideas on this dependency? Can I use the 13.37 package?

Regards, Robby

you can rebuild it passing "--without-hal" to configure: if you like, I have an updated SlackBuild for -current (note that now libvirt needs yajl)

http://cgit.ponce.cc/slackbuilds/commit/?h=libvirt

(you can find also the other virt-manager related stuff updated in my repository for -current)

Thanks Ponce, I'll take a look!

Hi Ponce, I need a little more help. I downloaded the slackbuilds-libvirt.tar.gz file from your link however it appears to have the entire slackbuilds repo in it rather than just the libvirt stuff - is this correct?

I've targeted the following packages so far:

system/virtinst
system/virt-manager
system/virt-viewer
libraries/libvirt

And maybe

network/openvswitch

Is there anything I'm missing?

Regards, Robby

that .tar.gz is a git snapshot of the only libvirt branch (it contains only modifications to the libvirt.SlackBuild).
you can easily use the -current repo with sbopkg or just clone the default branch from github
you will have a folder with all the modified slackbuilds (but using with sbopkg is more practical)

note that I haven't modified openvswitch: you can see my modifications in the branches details.

if you want to build the updated libvirt/virt-manager stuff, this a possible queue you can use (you can also save it as /var/lib/sbopkg/queues/myvirt.sqf and build everything with "sbopkg -i myvirt" -that's the slack!)
if you are not interested in spice support, you can omit
the same with qemu, if you are not interested in that version (that includes qemu-1.1.1 and qemu-kvm-1.1.1) and prefer using your own.
you will probably need also to build netcat-openbsd to use in place of the default netcat in slackware, as this latest lack some options used by libvirt: install it, then

Thanks Ponce!

I've decided to use the sbopkg git option as that is probably the easiest. I'd like spice support but get an error when doing the spice-gtk package:

Not sure what the is all about ...

Any ideas?

I'm also getting a failure on your netcat-openbsd package with the patch checksum:

- build spice-gtk with the option VALA=yes (needs vala installed): you can also set it in the queuefile with
or on the command line
- the patch checksum is wrong, so I think you can say to sbopkg to build it regardlessly.

Sorry my mistake - I didn't read your original response well enough.

I had a number of other dependencies that needed to be upgraded as follows:

libsigc++
glibmm
gconf

At least virt-manager istarting now but I've got some further errors. Will need to troubleshoot further. Thanks for all your help!

GConf in -current should be enough, the other two shouldn't be needed.
try to start from a clean configuration for libvirt: run
substituting /etc/libvirt/* with the new versions.

Ok the error I have now is libvirt-related - when starting virt-manager I get:

Unable to connect to libvirt.
Cannot recv data: Connection reset by peer

Libvirt URI is: qemu:///system

I've checked that libvirtd is running and also enabled logging ( info level ) - there is nothing beyond normal stuff in /var/log/messages.

Even at debug level, there are no additional messages in messages log when connecting from virt-manager. I've tired virsh as well:

I thought might be due to the fact that I only installed qemu-kvm ( and not qemu ) which is what I've done in the past. Only problem is that your qemu package compiles for all archs which takes a really long time. In any case, I'm not convinced it's required.

no, qemu shouldn't be a problem. BTW, you can build qemu-kvm, that is at the same version and builds only qemu-kvm (it's my qemu package that builds both).

set in /etc/libvirt/libvirtd.conf, uncommenting the relative lines
then issue an

Still no luck - same error. I've removed all of these packages and recompile/installed them again in case there was some issue in the upgrade process. I did note the following during the sbopkg build of virt-manager:

Libvirtd packages: none
KVM Packages: none

It seems that virt-manager configure is not picking up the dependencies? And because there is not kvm/libvirtd support in the build, it won't connect to the qemu service ...

that messages during the build of virt-manager are normal (got the same here).

if a simple (as root), from the host running libvirt (it tries to connect by default to qemu:///system, as you can see in /etc/libvirt/libvirt.conf)
don't list your vms, the only thing I can guess is that you got some problems with the configuration files (virt-manager is not even involved in this case): as your log shows, libvirtd seems to be running fine.

maybe setting log_level = 1 (debug) could help diagnose the problem, that apparently seems that you cannot just connect to it.

Thanks Ponce, yeah that's my thoughts as well:

virsh list --all
error: Failed to reconnect to the hypervisor
error: no valid connection
error: Unable to encode message header
error: Failed to reconnect to the hypervisor

I'm going to setup a slack14 vbox system ( the irony! ) for testing and redo these packages from start. My current system has been upgraded all the way from 13.0 so there may be something there causing an issue. Thanks very much for your help in any case.

Regards, Robby