Search results

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>...

ah ok i get what you mean now. yes this seems this was overlooked in the datacenter view you can however register as many custom accounts you want on the cli with pvenode acme account register

hi i'm not super sure what you mean? on pve you can create multiple accounts for ACME? i can create multiple acme accounts without a problem?

hi, this is currently by design so that the source can't be started accidentally (since the guest would run twice in that scenario), see also: https://bugzilla.proxmox.com/show_bug.cgi?id=6017 one possible workaround would be to clone the vm first and then migrate it with 'delete-source'

i think this only relevant to pve not the datacenter manager? (if yes, i'll move the thread to the correct forum) could you please provide a bit more info? how is the host & guest network configured? what tests did you run? (ping, traceroute, etc.)

could you try to set the vga type to 'cirrus' ? you can do this with qm set 128 -vga cirrus NOTE: this is one of the recommended vga types, and should only be used for old operating systems (such as this i guess), see also...

Hi, can you post the vm config? qm config ID ? is there any setting regarding color depth or similar (i'm not very familiar with netware ;) )?