Modprobe: fatal: module kvmgt not found, kvmgt has no module, kvmgt has no driver, gvt-g precautions, gvt-g precautions for starting win10 in UEFI mode

About starting kernel modules kvmgt Problems encountered

Only add kernel parameters intel_iommu=on i915.enable_gvt=1 i915.enable_guc=0 To grub Configuration file to start kvmgt, Otherwise, in the next step , When starting the kernel module modprobe kvmgt vfio-iommu-type1 mdev You will encounter an error report

There are two small pits ：
1、 After revising grub The configuration file must execute update-grub And restart to take effect
2、 perform modprobe kvmgt vfio-iommu-type1 mdev after , Only effective for this startup ; This means that you need to turn it on to automatically execute this command

GVT-g With UEFI Mode start Win10

On the Internet about using GVT-g By tradition BIOS Mode start Win10 The tutorial has been perfected , Most of them refer to ArchWiKi：
https://wiki.archlinux.org/title/Intel_GVT-g

But the “Using DMA-BUF with UEFI/OVMF” There are some puzzling problems in the chapter , In the client, the performance is ; You can't install the graphics driver anyway 、 The graphics card driver is stuck during installation 、 Even cause the physical machine to jam

It's actually kvm Configuration error , The core display of virtualization is not provided to the virtual machine .

I tried again and again , Through the following operations, we succeeded in UEFI Mode start Win10：

First , Make sure you have the virtualization kernel ready , perform ls /sys/bus/pci/devices/0000:00:02.0/mdev_supported_types/ To see ;0000:00:02.0 It depends on your graphics card , Use lspci -D -nn Command to find .

The above command should get something like i915-GVTg_V5_4 i915-GVTg_V5_8 Output

Make sure you have generated uuid For the virtualized graphics card , The order is similar to
echo "$GVT_GUID" > "/sys/devices/pci${GVT_DOM}/$GVT_PCI/mdev_supported_types/$GVT_TYPE/create"

about “libvirt qemu hook”, Again, make sure that it has executable permissions ; If libvirt qemu hook Not working properly , start-up KVM The client will report an error , Be similar to
Error starting domain : device not found: mediated device 'c3e42018-b346-4fe5-b82c-ca0419f6e4eb' not found

When you think everything is all right , About to operate “Assign a virtual GPU to the virtual machine” For a period of time , Please do this ：

operation “Assign a virtual GPU to the virtual machine” a section ; But will <hostdev mode='subsystem' type='mdev' managed='no' model='vfio-pci' display='off'> Medium display='off' Change it to display='on'.

operation “Getting virtual GPU display contents” a section （ Yes , You're not mistaken , Although it is UEFI; But to operate this section ）.

operation “Using DMA-BUF with UEFI/OVMF” a section .

operation “Enable RAMFB display (optional)” a section .

operation “Display virtual GPU output” Medium “Output using QEMU display (QEMU CLI only)” perhaps “libvirt”（ Depends on using the command line to create KVM The client still uses xml File creation ）; And use <gl enable='yes' rendernode='/dev/dri/by-path/pci-0000:00:02.0-render'/> Replace

$ virsh edit vmname

...
    <graphics type='spice'>
      <listen type='none'/>
      <gl enable='yes'/>
    </graphics>
    <video>
      <model type='none'/>
    </video>
...

Medium <gl enable='yes'/>; Be careful 0000:00:02.0 It depends on your graphics card

Don't operate “Output using SPICE with MESA EGL” and “Output using SPICE with NVIDIA EGL or VNC”; Unless you know how to use it

operation “Changing the display resolution of virtual GPU”

thus , start-up KVM The client and the kernel display driver can run normally