fstrankowski's latest activity
-
fstrankowski replied to the thread Proxmox für 500-1000 VMs.Beste Zusammenfassung hier. Sehr schön aufbereitet. Sieht aber nach einer vollständig durch KI generierten Antwort aus, korrekt? Wenn dem so ist, bitte kennzeichnen. -
fstrankowski replied to the thread [SOLVED] apt update is not working.First: Welcome to the Forum! The previous answers are correct but i would like to add more information to it. Your internetprovider "ROSTELECOM" MITM your connection (is reading what you are visiting) and modifies the original endpoints answer...
-
Für die pfSense-Ersteinrichtung reicht der minimale Ansatz locker. Openbox + Firefox im LXC, per noVNC zugreifen — fertig. GPU-Passthrough brauchst du dafür nicht, die pfSense-Weboberfläche ist anspruchslos. Wenn der Container danach nicht mehr...
-
fstrankowski replied to the thread [SOLVED] Qemu agent not connecting.I expect it to work now, correct? If so, please change the thread title to solved. Glad i could help :)
-
fstrankowski replied to the thread Container mit Desktop.Guter Anfang. Ich nutze gerne dies https://hub.docker.com/r/jlesage/baseimage-gui
-
fstrankowski replied to the thread [SOLVED] Qemu agent not connecting.That means you did not enable the guest agent in Proxmox. After doing so the VM needs to be completely shut down and started via Proxmox to make the changes take affect. Please do so and try again.
-
fstrankowski replied to the thread CEPH heartbeat issue after reboot.Problem is, most of it just doesnt make any sense whatsoever as its just thrown in a thread without even investing time to markup the post and remove the nonsense in it in the slightest way. Please invest the time to either adequately edit...
-
fstrankowski replied to the thread [SOLVED] Qemu agent not connecting.Oh i just notice, you try to enable it. That doesnt work. Can you post the output of systemctl start qemu-guest-agent
-
fstrankowski replied to the thread [SOLVED] Qemu agent not connecting.Welcome to the Forum! Did you try reinstalling the guest-agent on said VM? apt reinstall qemu-guest-agent
-
-
fstrankowski replied to the thread Feature Suggestion: Custom Attribute.Welcome to the Forum, happy you enjoy using Proxmox! If you'd like to have certain features added, please file a feature request at bugzilla.proxmox.com
-
fstrankowski replied to the thread CEPH heartbeat issue after reboot.Welcome to the Forum. Please format your post and dont copy & paste AI Slop.
-
fstrankowski reacted to tommymcguiver's post in the thread multipathd and udev-worker deadlock requires kernel reboot with
Like.
I thought this may useful to people that are having multipathd and udev-worker deadlocking issues. My Environment - Proxmox 9.1.1 - Purestorage ISCSI server Purestorage requires device queue limits, and scheduling attributes to be changed via... -
fstrankowski replied to the thread Error migration conntrack in live mode.its probably because the CPUs of said nodes feature or highly different feature-stack. Thats why for example x86-64 v2 works as it presents a homogenous subset of certain CPU instructions to the VM.
-
fstrankowski replied to the thread Abschalten von "You do not have a valid subscription for this server ...................".Hatte ich vor einiger Zeit auch nochmal zur Diskussion gestellt und es gab die klare Ablehnung aufgrund der nicht rechtfertigbarer Kosten für Aufwand/Verwaltung dieser Lizenzen. Edit: Johannes war schneller.
-
fstrankowski replied to the thread Offtopic: Jellyfin erzeugt beim Abspielen hohe Load auf ProxmoxVE.Transkodierst Du die Filme beim Abspielen? Wenn dem so ist, schalte mal alle Transkodierungsoptionen aus.
-
fstrankowski replied to the thread [SOLVED] Another io-error with yellow triangle.Maybe useful for people coming back to this thread one day: Take a look at the kernel.org thread which describes this bug including examples from Proxmox and QEMU. There is also an excellent writeup here.
-
fstrankowski replied to the thread Max cluster size.TLDR; This is an excellent go-through the requirements of corosync-tuning for larger clusters by @fweber (which is in fact part of linked thread by @bbgeek17)
-
A status update on this: Two corosync parameters that are especially relevant for larger clusters are the "token timeout" and the "consensus timeout". When a node goes offline, corosync (or rather the totem protocol it implements) will need to...
-
It's already solved, seems it took a long time to propagate. Thanks!
