Libvirt Error: virNetSocketReadWire:1791 : End of file while reading data: Input/output error after upgrading to 6.11.5

[phoria]

On 1/19/2023 at 3:44 PM, bobobeastie said:

I just started having this same issue after changing all of my cache mounts from referencing user to the cache drives name because I saw a youtube video about IO Wait.  Changed the 2 path settings in the VM config back and still have the issue. it's a home assistant VM if anyone cares.  I was having rebooting issues before today, but I found a message regarding insufficient memory, which I think I solved by changing the memory settings for the VM, so probably unrelated.

 

Reboot didn't do anything.  Tried creating a new debian VM and that wont start either.  Diagnostics attached are from after reboot and Debian attempt/test.

nastheripper-diagnostics-20230119-1642.zip 264.56 kB · 2 downloads

I did this exact same thing.  Did you find an answer?

[bobobeastie]

1 hour ago, phoria said:

I did this exact same thing.  Did you find an answer?

Sorry, my solution was buying a used SFF desktop from ebay to run proxmox on. Bonus of now having an intel igpu for transcoding, my 2 nasses are AM4 Ryzen based.

[pbear]

Hello,

 

I see the same error messages in my libvirt logs:

 

2023-04-21 05:06:45.301+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
2023-04-21 05:16:47.245+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
2023-04-21 05:26:49.130+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
2023-04-21 05:36:51.072+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
2023-04-21 05:46:52.946+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
2023-04-21 05:56:54.872+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error

 

Also, when I reboot my unraid server I receive an email about an error:

Event: VM Autostart disabled
Subject: vfio-bind-error
Description: VM Autostart disabled due to vfio-bind error
Importance: alert

 

I'm not sure that both events are related.

 

[SimonF]

12 minutes ago, pbear said:

Hello,

 

I see the same error messages in my libvirt logs:

 

2023-04-21 05:06:45.301+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
2023-04-21 05:16:47.245+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
2023-04-21 05:26:49.130+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
2023-04-21 05:36:51.072+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
2023-04-21 05:46:52.946+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
2023-04-21 05:56:54.872+0000: 11094: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error

 

Also, when I reboot my unraid server I receive an email about an error:

Event: VM Autostart disabled
Subject: vfio-bind-error
Description: VM Autostart disabled due to vfio-bind error
Importance: alert

 

I'm not sure that both events are related.

 

You must be running 6.12rc3 and your hardware has changed. You need to look at vfio log

 

Upon boot, if all PCI devices specified in 'config/vfio-pci.cfg' file do not properly bind, VM Autostart is prevented. You may still start individual VMs. This is to prevent Unraid host crash if hardware PCI IDs changed because of a kernel update or physical hardware change. To restore VM autostart, examine '/var/log/vfio-pci-error' and remove offending PCI IDs from 'config/vfio-pci.cfg' file and reboot.

[artx]

2023年7月18日了，这个问题似乎没有解决办法，哪怕我重新使用全新制作的unraid启动程序，依然报这个烦人的错误，很奇怪，它每10分钟报错一次，心态快崩溃了！来自——unraid 6.11.5

Edited July 18, 2023 by artx

[artx]

THIS FAILURE IS RELATED TO UNRAID CONNECT："LIBVIRT ERROR: VIRNETSOCKETREADWIRE:1791 : END OF FILE WHILE READING DATA: INPUT/OUTPUT ERROR"

 

The reason for this problem has been found so far, I hope it can help everyone!

[SimonF]

This should be fixed in next connect release. Are all people getting this using myservers or connect?

[sonic6]

@SimonF this is still present in Version: 6.12.4-rc18  

 

2023-08-22 06:53:15.285+0000: 21622: info : libvirt version: 8.7.0
2023-08-22 06:53:15.285+0000: 21622: info : hostname: Unraid-1
2023-08-22 06:53:15.285+0000: 21622: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
2023-08-22 07:03:17.050+0000: 21622: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
2023-08-22 07:13:18.738+0000: 21622: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error

 

Diagnostic is attached

unraid-1-diagnostics-20230822-0920.zip

[elibosley]

@SimonF MyServers and Connect are the same thing - Connect is the successor to My Servers.

 

We're going to be shipping an updated plugin within the next couple of weeks that resolves this. 

[elibosley]

Hi Everyone - Current plan is to ship a new plugin build tomorrow or Wednesday that should solve these problems.

 

Stay tuned and hopefully this new build will resolve your issues!

[OsoPolar]

HI Guys

 

I have updated everything but still getting this error all the time has the fix been released yet?

 

error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error

 

bearcave-diagnostics-20230906-1852.zip

Edited September 6, 2023 by OsoPolar