Search results

Hi! Currently, there is no cluster-wide option to order the HA resource starts/make HA resources depend on other HA resources to be already started. As you already mentioned, there is the node-wide Start/Shutdown order and node-specific startup delay. As already pointed out in our bugzilla [0]...

Welcome to the Proxmox forum! What does dhclient -v output if it is executed after the installation aborted or if it is executed in the installer debug console? What is the date/time on the machine according to timedatectl? Is the BIOS/firmware of the server hardware on the most recent version...

Hi! Just a FYI that a Proxmox VE cluster over WAN (i.e., interconnecting networks that are wider apart) is neither officially supported nor recommended, because PVE uses corosync for its cluster, which needs low latency in the whereabouts of 5-10 ms to be stable depending on the cluster size.

Hi! Which kernel version are you running on your Proxmox VE host? Can you give a lspci -nnk for the board and card?

Hi! Does the serial console installer option for a Proxmox VE ISO not work for your hardware? What is the status of pve-cluster.service on the machine? Which steps did you follow to setup Proxmox VE on top of Debian?

The NIC statistics can be viewed with ethtool -S enp8s0, where it also has hw/sw counters for e.g. rx/tx_errors, etc.

The statistics of the NIC provided by ethtool would be interesting as they also can usually tell whether any errors occurred on the hardware itself and/or if there were any resolved by the kernel. Does a tcpdump indicate any failures to send packets (e.g. many TCP resends, etc.) between...

Hi! It seems like that one of your guests is in an error state, which indicates that you're using the HA Manager. Does any of your VMs/containers on the left side have an error icon on them? What is the output of ha-manager status? You can check why the guest was put in error state through the...

Hi! All of the current Proxmox VE repositories have the more recent pve-esxi-import-tools 0.7.4 available on them, which should have fixed the error you are experiencing. Is the apt cache up to date (i.e. apt dist-upgrade)?

Hm, interesting, thanks for getting back so quick! What is the exact switch model that you currently use? Are there any known issues between the i225-LM, x520-da or x550-t2 NICs and the switch you have? What does ethtool tell you about the NIC?

Welcome to the Proxmox forum, rpierluigi! The options should still be preserved even after changing them through the web interface. This shouldn't be necessary, but if you want to make sure that there is no interference, you can always create an extra configuration file in...

Hi! Which kernel version are you using with these cards? Have you tried running other kernel versions? Could you provide a lspci -nnk of the network cards and if there's any interesting logs while these stutters persist in dmesg (e.g. dmesg | grep igb or dmesg | grep ixgbe)?

Hi! Currently, there is no option to add custom flags to the network device parameters. You could pass these via -args but bare in mind that the tap devices aren't created for them automatically, so they need to be set up manually or you could write a script that does that, but this is of...

In that case you really want to setup these firewall rules on the VNet bridge itself, i.e. you should create these rules in the Datacenter firewall as stated in the same paragraph ;)

Hi! If you want to setup SNAT and DHCP with the SDN, then you need to enable automatic DHCP in the dhcpsnat zone, make the VMs use the vnet1 bridge, and define a DHCP range in the VNet's subnet. There is a guide for this setup here [0]. [0]...

Hi! How did you setup the cloud init VM? Usually, cloud init VMs are expected to be used over a serial interface instead of a graphical display. Usually this is done by setting kernel parameters, e.g. providing the console parameter to the kernel. You can see the current kernel parameters in...

Hi! Thanks for reaching out, there's another user that seems to have similar problems [0]. It would be helpful to have more information, could you provide a boot log for the system? Does the NIC have the most recent firmware on it? [0] https://forum.proxmox.com/threads/167132/

Yes, some boot logs would be great to further investigate here what the problem is, so dmesg/journalctl, and optionally a lspci and ethtool output would be great. On another note, have you tried to upgrade the firmware for the BCM57416?

How did you make sure that the change did not take effect on the container? The container shares the host's kernel, so if the sysctl config has been set there, it is also set for the container. Either way, aren't there better defenses for these attacks then enlarging the receive buffer?

Hi! Does the error occur also for the first restart after the installation? The current ISO image does only ship the 6.8 kernel and as it's not a network installer, it is only designed to install packages which are shipped with the ISO image and doesn't have knowledge about other available...