Remove igfx_off from boot args for iGPU passthrough?

English Container & Virtualization
,
1

How can I remove igfx_off from the boot arguments? That flag tells the Intel IOMMU driver to disable IOMMU for the integrated GPU. I want to passthrough the iGPU to a Windows container (dockur/windows). I don’t mind detaching the iGPU from QTS since I don’t use any media apps, video transcoding, or HD/Ubuntu Station. The iGPU is basically unused most of the time.

Boot args:
[~] # cat /proc/cmdline consoleblank=0 console=ttyS0,115200n8 intel_iommu=on,igfx_off i915.enable_hd_vgaarb=1 iommu=pt i915.disable_power_well=0 i915.enable_rc6=0 i915.enable_guc=2 memmap=2M$0x8000000 ramoops.mem_address=0x8000000 ramoops.mem_size=0x200000 ramoops.console_size=0x100000 usbcore.autosuspend=-1 zswap.enabled=1 zswap.compressor=lz4 BOOT_IMAGE=/boot/bzImage root=/dev/ram0 rw

Specs:
Model: TS-364-8G
OS: QTS 5.2.6 (20250715) x86_64
Kernel: 5.10.60-qnap
CPU: Intel Celeron N5105 (4) @ 2.900GHz
GPU: Intel JasperLake (UHD Graphics) @ 0.80 GHz
Memory: 16GB

2

Hi, we’ve discussed the modification you mentioned with our internal team. This isn’t officially supported, and we can’t be sure what the consequences might be.

However, if you’re willing to take on the risk, we’re happy to help you with the experiment. If you agree, please open a support ticket.
Thanks!

3

Ok, I will reconsider

4

If you exclusively give the full IGPU to a container or host, you would not be able to access the video output anymore for QTS, so unless QNAP puts the reversal of this modification in their button reset routine, you would be SOL if you need to troubleshoot QTS issues directly via HDMI after this modification.

5

Can you please share more details?

Whenever I try to contact support, I’m always redirected to the same regional agent, who is consistently unhelpful and unable to provide any assistance with the requests I’ve submitted.