Search results

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 are patched, e.g. to use different dependencies...

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

hi, one way would be to use the 'pvesm' tool: pvesm set <storage-id> --password

Hi, I cannot reproduce on current master here. What does git status cargo tree say? what's the steps and command that you use to build it ?

can you post the output of apt update please ?

i don't think it's possible to configure tls1.3 only is there a specific reason why you want to do this?

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