Search results

B Been down that road. Got docker-swarm working in LXC-priv containers. Preferred it to KVM, but you can't snapshot them to back them up (long story) so moving away from that as well. 99.9% of what is running in my lab & home clusters are LXC containers. (even moved plex/jellyfin into...

Great answer. I assume that matters for things like snapshots and backups?

Just keep in mind if you care about iGPU passthrough (like intel) - nomodeset breaks Intel GVT-G The *right* answer is for proxmox to allow you to pick a console resolution at the start of the install, then write that during the install, then boot afterwards using that resolution. As screen...

If you're to do both link aggregation and vlan tags, I've found it *far* easy to use Open-vSwitch. apt update apt install openvswitch-switch openvswitch-common Here's an example showing two ethernet interfaces, bundled into an 802.3ad/LACP bundle, with tagged VLAN's, including proxmox...

doing that already. KVM has: more disk space overhead more cpu overhead more ram overhead doesn't directly offer peripheral reuse (shared gpus) especially on smaller boxes (4-8 cores) running a thin LXC is much preferred to a fat KVM. That being said, that's how I'm running Frigate right now...

As a follow up -- did just that, running ceph on top of bcache for the last 12 months, zero issues. The access times are great (thank you NVME) and the rebuild times are much faster.

Wondering if anyone has a script/directions/etc to convert docker images into Proxmox Compatible LXC containers? Several projects I use are only available as docker containers, and I'd rather run it in an LXC than run docker JUST for them. I've found a few resources online that deal with...

I feel your pain, been there. If you haven't already, pin a kernel to 6.2 version -- lots of issues with coral/apex under 6.5 kernels. Do that and you don't have to build your own version, the "off the net" directions work fine. root@pmx:~# proxmox-boot-tool kernel list Manually selected...

(from random internet searches) pci=nommconf to /etc/default/grub - then update-grub - then reboot, stops the errors, but breaks IOMMU remapping. does NOT FIX the problem. however THIS: pcie_aspm=off DOES appear to solve the problem.

Actually you can. Healthy amount of cores, ram, and diskIO on the current generation PI/ARM/etc boxes.

Since pve v5, I've struggled with getting a usable video resolution on the proxmox console. Especially with servers that have VGA output, proxmox tends to default to the highest possibly supported resolution, often leaving the KVM or rack-mounted-VGA out of range. Up to this point, I've been...

FWIW, same on NUC7's with USB3 ethernet plugged into USB/Thunderbolt port. Mar 03 23:48:56 pve11 kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:03:00.0 Mar 03 23:48:56 pve11 kernel: pcieport 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver...

Absolutely agree. Resharing in case the original goes away. #TL;DR How do you mount NFS shares inside an LXC container? Create a privileged LXC container, using any guest distribution of your choosing Once created, modify the config file (/etc/pve/lxc/<id>.conf on Proxmox) and add features...

same issue. Can't snapshot LXC containers with FUSE enabled. -- there has to be a better way --

Snapshots on LXC-over-NFS would be really sweet. Backups w/o VM shutdown/restart would be the primary win.

Yep - otherwise it would be my first choice. An NVMe pool with an HDD pool behind it is the best of both worlds. Cache Tiering, in CEPH, is for specific workloads, and if the first tier isn't big enough, not tuned right, etc, it can be worse than no tiers at all. I've experimented with it...

Ahh - something just occurred to me. Two problems here really: 1. Old device are still present - some sort of cleanup will solve that. 2. NEW devices are missing :lightbulb: -- my lab pool is running CEPH on bcache - so I'm guessing CEPH can't reach down to the actual drive serial numbers if...

Thank you, much appreciated. I couldn't find anything obvious wrong - I suspect something got toggled over time when upgrading from 15 to 16 to 17, and just never got turned back on.

ok then..... Not a lot to see there - each device is correctly in the list (at the top) and each node has the right drives.

yes to both "ceph osd free" and "pve webui" crushmap is also correct - pmx1 for example. host pmx1 { id -3 # do not change unnecessarily id -13 class ssd # do not change unnecessarily id -2 class hdd # do not change unnecessarily # weight 37.84184 alg...