Recent content by mjw

  1. M

    Proxmox VE Node Driver for Rancher

    I didn't try it, but my research suggests that the modern tooling would be CAPI (Cluster API). Rancher supports CAPI with Rancher Turtles and on the Proxmox VE side, you need a Cluster API Provider.
  2. M

    Restrict pvemanager default_views per-user

    Feature Request: https://bugzilla.proxmox.com/show_bug.cgi?id=5667
  3. M

    How to Set default view for user or/and disable datacenter view

    Feature Request: https://bugzilla.proxmox.com/show_bug.cgi?id=5667
  4. M

    Grouping VM IDs (vmids) under storage pool IDs (in the Proxmox GUI)

    Feature Request: https://bugzilla.proxmox.com/show_bug.cgi?id=5667
  5. M

    (Unofficial) Proxmox VE VDI Client - Initial Release!

    My VDI use-case is providing applications (not full desktops) that run on a central server to multiple users.
  6. M

    (Unofficial) Proxmox VE VDI Client - Initial Release!

    With SPICE being deprecated by Red Hat it is a bad idea to depend on it in the long term - at least until somebody shows interest in maintaining it and developing it further. The GNU/Linux ecosystem (mainly the big DEs) seem to focus on the RDP-protocol for remote-desktop use cases. There is a...
  7. M

    [SOLVED] Hide nodes a user has no permission for

    There is a related issue: https://bugzilla.proxmox.com/show_bug.cgi?id=1222
  8. M

    [SOLVED] perl: warning: Setting locale failed.

    I'd argue that "en_US.UTF-8" should be installed and set as the default on a server-system.
  9. M

    noVNC not working behind HAproxy

    Others in the forum mentioned (e.g. here) that round-robin will break in some cases and you better use a reverse proxy. You can either install that externally (some people do so on OPNsense), on a HA VM inside of PVE or on multiple PVE-hosts (HAproxy, VIP, keepalived, sticky sessions) as...
  10. M

    Implementing PVLAN isolation for VMs using OVS

    There is an entry on ServerFault where ebtables and bridge are mentioned. Hope that helps. And there is a german thread about this topic.
  11. M

    Debian 9 / Proxmox 5 : memory bug ?

    Linux uses free memory as disk cache. Detailed explanation: http://www.linuxatemyram.com/
  12. M

    KVM fixed memory - ballooning?

    So fixed memory size means the memory is never available for the host or other VMs, even if ballooning is on and the VM doesn't use the memory itself? What are the reasons for using fixed size memory (as the default)?
  13. M

    Proxmox and HP RAID controller

    CentOS 7 has the same behaviour on HP Servers (with p410i). https://bugs.centos.org/view.php?id=13184
  14. M

    4.4 and memory usage

    I checked the tuned profiles that Red Hat distributes in their systems. The profiles "virtual-guest" and "virtual-host" both use vm.swappiness=10. According to this the PVE installer should use a lower default value than 60 (which is the Debian default).
  15. M

    Resource Pool Limits

    In the meantime the issue was created here.