Recent content by Cookiefamily

Yup that did the trick... wow o_O Thats... mildly inconvenient. We usually need docker as some monitoring checks run inside a docker container. At least we now know where the issue lies, not sure yet how to fix that...

sure, here is the output: root@node01:~# cat /etc/network/interfaces.d/sdn #version:2 auto v0074 iface v0074 bridge_ports vmbr0.74 bridge_stp off bridge_fd 0 root@node01:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000...

I needed to set up a new cluster anyway for some testing and I managed to reproduce the issue. This time I used normal Linux Bridges from the start and not OVS Bridges, same result. This is the network config: # network interface settings; autogenerated # Please do NOT modify this file...

Hi, sorry for the late reply, I was on an two week vacation. testing from inside the VM trying to ping its gateway: tap131i0 sees it v0074 sees it ln_v0074 doesn't see it vmbr0 doesn't see it bond1 doesn't see it trying to ping another VM that doesn't use the SDN VLAN but just vmbr0 bridge...

Hi Stefan, I attached the ip a and ifreload output as it is too verbose for a normal post. The journal looks like this: root@node02:~# journalctl -u openvswitch-switch.service -b May 21 18:03:33 node02 systemd[1]: Starting openvswitch-switch.service - Open vSwitch... May 21 18:03:33 node02...

I was using a VLAN Zone with two VNets and it seemed to work well. Yesterday evening I updated our staging environment to 9.2.2 and since then I can no longer get connectivity through those VNets - when I use the vmbr0 bridge directly and tag it on the VMs network interface, it works fine...

I created a systemd oneshot service for this: /etc/systemd/system/nvidia-shm.service [Unit] Description=Enable NVIDIA Heterogenous Time-Slice Sizes Before=pve-guests.service After=nvidia-vgpud.service nvidia-vgpu-mgr.service [Service] Type=oneshot ExecStart=nvidia-smi vgpu -shm 1 -i 0...

Hi Daniel, thanks for the reply! not right now, no. I was just thinking ahead to the future :D Right now it is only active on two small 3-node test clusters, one of which has some Nvidia GPUs with NVAIE (yes, works the same as "normal" vGPUs, didn't experience any issues apart from the usual...

@dakralex Thank you very much for the answer! That clears things up a lot. As for the modes, I think we will just need to try the modes and see what happens. TOPSIS sounds best for our production clusters as they are usually memory limited. One thing I would have as feedback is that it is way...

@EllerholdAG my staging clusters are running no-subscription repos and there the 5.2.0 pve-ha-manager is already available. I have yet to roll it out on the enterprise ones.

Hello, I noticed that a dynamic mode was introduced to the CRS (yay! Been waiting for this for so long and it really comes in handy now with us planning our migration away from VMware, thank you so much Team!!!). I enabled it on all my testing environments and it seemed to work pretty well...

Ok, thank you for the reply. Maybe I will need to write a wrapper script to reimplement that functionality to our deploy mechanic in the meantime. For people looking for the bugzilla report: I created the feature request here: https://bugzilla.proxmox.com/show_bug.cgi?id=7260

Thank you @dakralex that makes a lot of sense. That leaves the question: How does one add a single ha resource to an existing rule via the CLI?

Hi, in the past we used ha-manager add $VMID --group $groupname to be able to assign a VM to what then was a "rule" (HA Groups). With PVE 9 HA Groups have been removed in favor of affinity rules which do offer more functionality - But I am wondering how I can add a HA resource (e.g. vm:123) to...

Hi, I assume there has not been a new release of pom to publish this patch? I am still on version 0.6.7 from Sep 2024 and can't find a newer version.