I installed a new VM into my Proxmox two weeks ago and network adapter started dropping every 3-5 days, Proxmox completely losing its ability for management, somebody has to hard-reset the machine at the property.
Any idea how to fix this?
syslog messages from the time of the incident: (middle of the night, yeah...)
Feb 24 01:47:46 proxmox-2 kernel: [285519.951199] xhci_hcd 0000:3e:00.0: xHCI host controller not responding, assume dead
Feb 24 01:47:46 proxmox-2 kernel: [285519.951269] xhci_hcd 0000:3e:00.0: HC died; cleaning up
Feb 24 01:47:46 proxmox-2 kernel: [285519.951345] r8152 4-1:1.0 enx00e04c3628da: Tx status -108
Feb 24 01:47:46 proxmox-2 kernel: [285519.951516] usb 4-1: USB disconnect, device number 2
Feb 24 01:47:46 proxmox-2 kernel: [285519.955832] bond0: (slave enx00e04c3628da): Releasing backup interface
Feb 24 01:47:46 proxmox-2 kernel: [285519.955838] device enx00e04c3628da left promiscuous mode
Feb 24 01:47:47 proxmox-2 corosync[986]: [KNET ] link: host: 3 link: 0 is down
Feb 24 01:47:47 proxmox-2 corosync[986]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
Feb 24 01:47:47 proxmox-2 corosync[986]: [KNET ] host: host: 3 has no active links
syslog messages containing the name of the network interface:
$ cat /var/log/syslog | grep enx00e04c3628da
Feb 24 01:47:46 proxmox-2 kernel: [285519.951345] r8152 4-1:1.0 enx00e04c3628da: Tx status -108
Feb 24 01:47:46 proxmox-2 kernel: [285519.955832] bond0: (slave enx00e04c3628da): Releasing backup interface
Feb 24 01:47:46 proxmox-2 kernel: [285519.955838] device enx00e04c3628da left promiscuous mode
Feb 24 08:12:28 proxmox-2 kernel: [ 15.375492] r8152 4-1:1.0 enx00e04c3628da: renamed from eth0
Feb 24 08:12:28 proxmox-2 kernel: [ 16.513872] bond0: (slave enx00e04c3628da): Enslaving as a backup interface with a down link
Feb 24 08:12:30 proxmox-2 kernel: [ 18.743157] r8152 4-1:1.0 enx00e04c3628da: carrier on
Feb 24 08:12:30 proxmox-2 kernel: [ 18.824179] bond0: (slave enx00e04c3628da): link status definitely up, 1000 Mbps full duplex
Feb 24 08:12:30 proxmox-2 kernel: [ 18.824187] bond0: (slave enx00e04c3628da): making interface the new active one
Feb 24 08:12:30 proxmox-2 kernel: [ 18.824189] device enx00e04c3628da entered promiscuous mode
Feb 24 08:12:30 proxmox-2 kernel: [ 18.824340] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:51 proxmox-2 kernel: [ 39.165699] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:51 proxmox-2 kernel: [ 39.166401] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:51 proxmox-2 kernel: [ 39.173607] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:51 proxmox-2 kernel: [ 39.180395] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:51 proxmox-2 kernel: [ 39.194397] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:51 proxmox-2 kernel: [ 39.194641] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:56 proxmox-2 kernel: [ 44.740178] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:56 proxmox-2 kernel: [ 44.740470] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:56 proxmox-2 kernel: [ 44.746637] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:56 proxmox-2 kernel: [ 44.746808] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
This HW has been running for about 2 years before creating a new Ubuntu VM -- so it mas have some connection to it, I just can't tell how can I VM bring down the entire network adapter. The VM does have a VLAN tag assigned, but it is *not* the only VM having a VLAN tag.
Any idea how to fix this?
syslog messages from the time of the incident: (middle of the night, yeah...)
Feb 24 01:47:46 proxmox-2 kernel: [285519.951199] xhci_hcd 0000:3e:00.0: xHCI host controller not responding, assume dead
Feb 24 01:47:46 proxmox-2 kernel: [285519.951269] xhci_hcd 0000:3e:00.0: HC died; cleaning up
Feb 24 01:47:46 proxmox-2 kernel: [285519.951345] r8152 4-1:1.0 enx00e04c3628da: Tx status -108
Feb 24 01:47:46 proxmox-2 kernel: [285519.951516] usb 4-1: USB disconnect, device number 2
Feb 24 01:47:46 proxmox-2 kernel: [285519.955832] bond0: (slave enx00e04c3628da): Releasing backup interface
Feb 24 01:47:46 proxmox-2 kernel: [285519.955838] device enx00e04c3628da left promiscuous mode
Feb 24 01:47:47 proxmox-2 corosync[986]: [KNET ] link: host: 3 link: 0 is down
Feb 24 01:47:47 proxmox-2 corosync[986]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
Feb 24 01:47:47 proxmox-2 corosync[986]: [KNET ] host: host: 3 has no active links
syslog messages containing the name of the network interface:
$ cat /var/log/syslog | grep enx00e04c3628da
Feb 24 01:47:46 proxmox-2 kernel: [285519.951345] r8152 4-1:1.0 enx00e04c3628da: Tx status -108
Feb 24 01:47:46 proxmox-2 kernel: [285519.955832] bond0: (slave enx00e04c3628da): Releasing backup interface
Feb 24 01:47:46 proxmox-2 kernel: [285519.955838] device enx00e04c3628da left promiscuous mode
Feb 24 08:12:28 proxmox-2 kernel: [ 15.375492] r8152 4-1:1.0 enx00e04c3628da: renamed from eth0
Feb 24 08:12:28 proxmox-2 kernel: [ 16.513872] bond0: (slave enx00e04c3628da): Enslaving as a backup interface with a down link
Feb 24 08:12:30 proxmox-2 kernel: [ 18.743157] r8152 4-1:1.0 enx00e04c3628da: carrier on
Feb 24 08:12:30 proxmox-2 kernel: [ 18.824179] bond0: (slave enx00e04c3628da): link status definitely up, 1000 Mbps full duplex
Feb 24 08:12:30 proxmox-2 kernel: [ 18.824187] bond0: (slave enx00e04c3628da): making interface the new active one
Feb 24 08:12:30 proxmox-2 kernel: [ 18.824189] device enx00e04c3628da entered promiscuous mode
Feb 24 08:12:30 proxmox-2 kernel: [ 18.824340] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:51 proxmox-2 kernel: [ 39.165699] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:51 proxmox-2 kernel: [ 39.166401] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:51 proxmox-2 kernel: [ 39.173607] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:51 proxmox-2 kernel: [ 39.180395] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:51 proxmox-2 kernel: [ 39.194397] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:51 proxmox-2 kernel: [ 39.194641] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:56 proxmox-2 kernel: [ 44.740178] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:56 proxmox-2 kernel: [ 44.740470] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:56 proxmox-2 kernel: [ 44.746637] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
Feb 24 08:12:56 proxmox-2 kernel: [ 44.746808] r8152 4-1:1.0 enx00e04c3628da: Promiscuous mode enabled
This HW has been running for about 2 years before creating a new Ubuntu VM -- so it mas have some connection to it, I just can't tell how can I VM bring down the entire network adapter. The VM does have a VLAN tag assigned, but it is *not* the only VM having a VLAN tag.