Ahmad

Members
  • Posts

    9
  • Joined

  • Last visited

Ahmad's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. I had to look up the difference between qcow2 and RAW ... thanks for the suggestion. I might give that a try with a fresh Windows VM setup, but, based on my Ubuntu VM, which uses a RAW disk type, and works fine with the agent installed and running, I don't think this is the answer, besides, reading about qcow2 seems to indicate performance hit vs. RAW
  2. I have a Windows VM with a passthrough Nvidia GPU (Quadro RTX 4000), and I also passthrough the primary USB Host controller (which is bound to VFIO at boot): I have the primary Monitor connected through USB-C connection (which in turn allows me to use the monitor's USB hub for keyboard, mouse, etc ...) There are also two other monitors connected through DisplayPort. Everything works fine... typically ... except if I reboot the server (when doing upgrades) Windows VM will not load while the USB-C is connected! if I disconnect the USB-C and keep the other DP connections, windows will boot just fine, and I can connect the USB-C cable after the login screen shows up and everything is peachy ... here are the logs for the VM when it fails to boot: -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=31,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x7 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Windows 10/vdisk1.img","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-2-storage"}' \ -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=libvirt-2-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/gparted-live-1.3.0-1-amd64.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.0,unit=0,drive=libvirt-1-format,id=ide0-0-0,bootindex=2 \ -netdev tap,fd=33,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:fd:98:50,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=34,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device vfio-pci,host=0000:01:00.0,id=hostdev0,bus=pci.0,addr=0x5 \ -device vfio-pci,host=0000:01:00.1,id=hostdev1,bus=pci.0,addr=0x6 \ -device vfio-pci,host=0000:00:14.0,id=hostdev2,bus=pci.0,addr=0x8 \ -device vfio-pci,host=0000:01:00.2,id=hostdev3,bus=pci.0,addr=0x9 \ -device vfio-pci,host=0000:01:00.3,id=hostdev4,bus=pci.0,addr=0xa \ -device vfio-pci,host=0000:05:00.0,id=hostdev5,bus=pci.0,addr=0xb \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2021-06-21 15:19:52.569+0000: Domain id=1 is tainted: high-privileges 2021-06-21 15:19:52.569+0000: Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2021-06-21T15:19:58.643997Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:14.0, no available reset mechanism. 2021-06-21T15:19:59.799926Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:14.0, no available reset mechanism. 2021-06-21T15:20:10.450529Z qemu-system-x86_64: vfio_err_notifier_handler(0000:01:00.3) Unrecoverable error detected. Please collect any data possible and then kill the guest 2021-06-21T15:20:12.871957Z qemu-system-x86_64: vfio_err_notifier_handler(0000:01:00.2) Unrecoverable error detected. Please collect any data possible and then kill the guest 2021-06-21T15:20:12.872021Z qemu-system-x86_64: vfio_err_notifier_handler(0000:01:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest 2021-06-21T15:20:12.872048Z qemu-system-x86_64: vfio_err_notifier_handler(0000:01:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest Thoughts? where do I look for more debugging info?
  3. 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 ..
  4. 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!
  5. 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)
  6. 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
  7. 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.
  8. 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: