VM network freeze

Discussion in 'Proxmox VE: Networking and Firewall' started by Kiril, Sep 25, 2017.

  1. mladen popov

    mladen popov New Member
    Proxmox Subscriber

    Joined:
    Sep 26, 2017
    Messages:
    11
    Likes Received:
    0
    After running kernel 4.15.18-7-pve for a couple of weeks we HAVENT encounter any of the problems mentioned before by or any of the other users. The nod is running fine and it is housing mix of LXC and KVMs.
     
  2. norderstedt

    norderstedt Member

    Joined:
    Nov 28, 2016
    Messages:
    49
    Likes Received:
    2
    We plan to upgrade our test-cluster to -7 on monday. We'll report our investigations regarding the mentioned problems afterwards.
     
  3. norderstedt

    norderstedt Member

    Joined:
    Nov 28, 2016
    Messages:
    49
    Likes Received:
    2
    We've tested the latest kernel right now, same problems:

    SCP transfer (and other kind of communications) from one LXC to another shows stalling transferspeeds after X amount of transferred bytes. We'd highly suggest to look into this as this affects all of our current cluster setups and we're forced to stick with an older kernel as of now.

    Appreciated.
     
  4. norderstedt

    norderstedt Member

    Joined:
    Nov 28, 2016
    Messages:
    49
    Likes Received:
    2
    Hello again,

    we really need some help now. We're paying a huge amount of money to Proxmox per year and would like to have this issue solved. We cannot upgrade _any_ machine and are stuck with an old version. Please help us.

    Appreciated.
     
  5. tom

    tom Proxmox Staff Member
    Staff Member

    Joined:
    Aug 29, 2006
    Messages:
    13,469
    Likes Received:
    395
    Do you run latest kernel? If not, please upgrade and test again.

    If you have a valid subscription with support ticket support, please get in touch via our enterprise support team via https://my.proxmox.com
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. norderstedt

    norderstedt Member

    Joined:
    Nov 28, 2016
    Messages:
    49
    Likes Received:
    2
    The problem is it exists only in newer kernel versions. We're running version 4.15.18-4-pve #1 SMP PVE 4.15.18-23 (Thu, 30 Aug 2018 13:04:08 +0200) because all kernels released afterwards are faulty, although we could not find any changes in your git repository concerning our observed bug.

    We'll try to use the ticket system now. Appreciated.
     
  7. PotterNick

    PotterNick New Member

    Joined:
    Jan 2, 2019
    Messages:
    2
    Likes Received:
    0
    Reset 'mate' settings, not? or read the logs
     
  8. mladen popov

    mladen popov New Member
    Proxmox Subscriber

    Joined:
    Sep 26, 2017
    Messages:
    11
    Likes Received:
    0
    Quick update and reality check!

    I don't know if this is still the same issue, but it definitely looks like it so I'm gonna post it here. After having a very smooth sail for a while i got one of our server updated with 5.4 and running 4.15.18-12-pve #1 SMP PVE 4.15.18-35, and after that im getting very weird behavior from some if not most of the vm's that are running on that node. The VMs would lose network connectivity for no apparent reason, you cant ping anything on the network for short periods of time then it would work until it doesn't. Its dropping connections at a totally random, for example, i would use one of the Vm's to connect to customers vpn and it would start dropping packets like crazy or once it connects ill get reconnecting every few seconds. I have not made any changes related to the setup rather than updating the installed packages. I saw a few networking related topics in the forum that look awfully familiar to what i experience. I was wondering if it just me or any of the participants of this topic could relate?
    Thanks,
    Mladen
     
    #68 mladen popov, Apr 19, 2019
    Last edited: Apr 19, 2019
  9. mac.linux.free

    Joined:
    Jan 29, 2017
    Messages:
    99
    Likes Received:
    5
    I had the same symptoms. It only applys to windows vms and virtio. I fixed it by editing the vm-nic (in windows) and disable all offloading features or change to e1000.
     
  10. mladen popov

    mladen popov New Member
    Proxmox Subscriber

    Joined:
    Sep 26, 2017
    Messages:
    11
    Likes Received:
    0
    I wish your solution would've worked. I have problems with both, win and Linux vm's, but the interruptions are totally weird. And from the looks of it seems like those vms just their knowledge of the network and they need some time to rediscover everything but also drops the connectivity. The old trick with ping from withing vm seems to work, but is not ideal. My windows vms are running e1000, but ill try to switch it with vritio to test it out for a little before i revert to the one kernel i know it works just fine. ill keep you all posted.

    UPDATE: After switching to virtio things got even worst. The vm would lose connectivity every 30ish or so seconds, but if i start a ping to anything it will go uninterrupted and vm is working just fine. Im reverting to e1000, and maybe to an older kernel version later today.

    UPDATE2: reverted to kernel - 4.15.18-9-pve and its all back to normal

    Thanks,
    Mladen
     
    #70 mladen popov, Apr 22, 2019
    Last edited: Apr 22, 2019
  11. mladen popov

    mladen popov New Member
    Proxmox Subscriber

    Joined:
    Sep 26, 2017
    Messages:
    11
    Likes Received:
    0
    Quick update: Ive been running 4.15.18-14-pve #1 SMP PVE 4.15.18-39 kernel for the past 10 days on all 3 of our nodes and have not noticed any of the problems mentioned before.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice