May 27, 20215 yr When I start a VM, it works fine but triggers this error. I think it's due to onboard audio pass-through. The actual error is: 2021-05-27T10:30:24.611787Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.4, depends on group 38 which is not owned. Here are my IOMMU groups: I was wondering, what would happen if I pass-through group 38 (Starship/Matisse Reserved SPP)? I tried finding out what it was but it's not documented (or at least I didn't find anything useful).
February 25, 20224 yr Same here, it is since OP "may 27 2021" no solutions ???? 2022-02-25T18:44:31.746305Z qemu-system-x86_64: vfio: Cannot reset device 0000:4f:00.2, depends on group 69 which is not owned. 2022-02-25T18:44:31.758293Z qemu-system-x86_64: vfio: Cannot reset device 0000:4f:00.0, depends on group 69 which is not owned. Loading config from /boot/config/vfio-pci.cfg BIND=0000:4f:00.0|1002:73bf 0000:4f:00.1|1002:ab28 0000:4f:00.2|1002:73a6 --- Processing 0000:4f:00.0 1002:73bf Vendor:Device 1002:73bf found at 0000:4f:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:4f:00.0/iommu_group/devices/0000:4f:00.0 Binding... Successfully bound the device 1002:73bf at 0000:4f:00.0 to vfio-pci --- Processing 0000:4f:00.1 1002:ab28 Vendor:Device 1002:ab28 found at 0000:4f:00.1 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:4f:00.1/iommu_group/devices/0000:4f:00.1 Binding... Successfully bound the device 1002:ab28 at 0000:4f:00.1 to vfio-pci --- Processing 0000:4f:00.2 1002:73a6 Vendor:Device 1002:73a6 found at 0000:4f:00.2 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:4f:00.2/iommu_group/devices/0000:4f:00.2 Binding... Unbound 0000:4f:00.2 from xhci_hcd Successfully bound the device 1002:73a6 at 0000:4f:00.2 to vfio-pci --- vfio-pci binding complete Devices listed in /sys/bus/pci/drivers/vfio-pci: lrwxrwxrwx 1 root root 0 Feb 25 18:40 0000:4f:00.0 -> ../../../../devices/pci0000:40/0000:40:03.1/0000:4d:00.0/0000:4e:00.0/0000:4f:00.0 lrwxrwxrwx 1 root root 0 Feb 25 18:40 0000:4f:00.1 -> ../../../../devices/pci0000:40/0000:40:03.1/0000:4d:00.0/0000:4e:00.0/0000:4f:00.1 lrwxrwxrwx 1 root root 0 Feb 25 18:40 0000:4f:00.2 -> ../../../../devices/pci0000:40/0000:40:03.1/0000:4d:00.0/0000:4e:00.0/0000:4f:00.2
February 25, 20224 yr 4 minutes ago, ddk-input said: Same here, it is since OP "may 27 2021" no solutions ???? Forgetting about no answers to the OP's question, you need to post your diagnostics in order for anyone to begin to answer anything.
February 27, 20224 yr On 2/25/2022 at 7:57 PM, Squid said: Forgetting about no answers to the OP's question, you need to post your diagnostics in order for anyone to begin to answer anything. Thank you , I wrote my solution here
April 27, 20242 yr I've got the same error, and i cannot connect to the VM (though i've got a green icon saying it's running) Just before, i've tried to increase the RAM allocated. The diagnostics are attached. nas-diagnostics-20240427-1547.zip
April 27, 20242 yr Edit : seems to be running now. I've been back to less RAM than before. No idea if it has a relationship
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.