VM looses network

Discussion in 'Proxmox VE: Networking and Firewall' started by kenneth_vkd, Nov 8, 2018.

  1. kenneth_vkd

    kenneth_vkd New Member

    Joined:
    Sep 13, 2017
    Messages:
    7
    Likes Received:
    0
    Hi
    Right around the same time as PVE 5.2 was released, we deployed a new cluster of PVE servers running on PVE 5.2.0

    Everything went fine and all VMs are working with no problems.

    For system monitoring we use Zabbix 3.0 LTS and we have a zabbix proxy on one of the nodes. A few months ago we started to have some issues where the network to the proxy-VM would drop for 15-20 minutes then come back for around 5 minutes and then drop again for 15-20 minutes.
    At that time we had the proxy running on CentOS 7.4 with SELinux disabled. As we thought that maybe something is wrong with the data on the VM, we formatted the VM and installed everthing again. Still nothing changed. Then we deleted the VM and created a new one with the same VM ID, but this time we installed Debian 9. Same result.

    Just today I wanted to try it again and deleted the VM. Then I created it again, but on another host and installed CentOS 7.4 again. It ran fine and then I installed everything, but as soon as the zabbix-proxy service was started, it ran for around an hour with no issues and we started the zabbix-agent on one of the VMs that should report to the proxy instead of the zabbix-server directly. Then after about 10 minutes, then VM lost all network connectivity and it did not come back even after rebooting and even shutting down and moving to another host.

    We have verified that the network card shows up with `ip a` and that it goes away when we shut down the VM.

    Has anyone else experienced similar issues with Zabbix or other similar software products?

    Output of pveversion -V:
    Code:
    proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve)
    pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
    pve-kernel-4.15: 5.2-8
    pve-kernel-4.15.18-5-pve: 4.15.18-24
    pve-kernel-4.15.18-4-pve: 4.15.18-23
    pve-kernel-4.15.18-3-pve: 4.15.18-22
    pve-kernel-4.15.18-2-pve: 4.15.18-21
    pve-kernel-4.15.18-1-pve: 4.15.18-19
    pve-kernel-4.15.17-3-pve: 4.15.17-14
    pve-kernel-4.15.17-2-pve: 4.15.17-10
    corosync: 2.4.2-pve5
    criu: 2.11.1-1~bpo90
    glusterfs-client: 3.8.8-1
    ksm-control-daemon: 1.2-2
    libjs-extjs: 6.0.1-2
    libpve-access-control: 5.0-8
    libpve-apiclient-perl: 2.0-5
    libpve-common-perl: 5.0-40
    libpve-guest-common-perl: 2.0-18
    libpve-http-server-perl: 2.0-11
    libpve-storage-perl: 5.0-29
    libqb0: 1.0.1-1
    lvm2: 2.02.168-pve6
    lxc-pve: 3.0.2+pve1-2
    lxcfs: 3.0.2-2
    novnc-pve: 1.0.0-2
    proxmox-widget-toolkit: 1.0-20
    pve-cluster: 5.0-30
    pve-container: 2.0-27
    pve-docs: 5.2-8
    pve-firewall: 3.0-14
    pve-firmware: 2.0-5
    pve-ha-manager: 2.0-5
    pve-i18n: 1.0-6
    pve-libspice-server1: 0.12.8-3
    pve-qemu-kvm: 2.11.2-1
    pve-xtermjs: 1.0-5
    qemu-server: 5.0-36
    smartmontools: 6.5+svn4324-1
    spiceterm: 3.0-5
    vncterm: 1.5-3
    zfsutils-linux: 0.7.11-pve1~bpo1
     
  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