Search results

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 every day, of course the outcome will be different...

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 how we can fix that at the moment, but it's just a...

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 at some point?) our code assumes that ovs is...

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)

from what i can tell the line 1224 of INotify is in reference to the network config, can you post maybe your /etc/network/interfaces ?

Hi, not sure if these are things we want to implement (since there are enough tools to do that if you're interested (like fio, iperf, etc.) but feature requests should be opened on https://bugzilla.proxmox.com thanks!

Hi this sounds indeed very weird and unusual. Just to clarify do you mean it reboots every 19-20hours or every day between 19:00 and 20:00 ? Where in the logs did the reboot occur ? (or was that only between reboots?) Sorry if i have missed something, but it seems you replaced basically every...

hi again, that issue is on upstream debians side though, nothing we can fix here ;)

i don't think this is correct. I regularly passed through gpus with 24+ GiB memory in vms with less than 8 GiB, not sure why you would think that ? Is that documented anywhere ? while both might influence it, in general it's not necessary to set these parameters. balloning will not work with...

hi, thanks for reporting! this should now be fixed

i don't know exactly what happened, but your other post was not deleted? it's here: https://forum.proxmox.com/threads/rtx-pro-6000-passthrough.169856/ locking this thread so we can continue in the other one

Hi, first, to clarify, do you want/use any of the gpus with vGPU ? I ask because, using pre ada lovelace cards with ada+ (including blackwell) drivers only work in one specific scenario: if you want to use the pre ada cards with vgpu and the ada+ as full passthrough. Wen you want that you'd...

does it work with the older kernel? if yes, check/post the syslog from the boot with the blank display to see what might cause the errors

it uses the api call /node/localhost/network api call and shows everything with a cidr so if you post the output of pvesh get /nodes/localhost/network --output-format json-pretty i can check what might be the problem

you can remove a config line again with qm set VMID -delete <config> so e.g. if you added a 'hostpci0' config you can do qm set VMID -delete hostpci0 note that e.g. disks will be added as unusedX if you do this (only when the unused config is deleted, the underlying disk will be deleted)

the template file name is included in the api call, but not currently shown on the webui but on the cli it's shown: pveam available if i may ask, why do you want to know the format? this should not matter really how it's compressed? also lxc templates are always tarballs (with various...

fyi: i opened a tracking bug for that: https://bugzilla.proxmox.com/show_bug.cgi?id=6668

yes, these are call 'group filters' in the code and have 3 types, 'type' (so either host/ct/vm), 'group' (e.g. vm/100) and 'regex'

Hi, looking at the code, the group filters are really only effective on group names, not including the namespace so no, regex filtering will not work here what you can do however is to add a tape backup job for each namespace with it's own group filter, and schedule them close one after...

ah ok, the latest version of the patches are here: https://mail.gnu.org/archive/html/qemu-devel/2025-06/msg00011.html and they are not yet applied in qemu, so maybe in a later qemu 10.x release