Recent content by mhaluska

  1. M

    LXC template

    Here: https://fra1lxdmirror01.do.letsbuildthe.cloud/images/ For example for Rocky: https://fra1lxdmirror01.do.letsbuildthe.cloud/images/rockylinux/8/amd64/cloud/20231202_02%3A06/rootfs.tar.xz
  2. M

    PVE 8.1: missing ondemand CPU governor, high power usage & one kernel crash

    Since upgrade to 8.1 and kernel 6.5, I'm experiencing high power usage on my system. With PVE 8.0 and kernel 6.2, power usage was around 7-8W, now with powersave governor usage is around 18-20W. Nothing else changed, same number of lxc/kvm, same CPU usage. System is most of time idling. System...
  3. M

    [SOLVED] PBS upgraded to 2.0 - Task log / status

    Awesome, fix from pbstest works like a charm. Vielen Dank Thomas!
  4. M

    [SOLVED] PBS upgraded to 2.0 - Task log / status

    No log output from task log + task status tab - err 400. This is PBS upgraded from latest 1.* version. # proxmox-backup-manager versions proxmox-backup-server 2.0.10-1 running version: 2.0.10 Error output in Task -> Status: Bad Request (400) parameter verification errors parameter 'upid'...
  5. M

    Rocky Linux Template

    Working = I'm able to do everything. Those LXC containers are working fine and are reachable from outside.
  6. M

    Rocky Linux Template

    Tested privileged and unprivileged, both are working fine in my PVE 7.0 VM (just required additional reboot after 1st start to take configured IP address) Unprivileged: arch: amd64 cores: 2 hostname: rocky-unprivileged memory: 1024 nameserver: 10.31.1.1 net0...
  7. M

    Rocky Linux Template

    Priviledged and unprivileged tested, both are working fine. I can test also on PVE 7.0, I've one in VM for testing.
  8. M

    Rocky Linux Template

    # pveversion pve-manager/6.4-12/8c75fb0e (running kernel: 5.4.119-1-pve)
  9. M

    Rocky Linux Template

    Actually I don't remember, but I think I had some issue(s) with default ones - but this is long long time ago.
  10. M

    Rocky Linux Template

    Working fine for me. But instead of default, I'm using cloud images. Detection should work fine for you too, part of CentOS.pm for version detection: if (($release =~ m/release\s+(\d+\.\d+)(\.\d+)?/) || ($release =~ m/release\s+(\d+)/)) { if ($1 >= 5 && $1 <= 9) {...
  11. M

    [SOLVED] PVE 6.3-4 and ZFS 2.0 ignores zfs_arc_max

    Since OpenZFS 2.0 arcstat looks little bit different, size is current used size and c is max ARC size defined, where avail is free/available memory on system. # arcstat time read miss miss% dmis dm% pmis pm% mmis mm% size c avail 16:38:47 0 0 0 0 0 0...
  12. M

    [SOLVED] PVE 6.3-4 and ZFS 2.0 ignores zfs_arc_max

    Your ARC max size looks fine = 10G. Check details from arc_summary command like this: ARC size (current): 97.9 % 62.6 GiB Target size (adaptive): 100.0 % 64.0 GiB Min size (hard limit): 100.0 %...
  13. M

    [SOLVED] PVE 6.3-4 and ZFS 2.0 ignores zfs_arc_max

    I'm not 100% sure, but I think you should do so. Anyway this will cause any harm... ;)
  14. M

    [SOLVED] PVE 6.3-4 and ZFS 2.0 ignores zfs_arc_max

    Correct, this file is not there by default. But you can create this file. And also change this dynamically without reboot using: echo 68719476735 > /sys/module/zfs/parameters/zfs_arc_min # For ARC min value echo 68719476736 > /sys/module/zfs/parameters/zfs_arc_max # For ARC max value
  15. M

    [SOLVED] PVE 6.3-4 and ZFS 2.0 ignores zfs_arc_max

    Hi, just add min size < max size, example: # cat /etc/modprobe.d/zfs.conf options zfs zfs_arc_min=68719476735 # This is 64GB - 1B options zfs zfs_arc_max=68719476736 # This is 64GB