Search results

The last macOS to support nVidia was High Sierra released in 2017.

Any potential fixes in testing?

I can confirm that nesting fixes the problem on a test container, but I am reluctant to run nested and privileged on anything but a test environment.

root@maverick:~# cat /etc/pve/lxc/101.conf arch: amd64 cores: 2 cpuunits: 99 hostname: radarr memory: 1024 mp1: /plex/plex,mp=/media/Plex,acl=1,backup=0,replicate=0,shared=0 mp2: /plex/plex/Music,mp=/media/Plex/Music,acl=1,backup=0,replicate=0,shared=0 nameserver: 192.168.2.1 net0...

I still can’t boot an LXC container after upgrade to 24.04 from 23.10. They hang at the console and never come all the way up. No errors in log. Proxmox is fully up to date.

It looks like kernel headers aren’t installed.

It officially releases today, but I can’t be the only user who would have preferred to test the beta before full deployment. It’s surprising that LXC support isn’t implemented prior to an LTS official release.

LXC support is still missing for Ubuntu 24.04. When will this be added? (ie inclusion in /usr/share/perl5/PVE/LXC/Setup/Ubuntu.pm)

It was merged into master. It hasn't been cut into any release and won't but until the next major point release. RAIDZ Expansion isn't available yet in any stable ZFS release build.

For write endurance, 99th percentile latency, overall latency, and 4K random write performance.

Yes, and I would suggest optane or nothing. Ceph latency is always going to be slow since a write is acknowledged until the last write is committed, which over a network is several latent hops. With the RBD persistent cache the write is considered committed as soon as it hits the local, on node...

Have you tested RBD persistent writeback caching?

I had similar issues. Eventually it boots past the EFI stub, but then scrolls endless mptsas3 errors, presumably related to the LSI SAS HBA. Rock solid on ZFS 2.1.13 and kernel 6.2. I rolled everything back and was fine.

The commit hasn’t been merged. You would need to pull and build your own version to test.

Two problems. (1) You are basing your capacity on manufacture quoted capacity which is in TB but the OS is representing the space in TiB. (2) You aren’t calculating in other ZFS overhead. You should only have about 10.2 TiB of usable capacity.

You don’t have to recreate the OSD to move the WAL/DB. No need to rebalance.

All datasets and zvol are set to “all”.

Running ZFS on Proxmox 8. Everything is updated to newest packages. The ARC limit is 768 GB and arc_summary reports 99% hit ratio. However, actual total ARC access is only 350mb after 24 hours uptime on a loaded system. Any reason for such low utilization of ARC?

Seeing same behavior on 6.2.16-3. Jul 02 14:34:07 maverick kernel: ------------[ cut here ]------------ Jul 02 14:34:07 maverick kernel: WARNING: CPU: 21 PID: 26736 at arch/x86/kvm/mmu/mmu.c:6949 kvm_nx_huge_page_recovery_worker+0x3c4/0x410 [kvm] Jul 02 14:34:07 maverick kernel: Modules linked...

DAX is just for Optane DCPMM and NVDIMMs. The SSD mode works great with a few caveats.