HP DL380G7 - Broadcom limited - nextreme II BCM5709 Gigabit Ethernet

[tribuna]

Hello guys, I have a hp dl380 g7 with Broadcom Limited NetXtreme II BCM5709 Gigabit Ethernet network card, but I have several problems:
- in windows server 2016 the card appears with 10gbits. The drivers used are virtio.
- in windows server 2016 whenever i make a query to the network that requires more processing, i lose the connection.



GNU nano 3.2 /etc/network/interfaces

# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface enp3s0f0 inet manual

auto enp3s0f1
iface enp3s0f1 inet manual

auto enp4s0f0
iface enp4s0f0 inet manual

auto enp4s0f1
iface enp4s0f1 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.10.18/24
gateway 192.168.10.1
bridge-ports enp3s0f0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094

 

[Stefan_R]

- in windows server 2016 the card appears with 10gbits. The drivers used are virtio.

Well, yes. The virtio-based connection from the VM to the host is in fact 10 Gbit/s, or even faster.

- in windows server 2016 whenever i make a query to the network that requires more processing, i lose the connection.

Hard to debug without more info. Could you post your VM config ('qm config <vmid>'), network config ('ip link'/'ip addr') and 'pveversion -v'? Also check for any log entries, both in the VM and on the host during the connection interruptions (e.g. 'journalctl -e', 'dmesg').

 

[tribuna]

Hello @Stefan_R,
root@pve-001:~# qm config 100
agent: 1,type=virtio
boot: order=ide0;net0
cores: 4
ide0: armazenamento:vm-100-disk-0,size=350G
ide1: none,media=cdrom
memory: 32768
name: tribuna-srv2016
net0: e1000=76:8D:AC:AC:F5:C6,bridge=vmbr0,queues=1
numa: 0
onboot: 1
ostype: win10
parent: srv2016
scsihw: virtio-scsi-pci
smbios1: uuid=d376601e-446f-42e9-b10b-6e98c3ffbbf4
sockets: 2
vmgenid: b3505b65-6df1-4b7e-8843-5becea2eae86

-------------------------------------
root@pve-001:~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.101-1-pve)
pve-manager: 6.3-4 (running version: 6.3-4/0a38c56f)
pve-kernel-5.4: 6.3-6
pve-kernel-helper: 6.3-6
pve-kernel-5.4.101-1-pve: 5.4.101-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-4
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.8-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-5
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.2.0-2
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-5
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.3-pve2

-------------------------------------
root@pve-001:~# journalctl -e
after many lines......... i think this coud be the problem, but i dont have knowledge to resolve.


[ 14.207931] vmbr0: port 1(enp3s0f0) entered disabled state
[ 16.815099] bnx2 0000:03:00.0 enp3s0f0: NIC Copper Link is Up, 1000 Mbps full duplex
[ 16.815112] , receive & transmit flow control ON
[ 16.815209] vmbr0: port 1(enp3s0f0) entered blocking state
[ 16.815211] vmbr0: port 1(enp3s0f0) entered forwarding state
[ 24.324153] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
[ 25.033345] device tap100i0 entered promiscuous mode
[ 25.043615] vmbr0: port 2(tap100i0) entered blocking state
[ 25.043617] vmbr0: port 2(tap100i0) entered disabled state
[ 25.044121] device enp3s0f0 entered promiscuous mode
[ 25.045942] vmbr0: port 2(tap100i0) entered blocking state
[ 25.045944] vmbr0: port 2(tap100i0) entered forwarding state
[ 200.163496] vmbr0: port 2(tap100i0) entered disabled state
[ 200.221387] device enp3s0f0 left promiscuous mode
[ 242.869812] device tap100i0 entered promiscuous mode
[ 242.880388] vmbr0: port 2(tap100i0) entered blocking state
[ 242.880391] vmbr0: port 2(tap100i0) entered disabled state
[ 242.880885] device enp3s0f0 entered promiscuous mode
[ 242.882658] vmbr0: port 2(tap100i0) entered blocking state
[ 242.882659] vmbr0: port 2(tap100i0) entered forwarding state
[ 2791.959847] perf: interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
[ 6490.912788] perf: interrupt took too long (3141 > 3126), lowering kernel.perf_event_max_sample_rate to 63500
[10830.913410] perf: interrupt took too long (3927 > 3926), lowering kernel.perf_event_max_sample_rate to 50750
[16764.643706] vmbr0: port 2(tap100i0) entered disabled state
[16764.701867] device enp3s0f0 left promiscuous mode
[16765.478678] device tap100i0 entered promiscuous mode
[16765.489120] vmbr0: port 2(tap100i0) entered blocking state
[16765.489123] vmbr0: port 2(tap100i0) entered disabled state
[16765.489625] device enp3s0f0 entered promiscuous mode
[16765.491444] vmbr0: port 2(tap100i0) entered blocking state
[16765.491446] vmbr0: port 2(tap100i0) entered forwarding state
[18435.863582] device tap101i0 entered promiscuous mode
[18435.910094] fwbr101i0: port 1(fwln101i0) entered blocking state
[18435.910097] fwbr101i0: port 1(fwln101i0) entered disabled state
[18435.910188] device fwln101i0 entered promiscuous mode
[18435.910243] fwbr101i0: port 1(fwln101i0) entered blocking state
[18435.910245] fwbr101i0: port 1(fwln101i0) entered forwarding state
[18435.914024] vmbr0: port 3(fwpr101p0) entered blocking state
[18435.914026] vmbr0: port 3(fwpr101p0) entered disabled state
[18435.914098] device fwpr101p0 entered promiscuous mode
[18435.914846] vmbr0: port 3(fwpr101p0) entered blocking state
[18435.914848] vmbr0: port 3(fwpr101p0) entered forwarding state
[18435.978731] fwbr101i0: port 2(tap101i0) entered blocking state
[18435.978734] fwbr101i0: port 2(tap101i0) entered disabled state
[18435.978854] fwbr101i0: port 2(tap101i0) entered blocking state
[18435.978856] fwbr101i0: port 2(tap101i0) entered forwarding state
[18749.097554] fwbr101i0: port 2(tap101i0) entered disabled state
[18749.129884] fwbr101i0: port 1(fwln101i0) entered disabled state
[18749.129954] vmbr0: port 3(fwpr101p0) entered disabled state
[18749.131630] device fwln101i0 left promiscuous mode
[18749.131634] fwbr101i0: port 1(fwln101i0) entered disabled state
[18749.155160] device fwpr101p0 left promiscuous mode
[18749.155162] vmbr0: port 3(fwpr101p0) entered disabled state
[18784.238456] device tap101i0 entered promiscuous mode
[18784.269136] fwbr101i0: port 1(fwln101i0) entered blocking state
[18784.269139] fwbr101i0: port 1(fwln101i0) entered disabled state
[18784.269215] device fwln101i0 entered promiscuous mode
[18784.269274] fwbr101i0: port 1(fwln101i0) entered blocking state
[18784.269275] fwbr101i0: port 1(fwln101i0) entered forwarding state
[18784.273571] vmbr0: port 3(fwpr101p0) entered blocking state
[18784.273573] vmbr0: port 3(fwpr101p0) entered disabled state
[18784.273635] device fwpr101p0 entered promiscuous mode
[18784.274414] vmbr0: port 3(fwpr101p0) entered blocking state
[18784.274416] vmbr0: port 3(fwpr101p0) entered forwarding state
[18784.337863] fwbr101i0: port 2(tap101i0) entered blocking state
[18784.337866] fwbr101i0: port 2(tap101i0) entered disabled state
[18784.337972] fwbr101i0: port 2(tap101i0) entered blocking state
[18784.337974] fwbr101i0: port 2(tap101i0) entered forwarding state
[19210.142567] fwbr101i0: port 2(tap101i0) entered disabled state
[19210.164452] fwbr101i0: port 1(fwln101i0) entered disabled state
[19210.164511] vmbr0: port 3(fwpr101p0) entered disabled state
[19210.166191] device fwln101i0 left promiscuous mode
[19210.166195] fwbr101i0: port 1(fwln101i0) entered disabled state
[19210.185736] device fwpr101p0 left promiscuous mode
[19210.185738] vmbr0: port 3(fwpr101p0) entered disabled state
[19235.390860] zd48: detected capacity change from 34359738368 to 141733920768
[19250.857254] device tap101i0 entered promiscuous mode
[19250.888849] fwbr101i0: port 1(fwln101i0) entered blocking state
[19250.888852] fwbr101i0: port 1(fwln101i0) entered disabled state
[19250.888935] device fwln101i0 entered promiscuous mode
[19250.889001] fwbr101i0: port 1(fwln101i0) entered blocking state
[19250.889003] fwbr101i0: port 1(fwln101i0) entered forwarding state
[19250.892923] vmbr0: port 3(fwpr101p0) entered blocking state
[19250.892925] vmbr0: port 3(fwpr101p0) entered disabled state
[19250.892991] device fwpr101p0 entered promiscuous mode
[19250.893731] vmbr0: port 3(fwpr101p0) entered blocking state
[19250.893733] vmbr0: port 3(fwpr101p0) entered forwarding state
[19250.954077] fwbr101i0: port 2(tap101i0) entered blocking state
[19250.954081] fwbr101i0: port 2(tap101i0) entered disabled state
[19250.954180] fwbr101i0: port 2(tap101i0) entered blocking state
[19250.954183] fwbr101i0: port 2(tap101i0) entered forwarding state
[19921.008162] fwbr101i0: port 2(tap101i0) entered disabled state
[19921.036265] fwbr101i0: port 1(fwln101i0) entered disabled state
[19921.036319] vmbr0: port 3(fwpr101p0) entered disabled state
[19921.037755] device fwln101i0 left promiscuous mode
[19921.037762] fwbr101i0: port 1(fwln101i0) entered disabled state
[19921.053515] device fwpr101p0 left promiscuous mode
[19921.053517] vmbr0: port 3(fwpr101p0) entered disabled state
[20645.989890] device tap101i0 entered promiscuous mode
[20646.022231] fwbr101i0: port 1(fwln101i0) entered blocking state
[20646.022234] fwbr101i0: port 1(fwln101i0) entered disabled state
[20646.022319] device fwln101i0 entered promiscuous mode
[20646.022380] fwbr101i0: port 1(fwln101i0) entered blocking state
[20646.022382] fwbr101i0: port 1(fwln101i0) entered forwarding state
[20646.026427] vmbr0: port 3(fwpr101p0) entered blocking state
[20646.026429] vmbr0: port 3(fwpr101p0) entered disabled state
[20646.026500] device fwpr101p0 entered promiscuous mode
[20646.027237] vmbr0: port 3(fwpr101p0) entered blocking state
[20646.027239] vmbr0: port 3(fwpr101p0) entered forwarding state
[20646.080881] fwbr101i0: port 2(tap101i0) entered blocking state
[20646.080884] fwbr101i0: port 2(tap101i0) entered disabled state
[20646.080991] fwbr101i0: port 2(tap101i0) entered blocking state
[20646.080993] fwbr101i0: port 2(tap101i0) entered forwarding state
[21610.802537] perf: interrupt took too long (4911 > 4908), lowering kernel.perf_event_max_sample_rate to 40500
[34439.366538] perf: interrupt took too long (6404 > 6138), lowering kernel.perf_event_max_sample_rate to 31000
[109123.058510] vmbr0: port 2(tap100i0) entered disabled state
[109141.541179] device tap100i0 entered promiscuous mode
[109141.552566] vmbr0: port 2(tap100i0) entered blocking state
[109141.552569] vmbr0: port 2(tap100i0) entered disabled state
[109141.553380] vmbr0: port 2(tap100i0) entered blocking state
[109141.553383] vmbr0: port 2(tap100i0) entered forwarding state
[162706.323957] fwbr101i0: port 2(tap101i0) entered disabled state
[162706.350455] fwbr101i0: port 1(fwln101i0) entered disabled state
[162706.350529] vmbr0: port 3(fwpr101p0) entered disabled state
[162706.352155] device fwln101i0 left promiscuous mode
[162706.352162] fwbr101i0: port 1(fwln101i0) entered disabled state
[162706.371716] device fwpr101p0 left promiscuous mode
[162706.371718] vmbr0: port 3(fwpr101p0) entered disabled state
root@pve-001:~#

 

[Stefan_R]

net0: e1000=76:8D:AC:AC:F5:C6,bridge=vmbr0,queues=1

That's not a virtio interface though, that's e1000... Change your network interface type to "virtio" in the GUI and restart your VM. Just installing the Windows drivers is not enough.

after many lines......... i think this coud be the problem, but i dont have knowledge to resolve.

There's nothing wrong in the log you posted... no errors anyway. The L1TF warning is just that, a warning, and the 'perf' interrupt lines can usually be ignored.

 

[tribuna]

@Stefan_R ,
yesterday i change the network cardo e1000. but the problem persistes.
But now i change the network e reboot the vm.
Have you need the logs?

 

[tribuna]

@Stefan_R
new dmesg


[ 4.338179] bnx2 0000:03:00.0 eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f4000000, IRQ 16, node addr 64:31:50:4a:86:38
[ 4.338936] bnx2 0000:03:00.1 eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f2000000, IRQ 17, node addr 64:31:50:4a:86:3a
[ 4.339157] ACPI Warning: SystemIO range 0x0000000000000928-0x000000000000092F conflicts with OpRegion 0x0000000000000920-0x000000000000092F (\SGPE) (20190816/utaddress-213)
[ 4.339163] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 4.339193] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 4.339486] ehci-pci: EHCI PCI platform driver
[ 4.339689] bnx2 0000:04:00.0 eth2: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f8000000, IRQ 18, node addr 64:31:50:4a:86:3c
[ 4.339770] ehci-pci 0000:00:1d.7: EHCI Host Controller
[ 4.339780] ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 1
[ 4.339795] ehci-pci 0000:00:1d.7: debug port 1
[ 4.339967] uhci_hcd: USB Universal Host Controller Interface driver
[ 4.340392] bnx2 0000:04:00.1 eth3: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f6000000, IRQ 19, node addr 64:31:50:4a:86:3e
.............

[ 13.197373] bnx2 0000:03:00.1 enp3s0f1: using MSIX
[ 13.393361] bnx2 0000:04:00.0 enp4s0f0: using MSIX
[ 13.505329] bnx2 0000:04:00.1 enp4s0f1: using MSIX
[ 13.544970] vmbr0: port 1(enp3s0f0) entered blocking state
[ 13.544973] vmbr0: port 1(enp3s0f0) entered disabled state
[ 13.545046] device enp3s0f0 entered promiscuous mode
[ 13.625313] bnx2 0000:03:00.0 enp3s0f0: using MSIX
[ 13.628470] vmbr0: port 1(enp3s0f0) entered blocking state
[ 13.628472] vmbr0: port 1(enp3s0f0) entered forwarding state
[ 13.765036] device enp3s0f0 left promiscuous mode
[ 13.996491] bpfilter: Loaded bpfilter_umh pid 2135
[ 13.996660] Started bpfilter
[ 14.207931] vmbr0: port 1(enp3s0f0) entered disabled state
[ 16.815099] bnx2 0000:03:00.0 enp3s0f0: NIC Copper Link is Up, 1000 Mbps full duplex
[ 16.815112] , receive & transmit flow control ON
[ 16.815209] vmbr0: port 1(enp3s0f0) entered blocking state
[ 16.815211] vmbr0: port 1(enp3s0f0) entered forwarding state
[ 24.324153] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
[ 25.033345] device tap100i0 entered promiscuous mode
[ 25.043615] vmbr0: port 2(tap100i0) entered blocking state
[ 25.043617] vmbr0: port 2(tap100i0) entered disabled state
[ 25.044121] device enp3s0f0 entered promiscuous mode
[ 25.045942] vmbr0: port 2(tap100i0) entered blocking state
[ 25.045944] vmbr0: port 2(tap100i0) entered forwarding state
[ 200.163496] vmbr0: port 2(tap100i0) entered disabled state
[ 200.221387] device enp3s0f0 left promiscuous mode
[ 242.869812] device tap100i0 entered promiscuous mode
[ 242.880388] vmbr0: port 2(tap100i0) entered blocking state
[ 242.880391] vmbr0: port 2(tap100i0) entered disabled state
[ 242.880885] device enp3s0f0 entered promiscuous mode
[ 242.882658] vmbr0: port 2(tap100i0) entered blocking state
[ 242.882659] vmbr0: port 2(tap100i0) entered forwarding state
[ 2791.959847] perf: interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
[ 6490.912788] perf: interrupt took too long (3141 > 3126), lowering kernel.perf_event_max_sample_rate to 63500
[10830.913410] perf: interrupt took too long (3927 > 3926), lowering kernel.perf_event_max_sample_rate to 50750
[16764.643706] vmbr0: port 2(tap100i0) entered disabled state
[16764.701867] device enp3s0f0 left promiscuous mode
[16765.478678] device tap100i0 entered promiscuous mode
[16765.489120] vmbr0: port 2(tap100i0) entered blocking state
[16765.489123] vmbr0: port 2(tap100i0) entered disabled state
[16765.489625] device enp3s0f0 entered promiscuous mode
[16765.491444] vmbr0: port 2(tap100i0) entered blocking state
[16765.491446] vmbr0: port 2(tap100i0) entered forwarding state
[18435.863582] device tap101i0 entered promiscuous mode
[18435.910094] fwbr101i0: port 1(fwln101i0) entered blocking state
[18435.910097] fwbr101i0: port 1(fwln101i0) entered disabled state
[18435.910188] device fwln101i0 entered promiscuous mode
[18435.910243] fwbr101i0: port 1(fwln101i0) entered blocking state
[18435.910245] fwbr101i0: port 1(fwln101i0) entered forwarding state
[18435.914024] vmbr0: port 3(fwpr101p0) entered blocking state
[18435.914026] vmbr0: port 3(fwpr101p0) entered disabled state
[18435.914098] device fwpr101p0 entered promiscuous mode
[18435.914846] vmbr0: port 3(fwpr101p0) entered blocking state
[18435.914848] vmbr0: port 3(fwpr101p0) entered forwarding state
[18435.978731] fwbr101i0: port 2(tap101i0) entered blocking state
[18435.978734] fwbr101i0: port 2(tap101i0) entered disabled state
[18435.978854] fwbr101i0: port 2(tap101i0) entered blocking state
[18435.978856] fwbr101i0: port 2(tap101i0) entered forwarding state
[18749.097554] fwbr101i0: port 2(tap101i0) entered disabled state
[18749.129884] fwbr101i0: port 1(fwln101i0) entered disabled state
[18749.129954] vmbr0: port 3(fwpr101p0) entered disabled state
[18749.131630] device fwln101i0 left promiscuous mode
[18749.131634] fwbr101i0: port 1(fwln101i0) entered disabled state
[18749.155160] device fwpr101p0 left promiscuous mode
[18749.155162] vmbr0: port 3(fwpr101p0) entered disabled state
[18784.238456] device tap101i0 entered promiscuous mode
[18784.269136] fwbr101i0: port 1(fwln101i0) entered blocking state
[18784.269139] fwbr101i0: port 1(fwln101i0) entered disabled state
[18784.269215] device fwln101i0 entered promiscuous mode
[18784.269274] fwbr101i0: port 1(fwln101i0) entered blocking state
[18784.269275] fwbr101i0: port 1(fwln101i0) entered forwarding state
[18784.273571] vmbr0: port 3(fwpr101p0) entered blocking state
[18784.273573] vmbr0: port 3(fwpr101p0) entered disabled state
[18784.273635] device fwpr101p0 entered promiscuous mode
[18784.274414] vmbr0: port 3(fwpr101p0) entered blocking state
[18784.274416] vmbr0: port 3(fwpr101p0) entered forwarding state
[18784.337863] fwbr101i0: port 2(tap101i0) entered blocking state
[18784.337866] fwbr101i0: port 2(tap101i0) entered disabled state
[18784.337972] fwbr101i0: port 2(tap101i0) entered blocking state
[18784.337974] fwbr101i0: port 2(tap101i0) entered forwarding state
[19210.142567] fwbr101i0: port 2(tap101i0) entered disabled state
[19210.164452] fwbr101i0: port 1(fwln101i0) entered disabled state
[19210.164511] vmbr0: port 3(fwpr101p0) entered disabled state
[19210.166191] device fwln101i0 left promiscuous mode
[19210.166195] fwbr101i0: port 1(fwln101i0) entered disabled state
[19210.185736] device fwpr101p0 left promiscuous mode
[19210.185738] vmbr0: port 3(fwpr101p0) entered disabled state
[19235.390860] zd48: detected capacity change from 34359738368 to 141733920768
[19250.857254] device tap101i0 entered promiscuous mode
[19250.888849] fwbr101i0: port 1(fwln101i0) entered blocking state
[19250.888852] fwbr101i0: port 1(fwln101i0) entered disabled state
[19250.888935] device fwln101i0 entered promiscuous mode
[19250.889001] fwbr101i0: port 1(fwln101i0) entered blocking state
[19250.889003] fwbr101i0: port 1(fwln101i0) entered forwarding state
[19250.892923] vmbr0: port 3(fwpr101p0) entered blocking state
[19250.892925] vmbr0: port 3(fwpr101p0) entered disabled state
[19250.892991] device fwpr101p0 entered promiscuous mode
[19250.893731] vmbr0: port 3(fwpr101p0) entered blocking state
[19250.893733] vmbr0: port 3(fwpr101p0) entered forwarding state
[19250.954077] fwbr101i0: port 2(tap101i0) entered blocking state
[19250.954081] fwbr101i0: port 2(tap101i0) entered disabled state
[19250.954180] fwbr101i0: port 2(tap101i0) entered blocking state
[19250.954183] fwbr101i0: port 2(tap101i0) entered forwarding state
[19921.008162] fwbr101i0: port 2(tap101i0) entered disabled state
[19921.036265] fwbr101i0: port 1(fwln101i0) entered disabled state
[19921.036319] vmbr0: port 3(fwpr101p0) entered disabled state
[19921.037755] device fwln101i0 left promiscuous mode
[19921.037762] fwbr101i0: port 1(fwln101i0) entered disabled state
[19921.053515] device fwpr101p0 left promiscuous mode
[19921.053517] vmbr0: port 3(fwpr101p0) entered disabled state
[20645.989890] device tap101i0 entered promiscuous mode
[20646.022231] fwbr101i0: port 1(fwln101i0) entered blocking state
[20646.022234] fwbr101i0: port 1(fwln101i0) entered disabled state
[20646.022319] device fwln101i0 entered promiscuous mode
[20646.022380] fwbr101i0: port 1(fwln101i0) entered blocking state
[20646.022382] fwbr101i0: port 1(fwln101i0) entered forwarding state
[20646.026427] vmbr0: port 3(fwpr101p0) entered blocking state
[20646.026429] vmbr0: port 3(fwpr101p0) entered disabled state
[20646.026500] device fwpr101p0 entered promiscuous mode
[20646.027237] vmbr0: port 3(fwpr101p0) entered blocking state
[20646.027239] vmbr0: port 3(fwpr101p0) entered forwarding state
[20646.080881] fwbr101i0: port 2(tap101i0) entered blocking state
[20646.080884] fwbr101i0: port 2(tap101i0) entered disabled state
[20646.080991] fwbr101i0: port 2(tap101i0) entered blocking state
[20646.080993] fwbr101i0: port 2(tap101i0) entered forwarding state
[21610.802537] perf: interrupt took too long (4911 > 4908), lowering kernel.perf_event_max_sample_rate to 40500
[34439.366538] perf: interrupt took too long (6404 > 6138), lowering kernel.perf_event_max_sample_rate to 31000
[109123.058510] vmbr0: port 2(tap100i0) entered disabled state
[109141.541179] device tap100i0 entered promiscuous mode
[109141.552566] vmbr0: port 2(tap100i0) entered blocking state
[109141.552569] vmbr0: port 2(tap100i0) entered disabled state
[109141.553380] vmbr0: port 2(tap100i0) entered blocking state
[109141.553383] vmbr0: port 2(tap100i0) entered forwarding state
[162706.323957] fwbr101i0: port 2(tap101i0) entered disabled state
[162706.350455] fwbr101i0: port 1(fwln101i0) entered disabled state
[162706.350529] vmbr0: port 3(fwpr101p0) entered disabled state
[162706.352155] device fwln101i0 left promiscuous mode
[162706.352162] fwbr101i0: port 1(fwln101i0) entered disabled state
[162706.371716] device fwpr101p0 left promiscuous mode
[162706.371718] vmbr0: port 3(fwpr101p0) entered disabled state
[169212.554862] vmbr0: port 2(tap100i0) entered disabled state
[169212.696525] device enp3s0f0 left promiscuous mode
[169255.348283] device tap100i0 entered promiscuous mode
[169255.359316] vmbr0: port 2(tap100i0) entered blocking state
[169255.359319] vmbr0: port 2(tap100i0) entered disabled state
[169255.359817] device enp3s0f0 entered promiscuous mode
[169255.361585] vmbr0: port 2(tap100i0) entered blocking state
[169255.361587] vmbr0: port 2(tap100i0) entered forwarding state

 

[Stefan_R]

Again, there's no errors anywhere in these logs. Please look through them yourself to see if they're worthy of posting before you do, and put them in [CODE]...[/CODE] tags to make it easier to see.

Since you tried changing to e1000 and it didn't help, I'm assuming the fault is with the NIC on the host. Have you tried a different NIC? Or even a different port on your switch, router, or whatever else you have? Potentially the fault is outside the PVE server.