Hi @molotch ,
If what you are showing for the sources.list is the entirety of the file, remove that file completely, otherwise remove just those lines.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
Hi,
You could remove either, but the latter is the newer deb822 format and is what PVE 9 ships with per default, so I'd remove the entry in /etc/apt/sources.list.
Hi @molotch ,
If what you are showing for the sources.list is the entirety of the file, remove that file completely, otherwise remove just those lines.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
HI @RMaxwell72,
So this worked for me. I executed the command twice. The first time it got rid of the admin key but fail querying the monitors.
/usr/share/pve-manager/migrations/pve-cephx-rotate-service-keys --apply \...
Ohhhhhh thank you! I understand now. Definitely meant hostnodes=0 in this instance
One question with your last point about setting affinity, do you mean to set the affinity for all other VMs on that node to cores not isolated?
That's isolcpus doing exactly what it says. It disables the scheduler's load balancing on those cores, and PVE's affinity: option only sets a mask on the whole qemu process. So all 16 vcpu threads end up on the same one or two cores and nothing...
Avec plaisir ! Bon courage pour résoudre votre problème actuel. N’hésitez pas à revenir vers moi si vous décidez de tester le projet plus tard ou si vous avez des questions. Tout retour d’expérience sera le bienvenu.
qm guest cmd $VMID fsfreeze-freeze exactly triggers my recognised behaviour.
From a Kubernetes point of view everything works as expected, I can also access the pods running on the VMs as the logic sits in the RAM but as soon as I would like to...
It seems that you do not have a EFI because your server is in Legacy mode.
You can just ignore the message or change in BIOS to UEFI mode an reinstall the system.
Ich lese grad nach zur ZFS-Replication. Was mir grad dämmert (gerne Feedback): bedeutet das dann, dass ich Node2 im Normalfall ohne laufende VMs betreibe? Und Node2 den ZFS-Pool quasi eher als read-only behandelt im Normal-Betrieb?
Also kein...
Hello, thanks for the insights. I'll double check on "freshness" on my side, there might be improvement opportunities.
No feedback on the proposal unfortunately.
As stated here, kvm32/kvm64 are non-recomended x86 CPU, listed "just for historical compatibility with ancient QEMU versions", so the way to go is either:
- Use qemu32/qemu64 CPU (lower performance and increased security risks as such QEMU cpu...
Thanks. On freshness, the trick is cheap: a daily job that only reads Proxmox's InRelease and Packages, compares the newest version with what we already publish, and exits when they match. The build only runs when there is something new, so it...
Wenn es Dir so geht wie mir und vermutlich auch div. anderen Usern, dann wirst Du im Laufe der Zeit - sprich nach x oder xx Monaten - sicherlich auf die Idee kommen Dinge vielleicht doch wieder (ganz) anders zu machen. :)
Mal der grobe Ablauf...
Hello, thanks for the insights. I'll double check on "freshness" on my side, there might be improvement opportunities.
No feedback on the proposal unfortunately.