Search results

  1. B

    Limit Proxmox VE update versions (testing purposes), best way?

    Thanks for the insights folks! Also, if we could get the ISO repo to re-upload an PVE v8.1.x ISO that would be stellar (and if that is possible/has happened, please tag me so I can check again, thanks!).
  2. B

    Limit Proxmox VE update versions (testing purposes), best way?

    I've never heard of disabling an apt repo forcing the packages to be removed. Can you prove that? I think I probably should just test this on my end to find out :/ well thanks anyways
  3. B

    Limit Proxmox VE update versions (testing purposes), best way?

    It's not. This is the kind of thing I need to rebuild to test things. So that often includes reinstalling Ceph as part of rebuild. ... pretty sure disabling Apt repos doesn't automatically remove packages, not sure what you mean there.
  4. B

    Limit Proxmox VE update versions (testing purposes), best way?

    Sure, but do you know if that would interfere with Ceph package installation stuff?
  5. B

    Limit Proxmox VE update versions (testing purposes), best way?

    Hey so I'm building out some PoC stuff in my lab and I want to prevent my nodes from updating to v8.3.x as the testing I'm doing involves specific Ceph version aspects. I'm not entirely sure the "recommended" way to do this as searching did not turn up reliable info on the matter. Upgrading to...
  6. B

    Memory usage accuracy has never been accurate and I still cannot find why after many years

    Well I'm rocking the default cache setting of no cache. I'm not a fan of losing data in-flight ;)
  7. B

    Memory usage accuracy has never been accurate and I still cannot find why after many years

    In my case I don't have storage on any of the PVE Nodes, it's over NFS on a dedicated NAS.
  8. B

    Memory usage accuracy has never been accurate and I still cannot find why after many years

    The performance problems I saw with Ballooning is so substantial that I'm never going to re-enable that, but certainly worth raising as a relevant aspect.
  9. B

    Memory usage accuracy has never been accurate and I still cannot find why after many years

    The example VMs are fresh VMs, there should not be such a huge discrepancy. 500MB used vs 6.5GB used... Yes, I know this has been discussed to death, clearly the problem persists, and as such it defeats the whole point of even having this metric presented. And I was already accounting for disk...
  10. B

    Memory usage accuracy has never been accurate and I still cannot find why after many years

    I've intentionally turned Ballooning off for all RAM for all VMs because it has caused significant performance issues. But this problem also persisted when Ballooning was on for some of them.
  11. B

    Memory usage accuracy has never been accurate and I still cannot find why after many years

    I'm rocking PVE v8.2.7 in my cluster, and I've upgraded it in-place since v2.3, and in all this time (over a decade?) I have almost never found the "Memory usage" metric at the webGUI scope of VMs to be accurate. I namely run Linux VMs, but even for Windows, FreeBSD, whatever, it's _never_...
  12. B

    Question for PVE Staff/Devs - Enabling cephadm, what are the known (with evidence) problems?

    As I said, I'm trying to get insights from the Devs here, and not opinions but facts with evidence. I don't really see how that was unclear.
  13. B

    Question for PVE Staff/Devs - Enabling cephadm, what are the known (with evidence) problems?

    Hey Folks, Hoping to get some response from the Proxmox Staff/Devs on this. Namely looking for evidence of known problems in a particular scenario. I'm currently building out a PoC for 3x PVE cluster, whereby it also provisions a Ceph cluster, and I extend that Ceph Cluster to provide NFS HA...
  14. B

    zram - why bother?

    I want to clarify a bit on what I mean by "Swap, in my professional experience and opinion, should only ever be used as last resort.". Swap should (almost) _NEVER_ be turned off, except maybe special circumstances like on kubernetes nodes where it is part of the recommended architecting (by the...
  15. B

    zram - why bother?

    I've been working with Linux for 20+ years and using swap for more than emergency situations has tangible performance and wear-level costs. I am in the real world, just like you, and it is my responsibility to deal with aspects like this of architecture. Consider for a moment what forum we're...
  16. B

    zram - why bother?

    Sure, and none of that warrants ZRAM IMO. Also, you don't need swap to enable rapid RAM loading/unloading, that would actually substantially slow it down as the swap device itself would be a huge bottleneck relative to the performance of said RAM. It would be substantially more sensible to just...
  17. B

    Node elevated CLI using Proxmox VE Authentication Server, can't see how

    Well the LDAP aspect is more asking ahead on the topic, not something for immediately today. That being said, I really was hoping that the PVE Cluster environment would manage PAM on behalf of the admins for extending PAM to work with Proxmox VE Authentication Server by default. And if others...
  18. B

    Node elevated CLI using Proxmox VE Authentication Server, can't see how

    I'm trying to figure out how to use accounts managed by the Proxmox VE Authentication Server in such a way that I can get CLI access (elevated/sudo/whatever) to the nodes in the cluster. Whether it's all nodes, limited notes, or whatever. I can't find anyone talking about this so far, and the...
  19. B

    Default settings of containers and virtual machines

    Ahh nice! I can see the appeal of APIs, but there's use-cases I have where the webGUI is the method used, hence interest in this. :)