Search results

Power efficient performance is a big thing nowadays, ARM chips beat x86 in this race. There have been multiple discussions in these forums asking for ARM/AARCH64 support officially. Any recent word on this from Proxmox leadership? For context; a major windows laptop on ARM will soon be...

I'm seeing some kernel crashes with igc (intel nic driver) on the current kernel. How often is a new kernel version released? If this kernel is based off ubuntu; where can I check what version ubuntu is on? my latest crash https://pastebin.com/X1X3gbwf

anyone find a solution other than editing every single container and restarting it with that option? It feels like there must be something on the OS wide level that could be changed to avoid this hassle.

thank you! TL;DR add to 101.conf of the lxc container. I hope this feature makes it to web GUI soon.

Hi, I found the "CPU affinity" (cpu pinning) setting for VMs inside hardware panel in proxmox but I am unable to find this setting for LXC containers. How can I pin a specific LXC container to specific CPU cores in PVE 7.3.3?

Were you able to fix this? I'm seeing these "Memory cgroup out of memory" for Plex LXC container.

I am wondering if you ever figured this out? As I am seeing something similar as I implement NFS on my network.

Just to make sure I understand, there is a different RPC made by pvestatd that is waiting for response that is timing out after 10 seconds causing the `pvestatd` message in syslog? OK my script returned an instance timestamp for me to try to correlate. Run 234 + Thu 24 Nov 2022 03:33:03 AM...

thank you for help confirming :) I'll try CPU affinity settings to "12,13,14,15" and watch htop on proxmox to see if only those cores are maxed out and keep an eye on power consumption too

thanks for the pointer. I exclusively use NFS version 4.2 - taking a hint from the script you shared I wrote an endless loop script. #!/bin/bash # Basic script to run on an endless loop on a NFS client # idea is to catch failure in rpcinfo and log timestamp. counter=1 while : do echo "Run...

I'm trying to debug a condition where it seems that using NFS v4.2 there is a brief period of connection timeout between proxmox and my NFS server. Looks like `pvestatd` monitors storage mounts and prints some useful messages - can these be made more verbose? Nov 23 15:43:16 centrix...

Not to thread hijack but related question. "CPU Affinity" under Processors setting of the VM does not seem to allow me to explicitly select which CPU cores I want mapped to a VM... Can you add this feature please? Rationale: Intel's latest Raptor Lake/Alder Lake processors have "performance"...

oh wow, this is it! thank you so much. 02:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation E16 PCIe4 NVMe Controller [1987:5016] (rev 01) Subsystem: Phison Electronics Corporation E16 PCIe4 NVMe Controller [1987:5016] Kernel driver in use: nvme Kernel...

I'm trying to permanently passthrough a Samsung 980 NVME m.2 disk to VMs. The problem is that my host node continues to load this device with 'nvme' driver instead of vfio for passthrough. I have followed all of the documentation and recommended steps; yet I can't seem to unbind this specific...

This is perfect timing. I had a new Intel N6000 processor that wasn't working on kernel 5.15 - I was using https://github.com/fabianishere/pve-edge-kernel to fill in the gap to get proper hardware working.

This fixed my issue on my Intel Alder Lake proxmox host. Thanks!

I was following the WIKI (https://pve.proxmox.com/wiki/Pci_passthrough) and it wasn't working. It wasn't until I found this comment that with 'multifunction' my AMD Ryzen 3700X finally had the IOMMU groups fixed. Thanks!

Edit: this system crash was due to IOMMU isolation being broken on my AMD cpu requiring ` pcie_acs_override=downstream,multifunction` to fix it. The system was hanging due to shared group with a core controller for the PCI bus on the board for a pass thru device.

Ok it looks like my web browser had an old javascript cache because that option wasn't there until I cleared cache and re-loaded. Reconfigured everything now with the API option and it seems to be working! Thanks for the protip.

I am using TrueNAS Scale and installed the https://github.com/TheGrandWazoo/freenas-proxmox on my PVE 7.2.7 install and while "it seems" to work you can't delete disks created via the workflow: I don't know if there's a fix but certainly not truly working out of the box, at least not for...