The fact that you're not experiencing this issue with the Linux guest is proof enough for me to point to the GPLPV drivers for Windows as the culprit here (or something in between them and the Xen kernel who actually knows who's to blame for it). Only using windows VM's and the other VM is only running plex which does not have the problem, (you really gotta torrent across the network for it to break). I lose all network connectivity for about 30 seconds, then everything comes back up. I dont have to do anything when it happens as it is self correcting. They are the GPLPV drivers, havent tried removing them. usr/bin/tail -n 42 -f /var/log/syslog 2>&1ĭec 31 07:58:23 Icarus kernel: vif vif-3-0 vif3.0: Carrier off due to lack of guest response on queue 0ĭec 31 07:58:23 Icarus kernel: br0: port 3(vif3.0) entered disabled stateĭec 31 07:58:23 Icarus kernel: vif vif-3-0 vif3.0: Carrier on againĭec 31 07:58:23 Icarus kernel: br0: port 3(vif3.0) entered listening stateĭec 31 07:58:33 Icarus kernel: mdcmd (54): spindown 0ĭec 31 07:58:38 Icarus kernel: br0: port 3(vif3.0) entered learning stateĭec 31 07:58:53 Icarus kernel: br0: topology change detected, propagatingĭec 31 07:58:53 Icarus kernel: br0: port 3(vif3.0) entered forwarding stateĭec 31 07:59:59 Icarus emhttp: read_line: client closed the connectionĭec 31 08:01:00 Icarus emhttp: read_line: client closed the connectionĭec 31 08:02:01 Icarus emhttp: read_line: client closed the connectionĭec 31 08:03:02 Icarus emhttp: read_line: client closed the connectionĭec 31 08:04:03 Icarus emhttp: read_line: client closed the connectionĭec 31 08:05:05 Icarus emhttp: read_line: client closed the connectionĭec 31 08:06:06 Icarus emhttp: read_line: client closed the connectionĭec 31 08:07:07 Icarus emhttp: read_line: client closed the connectionĭec 31 08:08:08 Icarus emhttp: read_line: client closed the connectionĭec 31 08:09:09 Icarus emhttp: read_line: client closed the connectionĭec 31 08:10:11 Icarus emhttp: read_line: client closed the connectionĭec 31 08:11:12 Icarus emhttp: read_line: client closed the connectionĭec 31 08:12:13 Icarus emhttp: read_line: client closed the connectionĭec 31 08:13:15 Icarus emhttp: read_line: client closed the connectionĭec 31 08:14:16 Icarus emhttp: read_line: client closed the connectionĭec 31 08:15:17 Icarus emhttp: read_line: client closed the connectionĭec 31 08:16:19 Icarus emhttp: read_line: client closed the connectionĭec 31 08:17:20 Icarus emhttp: read_line: client closed the connectionĭec 31 08:18:22 Icarus emhttp: read_line: client closed the connectionĭec 31 08:19:23 Icarus emhttp: read_line: client closed the connectionĭec 31 08:20:25 Icarus emhttp: read_line: client closed the connectionĭec 31 08:21:26 Icarus emhttp: read_line: client closed the connectionĭec 31 08:22:27 Icarus emhttp: read_line: client closed the connectionĭec 31 08:23:29 Icarus emhttp: read_line: client closed the connectionĭec 31 08:24:30 Icarus emhttp: read_line: client closed the connectionĭec 31 08:25:31 Icarus emhttp: read_line: client closed the connectionĭec 31 08:26:32 Icarus emhttp: read_line: client closed the connectionĭec 31 08:27:34 Icarus emhttp: read_line: client closed the connectionĭec 31 08:28:35 Icarus emhttp: read_line: client closed the connectionĭec 31 08:29:37 Icarus emhttp: read_line: client closed the connectionĭec 31 08:30:38 Icarus emhttp: read_line: client closed the connectionĭec 31 08:31:39 Icarus emhttp: read_line: client closed the connectionĭec 31 08:32:40 Icarus emhttp: read_line: client closed the connection How to reproduce: Fire up a windows VM under XEN, Map a network drive and download a few torrents across the network.Įxpected results: The torrents will kick out the same error.ĭec 11 05:52:44 Icarus emhttp: read_line: client closed the connectionĭec 11 05:53:47 Icarus emhttp: read_line: client closed the connectionĭec 11 05:54:20 Icarus kernel: vif vif-5-0 vif5.0: Carrier off due to lack of guest response on queue 0ĭec 11 05:54:20 Icarus kernel: br0: port 3(vif5.0) entered disabled stateĭec 11 05:54:20 Icarus kernel: vif vif-5-0 vif5.0: Carrier on againĭec 11 05:54:20 Icarus kernel: br0: port 3(vif5.0) entered listening stateĭec 11 05:54:35 Icarus kernel: br0: port 3(vif5.0) entered learning stateĭec 11 05:54:50 Icarus kernel: br0: topology change detected, propagatingĭec 11 05:54:50 Icarus kernel: br0: port 3(vif5.0) entered forwarding stateĭec 11 05:54:52 Icarus emhttp: read_line: client closed the connectionĭec 11 05:57:28 Icarus emhttp: read_line: client closed the connection This is from the mapped drive where it is downloading to disconnecting. (Write to Disk)" Or it can also say read from disk. Description: When using a Windows VM under Xen, the network mapped drive keeps dropping connection causing utorrent to report "Unexpected network error occured.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |