Search results

PVE remotes: proxmox-ve: 8.4.0 (running kernel: 6.8.12-11-pve) pve-manager: 8.4.1 (running version: 8.4.1/2a5fa54a8503f96d) PDM: Installed: 0.1.11 VM 10 GB + 1 TB disks All endpoints 3 devices are on the same subnet without fw, 10 Gbps network, hdd raid. This was 2nd try, 1st try was...

We filter by fqdn on firewall. We have rarely problem with any other repository, but PVE repo is standard for fail. Update? Fail. Dist-upgrade? Fail. Repeatedly fail, until firewall and apt are in sync. And all is connected to the same dns infra.

Hi, i am again reporting problem with cdn used by proxmox for apt repository. Our firewalls just doesn't work reliable with it's 1 minute ip cycling. ;; ANSWER SECTION: download.proxmox.com. 635 IN CNAME download.cdn.proxmox.com. <---- there is 600+ TTL ...

you need to debug via tcpdump/wireshark dhcp requests/responses

Try blacklist/whitelist/mail filter.

1x LAG with 4x 25G nics or 2x LAG with 2x 25G nics split vlans as needed + add 1G adapter 2x 1G - 2x corosync network (better) or 1x 1G - primary corosync, secondary on the LAG

Yes, newly added nic and suprised by different name. Looking into that git - well, that's not good info, especially with IaaC, who (human) will remember/count ifaces - it's X number before change, not possible to use cycle etc...Yes, we are using systemd, but using .link will require hard-coded...

agent: 1 boot: cdn bootdisk: scsi0 cores: 2 cpu: host ide2: none,media=cdrom ipconfig1: ip=SOMEIPV4/24,gw=SOMEIPV4 memory: 4096 name: SOMEFQDN net0: virtio=0A:44:61:8C:42:C7,bridge=vmbr0,tag=VLANID net1: virtio=0A:12:66:62:02:25,bridge=vmbr0,tag=VLANID net2...

PVE 7.4 /var/log# ip l 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen...

If you need shut/unshut ports on switch after PVE reboot -> with 99 % probability the switch is problem the 1 % is for server hw/sw problem

well... 1] direct mesh network for ceph backend 2] if not LACP/MLAG/etc possible - STP or maybe any dynamic fast routing protocol 3] get LACP/MLAG switches

google for example https://techcommunity.microsoft.com/blog/networkingblog/three-reasons-why-you-should-not-use-iperf3-on-windows/4117876

Hi, i am seeing regular cpu load spikes in the monitoring (zabbix, netdata), but can't find why. I have only 2 clusters with different use case, co can't compare with another. Some standalone PVE hosts has some regular spikes too, but it's not so visible so not 100% sure. Those regular spikes...

What server? HP? Dell? If Megaraid isn't supported out of box as hp Pxxx, ... I have some Dells with Megaraid on PVE7, how i can "test" PVE8 if no spare available? Just booting kernel from PVE8? It's doable? Boot from ISO?

Template only for now. https://forum.proxmox.com/threads/how-to-set-sending-domain-for-generated-mails-due-spf.163284/

auto bondX iface bondX inet manual ovs_type OVSBond ovs_bonds eth0 eth3 ovs_bridge brX ovs_options bond-mode=balance-tcp lacp=active auto brX iface brX inet static ovs_type OVSBridge ovs_ports bondX portX portY ... auto portX iface portX inet...

There isn't 100% safe update in the software world. So every update is less or more risky, even if you test it on spare hw.

PVE works with HP G8 servers even with current PVE version.

https://forum.proxmox.com/threads/nvidia-vgpu-software-18-support-for-proxmox-ve.163153/

We are using both integrated + addon network card for one LACP without problem on our Dell/Supermicro 10G setups.