Search results

I have two MS-01 servers in my cluster as well, along with two HP server. Mine are also the i9-13900H, one of which is running 96 GB of ram and the other is running 64 GB. This started after the Proxmox 8.4 update a few weeks ago... prior to that, I never had issues. My MS-01 servers are...

Here are my own tests using kernel 6.8.8.2 with the OOT ixgbe 5.20.9 on the Qotom Q20332G9-S10 device along with some Minisforum MS-01 devices that have an Intel X710 controller that works with the default kernel drivers. Also, I'm using DAC cables with an ICX 6610 switch and leaving the...

As you say, it may be a limit of the hardware you are using. I personally have not verified if you can get bidirectional 10gb/s over this x553 port, but I would definitely start looking into your transceivers and switch. Maybe as a quick and easy test, connect two of the x553 ports together...

Not sure if this will work for others, but I went into the bios settings for the 10gb card and disabled all references to PXE and SRIOV. This seems to have solved the issue and no further errors. Don't forget to disable shared memory setting also in the network device config - that will break...

Not sure if this will work for others, but I went into the bios settings for the 10gb card and disabled all references to PXE and SRIOV. This seems to have solved the issue and no further errors.

Sorry to rehash this thread, but had a similar issue with a Cisco VIC 1227 network card. I had to setup the VLAN Aware setting on the bridge devices on the host networking section to make everything work correctly. I am not using VLANs, but I believe the VIC 1227 is using them internally which...

Wanted to share this in case others are encountering similar issues. When trying to use Proxmox on a C220 M4 with a VIC 1227 network card, it would typically work fine while in single host mode. Once I joined it with my existing Proxmox cluster, the network would no longer work within the VMs...

Thanks, this was very helpful. On several of my servers that I regularly update, I had no issues. On another server I try to only update once every several months, this issue occurred. My guess there was a small upgrade before the 7.2 release that applied this Perl package, and it was...