March 29, 20251 yr When passing through an Intel DG1 GPU to a virtual machine, as soon as I create the VM, the entire Unraid system crashes. I’ve tested this on both the official 7.0.0 release and the latest 7.1.0-beta.2 version, and the result is the same in both cases.
March 29, 20251 yr Author Posted in the wrong section; could an admin please move it to the appropriate section? Thanks!
March 29, 20251 yr 2 minutes ago, koim said: When passing through an Intel DG1 GPU to a virtual machine, as soon as I create the VM, the entire Unraid system crashes. I’ve tested this on both the official 7.0.0 release and the latest 7.1.0-beta.2 version, and the result is the same in both cases. Please try to post in an appropriate subforum. This has nothing to do in 'Feedback' for the Connect feature. I moved it in General Support.
April 7, 20251 yr Author On 4/4/2025 at 7:47 PM, Mardream said: Try to use 7.0.0 beta 2 I can only downgrade to 7.0.0 stable version, there is no option for 7.0.0 beta 2 Is there any way to downgrade to version 7.0.0 beta 2？there is no corresponding installation package on the website Edited April 9, 20251 yr by koim
April 12, 20251 yr On 4/7/2025 at 7:28 PM, koim said: I can only downgrade to 7.0.0 stable version, there is no option for 7.0.0 beta 2 Is there any way to downgrade to version 7.0.0 beta 2？there is no corresponding installation package on the website This is beyond my capabilities. I upgraded to beta 2 a long time ago and have not upgraded again since. After upgrading from beta 2 to 7.1, there will be issues with the DG1, so I finally downgraded back.
April 12, 20251 yr Community Expert 1 hour ago, Mardream said: This is beyond my capabilities. I upgraded to beta 2 a long time ago and have not upgraded again since. After upgrading from beta 2 to 7.1, there will be issues with the DG1, so I finally downgraded back. Can you provide details of the issue and diagnostics?
April 12, 20251 yr 6 hours ago, SimonF said: Can you provide details of the issue and diagnostics? Issue: Firstly, I successfully drove the dg1 GPU in version 7.0.0 beta2 according to the method(options i915 force_probe=!4908 AND options xe force_probe=4908). Hardware transcoding was successfully implemented in nyanmisaka/jellyfin. After upgrading to 7.1.0 RC1, I could still see the DG1 in /dev/dri, but video transcoding only showed a splash screen in Jellyfin. Of course, I'm not sure if it's a jellyfin issue, so I downgraded back to 7.0.0 beta2, without changing any settings, and transcoding in jellyfin returned to normal. I took a look at other users' posts on the forum, and it might be a jellyfin issue itself, as we can see the dg1 GPU driver in /dev/dri in 7.1.0. But since 7.0.0 beta 2 can handle jellyfin transcoding, I'm not inclined to delve into it further. Because of this, the diagnostic logs in 7.1.0 weren't preserved. Sorry about that.
April 14, 20251 yr On 4/12/2025 at 7:01 PM, Mardream said: Issue: Firstly, I successfully drove the dg1 GPU in version 7.0.0 beta2 according to the method(options i915 force_probe=!4908 AND options xe force_probe=4908). Hardware transcoding was successfully implemented in nyanmisaka/jellyfin. After upgrading to 7.1.0 RC1, I could still see the DG1 in /dev/dri, but video transcoding only showed a splash screen in Jellyfin. Of course, I'm not sure if it's a jellyfin issue, so I downgraded back to 7.0.0 beta2, without changing any settings, and transcoding in jellyfin returned to normal. I took a look at other users' posts on the forum, and it might be a jellyfin issue itself, as we can see the dg1 GPU driver in /dev/dri in 7.1.0. But since 7.0.0 beta 2 can handle jellyfin transcoding, I'm not inclined to delve into it further. Because of this, the diagnostic logs in 7.1.0 weren't preserved. Sorry about that. Now I understand why there was a problem. In 7.0.0 beta 2, filling in '!4908' for i915 can normally drive the dg1, while in 7.1.0 rc1, it is necessary to fill in 'blacklist i915' to drive the dg1
April 17, 20251 yr Author On 4/14/2025 at 10:11 PM, Mardream said: On 4/12/2025 at 7:01 PM, Mardream said: 在 2025 年 4 月 12 日晚上 7:01，Mardream 说： Issue: Firstly, I successfully drove the dg1 GPU in version 7.0.0 beta2 according to the method(options i915 force_probe=!4908 AND options xe force_probe=4908). Hardware transcoding was successfully implemented in nyanmisaka/jellyfin. After upgrading to 7.1.0 RC1, I could still see the DG1 in /dev/dri, but video transcoding only showed a splash screen in Jellyfin. Of course, I'm not sure if it's a jellyfin issue, so I downgraded back to 7.0.0 beta2, without changing any settings, and transcoding in jellyfin returned to normal. 问题：首先，我根据方法（options i915 force_probe=!4908 AND options xe force_probe=4908）在 7.0.0 beta2 版本中成功驱动了 dg1 GPU。在 nyanmisaka/jellyfin 中成功实现了硬件转码。升级到 7.1.0 RC1 后，我仍然可以在/dev/dri 中看到 DG1，但视频转码在 Jellyfin 中只显示了启动画面。当然，我不确定是否是 Jellyfin 的问题，所以我降级回 7.0.0 beta2，没有改变任何设置，Jellyfin 中的转码恢复正常。 I took a look at other users' posts on the forum, and it might be a jellyfin issue itself, as we can see the dg1 GPU driver in /dev/dri in 7.1.0. But since 7.0.0 beta 2 can handle jellyfin transcoding, I'm not inclined to delve into it further. Because of this, the diagnostic logs in 7.1.0 weren't preserved. Sorry about that. 我查看了论坛上其他用户的帖子，它可能本身就是 Jellyfin 的问题，因为我们在 7.1.0 中可以在/dev/dri 中看到 dg1 GPU 驱动。但由于 7.0.0 beta 2 可以处理 Jellyfin 转码，我不想进一步深入调查。因此，7.1.0 中的诊断日志没有被保留。很抱歉。 Now I understand why there was a problem. In 7.0.0 beta 2, filling in '!4908' for i915 can normally drive the dg1, while in 7.1.0 rc1, it is necessary to fill in 'blacklist i915' to drive the dg1 现在我明白了为什么有问题。在 7.0.0 beta 2 中，为 i915 填写'!4908'可以正常驱动 dg1，而在 7.1.0 rc1 中，需要填写'blacklist i915'来驱动 dg1。 Do you mean to fill in 'blacklist i915' in the i915 driver under 'system driver' Fill in 'options xe forcesprobe=4908' in dg1?
May 3, 20251 yr 看了你之前的帖子，直接用中文跟你说吧，我这几天看到别人折腾fedora的时候发现他“清空宿主机 dg1 显卡的 reset_method”。于是我在unraid中： cat /sys/bus/pci/devices/0000:06:00.0/reset_method（06:00.0根据你实际填写） 如果显示flr bus之类的，说明unraid还在占用dg1显卡，此时直通会死机。解决办法是echo "" | tee /sys/bus/pci/devices/0000:06:00.0/reset_method，然后再开虚拟机，就成功了（只测试了fnOS） 可能需要修改GO或者UserScript开启启动，免得开机自启动虚拟机会导致无限死机。 7.0.0 beta2在i915中用option i915 force_probe=!4908就可以，7.1.0我得用blacklist才行，这个你自己试一下。 On 4/17/2025 at 10:00 AM, koim said: Do you mean to fill in 'blacklist i915' in the i915 driver under 'system driver' Fill in 'options xe forcesprobe=4908' in dg1? Edited May 3, 20251 yr by Mardream
May 6, 20251 yr Author On 5/3/2025 at 11:00 AM, Mardream said: 看了你之前的帖子，直接用中文跟你说吧，我这几天看到别人折腾fedora的时候发现他“清空宿主机 dg1 显卡的 reset_method”。于是我在unraid中： cat /sys/bus/pci/devices/0000:06:00.0/reset_method（06:00.0根据你实际填写） 如果显示flr bus之类的，说明unraid还在占用dg1显卡，此时直通会死机。解决办法是echo "" | tee /sys/bus/pci/devices/0000:06:00.0/reset_method，然后再开虚拟机，就成功了（只测试了fnOS） 可能需要修改GO或者UserScript开启启动，免得开机自启动虚拟机会导致无限死机。 7.0.0 beta2在i915中用option i915 force_probe=!4908就可以，7.1.0我得用blacklist才行，这个你自己试一下。 感谢，晚点回去顺带升级最新系统后试试。刚才试了下确实是flr bus
May 6, 20251 yr Author On 5/3/2025 at 11:00 AM, Mardream said: 看了你之前的帖子，直接用中文跟你说吧，我这几天看到别人折腾fedora的时候发现他“清空宿主机 dg1 显卡的 reset_method”。于是我在unraid中： cat /sys/bus/pci/devices/0000:06:00.0/reset_method（06:00.0根据你实际填写） 如果显示flr bus之类的，说明unraid还在占用dg1显卡，此时直通会死机。解决办法是echo "" | tee /sys/bus/pci/devices/0000:06:00.0/reset_method，然后再开虚拟机，就成功了（只测试了fnOS） 可能需要修改GO或者UserScript开启启动，免得开机自启动虚拟机会导致无限死机。 7.0.0 beta2在i915中用option i915 force_probe=!4908就可以，7.1.0我得用blacklist才行，这个你自己试一下。 还是有问题的，使用命令后运行fnos虚拟机，unraid不会死机。但是使用虚拟机界面的关闭该虚拟机，unraid系统照样崩溃。。要强制重启才行 Edited May 6, 20251 yr by koim
May 7, 20251 yr 12 hours ago, koim said: 还是有问题的，使用命令后运行fnos虚拟机，unraid不会死机。但是使用虚拟机界面的关闭该虚拟机，unraid系统照样崩溃。。要强制重启才行 确实有这个问题，应该就是dg1本身的问题，我已经放弃折腾了
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.