Caveat: I'm new to these parts, investigating a switch from Proxmox to Scale (from Unraid, then a stock Debian build for awhile).
I want to isolate my GPU for use with VMs, but when I do I the UI tells me "At least 1 GPU is required by the host for it's functions. With your selection, no GPU is available for the host to consume."
However removing the GPU shows that the system is perfectly fine running headless.
I see how there's significant advantages to having a fallback output in case of network failure, but, a headless system wouldn't have this anyway.
I see how this might not be something TrueNAS has supported in the past as it's more of a VFIO setup than a traditional NAS setup.
But ... if I could do this, TrueNAS Scale really works for my converged system.
So 2 parts:
1) Is there a decent way to workaround this without breaking the concept of not trying to do much to the host OS? If no, I'm likely locked out of Scale for my uses and that would make me sad as I really like the rest of what I'm seeing.
2) Feature request for a future release: support this in the UI.
Brainstorming a bit further purely for the feature request:
In an ideal environment we might have an option to set a timeout on the boot menu that, if not interrupted, will boot with GPU on the host so that we can recover (systems with IPMI or other OOB management wouldn't need this, so it would be nice to have a config setup for the boot menu to switch the default behavior). Also in an ideal environment we'd be able to attach/detach the GPU from the host on demand (for instance, to have some part-time services via containers that use the GPU that can be turned off to then attach to a VM).
But even without those 2 ideal options, since the server runs fine headless, we should have the option to force headless mode even when there is a GPU present.
I want to isolate my GPU for use with VMs, but when I do I the UI tells me "At least 1 GPU is required by the host for it's functions. With your selection, no GPU is available for the host to consume."
However removing the GPU shows that the system is perfectly fine running headless.
I see how there's significant advantages to having a fallback output in case of network failure, but, a headless system wouldn't have this anyway.
I see how this might not be something TrueNAS has supported in the past as it's more of a VFIO setup than a traditional NAS setup.
But ... if I could do this, TrueNAS Scale really works for my converged system.
So 2 parts:
1) Is there a decent way to workaround this without breaking the concept of not trying to do much to the host OS? If no, I'm likely locked out of Scale for my uses and that would make me sad as I really like the rest of what I'm seeing.
2) Feature request for a future release: support this in the UI.
Brainstorming a bit further purely for the feature request:
In an ideal environment we might have an option to set a timeout on the boot menu that, if not interrupted, will boot with GPU on the host so that we can recover (systems with IPMI or other OOB management wouldn't need this, so it would be nice to have a config setup for the boot menu to switch the default behavior). Also in an ideal environment we'd be able to attach/detach the GPU from the host on demand (for instance, to have some part-time services via containers that use the GPU that can be turned off to then attach to a VM).
But even without those 2 ideal options, since the server runs fine headless, we should have the option to force headless mode even when there is a GPU present.