Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Any attempt to launch an LXC container is met with a 60+ second delay
Debugging found that the delay occurs when libvirt spawns the libvirt_lxc process.
Further debugging shows that the libvirt_lxc process is waiting on execution of
/bin/sh /usr/bin/pm-is-supported --suspend-hybrid
(or the same command with different --suspend args).
This is being run to initialize the capabilities.
The pm-is-supported program uses dbus to talk to hal, and it never gets a reply from hal, so suffers from the dbus message reply timeout (30 seconds IIRC)
In 6.4 the SELinux policy for libvirt_lxc was applied, so it runs in a context
unconfined_u:system_r:virtd_lxc_t:s0-s0:c0.c1023
And it seems this is blocked from communicating with hal
type=USER_AVC msg=audit(1379605503.647:24171): user pid=1262 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_return dest=:1.86 spid=13198 tpid=6431 scontext=unconfined_u:system_r:hald_t:s0 tcontext=unconfined_u:system_r:virtd_lxc_t:s0-s0:c0.c1023 tclass=dbus exe="/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'
This delay isn't seen in Fedora, but then Fedora doesn't use HAL anymore, so probably avoids the issue.
Version-Release number of selected component (if applicable):
# rpm -q libvirt selinux-policy
libvirt-0.10.2-18.el6_4.9.x86_64
selinux-policy-3.7.19-195.el6_4.12.noarch
How reproducible:
Always, if SELinux is enforcing and libvirtd is confined
Steps to Reproduce:
1. Install RHEL-6.4
2. Install libvirtd and run it 'service libvirtd start' (NB, must be run via 'service' to gain correct selinux context).
3. # virt-install --connect lxc:/// --name lxcsh --nodisks --ram 100 --init /bin/sh
Actual results:
60+ second delay in virt-install
Expected results:
Instant creation fo container.
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-1598.html
Description of problem: Any attempt to launch an LXC container is met with a 60+ second delay Debugging found that the delay occurs when libvirt spawns the libvirt_lxc process. Further debugging shows that the libvirt_lxc process is waiting on execution of /bin/sh /usr/bin/pm-is-supported --suspend-hybrid (or the same command with different --suspend args). This is being run to initialize the capabilities. The pm-is-supported program uses dbus to talk to hal, and it never gets a reply from hal, so suffers from the dbus message reply timeout (30 seconds IIRC) In 6.4 the SELinux policy for libvirt_lxc was applied, so it runs in a context unconfined_u:system_r:virtd_lxc_t:s0-s0:c0.c1023 And it seems this is blocked from communicating with hal type=USER_AVC msg=audit(1379605503.647:24171): user pid=1262 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_return dest=:1.86 spid=13198 tpid=6431 scontext=unconfined_u:system_r:hald_t:s0 tcontext=unconfined_u:system_r:virtd_lxc_t:s0-s0:c0.c1023 tclass=dbus exe="/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?' This delay isn't seen in Fedora, but then Fedora doesn't use HAL anymore, so probably avoids the issue. Version-Release number of selected component (if applicable): # rpm -q libvirt selinux-policy libvirt-0.10.2-18.el6_4.9.x86_64 selinux-policy-3.7.19-195.el6_4.12.noarch How reproducible: Always, if SELinux is enforcing and libvirtd is confined Steps to Reproduce: 1. Install RHEL-6.4 2. Install libvirtd and run it 'service libvirtd start' (NB, must be run via 'service' to gain correct selinux context). 3. # virt-install --connect lxc:/// --name lxcsh --nodisks --ram 100 --init /bin/sh Actual results: 60+ second delay in virt-install Expected results: Instant creation fo container. Additional info: