Bug 500577 - haldaemon starts too late during init to be used by other services
haldaemon starts too late during init to be used by other services
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: hal (Show other bugs)
All Linux
low Severity medium
: beta
: ---
Assigned To: Richard Hughes
Depends On:
  Show dependency treegraph
Reported: 2009-05-13 07:16 EDT by Daniel Berrange
Modified: 2009-09-02 07:25 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-09-02 07:25:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch to match fedora (510 bytes, patch)
2009-05-13 11:05 EDT, Richard Hughes
no flags Details | Diff

  None (edit)
Description Daniel Berrange 2009-05-13 07:16:24 EDT
Description of problem:
In RHEL5 the haldaemon initscript is set to start at position "98". This makes it hard for other services to use HAL, because it only leaves 1 single position left for all other services requiring HAL. 

In RHEL this breaks libvirt's hardware device management APIs, because libvirt starts at position 97 and is then unable to commnunicate with HAL.

In Fedora HAL is starting at a much more sensible position '26'. This needs to be done in RHEL too. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. chkconfig libvirtd on
2. chkconfig haldaemon on
3. shutdown -r now
4. wait for it to reboot and finish init
5. virsh nodedev-list 
Actual results:
# virsh nodedev-list --tree
error: Failed to count node devices
error: this function is not supported by the hypervisor: virNodeNumOfDevices
# service libvirtrd restart
# virsh nodedev-list --tree
  |   |
  |   +-net_00_16_3e_09_f5_eb
  |   |
  |   +-net_00_16_3e_09_f4_eb
  |   |
  |   +-net_00_16_3e_09_f3_eb
  |   |
.... etc...

Expected results:
# virsh nodedev-list works immediately following completion of boot. 

Additional info:
Comment 4 Richard Hughes 2009-05-13 11:05:14 EDT
Created attachment 343782 [details]
patch to match fedora
Comment 11 errata-xmlrpc 2009-09-02 07:25:20 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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