Der Punkt mit dem Pull-Sync ist so definitiv wertvoll.
Je nach Umgebung würde ich prüfen, wie das Adminkonzept für den PBS ist.
Theoretisch gehört da eine dedizierte Adminworkstation dazu.
Damit die letzte Bastion nicht von den gleichen Kisten...
I wouldn’t conclude that there are “no such rules for Proxmox”. There are just different layers involved here.
Linux itself is NUMA-aware: the scheduler and memory allocator try to maintain CPU/memory locality. QEMU can additionally expose a...
Hi @Patrik_V
thank you for posting on the forum!
This will probably never work since ZFS is not designed to work with hardware RAID controllers, see [1].
If the MRs are running in HBA mode it should be fine, but RAID mode is not supported...
I had the same problem and non of the example worked.
I wrote a small py script to solve this.
This changes the usb[x] mapping in the VM conf file during startup
#!/usr/bin/env python3
import sys
import subprocess
import string
#Info:
# 1st...
Welcome to the Forum, @krisshurley
I think this is the similar situation like mentioned e.g. there:
https://forum.proxmox.com/threads/lvm-storage-on-san-new-vm-and-disk-show-data-from-a-previous-deleted-system-disk.179574/
The solution is...
AFAIK or as other plugins do it, you don't have LVM and multipath part. The iSCSI volume can be directly attached to QEMU, so no middleware needed. For the FC-part, a lot needs to be changed in the backend for this to work. I tried it years ago...
Yes, I have tested both configurations.
With Wipe removed volumes enabled, I cannot reproduce the issue.
With it disabled (the default configuration), I can reproduce it consistently.
My expectation is that a newly created qcow2 image should...
Subject: PSA-2026-00038-1: TONTOU kernel memory leak via branch predictor re-poisoning
Advisory date: 2026-08-10
Packages: proxmox-kernel-*
Details:
A new technique to leak kernel memory despite spectre v2 mitigations being in place to...
Subject: PSA-2026-00037-1: SCTPhantom Local Privilege Escalation issue
Advisory date: 2026-08-10
Packages: proxmox-kernel-*
Details:
A use-after-free issue in the Linux kernels SCTP code allowed a unprivileged local attacker to obtain root...
Subject: PSA-2026-00036-1: "Zapscape" KVM guest to host escape on x86_64
Advisory date: 2026-08-10
Packages: proxmox-kernel-*
Details:
A use-after-free issue was discovered in the Linux kernel's KVM module's shadow MMU code. On hosts with...
@gurubert , @aaron Thanks for the information.
Yes, our plan is to keep all 4 nodes as a single Proxmox cluster.
Our main requirement is that our production VMs/web applications should continue running if one complete datacenter goes down...
As @gurubert already mentioned, you will need one node in a 3rd location.
Our Stretch Cluster guide has more details on how to get it up and running: https://pve.proxmox.com/wiki/Stretch_Cluster
You will have to span up a layer2 network between...
Basically you need three locations for automatic HA. Otherwise you will always have issues with split brain situations.
Addendum: If there is no common layer 2 network available for the VM traffic you cannot migrate a VM from one location to the...
Der Punkt mit dem Pull-Sync ist so definitiv wertvoll.
Je nach Umgebung würde ich prüfen, wie das Adminkonzept für den PBS ist.
Theoretisch gehört da eine dedizierte Adminworkstation dazu.
Damit die letzte Bastion nicht von den gleichen Kisten...
Run a VM that provides a network file share. All things can be accomplished in the same way as you would do with multiple physical systems (except that you use VMs or containers).
EDIT: TurnkeyLinux provides VM/CTs that can run on Proxmox, see...