Recent content by dcsapak

hi, i hope you did disable the vgpu frame limiter? (https://docs.nvidia.com/vgpu/20.0/grid-vgpu-user-guide/installing-configuring-grid-vgpu.html#setting-vgpu-plugin-parameters-on-red-hat-el-kvm ) this is currently not possible with PVE out-of-the box, you'd have to create the vgpus manually...

from another post from me: https://forum.proxmox.com/threads/on-limitations-and-maximums.179850/#post-834673 so currently there is a memory requirement of ~1MiB per resource + some overhead for the base system there is also the disk space required for rrd/task data of course

correct, the token does not use/inherit the users tfa. in fact, tokens can't have a second factor at all. This kind of use case is exactly why tokens exist in the first place to give access to users resources in an automated fashion that can be easily revoked, etc.

note that historic rrd/task data (etc.) will not be migrated over, so you might loose some rrd/task history (though i'm not sure if it's safe to just simply rename those folder/filenames too, they would be in /varlib/proxmox-datacenter-manager/ )

hi, the attachement quarantine sits right below the spam and virus quarantine in the admin interface, there is no separate url/page to go to. If you don't see the mails in the attachement quarantine (did you select the right timeframe and email? are you connected to the correct host if this is...

assuming that the ids will be the same (e.g from the individual drives/changers) you could try to copy /var/lib/proxmox-backup/tape from the old to the new installation this contains the inventory + chunk logs/indexes for the individual tapes

ok, so while I could not figure out how/when that broke (if it was ever functional..) i sent a fix now: https://lore.proxmox.com/pve-devel/20260902074338.914500-1-d.csapak@proxmox.com/T/#t thanks for reporting...

interesting, on my work machine i couldn't reproduce at all (neither with chrome/chromium nor firefox), on a different machine i can... (though in my case the xtermjs part doesn't overlap with the button) i'll see what might be the issue here...

hi, nice work. Did you consider sending patches directly instead of making a standalone thing? While we're probably wouldn't integrate react+vite, we're using our own rust based ui framework (that we use e.g. for the user quarantine mobile view) that could replicate most of this i reckon...

hi, this should now be fixed. It seems there was some error during upload that was not caught, thanks for the report!

hi, tested with multiple browsers here, but could not reproduce that. it always showed the guest not running button correctly and not any xtermjs part. can you give me the output of 'pct config ID' for the container, and 'pveversion -v' to see which versions and configs you're running...

yes, there is currently a bug with the permission on this api call, see the first version of the patch i sent: https://lore.proxmox.com/pdm-devel/20260708133630.1807997-3-d.csapak@proxmox.com/ i did not have time yet to send a v2, but will do soon

mhmm it could make sense to have that as an option somewhere. If you want you can open a feature request on https://bugzilla.proxmox.com for that

hi and thanks for the report. please do, there the visibility for the devs is simply higher and we can track it better thanks!

can you post the vm config? (qm config ID) and your host version? (pveversion -v) without that info it's impossible to say what might happen