Recent content by BJ Quinn

Hi, I added a mountpoint for my lxc container from the command line: pct set 141 -mp0 /path/on/host,mp=/path/on/guest This obviously works if I reboot the container. But is there any way to mount this w/o a container restart?

Thanks for the advice, I may try that as well. Do you have any idea what the best way is to judge how much more RAM can be allocated to VMs? If I can't look at used or buff/cache, what do I look at? Do I just add up allocated RAM and leave some nominal amount (say, 8GB) for the host? There's...

Thanks for the suggestion, I may end up handling it that way. Is this actually best practice for Proxmox? I certainly know how to set a fixed ARC size, but it would surprise me that that's what Proxmox expects us to do if we want to allocate >50% RAM to VMs/containers.

Does anyone have a suggestion especially on the question about what the proper metric is in order to know whether it's safe to allocate additional memory to VMs/containers? I'll figure out what went wrong with my container, but at least I need to know when to stop allocating additional RAM to...

Thank you, that is helpful. I incorrectly expected zfs cache to show up in buff/cache. What's the proper metric to use in order to know whether it's safe to allocate additional memory to VMs/containers? Is avail the right one? That seems odd, though, as it implies that I can't reclaim some...

On the 2nd (128GB) machine, here's the RAM allocation: Containers: 4GB, 4GB, 4GB, 4GB, 4GB = 20GB VMs: 3GB, 4GB, 16GB, 2GB, 8GB, 4GB, 8GB = 45GB Used RAM: 0.2GB, 2GB, 0.1GB, 0.7GB, 0.1GB, 2.5GB, 3.5GB. 4.5GB, 1.5GB, 4.5GB, 1.5GB, 3.5GB = 24.6GB This machine is the one that really confuses me...

Here's the same info from another machine, 128GB RAM, this one is actively OOM killing VMs. Tasks: 945 total, 2 running, 943 sleeping, 0 stopped, 0 zombie %Cpu(s): 14.8 us, 2.0 sy, 0.0 ni, 82.8 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st MiB Mem : 128542.3 total, 22820.0 free, 103553.7...

ZFS Subsystem Report Tue Nov 02 09:57:28 2021 Linux 5.4.34-1-pve 0.8.3-pve1 Machine: pve8 (x86_64) 0.8.3-pve1 ARC status: HEALTHY...

Container RAM config: 8GB, 1GB, 9GB, 8GB, 0.5GB, 2GB, 1GB, 8GB, 4GB, 8GB = 49.5GB Windows VM (with balloon driver) RAM config: 3GB, 4GB = 7GB So if you add up total allocated RAM, it makes sense. But I thought that it would only count RAM actually used by the VMs/containers. Container/VM RAM...

Here's one 64GB machine. top - 09:43:59 up 258 days, 18:34, 9 users, load average: 2.08, 2.96, 3.46 Tasks: 1722 total, 1 running, 1721 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.3 us, 0.8 sy, 0.0 ni, 97.8 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 64312.6 total, 7878.7 free...

I'm having an issue with a few Proxmox 6.x hosts where the total *used* RAM as shown in top and free are roughly double or more the amount of RAM used by the VMs themselves. There's a mixture of LXC and KVM, and in some cases I believe the Windows VMs do not have the balloon driver installed...

Ok sounds good, I'll try that. Thanks!

This is just part of my routine list of sysbench benchmarks, I didn't even notice the --memory-access-mode=rnd switch until I started trying to dig into what the issue was. I don't specifically know that my workload will require whatever the problem is here. I'm planning various workloads for...

I'm getting wildly different results on the host vs in an lxc container (Centos 8) when running a specific sysbench memory test (--memory-access-mode=rnd). I don't seem to be seeing this with other sysbench tests (CPU / IO / mutex) or even other memory tests (i.e. sequential). Any ideas? This...

This thread is a little old, but I could not find anything on the forums to fix this issue. There seems to be a couple of solutions based on this first option (see https://www.rpiathome.com/2020/10/21/proxmox-6-2-1-installation-fails-after-dhcp-lease-obtained/). Start from the prompt it dumps...