Recent content by jasonsansone

Still does not include a ZFS 2.3 kernel module, is that correct?

I respectfully disagree. First, none of those changes need to be addressed in the GUI or in manuals to simply update the build to 2.3.0 or 2.3.1. There is no reason functionality can’t be added to the GUI, and documented, in later releases. Further they can just drop in code without testing...

It takes zero plumbing to update ZFS now. The relevant functionality can be utilized from the CLI (which is where you should be managing ZFS). Future upgrades of plumbing in the GUI shouldn’t delay introduction of the functionality.

Nothing in test, yet. I’ve been monitoring. Surprised there still isn’t even a test build.

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...