I decided to change my network connection to static in unraid last night instead of assigning an ip via my router as previous to get rid of the ip renewal messages in my log. All went well with the change, but now all of the sudden my ArchVM(Iconicbadger's) seems to loose network connection at some point. So i changed it back hoping to fix the problem.......

 

my issue is that now that its changed back, ArchVM still seems to loose its connectivity after a period of time, I can't find anywhere in Arch to find log's & nothing shows up in unraid sys logs!!!

 

I see Arch is still running, as I can get access to the console with xl console command

any help would be appreciated!!

This is the Message I have been receiveing ....

 

Dec 15 09:32:38 test emhttp: read_line: client closed the connection
Dec 15 09:36:26 test emhttp: read_line: client closed the connection
Dec 15 09:48:12 test kernel: vif vif-4-0 vif4.0: txreq.offset: 8ee, size: 3858, end: 6144
Dec 15 09:48:12 test kernel: vif vif-4-0 vif4.0: fatal error; disabling device
Dec 15 09:48:12 test kernel: br0: port 3(vif4.0) entered disabled state

Alot of people are having this issue (including me). IMO when docker support came out XEN support went poof. Just do like most of us and try rolling back to a different beta. Google "Xen Bug#767261"

hmmm I have a very similar problem (with similar unraid vif log error showing) but it ONLY appears when running transmission inside Arch with an active leech/seed.  Multiple Plex streams don't seem to cause it so it isn't purely bandwidth related; two plex streams are way more bandwidth than a torrent saturated broadband connection. With transmission running it lasts for about 5 min tops which is abuot as long as it takes I guess for connections to pile up. If there aren't a bunch of connections (not leeching / low demand seed) then it doesn't fail. but once it does, the network into DomU is dead but I can still get there via xl console. powerdown of the VM also fails about 75% of the time (or takes waaaay longer than I will wait) and I have to destroy it. Seems to be hanging on shutting down transmission.

 

I've debated rolling back Xen versions. IIRC yuo can just copy the xen folder from an older beta. But I have no intention of rolling back unraid. I'm also just considering going to KVM [shrug] I haven't decided yet.  right now the simplest seems to rollback Xen so I might try that tonight. But jonp has been giving me some help with Xen=>KVM conversion so I might give that a try too

i fully expect Lime to drop Xen in the near future.

 

There are 3 different was to do VMs unraid docker, Xen, and KVM. It just sucks because i know how do use xen the most lol.

hahah same here. But KVM does seem to to be winning the race currently and I don't just mean in the unraid world [shrug] but my view is very limited. Learning something new is always a good idea anyway and that is part of the reason I'm starting the transition process now. I just converted completely to XFS and changed to an SSD cache drive (arch is still on my separate SSD at the moment though) to make it easier to convert my apps without disturbing my production VM. Part of me is even tempted to just go the docker route, but I really like the increased level of isolation of a full VM and I like playing around with Arch (another learning opportunity).

 

oh well ... we move on.