Recent content by dcsapak

mhmm in the subscription registry we already show the socket count per remote, maybe a node count there + total count there could be enough? or does it have to be on the dashboard?

can you post your container config as well as the output when starting with debug on: pct start <id> --debug

es gibt für changer tatsächlich ein 'eject-before-unload' flag, ist aber nicht über die gui zu setzten, sonder nur über die cli: proxmox-tape changer update <changername> --eject-before-unload true zum überprüfen kann man die config so ausgeben: proxmox-tape changer config <changername>

Hi, and thanks for sharing. Note that Proxmox is a registered trademark, so please don't include it in the name of the tool/repo/etc. You can indicate that your work is based-on/for Proxmox by, e.g., using a wording that avoids suggesting that this is a Proxmox project, but rather based on one...

the non-free repos should work just fine (e.g. i have it here on my proxmox install too). Our package dependencies should prevent any problems, or it would warn you that the proxmox-ve metapackage will be removed. Of course this is no guarantee, it can always happend that we missed some...

i don't think there is a widget currently that shows this. Is there a specific reason why you want to know this? (it shouldn't be hard to add, but having context why this is important can help when implementing so we can create/update the right widget with that)

HI, can you post the iommu groups, the vm config and the output of dmesg here? in general the error: is a mainboard/firmware limitation that the linux kernel enforces, so to really fix it, you'd have to either change some bios setting or ask the vendor for an updated bios

hi, nachdem sich bis jetzt noch niemand dem angenommen hat, hab ich jetzt einfach mal den patch geschickt (ist aber noch nicht reviewed/applied): https://lore.proxmox.com/pbs-devel/20260702123910.3975440-1-d.csapak@proxmox.com/T/#u

what exactly is the bug here? can you elaborate? the output you posted looks normal...

no AFAIK currently not, but it's a very sensible feature request ;)

then it sounds like it to be a guest driver issue? can you post the vm config and what kind of hardware you have?

Hi, what browser and version do you use? (looks more like a client issue to me)

hi, sorry for the late answer. did you make sure to also open the 3128 port? can the client reach the correct ip directly? (192.168.1.122 in this case)? you could also try opening the file with remote-viewers 'verbose' and/or 'debug' output: remote-viewer --verbose --debug <path-to-vv-file>

hi, You only mentioned ssh-key in the OP, and this can be done on container creation but not later (I misremembered that, sorry) there is no generic push/exec for containers via the api (yet), but feel free to open an enhancement request on our bugtracker: https://bugzilla.proxmox.com as a...

this is not possible with a single api call. you have to clone first and then configure the options you want to set.