<div dir="auto">The error message could however give a hint what is going on. It should sax that it is impossible to talk to libvirtd and that it might be stopped.</div><div class="gmail_extra"><br><div class="gmail_quote">On 9 Aug 2017 2:19 p.m., "Daniel P. Berrange" <<a href="mailto:berrange@redhat.com">berrange@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Aug 09, 2017 at 11:53:54AM +0800, netsurfed wrote:<br>
> Hi all,<br>
> I think it's a bug, when call virDomainGetState after "service libvirtd stop"<br>
> , I receive signal SIGPIPE.<br>
<br>
For the QEMU driver, the libvirt library just talks to libvirtd over an<br>
RPC layer. You killed libvirtd, so the libvirt library gets SIGPIPE.<br>
<br>
> I want to know how to avoid this problem? And Other interfaces will also<br>
<br>
If you want libvirt to work, don't stop libvirtd<br>
<br>
Regards,<br>
Daniel<br>
--<br>
|: <a href="https://berrange.com" rel="noreferrer" target="_blank">https://berrange.com</a> -o- <a href="https://www.flickr.com/photos/dberrange" rel="noreferrer" target="_blank">https://www.flickr.com/photos/<wbr>dberrange</a> :|<br>
|: <a href="https://libvirt.org" rel="noreferrer" target="_blank">https://libvirt.org</a> -o- <a href="https://fstop138.berrange.com" rel="noreferrer" target="_blank">https://fstop138.berrange.com</a> :|<br>
|: <a href="https://entangle-photo.org" rel="noreferrer" target="_blank">https://entangle-photo.org</a> -o- <a href="https://www.instagram.com/dberrange" rel="noreferrer" target="_blank">https://www.instagram.com/<wbr>dberrange</a> :|<br>
<br>
______________________________<wbr>_________________<br>
libvirt-users mailing list<br>
<a href="mailto:libvirt-users@redhat.com">libvirt-users@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/libvirt-users" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/libvirt-users</a><br>
</blockquote></div></div>