Search results

this is, in fact, the right way to do it. PBS just uses any tape that is available (no order here is guaranteed) but decides before checking the drive see the examples in the docs: https://pbs.proxmox.com/docs/tape-backup.html#example-setups

hi, the issue in the first post looks like a bug, would you mind opening one on https://bugzilla.proxmox.com with the logs and relevant info to reproduce (configs, storages, etc.) the error in your second post is not really a bug, even if you use root@pam for pdm, it will create a token to...

just fyi: you can define pools as 'child' pools by using a slash in the name, so you can create the pool 'foo' and the pool 'foo/bar' in the gui they won't be shown nested, but i think for the purposes of permissions this should work.

please don't double post your questions, see my answer here: https://forum.proxmox.com/threads/nvidia-vgpu-software-18-support-for-proxmox-ve.163153/page-2#post-811872

this is not really a vgpu question, as that only works with virtual machines. please open a separate thread for that question

i generaly layering cow filesystems should not break anything, but it will slow down (since each layer has to do cow) Personally, i'd use only one cow layer, be it in the vm or at the hardware storage level. In any case, you could run tests in the vm if the performance is acceptable if you...

the vCS license is only for nvidias ai enterprise driver/software (https://www.nvidia.com/en-us/data-center/products/ai-enterprise/) which is distinct from vgpu (not sure why that site still has them up for sale...) note that AI Enterprise is currently *not* officially supported in Proxmox even...

yes, see the link in the first post and this table by nvidia: https://docs.nvidia.com/vgpu/gpus-supported-by-vgpu.html i don't think there is a "best" way, but you can buy it in a shop like you linked, or if you're working with a vendor to get you servers, if these are partners with nvidia...

we're using a (slightly) modified ubuntu kernel, so if that card is supported in a recent version of that kernel (6.14, 6.8; depends on the pbs/pve version and the kernel version you installed) then it should work

Please write your posts in english so that we're able to help you

yes, i agree that having a more 'intelliget' way of selecting how to do the actual migration would be good, would you mind opening a feature request on our bugtracker? https://bugzilla.proxmox.com it may involve some changes on PVE too, so not sure how/when we could do something like that

Hi, my guess is that on the PDM you use the cross-cluster migration? If yes, the hostname/ips used in the remote configuration of the PDM is used for the migration, so which network is used depends on the network/dns/etc. setup

hmm that would probably only make sense if we autogenerated the token, else removal of a remote might mean that some important token is gone nonetheless, would you mind opening a feature request on our bugzilla? https://bugzilla.proxmox.com

hi, this should already be possible. After adding a remote, simply edit the remote in the gui and enter the url in the 'web ui url' field

Hi, what is the info of the data you entered? (remote id, etc.) maybe you can post a screenshot of the summary page in the wizard?

i think the correct command here would be pvesh delete /cluster/acme/account/pvecluster so the name in the path yes on deletion we try to unregister that account. if you delete the file from /etc/pve this should not break our stack, but without backing up the secrets there, you'll not be...

ah ok, so that too is missing.. don't worry, there is still a way that should work ;) you can directly use the api or use the cli helper tool 'pvesh' (which exposes the whole api on the cli) pvesh create /cluster/acme/account --contact <contact> --eab-hmac-key <key> ... the usage can be...

hi, i answered a bit more detailed in your other thread: https://forum.proxmox.com/threads/pve9-in-place-upgrade-failed-due-to-mellanox-nvidia-networking.173385/#post-806883 please let's continue this discussion there

hi, just for your information, the nvidia driver does not have to directly support debian 13, but actually the kernel version is more the reason here. Since we base our kernel on ubuntus and not on debians this is different from debian 13. This can always happen with out of tree modules and...

see the help output on the cli: # pvenode help acme account register USAGE: pvenode acme account register [<name>] {<contact>} [OPTIONS] Register a new ACME account with a compatible CA. <name> <name> (default=default) ACME account config file name. <contact>...