Search results

  1. M

    Cannot allocate memory

    I'm afraid it will break.
  2. M

    Cannot allocate memory

    I did a lot of Google searches before posting on the forum. ~# pveversion -v proxmox-ve: 5.1-27 (running kernel: 4.13.8-1-pve) pve-manager: 5.1-36 (running version: 5.1-36/131401db) pve-kernel-4.13.8-1-pve: 4.13.8-27 pve-kernel-4.10.17-1-pve: 4.10.17-18 libpve-http-server-perl: 2.0-6 lvm2...
  3. M

    Cannot allocate memory

    I had balloning enabled on all the virtual machines. TOP by memory: top - 10:34:35 up 1121 days, 22:40, 2 users, load average: 2.77, 2.83, 2.94 Tasks: 216 total, 1 running, 215 sleeping, 0 stopped, 0 zombie %Cpu(s): 7.3 us, 3.5 sy, 0.0 ni, 89.0 id, 0.1 wa, 0.0 hi, 0.1 si, 0.0 st...
  4. M

    Cannot allocate memory

    This is the problem, the HTOP is only showing me a 63% usage between the 3 virtual machines, but in the total it indicates me a 90%. :~# free -h total used free shared buff/cache available Mem: 30G 27G 2.7G 246M 417M...
  5. M

    Cannot allocate memory

    This? zpool status The ZFS modules are not loaded. Try running '/sbin/modprobe zfs' as root to load them.
  6. M

    Cannot allocate memory

    How I can check this?
  7. M

    Cannot allocate memory

    Hello, I have a 32GB RAM machine with a proxmox and 3 virtual machines installed, one uses 8GB, another 6GB and the last one 6GB, from time to time when one of these machines is turned off (due to some failure) and doesn't allow me to start it again, I get this error: "kvm: cannot set up guest...
Top Bottom
Back