Recent content by Gilberto Ferreira

The tools seems to be cool, but please, forget about EOL PVE version. Your focus needs to be PVE 9.

yes... we both sent some time... but that's the case... participate 02 restart... ok

I usually do my tests with virt-manager and vbmc ans a fence ipmi device. Works fine. That was not I experience here. If I turn 01 down, 02 restart. But not the other way around. Perhaps is just me doing something wrong.

I am doing some tests here, but everything in VM on top of Virt-Manager, using vmbc as ipmi. It's works as intendent. If the node 02 dies, the node 01 remains, but not the other way around. But I guess that was planned... I look forward to be able to used it with 2 nodes on top of Pacemaker...

And yes... It's work as a charm...

Hi again I suppose that with drbd 9 doesn't work. I tried and get this: proxmox01:~# mount -t mxfs /dev/drbd0 /data mount: /data: fsconfig() failed: mxfs: P-DRBD-ARM-REFUSED minor=0 -- replication protocol is '' (configured 'C'), not C; a DRBD device is admitted only with its fence evidence (set...

Hi there... I am testing... Everything was installed without no warnings However I couldn't see any options in Datacenter -> Storage -> Add. And when I tried to add via cli, I got this message: proxmox01:~# pvesm add mxfs Plugin "PVE::Storage::Custom::MXFSPlugin" is implementing an older storage...

Well... After some deep digging and with the Claude help I fix the issue. Turns out that the original problem had two causes, and both are now fixed: No rbd-mirror daemon on CLUSTER100. It wasn't pulling anything from CLUSTER200, so pve01 was left with the old image. There is now an active...

Thanks for the reply. I think not pve01:~# rbd mirror pool info VMS Mode: image Site Name: 7b50800f-4c5b-49de-8359-4168470e9044 Mirror UUID: 2e5f8d8a-173a-4dad-81ce-ef9182030394 Remote Namespace: Peer Sites: UUID: 7705efc1-f51b-4daa-b90e-56222d1232df Name...

Hi there I'm sorry if this topic aready appears here, but I cam looking for possible solution with my trouble. I followed the Proxmox wiki regarding CEPH rbd-mirror.[0] It's a 3-node Proxmox VE and Ceph, created with virtual machine over virt-manager. It's just a lab. So, let's named this 3-node...

It's looks promise. According to the github, there is an extensive real world test scenarios. I looking forward to test if myself...

In any case, I don't think this is a 0day vulnerability, because on this is happen due to out date servers and bad servers administration, to say the least. Many of this vulnerabilities are well-know documented, such as kernel and ssh vulnerabilities. So, your job is do not exposed a weak server...

I got reports from Proxmox VE 8.0.3, 8.2 and 8.4 as well... And here is a compromissed server:

Hi guys... Anybody can confirm if PVE 8 is also affected???

Perhaps you sould take a look in PVE-Zsync. One doesn't need to have the node in cluster, I guess. https://pve.proxmox.com/wiki/PVE-zsync Just an idea.