We are running two separated clusters using Proxmox VE, one is running on HP Proliant DL380G5 (bnx2) servers and one on Dell PowerEdge R200 (tg3). Both setups have been running - mostly without issues - for about 2 years now. Just today though one linux guest stopped responding via network. Looking at it using the VNC console didn't reveal anything other than that it wasn't able to send any packets to the outside anymore - not even to the host - but after issuing a /etc/init.d/network restart in the guest the problem magically went away. On the host nothing was visible as well, the guest's vmtab was still attached to the bridge and no dmesg hints whatsoever.
If it weren't for the fact exactly the same problem occurred again after a few minutes repeatedly and a reboot of the host also didn't do anything, I'd overlook this. Here is why:
We are sort of used to this problem (on both setups) already as it occurred a couple of times within the 2 years but right now I'm forced to run a network restart via cron every 15 minutes to keep the network up. Obviously I'd like to avoid this and would like to find out what the real cause is. I suspect it's somewhere in qemu as I cannot find any hints inside the guest nor on the host as mentioned.
We are running the following versions which are the latest taken from:
If it weren't for the fact exactly the same problem occurred again after a few minutes repeatedly and a reboot of the host also didn't do anything, I'd overlook this. Here is why:
We are sort of used to this problem (on both setups) already as it occurred a couple of times within the 2 years but right now I'm forced to run a network restart via cron every 15 minutes to keep the network up. Obviously I'd like to avoid this and would like to find out what the real cause is. I suspect it's somewhere in qemu as I cannot find any hints inside the guest nor on the host as mentioned.
We are running the following versions which are the latest taken from:
deb http://download.proxmox.com/debian lenny pvetest
The host's /etc/network/interfacespve-manager: 1.5-10 (pve-manager/1.5/4822)
running kernel: 2.6.24-12-pve
pve-kernel-2.6.24-7-pve: 2.6.24-11
pve-kernel-2.6.24-12-pve: 2.6.24-24
pve-kernel-2.6.24-5-pve: 2.6.24-6
qemu-server: 1.1-16
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.24-1pve2
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
And that of the guest's which is failing:# network interface settings
auto lo
iface lo inet loopback
iface eth0 inet manual
iface eth1 inet manual
iface eth2 inet manual
iface eth3 inet manual
auto vmbr0
iface vmbr0 inet static
address 172.24.0.30
netmask 255.255.00.0
gateway 172.24.0.1
bridge_ports eth0
bridge_stp off
bridge_fd 0
auto vmbr1
iface vmbr1 inet static
address 172.22.1.101
netmask 255.255.255.0
bridge_ports eth2
bridge_stp off
bridge_fd 0
brctl show from the host:auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 172.24.0.201
netmask 255.255.0.0
gateway 172.24.0.1
bridge name bridge id STP enabled interfaces
vmbr0 8000.00215ad1f0b2 no eth0
veth108.0
veth110.0
veth116.0
veth125.0
vmtab103i0
vmtab104i0
vmtab117i0
vmtab123i0
vmbr1 8000.001f295d1a65 no eth2
vmtab103i1