Hi @svc,
it's very unlikely that the libpve-storage-perl update is related. It's a perl library for high-level interaction with storages, it does not touch low-level kernel stuff related to booting. The changelog also doesn't mention anything...
Before continuing down the PVE/kernel route, I'd validate the hardware. I've had a few of these small boxes and lost both SSDs and memory in them.
Your testing has ruled out a lot of the software side (though that's not to say there isn't a...
You can't re-encrypt; instead you can point new backups at a new key and keep the old ones archived until retention has pruned the last snapshot that used the old key.
https://pbs.proxmox.com/docs/backup-client.html
Before continuing down the PVE/kernel route, I'd validate the hardware. I've had a few of these small boxes and lost both SSDs and memory in them.
Your testing has ruled out a lot of the software side (though that's not to say there isn't a...
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...
Agree with @UdoB : a common distro (Debian/Ubuntu) with SSH access/server, docker base install and maybe portainer (or dockhand) for an easy entry or more simple management would the better choice. Your initial idea is like driving a formula one...
HI, I believe this is similar to this issue. https://bugzilla.proxmox.com/show_bug.cgi?id=5895 .
EDIT: Could you please also share the zpool status -pP output?
Where does the HELO/EHLO banner mention the IP-address for you?
connecting to port 25, and issuing a EHLO testhost - to a PMG does not show any IP-addresses in the output coming from the server for me.
EDIT: without testing this explicitly - I'd...
Regarding „NUMA or not“ please see also this thread:
https://forum.proxmox.com/threads/multiple-cpu-motherboard-settings-for-windows-vms.169476/post-864964
yep, I did had NUMA enabled in proxmox, the vmware logic was very nicely explained, from https://weestro.wordpress.com/2016/04/01/vsphere-design-for-numa-architecture-and-alignment/:
When the NUMA topology is exposed to a guest VM, one of two...
To provide more context: This is my lscpu data for both the machines:
FieldProxmoxVMware
Hostnamepmx_host-1vmw_host-1
Architecturex86_64x86_64
CPU op-mode(s)32-bit, 64-bit32-bit, 64-bit
Address sizes46 bits physical, 48 bits virtual45...
Hi @bdr
thanks for chiming in!
Could you please also try if the problem is gone for you on kernel 7.0.14-5, as mentioned by @weppa.
How is your storage / your disks configured? Are you also using mdraid?
Best regards
Jonas
Generell ist es bei einer Migration auch nicht verkehrt sich einen Proxmox Partner an Bord zu holen, gerade wenn es um solche kritischen Anforderungen geht.
Zum PBS: Die Wiederherstellung dauert natürlich immer so lange, wie sie halt dauert...
You can't re-encrypt; instead you can point new backups at a new key and keep the old ones archived until retention has pruned the last snapshot that used the old key.
https://pbs.proxmox.com/docs/backup-client.html
There is no universal “always use 1 socket and disable NUMA” recommendation. The correct configuration depends on the VM size and on the actual NUMA resource situation on the host.
Your host has two physical NUMA nodes, one per CPU socket, each...
Hi all,
We are planning to set up a 4-node Proxmox cluster with Ceph across 2 datacenters.
Our setup will be:
DC1: Node 1 and Node 2
DC2: Node 3 and Node 4
Node 1 and 2 are using one network range.
Node 3 and 4 are using a different network...
You have not much experience with PVE, are using sub-optimal (not recommended) hardware and are starting with "Docker in LXC". This lands you immediately inside a battle field. That combination means you are piling up multiple problem areas from...
Diese TrueNAS wird, auch jetzt schon, zusätzlich noch auf eine weitere TrueNAS am gleichen Standort synchronisiert. Habe ich leider versäumt zu erwähnen.
Vielen Dank für diesen Hinweis!
Mit drei Nodes pro Standort bist du das QDevice-Thema los, das reicht fürs Quorum. Und ja, OEM-Geräte mit vPro sind völlig okay, wenn du eh drei Hosts hast. Der BMC ist hauptsächlich dafür da, dass du remote hart aus- und wieder einschalten...