Search results

Hi I have a 48GB A40 GPU running Proxmox 8.2 (pve-manager/8.2.4/faa83925c9641325 (running kernel: 6.5.13-3-pve)) with nvidia driver ver. 535.161.05 I am running 7 vm with vgpu successfully (4GB Profile) I should be able to run 12 VM with the given video memory I have. But not able to start...

Hello, I was considering https://www.zabbix.com/ru/integrations/proxmox#proxmox or https://www.netdata.cloud/integrations/data-collection/containers-and-vms/proxmox-ve/ any thoughts

So lets assume that you want a backup policy like Keep last 6 hourly backups Keep last 7 days, 4 Weeks, 12 Months and 3 years. What would be the best GC and Prune settings for this

So does that mean that a GC interval below 1 day + 5min is meaningless, if so why have the option below this interval in the GUI or i have understood this all wrong

I dont think we have any process that touches the chunks in the backup server we just take backups everyday at 9 pm and then we were running a garbage collection (GC) every 2 hrs, changed it to every day at 00 am now. lets see if it helps

Hello Team, I dont see how I can get the pending removals of 1.34TB - this always shows as 0bytes removed I have tried daily garbage collect, hourly, every 2 hours every thing tried. Maybe i have not understood what actually happens here can somebody help

Thanks for the tips, in the meanwhile - added some space to the zfs pool by increasing the size of the proxmox backup - datastore disks by resizing them. and i am able to do the GC now Thanks a ton again

even after deleting backups and reducing the retention from last 7 to 4 and pruning the backups - this remains 0 and zero bytes free any ideas guys

Hi, At a customer site the backup datastore became full, we pruned the number of backups from keep 7 to keep 4 and ran prun, we even deleted the backups of 2-3 vm but still the storage is full at 100%, Any ideas on how to come out of this situation. Thanks in advance

Anyone has this template as this site seems to be offline. Trying to get some monitoring up and running with autodiscovery

Oh Daam ! I dont think it would work, but I shall try this on another host next week once I get my hands on another GPU I got it working with Kernel 6.5.13.3. straightforward works

oh yes I did all of that... no luck. but i have an AMD EPYC Server so iommu is enabled by default but i have still put amd_iommu=pt but after enabling the VFs i get write errors if i check iommu dmesg | grep -e DMAR -e IOMMU [ 3.467959] pci 0000:c0:00.2: AMD-Vi: IOMMU performance counters...

compiles if you patch it

I had tried all this, exact same steps but my mdevctl types is empty now i think the only way left is to go back to kernel 6.5 if this is not going to work

I confirm that on Proxmox 8.2.4 with Kernel 6.8.8.2-pve the 550.90.05 compiles successfully and nvidia-smi reports the card working but mdevctl types output is empty even though its A40 GPU - vGPU Capable

Nobody with any ideas? I even tried increasing the PG count to 512 but it strangely only sets it to an odd number 346 automatically (I put 512 basis the Ceph PG Calculator) rebuild speed continoues to be slow for over 2 days. With NVME drives this is very slow

Thats the right way to go

Try Kernel 6.5.15

Yes it will work but Ceph hates Raid cards and likes the disks exposed directly. not sure if your card is going to pass these disks as native disks like in IT Mode. I would keep all of them in IT Mode (convert the card to IT mode and not in RAID Mode, enough articles available google for it -...

https://forum.proxmox.com/threads/remote-migration-of-cold-vm-eerror-no-export-formats-for-vm-pool-vm-9999-disk-0-check-storage-plugin-support.123048/#post-678088