Search results

Bump :)

Hey, when using user:RANDOM password in a custom.yaml, is it possible to get the output of the passwords set to the task status window in the webgui? The config works, but I have to be fast to attach to the VM on a first boot to catch the passwords. I'm aware that I should use public keys, but...

grep CONFIG_NR_CPUS /boot/config-$(uname -r) What does this say on both of the hosts? I remember that Ubuntu's kernel used to be limited to 255 cores. Or maybe it was 256.. Anyway, are all of the CPUs online? This should print the CPUs which are offline: grep -L 1...

https://forum.proxmox.com/threads/efi-sub-loaded-initrd-from-command-line-option-system-cannot-boot.104377/#post-450093

Leaving the core limit value empty will result in 'unlimited'.

Ah, this was changed in 6.4 - my bad. I had a 6.3 system where I created an additional encrypted dataset on the rpool and made it unbootable (grub). I'm not sure which method is preferrable, ESP or bpool. As long as it works..

That's not the same thing though. Its impossible to run encryption on the root pool with the current setup.

When using zfs, could you consider creating a separate boot pool (like seen here: https://openzfs.github.io/openzfs-docs/Getting%20Started/Debian/Debian%20Buster%20Root%20on%20ZFS.html) so that some features might be enabled on the root pool, such as encryption?