I've released a near-production-ready version of pve-moosefs now that adds support for MooseFS Block Device (mfsbdev). This allows for high performance VMs that bypass FUSE and qcow2 entirely, suitable for database workloads...
Wenn mit Kernel 7 alles läuft würde ich an deiner Stelle mit apt remove proxmox-kernel-6* --purge alle alten Kernel deinstallieren.
Edit: daanw war schneller. :)
See the bug, I can reproduce this on Broadcom and Intel NICs as well so I think its a wider problem. The problem exists when newer linux kernel features in 6.16+ interact with new Qemu versions 11.0+ which introduce new offloading scenarios. I...
Genau so war es. Läuft jetzt sehr stabil, viel schneller und mit wesentlich weniger Ressourcenverbrauch auf meiner Synology als VM. Neben der Sicherung der VM's unter Proxmox mache ich einmal wöchentlich per cronjob noch ein backup vo´m /etc...
Proxmox VE implements it's own custom backup QMP command, it's not the same as from the upstream QEMU docs. The on-target-error could be exposed, but IMHO the default should stay as is. If there is an early error, then doing the rest of the...
These writeups by @bbgeek17
should cover everything: https://kb.blockbridge.com/technote/proxmox-qcow-snapshots-on-lvm/index.html
https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/
Awesome, that order did the trick. All looks good. I did the same for nh5 too, so they are all up. Thanks 100x for all your help!
Do you know why this may have happened? I've rebooted Proxmox nodes many times, including entire clusters that were...
that looks good so far, the question mark is probably because pvestatd is not running yet on that node. could you try starting it and see if it goes "green" then? if it does, you can start the other services as well on that node.
please then try...
Hi @vaschthestampede,
do you have IO thread enabled for your VM disks? If not, it's highly recommended to do so. It's also highly recommended to not start backups from all nodes at the very same time, since PBS might get overloaded with handling...
Hi...
I am using pve-network-interface-pinning to pin enp1s0, for instance, to eth0, eth1... and so on.
I have 9 nic each server.
But I need to change the hardware and after that, all nic turns back to previously name, like enp1s0, when I use ip...
I found that binary too already. But its not compatible with ARM.
From the dependencies it uses I don't see why it would not be compatible with ARM.
Is the Binary itself restricted to x86? Or is it easily doable to also offer an ARM Version with...
also statt pfsense würde ich eher opnsense empfehlen, weil das kostenlose pfsense kaum noch gepflegt wird.
aus sicherheitssicht dürfte sich da nicht so viel tun, aber grundsätzlich ist so eine dedizierte security appliance da schon der bessere weg