Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by SimonF

  1. The Nvidia Card as a built in USB you need to bind all three to VFIO and add to VM. IOMMU group 26: [10de:2184] 09:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660] (rev a1) IOMMU group 27: [10de:1aeb] 09:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1) IOMMU group 28: [10de:1aec] 09:00.2 USB controller: NVIDIA Corporation TU116 USB 3.1 Host Controller (rev a1)
  2. Suggest you open a new thread in General. provide lsusb.
  3. vfio-pci.cfg is in the config dir on the usb drive.
  4. Take a look at this video from spaceinvader one
  5. My usb manager plugin supports multiple same vendor product mapping to vms
  6. Hi, it may be worth posting on the support thread. Device page is only for mapping a physical device, but you still need to define the mappings on the initiator page.
  7. Try the following with your usb of 1-2 instead of 1-1.2 and you should be able to ID the info below to match to the lsusb. Maybe the ASMedia device. root@unraid:/sys/bus/usb/devices/1-1.2# cd /sys/bus/usb/devices/1-1.2 root@unraid:/sys/bus/usb/devices/1-1.2# cat idProduct 3609 root@unraid:/sys/bus/usb/devices/1-1.2# cat idVendor 13fd root@unraid:/sys/bus/usb/devices/1-1.2# cat busnum 1 root@unraid:/sys/bus/usb/devices/1-1.2# cat devnum 31
  8. do you have any dockers running? I have found if you stop dockers you can restart libvirt without a reboot. I think there is a bug report for this.
  9. root@unraid:~# lsscsi -t [12:0:0:0] cd/dvd usb:1-1.2:1.0 /dev/sr1 This should show the usb port
  10. I would supprised if it is not in lsusb. My BU40 is connected via the Initio Controller. The ASUS is Sata attached. Bus 001 Device 031: ID 13fd:3609 Initio Corporation USB3.0 DEVICE root@unraid:~# lsscsi | grep sr [5:0:0:0] cd/dvd ASUS BW-16D1HT 3.01 /dev/sr0 [12:0:0:0] cd/dvd HL-DT-ST BD-RE BU40N 1.03 /dev/sr1
  11. The physical interface is not being initialised for some reason. Oct 9 08:53:30 Tower kernel: e1000e 0000:00:1f.6: The NVM Checksum Is Not Valid Oct 9 08:53:30 Tower kernel: e1000e: probe of 0000:00:1f.6 failed with error -5 Do you have the latest Bios. This is taken from this post so may fix your issue My solution is much more simple: - enter the UEFI BIOS utility; - enter Advanced mode - navigate to Advanced\Network Stack Configuration and simply enable the network stack (i only enabled IPv4 to remain safely behind my NAT)
  12. I have started to create a plugin for Snapshots, Currently this is for BTRFS based snapshots only. It is still very early in the development process, so I would still class as Alpha, and not all functions are in place. I have been working with JorgeB to work through initial issues of formatting etc so thanks for the feedback and help, but there may be use cases outside of our current environments. If you use Docker folder support instead of image there could be a lot of subvols displayed. If people want to look at the current development, you can download the plugin at your own risk, any suggestions are welcome, but I will not be able to provide support on this at present until it is released as a beta. Schedule function is not developed, its just the edit page at present. {YMD} if used in the path prefix it will replace with date and time. Send does not support remote systems or incremental at this time. plugin download location access is on tools page under system information.
  13. WIP - Currently very earlier in the build process. Placeholder for future Support. Please post on feature request thread.
  14. @sergio.calhenoGlad we could help. For info the bind button in my plugin is to bind to the usbip process but donesn't remove it from the host. The other suggested options would have worked but I dont think you have virtualisation enabled in the BIOS so could not stub the pcie device.
  15. @sergio.calheno i think you may need to do bluetooth also, have a look at this post. I know this is for 6.10 but should work on 6.9.2 also.
  16. My plugin will not help. I think the best course of action is to unload the blue tooth usb module btusb. modprobe -r btusb you will need to unload in the go file to make persistent. i will look at this more tomorrow.
  17. Hi ich777 has suggested you can try the following: echo ":msg,contains,\"Unsupported SCSI Opcode 0xa1\" stop" >> /etc/rsyslog.d/01-blocklist.conf /etc/rc.d/rc.rsyslogd restart Also you will need to add to your go file to make persistent
  18. Not that I know of, I think its the client probing for info.
  19. Do you have hyperthreading enabled in the bios?