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.
On 9 Aug 2017 2:19 p.m., "Daniel P. Berrange" <berrange@xxxxxxxxxx> wrote:
On Wed, Aug 09, 2017 at 11:53:54AM +0800, netsurfed wrote:
> Hi all,
> I think it's a bug, when call virDomainGetState after "service libvirtd stop"
> , I receive signal SIGPIPE.
For the QEMU driver, the libvirt library just talks to libvirtd over an
RPC layer. You killed libvirtd, so the libvirt library gets SIGPIPE.
> I want to know how to avoid this problem? And Other interfaces will also
If you want libvirt to work, don't stop libvirtd
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
