[libvirt] Issue with libvirtd

[Michal Privoznik]

On 06.02.2017 14:39, Boris Fiuczynski wrote:
> On 01/10/2017 10:19 AM, Michal Privoznik wrote:
>> On 01/10/2017 07:48 AM, Faysal Ali wrote:
>>> Hi Michal,
>>
>> [It is usually good idea to keep the list CCed - it may help others
>> finding a solution to their problems]
>>
>>>
>>> Well I have created my little python/libivrt app to manage my virtual
>>> machines. I am using python socket to check libivrt port
>>> availability, and
>>> the error End of file while reading data: Input/output error* only
>>> happens
>>> whenever that python socket script is trigger.
>>>
>>> Here is the script of python socket
>>>
>>> import libvirt, socket, sys
>>>
>>> hostname='kvm09'
>>> port = 16509
>>>
>>> try:
>>>       socket_host = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
>>>       socket_host.settimeout(1)
>>>       socket_host.connect((hostname, port))
>>>       socket_host.close()
>>>       print 'true'
>>> except Exception as err:
>>>       print err
>>
>> Ah, I haven't expected this. Of course your are seeing the error
>> message. Libvirt has its own protocol on the top of TCP and since you
>> are connecting and dying immediately - without sending any valid libvirt
>> packet, the daemon logs an error. This is perfectly expected.
>>
>> Also, this is *not* how you connect to libvirt. You want to open a
>> libvirt connection:
>>
>> conn = libvirt.open(uri)
>> dom = conn.lookupByName(name)
>> ...
>>
>> Michal
> 
> Michal,
> my expectation is that virsh is using a libvirt connection.
> Anyway I am getting the error whenever I use virsh start, virsh destroy
> or virsh shutdown on a domain, e.g.
> 
> Feb 06 14:01:30 s38lp24 virtlogd[42845]: 2017-02-06 13:01:30.675+0000:
> 42845: error : virNetSocketReadWire:1800 : End of file while reading
> data: Input/output error
> Feb 06 14:04:32 s38lp24 virtlogd[42845]: 2017-02-06 13:04:32.991+0000:
> 42845: error : virNetSocketReadWire:1800 : End of file while reading
> data: Input/output error
> 
> Would that also be covered under "This is perfectly expected."?
> 
> 

No. this shouldn't happen. Although, I'm not that familiar with the code
to tell why & what should be fixed.

Michal