ah ok, if that version is the culprit, then I think the cause of the bug(s) should already be fixed in git by this commit: https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=c2e2559d2176062c44aab9fc934f67f047ac585b
it's not yet...
from the exceprt of the log, i guess that you're german speaking ("Herunterfahrtyp") so i guess you're currently in GMT+2 timezone? then that would somehow fit because the timestamp:
is in UTC time, which would correspond to around 03:00 in...
could it be possible that somebody pressed on shutdown from the pve ui ? (or via the pve api/cli) ?
if the guest-agent is configured and installed, it will be used when shutting down a vm from the PVE side
EDIT: ah sorry, saw just now that you...
coincidentally i recently had also a ryzen 1700 processor that seems to be defective. it ran without problems for years, but recently i changed the power supply (that is good & new) and the processor would hang or reset. i replaced it with a...
no, such hooks are currently not implemented, but i can see that triggering some things on some events in the cluster could make sense. you could open a feature request on https://bugzilla.proxmox.com (also maybe a colleague there has another...
not that i'm aware, but you can always open a feature request on https://bugzilla.proxmox.com (no promises though)
in general, there speaks nothing against installing things like telegraf on the proxmox host directly, as long as you know what...
it seems this error comes from ansible itself, so has nothing to do with pve really, not sure why this only comes up on pve9 installs
it looks like there is somewhere a \uDCE9 character in the text (https://www.compart.com/en/unicode/U+DCE9)...
interesting, seems qemu believes this gpu is an itegrated one and tries to apply it's quirsk/requirements for it.
can you open a bug on https://bugzilla.proxmox.com so we can track this better? (it's probably an upstream bug, but still good to...
while i cannot say why this wasn't answered at the time. i can try to answer some things from the post
with the introduction of PVE 4, the HA stack changed as a whole, and fencing is only done now with the watchdog self-fencing. the old wiki...
the first issue with reload etc. i could imagine how they could happen, but the second one with the same tag i can't imagine how that would happen if the tags are really the same (so no whitespace, case difference,etc) but anyway, both are bugs...
Hi,
no, it's not a paid feature. Proxmox VE is 100% open source, and there is no feature gating.
As for why PCI pass-through does not work for you correctly, with the information i can't say exactly, but it's often a bit of trial and error...
thanks, sent a fix:
https://lore.proxmox.com/pdm-devel/20250912065857.249518-1-d.csapak@proxmox.com/T/#u
in the future don't shy away from filing a bug, even for such small things :)
that commit hash does not exist here in the proxmox-backup repository but in the 'pxar' repository, so it's not actually the proxmox-backup-client?
well, building it is only supported on debian with our developement repos. some of the pacakges...
Thanks! Ended up being the same thing. RAM. Problem solved - still some mysteries. Very strange as I swapped it previously on the Asrock Rack board*.
Reboots over the previous days before changing RAM were at 19hrs 55min, next day at...
can you post the output of
lspci
dmesg
from the host?
and
nvidia-smi -q
from the guest?
since you can install the driver and nvidia-smi (in the guest) shows the card, it's a different issue than the OP, so it might be better to open a new thread