Recent content by dcsapak

hi, maybe there is also a bios setting for the bar size? e.g. somebody here solved it with such a setting: https://forum.proxmox.com/threads/pcie-passtrough-problems-msix-pba-outside-of-specified-bar.140573/

yes, that also our experience, don't forget to update the guest drivers afterwards

great to hear that it works! glad to help and bring pbs/pve to more people ;) (i guess you won't be the only one that requires FIPS compliant backups) as for the import/export slot loading, it could be done, but as you said it's a separate issue (a bug report would help to triage and track...

note that this is only a warning, and this behavior did not change, it was just silent in the past, now we log that it did not work. Whatever happens with your pass-through, it probably has nothing to do with this warning

for your info: i sent a patch to increase the timeout if we detect calibrating: https://lore.proxmox.com/pbs-devel/20250415114043.2389789-1-d.csapak@proxmox.com/ but it could be a while before this lands in any repository, so for now it's still recommended to initialize beforehand with your...

ok, i sent a v2: https://lore.proxmox.com/pbs-devel/20250416070703.493585-1-d.csapak@proxmox.com/ and new packages were uploaded to the same folder as before but with different names + different checksums:

Thanks for testing! ah yes, of course i forgot that. we have added an additional assertion that verifies the set encryption mode is really set, we have to omit that too for this situation. (as I wrote, we don't have any hardware here that support such a library managed encryption mode, so I...

thanks i sent a patch in the meantime. If you could test it, that would be great we put a temporary build with that commit in http://download.proxmox.com/temp/tape-encryption-skip-fix/ (only the backup-server package should be necessary) the checksums are (since it's just http): with that...

i see that this is an lto9 drive. Usually when a LTO9 tape is loaded the first time into a drive, it gets initialized (which can take up to two hours) and during that time it and the drive is unavailable. Usually, libraries have some 'bulk initialization' feature where you can do that for all...

ok maybe this is the problem, from what i can see, you have to set it to 'Application Managed Encryption (AME)' for it to work with pbs. PBS assumes it can set the encryption parameters and will fail currently if it cannot do that (even if it is just setting the drive to unencrypted). The...

which driver did you use ? the vgpu one? if yes, this is the one where you cannot transcode on the host/lxcs .. you'd have to use the 'regular' nvidia driver (e.g. directly from the debian repositories)

that won't be possible, you can either have a 'regular' driver on the host and share it with containers, OR you pass the whole card through to a vm OR you use the vgpu driver to use in multiple vms but then you can't use it on the host for transcoding (and thus also not for containers) this is...

what is it you want to accomplish in the end? do you want to have multiple vms with vgpus? do you want to have a regular gpu driver installed on the host? depending on what you want to do, there are different drivers you'd have to use...

ok the response you posted indicated that the drive has the capability but the application (PBS) is prevented from changing the encryption parameters. maybe there is another separate setting to allow application controlled encryption in your library?

according to this: https://docs.nvidia.com/vgpu/gpus-supported-by-vgpu.html the tesla p4 is only supported until vgpu v16, but you use 570.124.03 which corresponds to the v18 branch... I guess you would have to use the v16 branch (note that this is not supported by nvidia/proxmox but can...