Recent content by Veeh

Hi, With a token it's much more simple. But keep in mind that your api token secret will be in clear text in your script. And if you want to automate or run unattended, at some point there will be a credential in clear somewhere. Like gfn mentioned, if you want to keep it secure, run it...

I just tried it on my infra I'm running 8.1.4 as well, and it worked. This script is not based on the api token secret. You need to enter the user password in the apip variable And there will be a first api call to obtain a ticket and cookie, which will then be used to log in and generate the...

No idea sorry Domenico. I have not set up anything with TFA, so I would not know. maybe someone else could help you out. Or if you use separate permission for the API token, it way me be possible to bypass the TFA. I'm just guessing at that point.

Hello, I have a question regarding the 7.3 > 7.4 upgrade. I'm running on kernel 6.1. Should I opt-in 6.2 prior to the 7.4 upgrade, or can I upgrade 7.4 first and do the kernel later or remain in 6.1? I don't mind having the kernel 6.2. I just want to upgrade the proper way. Thank you

Nice ! I'll update tonight. thank you

I did not know about padding overhead. ZFS is still relatively new to me. I'll look into that. Thank you Dunuin.

Hi, I creating this thread regarding ZFS Pool space utilization because I would like to make sense of how it is working. I have a ZFS Pool with 5 NVME drive of 1T. The pool is in raidz1 configuration. I did not enabled compression to get the maximum preformances. I enabled thin provisioning in...

You need to update your grub. List your avaiulable kernel with proxmox-boot-tool kernel list then update proxmox-boot-tool kernel pin <kernel-version> Also for futher info proxmox-boot-tool help Reboot then remove the the kernel again

I run a Threadripper with 2GPU in passthrough and a root ZFS install. I mounted /tmp on ram as indicated and I have no issues. Both passthrough are working fine. Thanks for releasing 6.1 this early!

I don't know the api that much but, if you check the api viewer https://pve.proxmox.com/pve-docs/api-viewer/ You have to specify the node name. I don't think you could use a wildcard. They might be a way to get the VM list for each node with the API. But it is just a guess Then from the list...

Not having anything is indeed the way to go ! I don't need the hook script to rescan the pci bus anymore Thank you for this.

You were right !! There was a mistake in the bash script. In the cookieid variable. I forgot to replace the user field by $apiu. It was set to api@pve. And off course it worked for me because that's the user I used... I fixed it. Try again

It's working fine for me. You can look in your syslog. You should see the api logging attemps. In my case my user is 'api@pve' Dec 14 13:00:13 qxmx pvedaemon[2121831]: <root@pam> successful auth for user 'api@pve' Dec 14 13:00:13 qxmx pvedaemon[2121831]: <api@pve> starting task...

Yeah, I have this already... the vendor-reset module as well. It does not help. To be fair I have no try without video=efifb:off" or "video=simplefb:off I kept adding stuff in my grub conf file but did not clean up. I'll try that Thank you

Thank you for that ! I applied the bios settings and had no issues after installing 5.19. It has not solved the "BAR 0: can't reserve [mem..." issue though. I still need to rely on the hookscript to reset the pci bus before starting the VM.