https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
👀 1
t
From virt-launcher
Copy code
Warning  SyncFailed        1s    virt-handler               server error. command SyncVMI failed: "LibvirtError(Code=1, Domain=10, Message='internal error: QEMU unexpectedly closed the monitor (vm='default_truenas'): 2026-04-29T02:23:09.140957Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.flushbyasid [bit 6]\n2026-04-29T02:23:09.140966Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.pause-filter [bit 10]\n2026-04-29T02:23:09.140974Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.pfthreshold [bit 12]\n2026-04-29T02:23:09.140984Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.vgif [bit 16]\n2026-04-29T02:23:09.161855Z qemu-system-x86_64: -device {\"driver\":\"vfio-pci\",\"host\":\"0000:05:00.0\",\"id\":\"ua-hostdevice-um890pro-000005000\",\"bus\":\"pci.15\",\"addr\":\"0x0\"}: vfio 0000:05:00.0: group 1 is not viable\nPlease ensure all devices within the iommu_group are bound to their vfio bus driver.')"
  Normal   Deleted           1s    virt-handler               Signaled Deletion
  Warning  SyncFailed        1s    virt-handler               unknown error encountered sending command SyncVMI: rpc error: code = Unavailable desc = error reading from server: EOF
c
```2026-04-29T022309.161855Z qemu-system-x86_64: -device {\"driver\":\"vfio-pci\",\"host\":\"00000500.0\",\"id\":\"ua-hostdevice-um890pro-000005000\",\"bus\":\"pci.15\",\"addr\":\"0x0\"}: vfio 00000500.0: group 1 is not viable
Please ensure all devices within the iommu_group are bound to their vfio bus driver.```
Changes to underlying kernel version? What’s all in that group on the new version?
t
I don’t think there is anything else in that group.
Copy code
05:00.0 Non-Volatile memory controller [0108]: MAXIO Technology (Hangzhou) Ltd. NVMe SSD Controller MAP1602 (DRAM-less) [1e4b:1602] (rev 01)
	Subsystem: MAXIO Technology (Hangzhou) Ltd. NVMe SSD Controller MAP1602 (DRAM-less) [1e4b:1602]
	Kernel driver in use: vfio-pci
	Kernel modules: nvme
Copy code
um890pro:~ # ls /sys/bus/pci/devices/0000:05:00.0/iommu_group/devices/
0000:00:02.0  0000:00:02.1  0000:00:02.2  0000:00:02.3  0000:00:02.4  0000:02:00.0  0000:03:00.0  0000:04:00.0  0000:05:00.0
Copy code
um890pro:~ # ls -asl /sys/bus/pci/devices/0000:05:00.0/iommu_group/devices/
total 0
0 drwxr-xr-x. 2 root root 0 Apr 29 02:58 .
0 drwxr-xr-x. 3 root root 0 Apr 29 02:41 ..
0 lrwxrwxrwx. 1 root root 0 Apr 29 02:56 0000:00:02.0 -> ../../../../devices/pci0000:00/0000:00:02.0
0 lrwxrwxrwx. 1 root root 0 Apr 29 02:56 0000:00:02.1 -> ../../../../devices/pci0000:00/0000:00:02.1
0 lrwxrwxrwx. 1 root root 0 Apr 29 02:56 0000:00:02.2 -> ../../../../devices/pci0000:00/0000:00:02.2
0 lrwxrwxrwx. 1 root root 0 Apr 29 02:56 0000:00:02.3 -> ../../../../devices/pci0000:00/0000:00:02.3
0 lrwxrwxrwx. 1 root root 0 Apr 29 02:56 0000:00:02.4 -> ../../../../devices/pci0000:00/0000:00:02.4
0 lrwxrwxrwx. 1 root root 0 Apr 29 02:56 0000:02:00.0 -> ../../../../devices/pci0000:00/0000:00:02.1/0000:02:00.0
0 lrwxrwxrwx. 1 root root 0 Apr 29 02:56 0000:03:00.0 -> ../../../../devices/pci0000:00/0000:00:02.2/0000:03:00.0
0 lrwxrwxrwx. 1 root root 0 Apr 29 02:56 0000:04:00.0 -> ../../../../devices/pci0000:00/0000:00:02.3/0000:04:00.0
0 lrwxrwxrwx. 1 root root 0 Apr 29 02:56 0000:05:00.0 -> ../../../../devices/pci0000:00/0000:00:02.4/0000:05:00.0
c
Sure looks like they're all in the same group.
t
What changed between versions?
c
New version of SLE and new kernel, I believe?
t
So the plot thickens. I have a new install of 1.7.1, on a new box. I was able to backup the VM and restore it to the new node. Now when I setup PCI Passthrough I am getting the following error:
Copy code
server error. command SyncVMI failed: "LibvirtError(Code=1, Domain=0, Message='internal error: Unknown PCI header type '127' for device '0000:01:00.0'')"
Big picture. box A had the nvme working flawlessly from 1.4-->1.7.1. upgraded to 1.8.0. Would not boot. New box with backup of VM. PCI still won’t boot with different error message.
🙃 1
15 Views
Open in Slack
PreviousNext
Powered by