GVT-G not working

[devtinoimao]

abokaborda@abokaborda-HP-ZBook-Fury-15-G7-Mobile-Workstation:~/Downloads/mvisor$ sudo sudo ./start.sh
[0.000] core/vfio_manager.cc:56 GetIommuGroup() panic-error: failed to read iommu_group errno=2, No such file or directory
terminate called after throwing an instance of 'std::runtime_error'
what(): Panic
Aborted

bokaborda@abokaborda-HP-ZBook-Fury-15-G7-Mobile-Workstation:/Downloads/mvisor$ for d in /sys/kernel/iommu_groups//devices/; do
n=${d#/iommu_groups/}; n=${n%%/}
printf 'IOMMU Group %s ' "$n"
lspci -nns "${d##/}"
done
IOMMU Group 0 00:00.0 Host bridge [0600]: Intel Corporation 10th Gen Core Processor Host Bridge/DRAM Registers [8086:9b54] (rev 02)
IOMMU Group 10 00:1b.0 PCI bridge [0604]: Intel Corporation Comet Lake PCI Express Root Port #17 [8086:06c0] (rev f0)
IOMMU Group 11 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:06b8] (rev f0)
IOMMU Group 12 00:1c.5 PCI bridge [0604]: Intel Corporation Comet Lake PCIe Port #6 [8086:06bd] (rev f0)
IOMMU Group 13 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:068e]
IOMMU Group 13 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Comet Lake PCH cAVS [8086:06c8]
IOMMU Group 13 00:1f.4 SMBus [0c05]: Intel Corporation Comet Lake PCH SMBus Controller [8086:06a3]
IOMMU Group 13 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH SPI Controller [8086:06a4]
IOMMU Group 13 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (10) I219-LM [8086:0d4e]
IOMMU Group 14 02:00.0 Non-Volatile memory controller [0108]: Toshiba Corporation XG6 NVMe SSD Controller [1179:011a]
IOMMU Group 15 03:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
IOMMU Group 16 04:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
IOMMU Group 17 04:01.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
IOMMU Group 18 04:02.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
IOMMU Group 19 04:04.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
IOMMU Group 1 00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 02)
IOMMU Group 1 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1)
IOMMU Group 1 01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:10fa] (rev a1)
IOMMU Group 20 05:00.0 System peripheral [0880]: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] [8086:15eb] (rev 06)
IOMMU Group 21 39:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)
IOMMU Group 22 6d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01)
IOMMU Group 2 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
IOMMU Group 3 00:12.0 Signal processing controller [1180]: Intel Corporation Comet Lake PCH Thermal Controller [8086:06f9]
IOMMU Group 4 00:13.0 Serial controller [0700]: Intel Corporation Device [8086:06fc]
IOMMU Group 5 00:14.0 USB controller [0c03]: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller [8086:06ed]
IOMMU Group 5 00:14.2 RAM memory [0500]: Intel Corporation Comet Lake PCH Shared SRAM [8086:06ef]
IOMMU Group 6 00:14.3 Network controller [0280]: Intel Corporation Comet Lake PCH CNVi WiFi [8086:06f0]
IOMMU Group 7 00:15.0 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH Serial IO I2C Controller #0 [8086:06e8]
IOMMU Group 7 00:15.1 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH Serial IO I2C Controller #1 [8086:06e9]
IOMMU Group 8 00:16.0 Communication controller [0780]: Intel Corporation Comet Lake HECI Controller [8086:06e0]
IOMMU Group 8 00:16.3 Serial controller [0700]: Intel Corporation Comet Lake Keyboard and Text (KT) Redirection [8086:06e3]
IOMMU Group 9 00:17.0 SATA controller [0106]: Intel Corporation Device [8086:06d3]
abokaborda@abokaborda-HP-ZBook-Fury-15-G7-Mobile-Workstation:$ mdevctl list -d
cf8e0a65-e94b-4ac0-bfa7-ed2c6f8de82f 0000:00:02.0 i915-GVTg_V5_4 auto

abokaborda@abokaborda-HP-ZBook-Fury-15-G7-Mobile-Workstation:~$
IOMMU enabled, gvt-g device split but wont work on mvisor

[78]

The error message you received:

[0.000] core/vfio_manager.cc:56 GetIommuGroup() panic-error: failed to read iommu_group errno=2, No such file or directory terminate called after throwing an instance of 'std::runtime_error'
what(): Panic
Aborted

This error indicates that the mvisor program is failing to read the IOMMU group information for a device it's trying to manage. The underlying system call is returning errno=2 ("No such file or directory"), suggesting a path related to IOMMU groups is missing or incorrectly structured.

Could you please provide your YAML configuration file for us to check the IOMMU path configuration?

[devtinoimao]

name: Default configuration
base: q35.yaml

machine:
  memory: 8G
  vcpu: 2
  bios: ../share/bios-256k.bin
  # Set vcpu thread priority value [-20, 19]
  # A higher value means a lower priority
  priority: 2
  # Turn on BIOS output and performance measurement
  debug: No
  # Turn on hypervisor to lower CPU usage (Hyper-V is used for Windows)
  hypervisor: Yes

objects:
  - class: qxl
  - class: spice-agent
  - class: usb-tablet

  - class: virtio-network
    mac: 00:50:00:11:22:33
    map: tcp:0.0.0.0:8022-:22
    # If you have configured the tap interface, you can uncomment the following lines
    # backend: tap
    # ifname: tap0

  - class: ata-disk
    image: /home/abokaborda/Desktop/win11.qcow2
    snapshot: No
  - class: ata-cdrom
    image: /home/abokaborda/Downloads/virtio-win-0.1.285.iso
    snapshot: No
    
  # - class: floppy
  #   image: /data/images/floppy.img

  # - class: virtio-block
  #   image: /data/empty.qcow2
  #   snapshot: No

  # - class: virtio-fs
  #   path: /tmp/fuse
  #   disk_name: mvisor-fs   #   inode_count: 200

  - class: vfio-pci
    sysfs: /sys/bus/mdev/devices/cf8e0a65-e94b-4ac0-bfa7-ed2c6f8de82f
    debug: Yes

 # - class: virtio-vgpu
 #   memory: 2G
#    staging: No
#    blob: No
 #   node: /dev/dri/renderD129

  # - class: virtio-cuda
  #   memory: 1G
  #   gpu_memory: 8G
  #   visible_gpus: GPU-0

[78]

The error message indicates that the VFIO driver failed to find the iommu_group symlink for your mediated device (mdev).

The expected location for the iommu_group file for an mdev device with the UUID cf8e0a65-e94b-4ac0-bfa7-ed2c6f8de82f is:

/sys/bus/mdev/devices/cf8e0a65-e94b-4ac0-bfa7-ed2c6f8de82f/iommu_group

The failure to read this file (errno=2, No such file or directory) is the root cause of the panic.

---

🛠️ Troubleshooting Steps

Here are the steps to diagnose why the iommu_group symlink is missing for your mdev device:

1. Verify MDEV Device Existence and Missing Link

First, confirm that the mdev device directory exists and that the iommu_group link is indeed missing.

• Check the Device Directory:

  ls -ld /sys/bus/mdev/devices/cf8e0a65-e94b-4ac0-bfa7-ed2c6f8de82f

• Check for the Missing iommu_group Symlink:

  ls -l /sys/bus/mdev/devices/cf8e0a65-e94b-4ac0-bfa7-ed2c6f8de82f/iommu_group

  (This command should fail with the "No such file or directory" error, confirming the problem.)

2. Identify the Parent PCI Device

An mdev device is created from a physical PCI device. You need to know the parent's address to check its IOMMU status.

• Find the Parent Device Address:

  readlink /sys/bus/mdev/devices/cf8e0a65-e94b-4ac0-bfa7-ed2c6f8de82f/device

  This will output the relative path to the parent PCI device (e.g., ../../../devices/pci0000:00/0000:05:00.0). Note the PCI address (e.g., 0000:05:00.0).

3. Check Parent Device IOMMU Status

The parent PCI device must be correctly assigned to an IOMMU group for its mdev children to function with VFIO.

• Check Parent IOMMU Group:
  Substitute <Parent_PCI_Address> with the address found in step 2 (e.g., 0000:05:00.0).

  ls -l /sys/bus/pci/devices/<Parent_PCI_Address>/iommu_group

  If this check also fails, the problem is likely with the system's IOMMU configuration or the parent device binding (e.g., the parent device is not bound to a VFIO or host driver that supports IOMMU grouping).

4. Verify Kernel Modules

Ensure the necessary VFIO and MDEV modules are loaded.

• Check Loaded Modules:

  lsmod | grep vfio

  You should see modules like vfio_mdev, vfio_iommu_type1, and vfio loaded. If vfio_mdev is not loaded, the mdev device cannot correctly interface with the VFIO subsystem to get an IOMMU group.

[devtinoimao]

abokaborda@abokaborda-HP-ZBook-Fury-15-G7-Mobile-Workstation:/Downloads/mvisor$ sudo !!
sudo mdevctl start --uuid 7599e1ef-3913-473d-bb2f-da1b805cb335
abokaborda@abokaborda-HP-ZBook-Fury-15-G7-Mobile-Workstation:/Downloads/mvisor$ sudo ./build/mvisor -c config/osx.yaml -vnc 5900
[0.000] core/vfio_manager.cc:143 AttachDevice() panic-error: failed to get device fd for /sys/bus/mdev/devices/7599e1ef-3913-473d-bb2f-da1b805cb335 errno=3, No such process
terminate called after throwing an instance of 'std::runtime_error'
what(): Panic
Aborted
abokaborda@abokaborda-HP-ZBook-Fury-15-G7-Mobile-Workstation:~/Downloads/mvisor$

different error this time despite making sure i started the meditated device

[78]

/sys/bus/mdev/devices/7599e1ef-3913-473d-bb2f-da1b805cb335

Make sure the file exists:

ls /sys/bus/mdev/devices/7599e1ef-3913-473d-bb2f-da1b805cb335`

If you reboot your computer, the path will change.