I have done some test and and reported it on Mortar telegram channel last week.
If you install a fresh debian bullseye and upgrade kernel from backports (6.xx), Mortar works if you install systemd-boot and system boots correctly.
But for now we can't install systemd-boot on debian + proxmox...
Just for feedback, I have created one user for PVE and another one for PBS.
I disabled root in PVE and PBS, and I can login with respected token in PVE and PBS authentication server.
Now PBS is connected to PVE with a token.
No more log
Very interesting
Thanks again
I played a little with API token, but I want to "full reset" this to recreate neatly.
I understood I can connect PBS to PVE with API token and secret, but after removed all token and user, and connect PBS with root@pam, I cant backup some VM anymore.
I explored some files in PVE and PBS case...
Ok, After remove and create another EFI disk with pre enrolled keys, i was able to had secure boot activated, but i had to disable signature vérification for storage controller. I will try later to change this driver.
I have broken all :/
I have added pvetest repo and upgrade the 3 paquets: pve-manager qemu-server pve-edk2-firmware
I had another version of trousers because of mortar framework installed:
root@pve:/mnt/temp/backup_ext# dpkg -l | grep trousers
iF trousers...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.