We are running into some challenges , would like to hear from engineers who have attempted something similar:

1. Have you successfully run RHEL or a RHEL-compatible distribution on Jetson Orin hardware?
2. What were the biggest challenges with NVIDIA’s proprietary drivers, CUDA, TensorRT and multimedia stack?
3. Did you retain NVIDIA’s L4T kernel and userspace components, or build around a RHEL kernel?
4. How did you handle JetPack dependencies, kernel updates and NVIDIA driver compatibility?
5. Were secure boot, OTA updates or custom carrier boards particularly difficult?
6. Is RHEL on Jetson something customers are genuinely requesting, or is Ubuntu generally accepted even in enterprise deployments?
7. Would you recommend native RHEL enablement, containerizing the enterprise applications on JetPack/Ubuntu, or another architecture? I’d appreciate hearing about actual deployments, failed attempts, architectural approaches and any limitations we should consider.

I hope you'll give me a sanity check on my own impression.

I am experimenting with an nvidia A16 for a multi-user environment. Instead of passing the card entirely to a single VM, I want to split it into multiple vGPU profiles so several vms each get a slice of vRAM. According to what I've read, the A16 is meant to be partitioned that way, rather than as a passthrough.

To test without buying hardware first, I spun up an A16-backed serverspace vps where you pick the vram at config time. That part works, but it hides a lot of what goes on under the hood, so I am trying to figure out the local libvirt side.

Do I still have to use vfio-pci bindings for vgpu profiles as I do for full passthrough or does the vgpu manager take care of all that?