Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About T0a

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Good news, localization is coming with Unraid 6.9 (English Master). In this context, Limetech were looking for professional translators in Arabic, French, Mandarin and Spanish here. Let's see what is coming. Maybe we can add more languages with a community-driven approach in the future.
  2. * Do you access your VM from another device via VNC? * Have you tried a wired connection? * Have you tested other remote accessing software such as nomachine, splashtop or parsec? * Do you have the same bad experience when you plug in a monitor directly to your MB port and use an attached keyboard and mouse? * Does Windows recognize your UHD 630 in the device manager with correct drivers loaded? * Have you tried to download the latest UHD 630 drivers from Intels Website? They usually perform better than the one shipped with Windows.
  3. Unraid: 6.8.3 Component: Docker, UX Type of issue: cosmetic, minor 1. Using the update button from the context menu (see docker-update-0.png) does not open the "Are you sure" dialog window (see docker-update.png). However, when using the update button from the docker overview, the dialog window pops up just fine. 2. Once a docker update is available, the update entry in the context menu is placed first (see docker-update-0.png). Usually, there is the start entry (docker-update-2.png). From an UX perspective, reordering the entries in the list is misleading for the user. The user is used to have the start button placed first, he has the intention to start a stopped container, muscle memory kicks, he accidentally clicks on update. No dialog window warned him due to issue (1). Impact of this issue: Both issues in combination will cause accidental updates of docker containers. docker-update.png docker-update-0.png docker-update-2.png
  4. This sounds like some sort of reset bug with the graphics card. What graphics card are you using (AMD)? This would be cool as I don't own the hardware to try it myself. Have a look at this video. You need to do some sort of transfer here as you want to passthrough your Thunderbold controller instead of the USB controller. To briefly summarize: * Install VFIO PCIE Config plugin from the Apps store * The plugin should list your IOMMU groups and also show the connected devices such as your eGPU * Tick the Thunderbold controller that has the eGPU connected to its port. This will blacklist the whole controller from the host (make sure you don't tick the device with your Unraid flash drive. Otherwise you cannot boot anymore). You may need to reboot. * Add the thunderbold controller to your VM template as shown in the video linked above ** For troubleshooting please add the VM template XML and the issues that occur while starting the VM (if so) in your next post * When booted, make sure Windows uses the correct Thunderbold driver (Devices Manager) Using this method, we will rule out Unraid as the culprit as we blacklist the whole controller from the host. I'm curious if that works for you! Feel free to reach back, if you have any problems.
  5. Can you reference the source of your finding?
  6. Hi @Malaga, by passing through the eGPU i.e. ticking the device in the VM template, Unraid adds a hostdev section to your Windows 10 template. When you now turn off your device, it is no longer available to the host. But the hostdev section remains in your Windows 10 template. When you start the VM then, it will try to find the device (which is turned off) and throw an error. I think this is expected behaviour. However, sad to hear that Unraid does not recognize the device when you turn the eGPU on again resulting in a VM startup issue. I guess this is truly an issue with Unraid as both utilize KVM under the hood. Haven't used Proxmox myself, so please correct me if I'm wrong. Thunderbold support can still be considered as experimental in Unraid. Personally, I'm also interested in eGPU support. Some people where able to run Unraid as VM in Proxmox [1] - in case you are missing Unraid features in Proxmox. A solution might be passing through the Thunderbold controller to the the VM. Why? Search for posts in the forum where people have problems with passing through USB devices (crackling sounds with USB sound cards, etc.). The solution to all of these problems is to pass through the whole USB controller. That also allows them to use the USB hot plug feature in their VM. In your case, it could solve the issues you observe with Thunderbold. It's just a theory. You would be one of the first Unraid users experimenting with thunderbold passthrough. cheers [1] https://forums.unraid.net/topic/29679-guide-virtualizing-unraid-on-proxmox-31/
  7. Thanks @testdasifor your input. I got my hands on a used Xeon-2146G for about 200 Euro on Ebay - waiting for it to arrive. For all that are interested in a comparison: Intel Xeon E-2146G Benchmarks (Idle is around 32W and maximum power consumption hits just under 109W) Intel Core i3-9100F Benchmarks (Idle Power (Performance Mode): 31W, STH 70% Load: 75W, STH 100% Load: 92W) Note that I ruled out the Core i7 option, because it does not support ECC RAM.
  8. Had the same problem with the rclone plugin today. Can't figure out what might caused this. Maybe another plugin update? Anyway, the workaround mentioned here works for me. Hopefully, this issue will not occur in the future as it breaks my offsite backup. In the Plugins tab select 'remove' for rclone. Then go to the Apps tab and search for rclone and reinstall it there.
  9. I assume that your VM does not have the driver support for the IGD yet. Either do a Windows update after the passthrough via RDP - you can also open the device manager, click on your graphics adapter and update the driver. Or even better (because most of the time more up-to-date) install the latest driver from Intel via their website. After you where able to passthrough you might still not see any output on your monitor (depending on VM Bios, maschine type, host boot mode etc.). Then take a look at this thread. I assume you already blacklisted the IGD via the known methods (i.e. vfio pci stubbing, kernel parameter etc.).
  10. I was wrapping my head around this solution for a few days now. In order to use legacy passthrough "The IGD device must have a VGA ROM, either provided via the romfile option or loaded automatically through vfio (standard)." [0]. From my understanding the iGPU does not expose a ROM via PCI when the host is booted in UEFI mode [1]. Thus, you probably where able to access the VM via remote access with full GPU support, but got no signal from the port. The symptom in most cases is the following error "vfio-pci: Cannot read device rom at 0000:00:02.0 Device option ROM contents are probably invalid" in the VM log. Further telling that the legacy pass through mode [2] [3] is disabled. To solve the issue you need to manually provide a ROM as vfio is not able to provide it. In your case, your MB is capable to boot in legacy mode that allows to expose the ROM via PCI. Sadly, I cannot go this route for my UHD 630 as my MB does not support legacy mode (probably the standard in the future). In this case I think, you need either a second GPU (don't own one) to dump the IGD ROM or ask someone with the same CPU to dump the ROM for you in legacy mode (a collection of IGD ROMs would be really nice): Update 14-05-2020: Finally, found a working solution for UEFI only MB owners out there that works with legacy GVT-G passthrough and OMVF Bios [6,7]. Following, the setup that resolved the black screen issue with an Intel Core i3-8100 (UHD 630). The trick for me made the "vbios_gvt_uefi.rom" (see [7]; disclaimer: be warned to use a random ROM file from the Internet): Unraid Settings: - Host boots in UEFI (no legacy mode no CSM) - "Unraid OS" boot mode - Permit UEFI boot: Yes - Kernel parameter: append video=efifb:off,vesafb:off modprobe.blacklist=i2c_i801,i2c_smbus,snd_hda_intel,snd_hda_codec_hdmi,i915,drm,drm_kms_helper,i2c_algo_bit - VFIO-PCI Config to stub 00:02.0 VM Settings: - Windows 10 OS, OMVF Bios, i44fx-4.2, Hyper-V: Yes PCI Passthrough cheers, - stay home and don't eat bats [0] https://github.com/qemu/qemu/blob/master/docs/igd-assign.txt [1] https://www.redhat.com/archives/vfio-users/2018-April/msg00022.html [2] https://unraid.net/blog/unraid-server-os-6-3-released (Legacy and UTP mode) [3] https://vfio.blogspot.com/2016/07/intel-graphics-assignment.html [4] https://github.com/qemu/qemu/blob/master/docs/igd-assign.txt [5] https://forums.unraid.net/topic/83802-intel-gvt-g-support-multiple-virtual-intel-igpus-we-already-have-gvt-d/?tab=comments#comment-776192&searchlight=1 [6] https://www.reddit.com/r/VFIO/comments/fzje5x/no_output_from_igpu_when_passed_through/ [7] https://github.com/intel/gvt-linux/issues/23 PS: I think the IGD passthrough will be more popular in the future as services like Stadia and Geforce Now will emerge and improve. This allows casual gamer to enjoy a gaming session with their IGD driven Windows 10 VM. Also GVT-D is a thing [5]. However, I think we will not see this in Unraid in the near future since its focus are NAS features.
  11. Have you already searched the forum? More Information is required to help.
  12. Does maybe this thread help: Symptoms are the same
  13. Seems like a duplicate of
  14. Which device did you exactly checked (8086:1539 or 8086:10bc)? Note, when ticking the wrong one, Unraid has no access to this device such as the eth controller, which could be the cause for your ping issues. The "ACS Override" option shouldn't be required as the device you want to pass through resides in its own IOMMU group, right? In case you haven't changed something else, you should be fine with only removing the pcie-vfio config file from the flash drive as you did. Can you attach a monitor to your server? Then pls look for any printed issues. Also try to boot in "save mode" (with disabled plugins and a virgin sys config file). Does this work? I'm so thankful that limetech put their OS on a flash drive with easy access in case of such a problem.