Bug 698539 - libvirtd can not start successfully in s390x box
Summary: libvirtd can not start successfully in s390x box
Keywords:
Status: CLOSED DUPLICATE of bug 698208
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.1
Hardware: s390x
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-21 07:52 UTC by Min Zhan
Modified: 2011-04-21 08:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-21 08:35:58 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Min Zhan 2011-04-21 07:52:22 UTC
Description of problem:
libvirtd can not start successfully in s390x box after installing libvirt pkgs.It fails on initializing udev state driver.

As far as I know, s390 don't have PCI buses, so the fact that initializing that library there fails, is well normal I guess. But the problem is that it should not prevent libvirtd from starting on s390x, as we need it for lxc there.

Version-Release number of selected component (if applicable):
libvirt-0.8.7-18.el6.s390x

How reproducible:
Always

Steps to Reproduce:
1. Install libvirt, libvirt-client, libvirt-python pkgs on s390x box
# rpm -q libvirt
libvirt-0.8.7-18.el6.s390x

2. # service libvirtd restart
Stopping libvirtd daemon: [FAILED]
Starting libvirtd daemon: [  OK  ]

# service libvirtd status
libvirtd dead but subsys locked

# virsh -c lxc:///
error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be started: No such file or directory
error: failed to connect to the hypervisor

Actual results:
libvirtd can not start successfully

Expected results:
libvirtd can start successfully and works well.


Additional Info:

# tail -f /var/log/messages
...
Apr 21 03:33:22 auto-s390-002 dbus: [system] Reloaded configuration
Apr 21 03:33:22 auto-s390-002 yum[28419]: Updated: polkit-0.96-2.el6_0.1.s390x
Apr 21 03:33:52 auto-s390-002 rhsm-complianced: This system is missing one or more valid entitlement certificates. Please run subscription-manager for more information.
Apr 21 03:37:17 auto-s390-002 libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: No such file or directory
Apr 21 03:37:18 auto-s390-002 libvirtd: 03:37:18.065: 29136: info : libvirt version: 0.8.7, package: 18.el6 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2011-04-18-10:28:07, s390-009.build.bos.redhat.com)
Apr 21 03:37:18 auto-s390-002 libvirtd: 03:37:18.065: 29136: error : udevDeviceMonitorStartup:1606 : Failed to initialize libpciaccess: No such file or directory
Apr 21 03:37:18 auto-s390-002 libvirtd: 03:37:18.065: 29136: error : virStateInitialize:1022 : Initialization of udev state driver failed
Apr 21 03:37:18 auto-s390-002 kernel: lo: Disabled Privacy Extensions
Apr 21 03:37:18 auto-s390-002 libvirtd: 03:37:18.268: 29136: error : main:3326 : Driver state initialization failed
Apr 21 03:37:18 auto-s390-002 libvirtd: 03:37:18.268: 29139: warning : qemudDispatchSignalEvent:403 : Shutting down on signal 3

Comment 1 Michal Privoznik 2011-04-21 08:35:58 UTC

*** This bug has been marked as a duplicate of bug 698208 ***


Note You need to log in before you can comment on or make changes to this bug.