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:
A running lxc guest will be stopped after restarting libvirtd service.
Version-Release number of selected component (if applicable):
# rpm -q libvirt
libvirt-0.10.2-4.el6.x86_64
How reproducible:
sometimes
Steps to Reproduce:
1. virsh -c lxc:// start toy
2. virsh -c lxc:// list
3. service libvirtd restart
4. repeat step 2
Actual results:
# virsh -c lxc:// start toy
Domain toy started
# virsh -c lxc:// list
Id Name State
----------------------------------------------------
23987 toy running
# service libvirtd restart
Stopping libvirtd daemon: [ OK ]
Starting libvirtd daemon: [ OK ]
# virsh -c lxc:// list --all
Id Name State
----------------------------------------------------
- toy shut off
Expected results:
the guest should be running status.
Additional info:
# virsh -c lxc:// dumpxml toy
<domain type='lxc'>
<name>toy</name>
<uuid>bb428983-cb9f-4702-0f8d-7d4e143d9aad</uuid>
<memory unit='KiB'>500000</memory>
<currentMemory unit='KiB'>500000</currentMemory>
<vcpu placement='static'>4</vcpu>
<os>
<type arch='x86_64'>exe</type>
<init>/bin/sh</init>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/libexec/libvirt_lxc</emulator>
<console type='pty'>
<target type='lxc' port='0'/>
</console>
</devices>
</domain>
I can only reproduce this some of the time. When it does occur though I see the following in /var/log/libvirt/lxc/$GUEST.log
2012-11-02 15:30:24.416+0000: 6378: error : virNetSocketReadWire:1184 : End of file while reading data: Input/output error
2012-11-02 15:30:24.423+0000: 6378: error : virNetServerAddClient:270 : Too many active clients (1), dropping connection from 127.0.0.1;0
For some reason libvirt_lxc process is not handling the EOF correctly, causing it to refuse the libvirtd connection. Libvirtd then kills off the container.
Upstream fix was
commit f33e43c2353cc10065b8a5f9965d5a57cfe8991f
Author: Daniel P. Berrange <berrange>
Date: Fri Nov 16 09:11:23 2012 +0000
Use virNetServerRun instead of custom main loop
The LXC controller code currently directly invokes the
libvirt main loop code. The problem is that this misses
the cleanup of virNetServerClient connections that
virNetServerRun takes care of.
The result is that when libvirtd is stopped, the
libvirt_lxc controller process gets stuck in a I/O loop.
When libvirtd is then started again, it fails to connect
to the controller and thus kills off the entire domain.
Signed-off-by: Daniel P. Berrange <berrange>
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/RHSA-2013-0276.html
Description of problem: A running lxc guest will be stopped after restarting libvirtd service. Version-Release number of selected component (if applicable): # rpm -q libvirt libvirt-0.10.2-4.el6.x86_64 How reproducible: sometimes Steps to Reproduce: 1. virsh -c lxc:// start toy 2. virsh -c lxc:// list 3. service libvirtd restart 4. repeat step 2 Actual results: # virsh -c lxc:// start toy Domain toy started # virsh -c lxc:// list Id Name State ---------------------------------------------------- 23987 toy running # service libvirtd restart Stopping libvirtd daemon: [ OK ] Starting libvirtd daemon: [ OK ] # virsh -c lxc:// list --all Id Name State ---------------------------------------------------- - toy shut off Expected results: the guest should be running status. Additional info: # virsh -c lxc:// dumpxml toy <domain type='lxc'> <name>toy</name> <uuid>bb428983-cb9f-4702-0f8d-7d4e143d9aad</uuid> <memory unit='KiB'>500000</memory> <currentMemory unit='KiB'>500000</currentMemory> <vcpu placement='static'>4</vcpu> <os> <type arch='x86_64'>exe</type> <init>/bin/sh</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> </domain>