Hi
it seems we hit a similar virtio-ethernet-bug that hit Ubuntu 10.04.2 too also on W2k8 R2 (Version 6.1 Build 7600).
It worked fine for months on 2.6.32 but as we upgraded proxmox to 2.6.35 it kicked it's network connectivity (virtio eth mapped to vmbr6 on the host - nothing else was/is connected to this vmbr6).
After two reboots it worked again for a few hours then network connectivity got lost again. We removed the virtio-ethernet and added intel e1000 - now it seems to work fine again.
Regards
hk
PS.
:~# pveversion -v
pve-manager: 1.8-17 (pve-manager/1.8/5948)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.8-11
pve-kernel-2.6.35-1-pve: 2.6.35-11
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.26-1pve4
vzdump: 1.2-12
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.0-3
ksm-control-daemon: 1.0-5
it seems we hit a similar virtio-ethernet-bug that hit Ubuntu 10.04.2 too also on W2k8 R2 (Version 6.1 Build 7600).
It worked fine for months on 2.6.32 but as we upgraded proxmox to 2.6.35 it kicked it's network connectivity (virtio eth mapped to vmbr6 on the host - nothing else was/is connected to this vmbr6).
After two reboots it worked again for a few hours then network connectivity got lost again. We removed the virtio-ethernet and added intel e1000 - now it seems to work fine again.
Regards
hk
PS.
:~# pveversion -v
pve-manager: 1.8-17 (pve-manager/1.8/5948)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.8-11
pve-kernel-2.6.35-1-pve: 2.6.35-11
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.26-1pve4
vzdump: 1.2-12
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.0-3
ksm-control-daemon: 1.0-5