Recent content by daros

I tried the I adjusted the settings, but I wasn't able to start any virtual machines afterward. In some cases useful info is found in syslog - try "dmesg | tail". rbd: sysfs write failed TASK ERROR: can't map rbd volume vm-551-disk-2: rbd: sysfs write failed

Just to be sure, you need to update the file on the node. and then all the vm's use the rxbounce option? And do you need to start stop the vm or only the restart the pvedaemon?

Hi, We have an proxmox cluster with 2 PBS servers. A customer would like to store there own VM's as an fail safe, so that created an own PBS. I can make an secure port forwaring that they can create an own sync but i would only that they can access there own VM's. Can someone point me in the...

I can install it, but when i run proxmox-boot-tool kernel pin pve-kernel-5.11.22-7-pve I got: Possible Proxmox kernel versions are: 5.13.19-6-pve 5.15.102-1-pve 5.15.83-1-pve And i think it has to do with the fact that im running proxmox 7.4

I'm running proxmox 7.4 and looks like i cannot pin kernal 5.11, only 5.13 and higher.

What version did you pinned? I would like to downgrade to that version then. My clusters starts with SLOW OSD's and the CRC errors.

Did you upgrade to 5.15? We have the same problems and running 5.15

Hello, We have 2 proxmox clusters, with both an own PBS. Both PBS will sync to each other. An customer would like an own pbs on there location that sync there servers from our DC. I got 2 questions, 1) is it possible to only sync the latest 3 or 4 versions? 2) is it possible to give the user...

So change the 1024 to 2048? And what service do you need to restart to get the new value active? And can this been done on an running environment?

When can we expect the patch to be live?

Its fixed but we now have a new problem, OpenID login Failed, please try againn Parameter verification failed. (400) code: value may only be 1024 characters long.

Here is what i did. proxmox-boot-tool kernel list proxmox-boot-tool kernel pin 5.13.19-6-pve reboot

Its not really the solution, its an way arround. But yes currently this is the only way to go. We run all the vm's that have these problems from 2 nodes that are running the old version.

I upgrade to the latest -3 when i disabled the nested virtualization and since then no crash. Could been fixed in -3 or the nested option works.

Yes its an server 2022.