Search results

Smooth sailing so far.

They still can’t execute an x86_64 instruction set, so what do you plan to run at scale on an ARM server?

Correct. vTPM won't utilize a physical TPM. The only purpose for a "real" TPM would be secure boot on the host, which I do not believe PVE (yet) supports.

Proxmox does not (to my knowledge) bundle and deploy cephadm.

Roughly the avg. I discounted major outlier values and adjusted to the most consistent results across the drive type. It has performed well using such a method. I have all types (NVMe, SSD, HDD).

I benchmark all of my drives multiple times and then set a consistent value for all of the same type across the cluster. The variance between each is easily explained by differences at the time of benchmarking (which occurs automatically when you upgraded or installed Ceph)

Here is the Ceph Manual. To set a custom mclock iops value, use the following command: ceph config set osd.N osd_mclock_max_capacity_iops_[hdd,ssd] <value> What type of drives are these?

When QEMU and LXC packages change, you have to either migrate or restart the VM / Container to have them running on the newest package.

Do vGPU drivers allow host access to the gpu, ie retain ability to use the GPU in LXC containers? I have gpu that are used in multiple LXC containers and it would be nice to also leverage vGPU in VM, but I’m not sure if the drivers permit both.

Intel Hardware Feedback Interface "HFI" was added in 5.18.

ETA on 17.2.3?

I needed to re-enable specific channels. "ceph telemetry enable channel all" cleared the flag, but "ceph telemetry on --license sharing-1-0" did not.

One (possibly) minor bug: The GUI throws a health warning that "Telemetry requires re-opt-in", even though I have opted in multiple times. This occurs on multiple nodes. A reboot doesn't clear the flag.

That doesn't change the underlying problem. The driver is from 2017 when the newest kernel available was 4.13. The driver has never been tested against Kernel 5 and simply may not work. I understand that support was dropped for Kepler, however you can use up to 470.129.06.

The current driver is 515.48.07. As the reply above mentions in referencing other threads, your driver build is far too old for your kernel version.

So far so good on a test cluster!

I am curious about your problems with macOS. Which versions and what are the issues?

I didn’t say there was. My storage is stable and I’m happy with that. Simply answering the question.

Quincy was released on April 19, 2022 and it is now June. Safe to say “months”.

Same. I installed the new build without issue.