Search results

  1. M

    Install Proxmox VE / ZFS on a LUKS encrypted volume

    I'm using a derived key for all dependent disks, therefore i have to enter only once: http://gw.tnode.com/debian/issues-and-workarounds-for-debian-8/
  2. M

    Install Proxmox VE / ZFS on a LUKS encrypted volume

    Would be nice, but unfortunately no one is doing this right now, due to the nature of complexity. We do use very small SSDs for Proxmox OS only and then store all other data on separate Luks+ZFS SSDs. So this is easy to maintain and allows us to use default Installer. And VMs and Data are...
  3. M

    Proxmox VE 5.0 beta1 released!

    You might also try https://github.com/morph027/pve-iso-2-pxe
  4. M

    71 GB/128 GB RAM used

    Then there must be something different allocating the memory...other VMs? Can you post a screenshot of htop? I guess the memory allocation is not from caches...
  5. M

    71 GB/128 GB RAM used

    http://www.linuxatemyram.com/ :D It definitely will not reboot when someone demands memory from FS cache. Even then there's an application eating all the memory the OOM killler will take care of it, also causing no reboot.
  6. M

    71 GB/128 GB RAM used

    Jip, just take a serious amount of memory. But normally there's no need to touch it...i mean, that's what memory is for..caching things. And ZFS is freeing up memory when someone else needs it...
  7. M

    zfs send receive resume compressed

    Stil not merged in ZoL : https://github.com/zfsonlinux/zfs/issues/4840
  8. M

    Modprobe NFS

    Mind the 401 error...You'll need to get an enterprise subscription or enable the non-subscription repo: https://pve.proxmox.com/wiki/Package_Repositories
  9. M

    Modprobe NFS

    Already rebooted?
  10. M

    ZFS over iSCSI

    I need to try gea's version. Also there's http://www.zeta.systems/zetavault/high-availability/ which sound promising.
  11. M

    ZFS over iSCSI

    His HA stack is quite interesting: http://napp-it.org/doc/downloads/z-raid.pdf Ceph does not scale really well in small setups :(
  12. M

    Creating VMs automatically - ansible, vagrant, API .. ?

    https://github.com/ansible/ansible/issues/21056 is resolved now, i've updated the snippet.
  13. M

    Problems installing Proxmox 4.4 on Xeon e3-1245 v5 with c236 chipset

    Its the GPU. You should be able to blacklist it. https://forum.proxmox.com/threads/intel-skylake-igpu-i915-breaks-proxmox-4-1.25892
  14. M

    ZFS trim and over-provisioning support

    But it's being worked on ;) https://github.com/zfsonlinux/zfs/pull/3656
  15. M

    Proxmox installation via PXE: solution

    Jip...when it's not working, it should throw some errors...probably do a zpool import first and chroot into the pool https://github.com/zfsonlinux/zfs/wiki/Ubuntu-16.04-Root-on-ZFS#rescuing-using-a-live-cd
  16. M

    Full flash PVE

    Same here...Enterprise SSDs only and all fine.
  17. M

    Proxmox installation via PXE: solution

    You can try to boot with debug mode enabled and then try to install grub manually from the rescue shell.
  18. M

    Creating VMs automatically - ansible, vagrant, API .. ?

    # Ansible version of https://morph027.gitlab.io/post/pve-kickseed/ # Example args file: https://gitlab.com/snippets/1548095 --- - hosts: localhost gather_facts: false vars_prompt: - name: "vmname" prompt: "VM name?: " private: no - name: "args_template" prompt: "args...