Recent content by PigLover

I think that direct support of Docker (the subject of that older referenced discussion) and the support of Docker-like features using OCI Containers are two totally different subjects - clearly related, but also clearly seperate topics. There are solid reasons for Proxmox not to support Docker...

As I've played with this more I am even more excited about the possibilities for this. At the same time, more convinced this current capability is just a pre-requisite to the desired solution rather than the solution itself (thus, I am sure, why the Proxmox team is only listing this as a tech...

I think having a buffer of stdout is a great idea - especially if the user can specify the buffer size and there is a way to allow it to be read/processed by other containers or VMs for log review. However - you still need some form of console access (similar to "docker exec") for...

Having the ability to import OCI images and run them in an LXC is fabulous! Thank you Proxmox team. This is a useful and necessary first step to a container runtime environment that may one day reduce the desire to run Docker/Podman VMs (or, though not advised, LXCs). Unfortunately, this...

Would this update address/fix the issues with intel iGPU passthrough?

Simple to do offline using pve backups: - create a dataset on a NAS (or on one of your PVE clusters) and export it using nfs - create a new PVE storage pool on each PVE cluster that both mount this nfs filesystem. Set this pve storage for dumps. - do a backup of the vm you want to migrate using...

Install the microcode update after installing Proxmox. The instructions are linked in my initial reply above.

Make sure you install the Intel Microcode updates. Instructions about halfway down the page here. These instructions are for PVE 7.x but they apply the same way to 8.x. This is important because (a) the more recent microcode improves stability of VMs on Intel Big/Little architecture CPUs used...

Yes (sorta). Pinned kernel 6.5. More seriously - I get the impression that this will not be fixed in the 6.8+ kernel stream anytime soon. Something got badly broken and looking at other message streams/email lists it appears that this is going to take a while.

Upgraded to kernel 6.8.8-1 and the memory leak appears to be fixed.

iGPU passthrough using PCIe passthrough for an Intel UHD 630 (i9-10900) works perfectly on Proxmox <= 8.0 and Kernel 6.5.x. But after upgrading to Proxmox 8.2 and kernel 6.8.x the whole system just hangs. Can't even get good logs to post. Reverting to the kernel 6.5 boot environment...

Your Zigbee/Zwave radio device (USB Stick or whatever) is always going to be a single point of failure for you. So even if you get the z2m application somehow "portable" for HA you are still down if you lose the z-device itself. You won't ever achieve HA using the existing Z protocols as they...

Give it a try with "intel_idle.max_cstate=1 processor.max_cstate=5". This setting seems to have given my AMD based system stability while maintaining reasonable power usage. Based on the open Linux bugs it appears the cstate >=6 is where troubles start.

Have you tried disabling C-state 6 (and lower)? There seems to be a running issue with random restarts using AMD systems and Linux 5+ kernel. All of them open and describe similar symptoms. Disabling C-state 6 is suggested in few of them as stabilizing their systems...

I think I've gotten my system stable but I am really not happy with the side effects of the workaround. Its been running stable for a few days but I'd really like to get at least 30 days running before declaring victory (a pyrrhic victory, perhaps). For background, so people don't have to...