Update — root cause found
My previous conclusion was inaccurate. Here is the full picture after more investigation today.
Reproduction
On any 6.17.13-x kernel, with pve-qemu-kvm 11.0.0-4, a sustained NFS write load (e.g. 4× parallel dd or cp)...
@Davidegb You need to send me a way to give you money for a coffee or beer (seriously). You absolutely just saved me.
My results were slightly different than yours however. Kernel 7.0.6-2-pve did NOT resolve my situation. However DOWNGRADING...
By default, Raspberry Pi OS on the Pi 5 uses a kernel configured with a 16KB memory page size. However, PBS (which is compiled primarily for amd64 architecture) relies on a 4KB page size for mapping, creating, and reading fixed index files...
Hallo Zusammen,
ich muss das Thema noch mal aktivieren, aus verschiedenen Gründen bin ich jetzt erst bei der Installation.
Jetzt habe ich eine etwas andere Idee was das Synology NAS angeht.
Sprich um den Netzwerk-Traffic etwas zu reduzieren, nun...
This is absolutely needed and has to be very precise. I.e. which exact metric is used for both CPU and Memory "loads": CPU load vs CPU usage vs CPU pressure, Mem usage vs Mem pressure.
Currently testing CRS in lab and it seems to allow a node to...
Be mindful that if HA is enabled, around 2 minutes after losing quorum HA will reset the no-longer-in-quorum hosts. If you plan on using pvecm expected N, do it gradually as @UdoB explained above instead of setting it to 3 directly when the whole...
I thought this would be easy but its turning into a complicated mess.
What I would like to do is simply copy a vm from one proxmox server to another. Yet I do not seem to be able to do that in any simple easy way using the GUI.
The setup I’m...
Not OP, but thank you for this! Works perfectly. I'm just using the native prometheus exporter for metrics and just wanted alloy for log collection, so simply mounting `/var/log` to `/host` read-only and tweaking your config worked a treat.
Well turns out there is an answer to this, so capturing here. Its possible to do this via editing the vm.conf file and adding comma seperated devices to a single host PCIE line (note the UI will see this as invalid and erase it if you try and...
maybe.
bad ram can be very consequential with a zfs filesystem (as in, it can cause severe data corruption.) I cannot stress enough that you should absolutely make sure your system is stable and ram is healthy before proceeding.
The first order...
Yes. dev and support have time and cost associated. In a world where both are at a premium, responsible devs direct those scarce resources to where they have the most value. I would have made the same decision, but good on you for shouldering the...
I already re-created the storage plugin, compatible with PVE 9 here: https://forum.proxmox.com/threads/want-to-use-glusterfs-with-pve9-i-made-a-custom-storage-plugin.184107/
Adding the UI stuff back is a different story (I have patches for that...
I already re-created the storage plugin, compatible with PVE 9 here: https://forum.proxmox.com/threads/want-to-use-glusterfs-with-pve9-i-made-a-custom-storage-plugin.184107/
Adding the UI stuff back is a different story (I have patches for that...
no... proxmox is the responsible body for removing the storage plugin, which is (essentially) what this whole thread is about....
see post above, like i already mentioned
right; so logically the body responsible for the decision is elsewhere (QEMU.)
directory support still works and requires no support from PVE anyway. If the QEMU storage backend serves no additional utility, then what is the actual request for?
Proxmox says they removed the storage plugin because it's dead because QEMU dropped the backend support (which QEMU did because they also say its dead). See post above for why the QEMU backend is only marginally important.
>Everything seems to lock up in a fashion that does not allow for any sort of kernel debugging- attempted kdump and netconsole, but no luck.
you mean the system hangs on boot ?
i you removed ram, maybe it locks up because of ram shortage?
you...
In order for it to be a true quorum provider, it has to be accessible to all nodes but NOT PHYSICALLY LOCATED at either site. The whole point is should one of the sites drop, the quorum provider is not affected.