pliangcho

有人帮忙看看啥情况没有

2022-02-24T15:32:07.968175Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eaf4, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968183Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eaf8, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968190Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eafc, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968198Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb00, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968205Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb04, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968212Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb08, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968220Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb0c, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968228Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb10, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968235Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb14, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968242Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb18, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968250Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb1c, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968257Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb20, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968264Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb24, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968272Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb28, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968279Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb2c, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968287Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb30, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968296Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb34, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968324Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb38, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968335Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb3c, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968346Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb40, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968370Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb44, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968395Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb48, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968405Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb4c, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968415Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb50, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968425Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb54, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968435Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb58, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968445Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb5c, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968455Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb60, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968465Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb64, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968475Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb68, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968502Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb6c, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968512Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb70, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968522Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb74, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968534Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb78, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968544Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb7c, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968554Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb80, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968564Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb84, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968575Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb88, 0x0,4) failed: Device or resource busy 2022-02-24T15:32:07.968585Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x10eb8c, 0x0,4) failed: Device or resource busy

请教一下，我这边直通后感觉还是不稳定，时常满载卡死，内存占用也高请教一下内存占用高正常吗 VID_20210618_234911.mp4

其实还真可以实机测试怎么能单独联系你呢加我qq17873897

只给一个核心，或者少几个核心就没问题，如果把大部分核心给Windows10还是会死机，这到底是怎么了

6.8.2就没有这个问题，难道6.9的直通CPU不能复用了？请教一下，虽说困扰我很长时间的问题终于解决了

请教怎么设置unraid独占1至2核心呢，另外为何6.8.2没问题，但到了6.9就不行了

解决了，囧，只要少绑定一个CPU核心就好了，囧，因为想用Windows10直通后的当主机生产机，但为什么会这样呢

这个日志一直满，如果是哪里出错有日志吗？

有没有邮箱，私聊一下，这个能私聊吧，我把地址给你，你帮我看看

请教一下，我上边发的日志能看出问题吗

unraid主机连接显示器会有gui界面，我的go文件里如果不加，我的主板启动进不去gui模式，你可以试一下你的看能不能进去

只要不直通显卡就没问题，想问一下，你那边同样配置如果不在go文件里加命令能进gui模式吗？感觉还是跟这块有关系？而且好像是通病不只是我的有问题

依然解决不了，郁闷咋回事呢

还是不行，囧无解了吗

6.8的时候因为没有驱动，声卡是可以选的，升级到，6.9以后直通声卡就不行了，因为声卡走的是HDMI属于显卡功能，不知道有影响吗

还有一个情况反馈一下，因为从新安装6.9以后无法进入gui模式，在go加参数才能进去gui的模式

感谢，配置来了

还是不行，郁闷，6.8.2一点问题都没有的

直接用630还是不行

驱动本来是驱动好的，启动了一夜，启动好了，但已删除驱动又卡死了