Das ist jetzt nicht dein Ernst?
Ganz Grundsätzlich könnest du ja mal schauen, wenn du morgens um 4 Uhr die Kiste anschaust, welcher Container / VM den die Last erzeugt - die haben ja alle eine Anzeige für Auslastung in der GUI.
Also Lösung wäre...
Nein, er nimmt in der Regel das, was eingestellt war. Bei vSphere ist das oft Standard, weil die schon 13x die Art wie man es einstellt geändert haben.
P.S. bei 12 vCPUs muss das schon eine Dicke DB VM sein. Gern mal beim migrieren überprüfen ob...
Viele meiner Homelab-Mainboards erlauben das Datum-/Uhrzeit-gesteuerte Einschalten direkt per BIOS-Setting. Andere Kisten kann ich per WOL aufwecken, aus einer crontab heraus. (Oder per schaltbarer Steckdose, "klassisch" oder per "Smart Socket"...
The resolving commit for mentioned vioscsi (and viostor) bug was merged 21 Jan 2026 into virtio master (commit cade4cb, corresponding tag mm315).
So if the to-be-released version will be tagged as >= mm315, the patch will be there.
As of me...
Yeah, that's one of the manifold pitfalls everybody enjoys; glad you made it work again!
There is only one countermeasure: exercise restore from time to time, not just run a backup ;-)
There are situations where stop-mode is recommended, yes...
Der Meinung bin ich nicht. Der sekundäre Storage ist ausgeschalten und kann nicht deshalb auch nicht an den meisten Tagen kompromittiert werden. Hier geht es hauptsächlich um maximal Storage mit hoher Leistung und tiefe Rücksicherungszeiten. In...
Before restarting a cluster node following the last update , only one VM reported error in the manual migration :
2026-02-08 08:07:40 migration status: completed
2026-02-08 08:07:40 ERROR: tunnel replied 'ERR: resume failed - VM 117 qmp command...
@fiona Is there anything we can do to support resolving this? or do you just need time? or should we talk with the qemu team?
If there is a test build, please grab me to test.
but such things will really keep proxmox far from "production ready" unless it is stated somewhere (maybe it is, I did not see it): "LXC are NOT for production - just for fun" ;-)
but such things will really keep proxmox far from "production ready" unless it is stated somewhere (maybe it is, I did not see it): "LXC are NOT for production - just for fun" ;-)
During the last big break (lxc docker), I think it was dissuaded from us using containers to host mission critical workloads and to use VMs instead for anything that must not go down. But it is difficult due to ram shortages right now...
how come such bugs happen BEFORE releasing the new version? bloody hell, testing in proxmox seems to be nowhere ;-(
no, I am not complaing - just stating the fact
anyway, thanks to all who posted the workaround
how come such bugs happen BEFORE releasing the new version? bloody hell, testing in proxmox seems to be nowhere ;-(
no, I am not complaing - just stating the fact
anyway, thanks to all who posted the workaround
I don't know if this was implied, but also software defined storage is a requirement so that you can quota the used storage for your clients / customers / tenants.
What is missing to turn this into a fully fledged setup are:
RAM restrictions...
copy folder and all fiels from
/var/lib/pmg/templates
to
/etc/pmg/templates
Edit the files: /etc/pmg/templates/main.cf.in
at the smtpd_sender_restrictions part,
add below content:
check_sender_access regexp:/etc/postfix/Blocked_Sender_Domain...
Hey,
Just setting up PBS with a dell tl2000 with 2 sas lto5 drives connected to the server. I have updated the firmware of the TL2000 and rebooted the server in order to troubleshoot.
When I try to run proxmox-tape barcode-label --pool I get the...