neoherozzz

建议到[Plugin] Nvidia-Driver板块下英文提问，开发者回复概率高

If you have two Unraid servers with the same machine-id, you can resolve the conflict by running the above command on one of the servers to change its machine-id. Alternatively, a simpler method is to delete the /boot/config/machine-id file; Reboot, a brand new machine-id will be generated automatically.

Tested on unraid 7.2.1-rc1, the machine-id conflict issue in wsd has been perfectly resolved. To generate a new machine-id, you can run dbus-uuidgen > /boot/config/machine-idor just delete /boot/config/machine-id and reboot. Thanks to the unraid team for their efforts!

5080首发用到现在8个月了，没有问题呀😅 1、我没有vfio绑定，安装了nvidia driver插件，平时docker跑ai，玩游戏直通虚拟机玩游戏也可以 2、机器尽量选Q35，直通会好点 3、看虚拟机日志有没有qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument，有的话参考下面帖子

[root@OpenWrtMain:09:48 AM ~] # wget --compression=auto -O /dev/null https://ca.unraid.net/assets/feed/applicationFeed.json --2025-11-05 09:49:02-- https://ca.unraid.net/assets/feed/applicationFeed.json Resolving ca.unraid.net... 2606:4700:20::681a:275, 2606:4700:20::ac43:45b0, 2606:4700:20::681a:375, ... Connecting to ca.unraid.net|2606:4700:20::681a:275|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/json] Saving to: '/dev/null' /dev/null [ <=> ] 1.98M 1.28MB/s in 1.6s 2025-11-05 09:49:05 (1.28 MB/s) - '/dev/null' saved [20729016]

1、将系统日志镜像到U盘，查看日志确定原因 2、大概率跟安装的某个插件有关，可以进入unraid的安全模式测试长时间是否卡住

这种一般就是网络问题，Docker Hub 对镜像拉取有速率限制：匿名用户（未登录）每 6 小时限 100 次拉取，免费账户限 200 次。如果超过限制，会返回 429 Too Many Requests 错误，导致 Docker 客户端重试或失败。可以在终端中登录自己的dockerhub账号 docker login

Thanks for your testing❤️

I searched previous posts and found mentions that earlier versions had a machine-id file under /boot/config/ used for Samba sharing I tried to fix this on server by generating a new ID with dbus-uuidgen > /boot/config/machine-id and rebooting, but the system still boots with the old, conflicting machine-id and ignores the file on the flash drive. https://forums.unraid.net/topic/164386-deleted-br0/#findComment-1415260

I have deployed two Unraid servers on my local network, but I discovered that their machine-id are identical. This is causing a WSD (wsdd) discovery conflict for network sharing, and as a result, I cannot see both servers at the same time. How can I properly change the machine-id on one of the Unraid servers? Even when I use a brand new 7.2.0 system in a VMWare VM, I still get the same result. Can anyone else please check and see if their cat /etc/machine-id result is also identical? root@Tower:~# cat /etc/machine-id 1f9334b9b3ea.....eb7d57469028723

Thank you for your reply. I changed the server name, but after rebooting, the machine-id still hasn't changed. If anyone has any suggestions, please feel free to discuss them in the thread below.

Even when I use a brand new 7.2.0 system in a VMWare VM, I still get the same result. Can anyone else please check and see if their cat /etc/machine-id result is also identical? root@Tower:~# cat /etc/machine-id 1f9334b9b3ea.....eb7d57469028723

I have deployed two Unraid servers on my local network, but I discovered that their machine-id are identical. This is causing a WSD (wsdd) discovery conflict for network sharing, and as a result, I cannot see both servers at the same time. How can I properly change the machine-id on one of the Unraid servers?

Create a new vm and use ISO image to test basic display output. add maxphysaddr, I see a little difference with yours. <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' clusters='1' cores='6' threads='2'/> <cache mode='passthrough'/> <maxphysaddr mode='passthrough' limit='39'/> </cpu> Start vm, If there's no signal, there are still some unknown issues in your unraid settings or vm template settings. If you can see some ouput on your physical monitor, i think there's no problem with vm config. Try to use Display Driver Uninstaller (DDU) to uninstall Nvidia driver with vnc(Graphic card set to vnc only). Then edit vm config, set graphic card to your gpu only. Start and wait windows to autoinstall graphic drivers. PS: when you restart unraid server, try to do a complete shutdown then press the power button. This can do a reset with your GPU card. This is all the solutions I can think of so far. Good luck! vm.xml

Make vnc the first gpu and A2000 the second in your vm config. Then reinstall the nvidia drivers.

@ich777 Thanks for your flash update! Everything works perfect so far. Hope the drivers wont brick my 5080🤣

I selected new feature branch by mistake. The open source shows follows: Nvidia Info: Nvidia Driver Version: 565.77 Open Source Kernel Module: Yes Installed GPU(s): NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. tower-diagnostics-20250204-2357.zip

It seems not worked with 565.77, Open Source Kernel Module is no. Nvidia Info: Nvidia Driver Version: 565.77 Open Source Kernel Module: No Installed GPU(s): NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. tower-diagnostics-20250204-2347.zip

There is something wrong with RTX5080 fe. It shows as follws: Nvidia Info: Nvidia Driver Version: 570.86.16 Open Source Kernel Module: No Installed GPU(s): No devices were found The system device shows: [10de:2c02] 01:00.0 VGA compatible controller: NVIDIA Corporation Device 2c02 (rev a1) [10de:22e9] 01:00.1 Audio device: NVIDIA Corporation Device 22e9 (rev a1) The Diagnostics is uploaded. tower-diagnostics-20250204-2322.zip

I don't think there is something wrong with the output. My output is as follows, and it works well. 2025-02-04 14:52:49.810+0000: Domain id=1 is tainted: high-privileges char device redirected to /dev/pts/0 (label charserial0) RTX3080 works well on my gaming vm. But today I received RTX 5080 fe, It shows a black screen and the VFIO_MAP_DMA error. After I tried maxphysaddr, everything is back to normal now. As for signal missing, maybe you can try to reinstall the graphic driver.

You can try this. It sometimes works. add maxphysaddr to cpu block. <cpu mode="host-passthrough" check="none" migratable="on"> <topology sockets="1" dies="1" clusters="1" cores="6" threads="2"/> <maxphysaddr mode="passthrough" limit="39"/> </cpu> This method is from this webpage.

It's a smooth upgrade from 6.12.13 to 7.0.0, all good, thanks🥰 But do I need to click the "upgrade pool" button? What changes will occur after upgrading?

一般跟权限有关，可以查看docker日志。

打开：工具——注册，显示什么？

请上传虚拟机xml配置文件