[Pkg-libvirt-maintainers] Bug#574177: Bug#574177: libvirt-bin: after upgrade of libvirt it crashes on system bootup, but afterwards a manual start works fine

[Guido Günther]

On Tue, Mar 16, 2010 at 10:48:35PM +0100, Sebastian Wienforth wrote:
> Package: libvirt-bin
> Version: 0.7.7-1
> Severity: important
> 
> Since the last upgrade, which upgraded the following packages:
> 
> [ENTFERNEN, NICHT VERWENDET] linux-headers-2.6.32-trunk-amd64
> [ENTFERNEN, NICHT VERWENDET] linux-headers-2.6.32-trunk-common
> [INSTALLIEREN, ABHÄNGIGKEITEN] linux-headers-2.6.32-3-amd64
> [INSTALLIEREN, ABHÄNGIGKEITEN] linux-headers-2.6.32-3-common
> [INSTALLIEREN, ABHÄNGIGKEITEN] linux-image-2.6.32-3-amd64
> [AKTUALISIERUNG] acpi-support-base 0.132-2 -> 0.133-1
> [AKTUALISIERUNG] cpio 2.10-1 -> 2.11-1
> [AKTUALISIERUNG] firmware-linux-free 2.6.32-5 -> 2.6.32-9
> [AKTUALISIERUNG] firmware-linux-nonfree 0.22 -> 0.23
> [AKTUALISIERUNG] gettext-base 0.17-9 -> 0.17-10
> [AKTUALISIERUNG] libgtk-vnc-1.0-0 0.3.10-2+b1 -> 0.3.10-5
> [AKTUALISIERUNG] libnewt0.52 0.52.10-5+b1 -> 0.52.10-8
> [AKTUALISIERUNG] libparted1.8-12 1.8.8.git.2009.07.19-5 -> 1.8.8.git.2009.07.19-6
> [AKTUALISIERUNG] libvirt-bin 0.7.6-2 -> 0.7.7-1
> [AKTUALISIERUNG] libvirt-doc 0.7.6-2 -> 0.7.7-1
> [AKTUALISIERUNG] libvirt0 0.7.6-2 -> 0.7.7-1
> [AKTUALISIERUNG] linux-headers-2.6-amd64 2.6.32+23 -> 2.6.32+25
> [AKTUALISIERUNG] linux-image-2.6-amd64 2.6.32+23 -> 2.6.32+25
> [AKTUALISIERUNG] linux-image-amd64 2.6.32+23 -> 2.6.32+25
> [AKTUALISIERUNG] linux-libc-dev 2.6.32-5 -> 2.6.32-9
> [AKTUALISIERUNG] python-gtk-vnc 0.3.10-2+b1 -> 0.3.10-5
> [AKTUALISIERUNG] python-libvirt 0.7.6-2 -> 0.7.7-1
> [AKTUALISIERUNG] rsyslog 4.4.2-2 -> 4.6.1-1
> [AKTUALISIERUNG] tzdata 2010b-1 -> 2010e-1
> [AKTUALISIERUNG] whiptail 0.52.10-5+b1 -> 0.52.10-8
> 
> libvirt does not seem to be running anymore after system bootup: 
> $ virsh list
> error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be started: Verbindungsaufbau abgelehnt
> error: failed to connect to the hypervisor
> 
> However the KVM-VMs which are set to boot up automatically are started as usual.
> 
> syslog says the following:
> Mar 16 21:55:54 zeus kernel: [   39.834290] lo: Disabled Privacy Extensions
> Mar 16 21:55:54 zeus libvirtd: 21:55:54.945: warning : lxcStartup:1748 : Unable to create cgroup for driver: No such device or address
> Mar 16 21:55:54 zeus libvirtd: 21:55:54.974: error : main:3160 : Driver state in itialization failed
> Mar 16 21:55:54 zeus libvirtd: 21:55:54.974: warning : qemudDispatchSignalEvent:385 : Shutting down on signal 3
> 
> issuing a 
> $ /etc/init.d/libvirt-bin start
> starts libvirt, and now also virsh is working as normal.
> 
> However syslog says the following:
> Mar 16 22:02:05 zeus libvirtd: 22:02:05.257: error : halDeviceMonitorStartup:737 : libhal_ctx_init failed, haldaemon is probably not running

The amd64 package is linked against hal which it shouldn't be. I'll
disable the usage of hal in explicitly and upload a new version. That
should fix your problem!
Thanks for the report,
 -- Guido