Everything posted by Ahmad
-
[Plugin] Nvidia-Driver
you can add that to a "FUNDING.yml" in the repo ... https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository also if you setup GH Sponsors, they will match donations ..
-
[Plugin] Nvidia-Driver
ah ... well that also makes sense ... (I have to learn more about VFIO I guess) and thank you for the prompt response! side note: I would encourage you to setup GitHub Sponsors so folks can buy you "a cup of coffee" for your efforts! cheers!
-
[Plugin] Nvidia-Driver
thank you for clarifying! makes sense! any clues from the attached diagnosis why it doesn't detect the card? (even with VM off / no passthrough)
-
[Plugin] Nvidia-Driver
attached the diagnosis, the card is a Quadro RTX 4000, I read elsewhere that I shouldn't expect the driver to be used when passing through the card entirely to the guest OS and that the plugin is mainly useful for using the GPU with Docker containers ... is that an accurate understanding? removing the plugin didn't seem to have any negative effects ... and I don't see the errors in the logs after removal. does using the plugin ad any benefit to a vm passthrough gpu? can I get the stats in unraid gui if it's passthrough? appreciate the help for as I'm trying to understand all this! server-diagnostics-20210620-1532.zip
-
Nvidia-nvlink: Unregistered the Nvlink Core, major device number 244
did you figure this out? I'm having the same problem!
-
[Plugin] Nvidia-Driver
everything works fine, except I keep getting this error in the logs: Jun 20 00:19:23 Server kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s). Jun 20 00:19:23 Server kernel: NVRM: This can occur when a driver such as: Jun 20 00:19:23 Server kernel: NVRM: nouveau, rivafb, nvidiafb or rivatv Jun 20 00:19:23 Server kernel: NVRM: was loaded and obtained ownership of the NVIDIA device(s). Jun 20 00:19:23 Server kernel: NVRM: Try unloading the conflicting kernel module (and/or Jun 20 00:19:23 Server kernel: NVRM: reconfigure your kernel without the conflicting Jun 20 00:19:23 Server kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module Jun 20 00:19:23 Server kernel: NVRM: again. Jun 20 00:19:23 Server kernel: NVRM: No NVIDIA devices probed. Jun 20 00:19:23 Server kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 244 I can't seem to get any stats on the GPU in the unraid gui, but the passthrough works just fine in Windows VM ... it's not really a show stopper, would be nice to get stats in unraid ... and not fill the log with this error ... any help is appreciated.
-
VM Backup Plugin
This works great for Linux vms, but I'm seeing an issue with Windows 10 vm ... error: internal error: unable to execute QEMU agent command 'guest-fsfreeze-freeze': failed to add C:\ to snapshot set: full log: Windows 10.xml sent 6,049 bytes received 35 bytes 12,168.00 bytes/sec total size is 5,939 speedup is 0.98 2021-06-19 12:02:00 information: copy of Windows 10.xml to /mnt/user/backups/Windows 10/20210619_1202_Windows 10.xml complete. sending incremental file list c15ed305-5492-a7c9-e457-92e090f81d25_VARS-pure-efi.fd sent 131,247 bytes received 35 bytes 262,564.00 bytes/sec total size is 131,072 speedup is 1.00 2021-06-19 12:02:00 information: copy of /etc/libvirt/qemu/nvram/c15ed305-5492-a7c9-e457-92e090f81d25_VARS-pure-efi.fd to /mnt/user/backups/Windows 10/20210619_1202_c15ed305-5492-a7c9-e457-92e090f81d25_VARS-pure-efi.fd complete. 2021-06-19 12:02:00 information: able to perform snapshot for disk /mnt/user/domains/Windows 10/vdisk1.img on Windows 10. use_snapshots is 1. vm_state is running. vdisk_type is raw 2021-06-19 12:02:00 information: qemu agent found. enabling quiesce on snapshot. error: internal error: unable to execute QEMU agent command 'guest-fsfreeze-freeze': failed to add C:\ to snapshot set: 2021-06-19 12:02:00 failure: snapshot command failed on vdisk1.snap for Windows 10. 2021-06-19 12:02:00 failure: snapshot_fallback is 0. skipping backup for Windows 10 to prevent data loss. no cleanup will be performed for this vm. 2021-06-19 12:02:00 information: Ubuntu can be found on the system. attempting backup. 2021-06-19 12:02:00 information: creating local Ubuntu.xml to work with during backup. 2021-06-19 12:02:00 information: /mnt/user/backups/Ubuntu exists. continuing. 2021-06-19 12:02:00 information: skip_vm_shutdown is false and use_snapshots is 1. skipping vm shutdown procedure. Ubuntu is running. can_backup_vm set to y. 2021-06-19 12:02:00 information: actually_copy_files is 1. 2021-06-19 12:02:00 information: can_backup_vm flag is y. starting backup of Ubuntu configuration, nvram, and vdisk(s). sending incremental file list I can confirm qemu agent is installed and running: