Bug with network speed on 6 servers with proxmox 6.0-4

[myz-rix]

hello,

i have recently install 5 same servers and 1 other with proxmox 6.0-4 .
My network is normaly 1000Mb/s but on 6 servers in different site i have this message

Jan 13 07:13:58 maison kernel: [   10.795994] fwbr100i2: port 1(fwln100i2) entered blocking state

Jan 13 07:13:58 maison kernel: [   10.797081] fwbr100i2: port 1(fwln100i2) entered disabled state

Jan 13 07:13:58 maison kernel: [   10.798217] device fwln100i2 entered promiscuous mode

Jan 13 07:13:58 maison kernel: [   10.799100] fwbr100i2: port 1(fwln100i2) entered blocking state

Jan 13 07:13:58 maison kernel: [   10.799683] fwbr100i2: port 1(fwln100i2) entered forwarding state

Jan 13 07:13:58 maison kernel: [   10.803140] vmbr2: port 2(fwpr100p2) entered blocking state

Jan 13 07:13:58 maison kernel: [   10.803726] vmbr2: port 2(fwpr100p2) entered disabled state

Jan 13 07:13:58 maison kernel: [   10.804325] device fwpr100p2 entered promiscuous mode

Jan 13 07:13:58 maison kernel: [   10.804885] vmbr2: port 2(fwpr100p2) entered blocking state

Jan 13 07:13:58 maison kernel: [   10.805404] vmbr2: port 2(fwpr100p2) entered forwarding state

Jan 13 07:13:58 maison kernel: [   10.808609] fwbr100i2: port 2(tap100i2) entered blocking state

Jan 13 07:13:58 maison kernel: [   10.809140] fwbr100i2: port 2(tap100i2) entered disabled state

Jan 13 07:13:58 maison kernel: [   10.809707] fwbr100i2: port 2(tap100i2) entered blocking state

Jan 13 07:13:58 maison kernel: [   10.810213] fwbr100i2: port 2(tap100i2) entered forwarding state

Jan 13 07:14:08 maison kernel: [   20.714277] r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow control rx/tx

Jan 13 07:14:08 maison kernel: [   20.714306] vmbr0: port 1(enp3s0) entered blocking state

Jan 13 07:14:08 maison kernel: [   20.714319] vmbr0: port 1(enp3s0) entered forwarding state

my problems is my network bug and go in 100Mb/s sometimes 10Mb/s

Can you help me please ?

seb

 

[Stefan_R]

Could you try upgrading to the latest version (6.1-2)? This should include a new kernel version, which might fix your issue.

Also, check your hardware setup (switches, network cables, etc...). I've personally experienced issues with Realtek cards in the past, where sometimes they downgrade their connection with some ethernet cables, but not others.

As a last resort you could try to disable autonegotiation, but that should really not be necessary...

 

[myz-rix]

When i have configured my 6 servers, i have upgraded them but my VM windows system was blocked to boot
i have installed in new my 6 servers and don't update them for going in production.

this after i see the network problem.

now they are in production, if i upgrade them and VM windows bug, i am died !!!
today i have configured 1 server for test on third motherboard type, i install proxmox6.0-4, i configure VM windows,
i configure apt to no-subscription, i do update & after i do upgrade, upgrade is ok but i stay in 6.0-4 and VM windows is blocked at boot too.
i test install new vm Windows, blocked at boot too.



i hate this 6.0-4

 

[Stefan_R]

i do update & after i do upgrade, upgrade is ok but i stay in 6.0-4 and VM windows is blocked at boot too.

If after an upgrade you're still on 6.0-4, you're update was not ok. Did you use apt dist-upgrade, as described in our documentation?

And when you say you're Windows VM is "blocked" at boot, what exactly is happening? Anything in your task log (i.e. at the bottom of the GUI, the 'start' task)? Anything in journalctl -e, or dmesg? This could be a bug, so with more information we could try to fix it.

Whatever you do, not upgrading your servers in a production environment is certainly not recommended for security concerns.

 

[myz-rix]

thanks for your response,

i have reset all my test server, and do:

install proxmox 6.0-4
install VM Windows 10
apt-get update & apt dist-upgrade
reboot the server

and all is ok

I have tested on 1 server in production less important than 5 others and netword is ok

now i will test on 5 servers in production with VM Windows ....

thanks a lot !!!