On Tue, Oct 17, 2023 at 09:21:16AM -0600, Alex Williamson wrote: > Do we therefore need some programatic means for the kernel driver to > expose the node configuration to userspace? What interfaces would > libvirt like to see here? Is there an opportunity that this could > begin to define flavors or profiles for variant devices like we have > types for mdev devices where the node configuration would be > encompassed in a device profile? I don't think we should shift this mess into the kernel.. We have a wide range of things now that the orchestration must do in order to prepare that are fairly device specific. I understand in K8S configurations the preference is using operators (aka user space drivers) to trigger these things. Supplying a few extra qemu command line options seems minor compared to all the profile and provisioning work that has to happen for other device types. Jason
