Search results

  1. J

    FreeBSD Guest - wrong ram usage

    "Did you install something additional or not?" no, i'm not...
  2. J

    FreeBSD Guest - wrong ram usage

    pfsense 2.6 / FreeBSD 12.2: # info balloon balloon: actual=3072 max_mem=3072 # qom-get /machine/peripheral/balloon0 guest-stats { "stats": { "stat-htlb-pgalloc": 18446744073709551615, "stat-swap-out": 18446744073709551615, "stat-available-memory"...
  3. J

    latest update (2/8/21) broke docker in container?

    Hi George, on PVE Host: run: sysctl -w net.ipv4.ip_forward=1 for permanent change, uncomment the "net.ipv4.ip_forward=1" line in /etc/sysctl.conf Julio
  4. J

    Wrong memory usage on KVM VM

    My opinion, Proxmox "pressure/inflate/deflate on mem. balloon" algorithm is not "aggressiv" enough for FreeBSD. Maybe new Option (FreeBSD) in OS Type, and more "aggressive" algorithm for mem. balloon handling? pfsense 2.5.0-DEVELOPMENT (FreeBSD 12.2-STABLE): Proxmox Monitor (in my case, for...
  5. J

    Disks can not sleep

    i've tested and works for me. Test setup: Host: 4 Disk - ZFS RaidZ-2 /etc/lvm/lvm.conf: global_filter = [ "r|/dev/zd.*|", "r|/dev/mapper/pve-.*|", "r|/dev/mapper/.*-(vm|base)--[0-9]+--disk--[0-9]+|", "r|/dev/sda|", "r|/dev/sdb|", "r|/dev/sdc|", "r|/dev/sdd|", "r|/dev/sde|" ] /etc/hdparm.conf...
  6. J

    Disks can not sleep

    please edit "lvm.conf" at the host!
  7. J

    Disks can not sleep

    try with this: https://forum.proxmox.com/threads/upgrade-from-5-x-to-6-x-harddrives-dont-sleep-no-more.69672/post-312634
  8. J

    [SOLVED] LXC won't start

    please restart your server, the newest kernel is not yet running...
  9. J

    [SOLVED] LXC won't start

    please post your pve version again (pveversion -v)
  10. J

    [SOLVED] LXC won't start

    "When I run apt update and apt upgrade and apt dist-upgrade, there are no new packages available." your system is not up to date, proxmox-ve: 6.1-2 vs. proxmox-ve: 6.2-2 (11.23.2020) please check your Package Repositorys, for example Proxmox VE No-Subscription Repository...
  11. J

    PVE update: Backups failed on LXCs with bind mount points

    Temporary solution: https://forum.proxmox.com/threads/bug-container-with-bind-mount-backup-error-unable-to-parse-volume-id.79334/post-351351
  12. J

    [SOLVED] Container with bind mount backup error (unable to parse volume ID)

    bug in "pve-container_3.2-3", after downgraded to "pve-container_3.2-2", backup working again!
  13. J

    [SOLVED] Container with bind mount backup error (unable to parse volume ID)

    Hi folks, i got following error (unable to parse volume ID) after pve update: Task Log: INFO: starting new backup job: vzdump 100 --remove 0 --storage backups --compress zstd --node pve --mode snapshot INFO: filesystem type on dumpdir is 'zfs' -using /var/tmp/vzdumptmp11973_100 for temporary...
  14. J

    New Mobile App for Proxmox VE!

    you said: "I see will be fixed in the next release thanks for sharing" and i'm just tested! ;)
  15. J

    New Mobile App for Proxmox VE!

    configs are already there: https://forum.proxmox.com/threads/new-mobile-app-for-proxmox-ve.76327/post-340604
  16. J

    New Mobile App for Proxmox VE!

    same error in version 1.0.2...
  17. J

    New Mobile App for Proxmox VE!

    see on attached screenshots...
  18. J

    New Mobile App for Proxmox VE!

    yes, installed from google play, version 1.0.1