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
i think this is just a misunderstanding how the prune simulator works
it only ever simulates the pruning once namely on the 'end date + time' and assumes that all backups exist from the backup job schedule
if in reality the prune job runs...
hi,
the cause of change seems to be this commit:
https://git.proxmox.com/?p=pve-xtermjs.git;a=commit;h=7b47cca8368e63c30f6227442570f9f35dd7ccf0
so we needed to change the behavior because of some timing change from bookworm -> trixie
not sure...
ok, i think i see what might be the problem:
you have lines like this in your config:
allow-bond1 ens4f0np0<br>
which should only be there if you're using openvswitch, but you're using plain linux bridges (did you maybe have ovs configured...
hi,
i think you're correct that we should improve the wording and reference here. If you want you can open a bu on https://bugzilla.proxmox.com/ so that we can better track it (and you can get updates when/if we fix it)