cyberdude

+1 here also for option of not auto-starting if disk is missing (array or cache pool device)

Hi Richard. I was also going to point you to the VBIOS thread. However. I'm very curious if you got this working without problems? When I started using Unraid, according to all sources, it was impossible to GPU passthrough 2 (or more) of the SAME Gfx cards. In order to achieve this you would have had to have different cards. I can't remember if the above was only true if you used the VBIOS method to passthrough Gfx 1 card. I've specifically added two different Gfx card to my setup to avoid this problem. So therefore I'm very curious if you got your setup working with 4 of same cards (With 1 being main card passthrouged to VM1).

Same problem here, with Nvidia card. - Only desyncs from websites/browsers (Using Chrome, haven't checked with other browsers), no problem using media players. - Only happens on HDMI Audio passthrough (Does NOT happen when using 6-channel audio). - Have tried both enabling/disabling hardware acceleration in Chrome. NotYetRated: I've read some threads here talking about enabling MSI. Some people have enabled MSI with success. I have had it enabled (and confirmed enabled) but it made the problem even worse, audio was suddenly stuttering like crazy. So currently living with having to refresh the page every once in a while when watching streams from Twitch or similar, and have had to resort to using my Chromecast a lot more xD. Wiki: https://wiki.lime-technology.com/UnRAID_6/VM_Guest_Support#Enable_MSI_for_Interrupts_to_Fix_HDMI_Audio_Support Others have talked about CPU pinning fixing the problem, I have yet to try that.

Thanks, and confirmed working here Another request (not so important, but if you feel like it/have time), would be the option to mount these ISO shares as optionally readonly. [x] Checkbox Read-only in the dialog => $info["readonly"] = true => "-r" to the command executed in the same line as the previous issue. Just a nice little extra touch, but nothing too important. Might also make sense on the other mounts? SMB/NFS, Disk? I'm not sure, maybe.

Just wanted you to be aware that I posted an issue on the Github issues. https://github.com/dlandon/unassigned.devices/issues/14 I've found that I couldn't mount ISOs that was dd'ed or qemu-img'd from physical disks. Unassigned-devices currently limits the mounting points to only CD/iso9660. I've posted an idea to a potential fix.

Hey Bungy, thanks for your help so far. I've booted a Win10 and installed Hyper-V manager succesfully through "Programs and Features". However, I still can't seem to boot a VM in Hyper-V, it errors with same error message as I originally had. Would you be able to try and see if your setup boots a VM in HyperV? For me it doesn't want to boot anything, no matter if I select a physical disk, or create a new vhd. Google doesn't give me much except the same problems using VMWare as main hypervisor. Edit: I'm afraid this leads back to the thread/bug that jonp is referencing: https://bugzilla.kernel.org/show_bug.cgi?id=106621 They specially state: "This, together with "-cpu host,-hypervisor,+vmx will allow Hyper-V to be installed. It will however not allow to start these Virtual Machines." I'm really curious as to whether your setup can boot the VM in HyperV bungy

Oh, thanks I'm already installing Win10 on SeaBios to try it. So I'm already doing it myself, I'll confirm here when done. Edit: Blargh! Maybe I could have just changed the XML to SeaBios instead. Anyways, I needed a secondary to experiment with anyways, so it's installing now anyways Update: Can confirm Hyper-V can install successful as soon as running on SeaBios. So I guess that's it.

Thanks Bungy, just compared your setup with my setup line by line and found: 1) I used Unraid 6.3.0 2) GPU Passthrough 3) I'm using Win10 you are using Server 2016 4) It seems your setup is on SeaBios and not OVMF. I've tried to resolve 1 and 2, upgraded unraid to 6.3.2 and using VNC. Still no luck. Only difference now is SeaBios vs OVMF and Windows 10 vs Server 2016. So question now becomes is it only Server 2016 that can do this? Shoudn't this also work with win 10? I've not been able to google anything that makes this a difference. Would seabios vs ovmf make any difference here? Maybe OVMF doesn't nest/support SLAT/EPT?

Update Thanks to Bungy's post I think I moved one step closer, however still no real success. Appending the kvm-intel nested to the syslinux config did something right I think. Before I couldn't install Hyper-V due to: "The processor does not have required virtualization capabilities". However no Windows says I can't install Hyper-V due to: "The processor does not have second level address translation (SLAT) capabilities". My CPU is 6800k and supports SLAT / EPT. So now I'm stuck here

The link that 1812 works perfectly, I used that thread to passthrough my primary gfx (1060 gtx) to windows vm. However the information is scattered all over the thread, and a mix of old and new information, so it took a bit of reading to get it right. However, all this information has been gathered and collected as a video guide by gridrunner here: https://lime-technology.com/forum/index.php?topic=52960.0

Wouldn't matter, unfortunately. I'm going to test out Bungy's post later today.

Wow.. Thanks jonp Although that's bad news for me Guess I'll have to try to see if I can get my p2v converted through other means. Looking at release notes, it looks as I can expect 6.4 to be in the range of at least 3-6 months. At least thanks for finding that KVM bug, now I know the source of the frustration

Thanks for clarifying jonp However that still doesn't really bring us closer. I see now that when I disable the Hyper-V setting on a VM I get the Nvidia passthrough problem that has been mentioned. By just enabling it, the problem is gone, which also shows that Unraid is already "faking" the vendor_id (with the text "none"?) Bungy wrote: Nested virtualization was disabled in 6.3rc9 and 6.3stable. It can be re-enable by adding these lines to the top of your /boot/config/go script: <code> echo "options kvm-intel nested=1" > /etc/modprobe.d/kvm-intel.conf echo "options kvm-amd nested=1" > /etc/modprobe.d/kvm-amd.conf </code> However even with that I still can't install/run Hyper-V VMs. I do not run Avast or other such software, so I'm really not concerned there. How do we enable nested virtualization? Is Bungy's tip correct? Or is there something missing to reenable nested virtualization? Would I be forced to downgrade to a Beta release? Linux 4.9.7-unRAID. root@Tower:~# cat /etc/modprobe.d/kvm-intel.conf options kvm-intel nested=1

No luck here either VM Guests won't start, error's about some Hyper-V component not running (it doesn't specify which component). Looking forward to see your XML Bungy

I think I solved it, with an additional note. I don't know if Buggy's post made a difference, but I'm guessing it did. However: I still couldn't install hyper-v through programs and features. Same message and greyed out as screenshot above. After a bit of googling and mumbling, I randomly stumbled on a microsoft link: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v By random chance I just attempted the powershell command written there: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All And success, it installed hyper, rebooted twice and I now have Hyper-V Manager and everything installed. NB: I have not yet tried booting anything through it, so whether it works or just installed I can't say yet. I'm keeping my hopes high, will try during the weekend. I'll update this thread/post if I have success.