zhtengw

Members
  • Posts

    57
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

zhtengw's Achievements

Rookie

Rookie (2/14)

13

Reputation

  1. 这是因为系统在加载插件驱动之前先执行了检查vfio绑定的脚本,在设备页面取消绑定就好了
  2. 这是因为系统在加载插件驱动之前先执行了检查vfio绑定的脚本,在设备页面取消绑定就好了
  3. 实在遗憾,Rocketlake现在是真的没人管,技术规格上是支持gvt-g,但是Intel的gvt-g驱动不更新对它的支持(见这个issue讨论),所以没办法。如果很依赖虚拟化多核显的话还是换平台吧。
  4. 但是我的i3-12100的UHD730,就是用的ARC版显卡驱动虚拟机Windows核显的,所以很抱歉之前没有给到你有用的信息。
  5. 你好,Linux下的日志都是正常的。Windows里报43错误可能跟几个因素相关: 1、虚拟机不是只留一个直通VF作为主显卡 2、虚拟机Windows系统没有安装最新的Intel核显驱动 3、使用的是测试版的CPU 或者你可以切换虚拟机的机型和BIOS试一下。
  6. 首先,分配的虚拟显卡可以不用在tools->system device 绑定到vfio-pci,这样就不会提示虚拟机无法自动启动了。 第二,群晖内核太老,无法驱动虚拟核显,分配给它也没用,不用分给群晖虚拟机。 第三,Windows远程控制用系统自带的rdp服务,是可以更改分辨率的。 最后,如果你不论怎么尝试都代码43的话,可能是测试版CPU的原因。 这个驱动本身还是测试版,还是有很多不完善的地方
  7. 你好,rc4的内核支持昨天已更新
  8. Hi, this works only on tiger-lake and later Intel iGPU. And if you have a supported hardware, you are not need to replace the kernel image, installing the i915-sriov is enough. 6.12.0-rc3 is supported.
  9. 你好,SR-IOV的虚拟显卡目前是没法显示输出的,用Windows自带的RDP服务可以保证不错的远程桌面体验,用mstsc或者其他支持rdp协议的远程桌面客户端都差不多的。VNC、向日葵这些体验就差一些了。
  10. 你好,您的虚拟机类型是不是q35,改成i440fx看看行不行
  11. Thanks for your feedback. I am using i3-12100 too and do not meet this issue. And I can not figure out what happen to you now. The 2023.04.06 updates only the setting page. If it is convenient to you, would you please install the version 2023.04.01 with the URL below to have a test? https://raw.githubusercontent.com/zhtengw/unraid-i915-sriov/525f2d329c6a7bea471964cf8f9364b2b8980ac5/i915-sriov.plg
  12. I borrowed a laptop with i5-11300H and intel HM570 chipset which in the same series as your platform. And I got the same "code 43" error in Windows Guest, even through I installed the latest intel graphics driver. It looks like a adaptation issue of the intel driver for the mobile platform.
  13. Hi giganode, [ 43.663221] i915 0000:00:02.1: GuC interface version 0.1.0.0 [ 43.663869] i915 0000:00:02.1: IOV: Failed to get runtime info (-EPROTO) [ 43.669365] i915 0000:00:02.1: Device initialization failed (-71) [ 43.669368] i915: probe of 0000:00:02.1 failed with error -71 According these info from your dmesg, I can locate the error in running this function. It happens when not enough MMIO resources for SR-IOV. Can you add "pci=realloc,assign-busses" to your boot kernel command line to have a try? By the way, I don't know how to see your signature to get your hardware info.
  14. 1. dmesg | grep i915 没有内容表示当时没有加载i915驱动,终端执行一下modprobe i915就行了; 2. 这个跟syslinux的gui引导没什么关系; 3. 目前SR-IOV的虚拟核显没办法输出到外接显示器,等后续Intel有无解决方案。