Search results

  1. B

    Server and Proxmox show 255 cores

    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...
  2. B

    [SOLVED] Unable to unlock zfs root dataset during boot

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

    are CT cores pinned during runtime or can switch between E and P cores ?

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

    Proxmox VE 7.0 (beta) released!

    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..
  5. B

    Proxmox VE 7.0 (beta) released!

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

    Proxmox VE 7.0 (beta) released!

    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?
Top Bottom
Back