Hide Forgot
Description of problem: As $subject says, if you have lxc domain which is inactive, you will see error like following in libvirtd log. 12:01:57.644: error : lxcMonitorClient:949 : Failed to connect to client socket: No such file or directory 12:01:57.644: error : lxcMonitorClient:949 : Failed to connect to client socket: No such file or directory The problem is caused by we load all the domain configs for lxc domains in one stage, and then trys to connect the all the domain's monitor, regardless of wether the domain is active or not. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
patch pushed in upstream, http://www.redhat.com/archives/libvir-list/2011-May/msg01849.html
This should be fixed by the libvirt-0.9.2-1.el6 rebase
verify pass on libvirt-0.9.2-1.el6 kernel-2.6.32-156.el6.x86_64 qemu-kvm-0.12.1.2-2.165.el6.x86_64 steps to reproduce: 1. cat toy.xml <domain type='lxc'> <name>vm1</name> <uuid>386f5b25-43ee-9d62-4ce2-58c3809e47c1</uuid> <memory>500000</memory> <currentMemory>500000</currentMemory> <vcpu>1</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> <interface type='network'> <mac address='52:54:00:f2:2c:ac'/> <source network='default'/> <target dev='veth0'/> </interface> <console type='pty'> <target port='0'/> </console> </devices> </domain> # virsh -c lxc:/// define toy.xml # virsh -c lxc:/// list --all Id Name State ---------------------------------- - vm1 shut off 2. setting /etc/libvirt/libvirtd.conf add log_outputs="1:file:/var/log/libvirt/libvirtd.log" 3. restart libvirtd several times # service libvirtd restart # service libvirtd restart 4. see log on /var/log/libvirt/libvirtd.log For libvirt-0.9.2-1.el6, can not see error info
Set it as VERIFIED per comment4
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-2011-1513.html