Hi all,
I think it's a bug, when call virDomainGetState after "service libvirtd stop",
I receive signal SIGPIPE.
I want to know how to avoid this problem? And Other interfaces will also
encounter this problem？
Below the bt information:
Below some information about my hypervisor:
root@ubuntu-05:/
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
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" wrote:
> On Wed, Aug 09, 2017 at 11:53:54AM +0800, netsurfed wrote:
> > Hi all,
> > I think it's a bug
On 08/09/2017 03:59 PM, Dominik Psenner wrote:
> 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.
[Please don't top post on technical lists]
Yes and no. There can be a lot of reasons why client ca
