Vanum

Here are my BIOS Pictures: https://imgur.com/a/iGFoFdE

I ran memtest and got my first pass. I didn't receive any error messages! Why would it I be able to boot into Windows, but I can't boot into a Linux distro? That struck me as really weird. Sent from my Pixel 3 XL using Tapatalk

I will run it through a pass now and see if it runs into anything. Sent from my Pixel 3 XL using Tapatalk

Yes, I've booted into safe mode with and without GUI. Same results. Gets hung on the same place. I started memtest, but wasn't quite ready to just let it from for 24 hours like some people online were suggesting. Sent from my Pixel 3 XL using Tapatalk

Hello friends and family! I'm reaching out to you guys because I'm stuck on my latest server. I've been using Unraid for quite some time now and usually I can figure these types of things out, but my Google Fu doesn't appear to be leading me to answer. I was having issues accessing the Web UI, so I decided to reboot the server through normal means. I restarted the server and attempted to reconnect to the Web UI. No dice. I hard powered off the server and rebooted again. Still no dice. I plugged the server up to a monitor and started looking at verbose logging. Attached is the console log of where it got stuck at. --- Things I've tried: I've built a new USB stick and copied over the config file I've built a new USB stick with stock stable Unraid I've built a new USB stick with 6.10 Unraid I have removed the CMOS battery Attempted to boot with stock settings Attempted to boot with adjusted settings for Unraid Used existing BIOS version, F20 and upgraded version, F21a I put in a separate USB controller and attempted to boot to Unraid I unplugged all other USB devices and left only my mouse and keyboard I have removed all sticks of RAM and attempted to boot with each one of them. I have removed all HDDs and SSDs and attempted to boot Removed both my graphics cards and attempted to just boot with onboard graphics. I've attempted to boot to Windows 10 installer (I am able to get to the install screen and browse at what drives I would like to install on) I am not able to get into Ubuntu Live CD for some reason. It just freezes at the Gigabyte logo screen I am also not able to launch Manjaro Live CD either. Same results. --- Specs GIGABYTE Z490 Vison G - BIOS Firmware 21a i9-10900K @ 5.00GHz cooled with a Noctua NH-D15 G.SKILL TridentZ RGB - 24GB @ stock speeds 24 TB Array - Mech storage 500 GB Cache Drive - SSD storage (2x) 256 GB Unassigned SSDs for VM 3070 RTX 3080 RTX TI --- Thank you all in advanced for this help! I really try not to bug you guys, but I've been at this since 12 PM today and I've spent almost 7 hours with what feels like no progress >_>

I did not. I looked everywhere and I wasn't able to find anything that would control the RGB headers via the host. Only via the BIOS and that wouldn't always last. I haven't checked around since posting this to see if anything has changed since then. So there might be a solution out there now!

@ClintE, That is what I thought. The system would just shut down until it cooled off and plus the CPU through iCue is only reporting 72c and Unraid is changing from 100c. It is exactly 100c the entire time. @John_M Yeah, I saw that 6.6.5 was released earlier this month. I will upgrade to that when I get home. Maybe I'll be able to use my SATA expansion card.

Hey John_M, Thank you for the quick response. I didn't mention that the pump is reporting water is pumping according to the BIOS and iCue. Even so, I am still at a dead end as to why it wouldn't be cooling if both the fan and the pump are reporting numbers. I have this issue a while back when I attempted to install an expansion card for more SATA ports. It crippled the performance of my 1080 TI, so I took them out and just got bigger drives instead. I didn't know if maybe there was a connection.

Yeah, I have considered it. I figure it would at least fail while it was running though and not just a restart. Also, I just checked the logs and I am getting IRQ 16: nobody cared. I've heard this can really slow down some devices. I wonder if that is somehow screwing with my devices. Nov 27 03:28:16 Azeroth kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Nov 27 03:28:16 Azeroth kernel: CPU: 8 PID: 0 Comm: swapper/8 Not tainted 4.18.8-unRAID #1 Nov 27 03:28:16 Azeroth kernel: Hardware name: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming 7/Z370 AORUS Gaming 7, BIOS F11 10/30/2018 Nov 27 03:28:16 Azeroth kernel: Call Trace: Nov 27 03:28:16 Azeroth kernel: <IRQ> Nov 27 03:28:16 Azeroth kernel: dump_stack+0x5d/0x79 Nov 27 03:28:16 Azeroth kernel: __report_bad_irq+0x32/0xac Nov 27 03:28:16 Azeroth kernel: note_interrupt+0x1d3/0x224 Nov 27 03:28:16 Azeroth kernel: handle_irq_event_percpu+0x4c/0x6a Nov 27 03:28:16 Azeroth kernel: handle_irq_event+0x33/0x51 Nov 27 03:28:16 Azeroth kernel: handle_fasteoi_irq+0x8c/0xfc Nov 27 03:28:16 Azeroth kernel: handle_irq+0x1c/0x1f Nov 27 03:28:16 Azeroth kernel: do_IRQ+0x43/0xbf Nov 27 03:28:16 Azeroth kernel: common_interrupt+0xf/0xf Nov 27 03:28:16 Azeroth kernel: </IRQ> Nov 27 03:28:16 Azeroth kernel: RIP: 0010:cpuidle_enter_state+0xe8/0x141 Nov 27 03:28:16 Azeroth kernel: Code: ff 45 84 ff 74 1d 9c 58 0f 1f 44 00 00 0f ba e0 09 73 09 0f 0b fa 66 0f 1f 44 00 00 31 ff e8 fb bc be ff fb 66 0f 1f 44 00 00 <48> 2b 1c 24 b8 ff ff ff 7f 48 b9 ff ff ff ff f3 01 00 00 48 39 cb Nov 27 03:28:16 Azeroth kernel: RSP: 0018:ffffc90003227ea0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdc Nov 27 03:28:16 Azeroth kernel: RAX: ffff88084ec20c00 RBX: 000000032d18fc58 RCX: 000000000000001f Nov 27 03:28:16 Azeroth kernel: RDX: 000000032d18fc58 RSI: 0000000000000000 RDI: 0000000000000000 Nov 27 03:28:16 Azeroth kernel: RBP: ffff88084ec28e40 R08: 000000258c55163c R09: 0000000000000002 Nov 27 03:28:16 Azeroth kernel: R10: 0000000000000000 R11: 071c71c71c71c71c R12: 0000000000000001 Nov 27 03:28:16 Azeroth kernel: R13: 0000000000000001 R14: ffffffff81e57778 R15: 0000000000000000 Nov 27 03:28:16 Azeroth kernel: do_idle+0x192/0x20e Nov 27 03:28:16 Azeroth kernel: cpu_startup_entry+0x6a/0x6c Nov 27 03:28:16 Azeroth kernel: start_secondary+0x197/0x1b2 Nov 27 03:28:16 Azeroth kernel: secondary_startup_64+0xa5/0xb0 Nov 27 03:28:16 Azeroth kernel: handlers: Nov 27 03:28:16 Azeroth kernel: [<00000000a3d7759a>] i801_isr [i2c_i801] Nov 27 03:28:16 Azeroth kernel: Disabling IRQ #16

Good morning all! This is my last hail Mary before I switch to air cooling that can be easily controlled by Unraid. Maybe with your brains combined, you can help me address this issue. I shut down my Unraid server last night to install a new 8TB drive (white label WD, black Friday deal). I unplugged the old drive after transferring everything off of it and plugged in the new drive. I booted into the BIOS to make sure I could see it and then proceeded to launch into Unraid to configure it. I had some problems getting into the GUI right off the bat, so I restarted the machines a couple of times. Finally, I was able to get into the GUI and configure the drive. I noticed the CPU temps were sitting at 100c and my AIO fans on the radiator were going full blast. I shut down the Unraid server and went back to the BIOS. I was unable to alter the fans by any means from the BIOS. Since I couldn't control the fans there, I booted the server back up and jumped into my Windows VM. I have the iCue software that controls the AIO water cooler installed on this VM, so I attempted to control it here. Same thing. The fans/pump are changing their profiles and the CPU temp is reading 72c instead of 100c. Extra notes: This incident is not the first time this has happened and it happened exactly the same way another time. I was replacing a drive with a new larger drive, booted up the server to configure, and the temps are stuck at 100c. I replaced the AIO thinking it was just a bad AIO. But now, it has me wondering. I've had the first AIO for almost a year and a half. I've had the second one about 3 months. I am aware that I can boot into Windows using bare metal and install iCue, but I am trying to configure/fix the issue without doing that if possible. I am trying to figure out how replacing a hard drive and my AIO stop working could be correlated. I haven't been able to find a thread to connect them The CPU is actually being throttled down to about 2 GHz from my normal 3.7 GHz/4.3 GHz Things I've Tried Thermal paste looks good Screws are tight on the mobo around the heatsink I'm not using a washer to make them fit better CPU fans are controls by PWM instead of Auto CPU fans are set to Full per Corsair's guidelines (changing this to any other setting doesn't change anything) Created custom fan profiles on BIOS or within iCue Reinstalled the drivers for the pump Reinstalled iCue Reinstalled the Corsair Link software (older version to manage pumps) Unplugged the fan connector and USB header connected to the heatsink and replugged them BIOS firmware upgrade (stock profile loaded afterward) Unplug the hard drive and attempt to boot without it (no change) Radiator and fans are clean, but I did blow some air through each of them. I was working on it all last night, but I did have to concede as it was approaching 2:00 AM. I would love for some suggestions to try when I get home tonight. Thank you in advance for your help! I am sure the others who haven't spoken up about their issues will appreciate it as well. -Vanum Diagnostics package attached! azeroth-diagnostics-20181127-0410.zip

Hello LimeTech! First off, this is not my first unRaid server. This is actually my third, so talk tech-y to me I have purchased the Z370 AORUS Gaming 7 motherboard with plans of building a 2-in-1 rig for me and the wife. Since this motherboard has a couple RGB headers, I wanted to know if I was going to be able to control these either through the host or can they be passed through to one of my VMs. If they cannot be controlled through the host or one of the clients, I can control them through the BIOS. Obviously that isn't ideal as I don't plan on seeing the BIOS screen very much since the server will always be on. Thanks for your help!

Yeah, I remember seeing that patch and if I remember correctly it was from AGES ago. Well before some of the best features of UnRaid were added. You could attempt to use that patched kernel, but you would have to run an older version of UnRaid. If you want to get further in your system without crashing, I would only have the bare minimum selected when you are trying to boot up. At least until you can get your normal drivers installed. Then, start introducing your other devices one by one until you have a stable VM. Thanks,

Hello Dontjudgememonkey, I am sure you have found out by now that you are not going to be able to get your Elgato HD Pro passed through to your VM. See below my quest to get this card working in unRaid. I had to go back to a normal desktop until they figure out how to make this work... Let me know if you end up finding something different!

Hello to anyone who else is having this issue. Looks like the issue related to this card has no support for Linux. I have asked Elgato if they have any plans to create a Linux driver and they currently do not. For now, I am going to switch my unRaid server off and switch back to a standard desktop. If someone else comes up with another solution, I would love to know! I love my unRaid server and I cannot wait to go back Thank you all!

Good morning all! Another wannabe streamer here asking for help on getting their Elgato HD Pro to work with their Unraid server. I really don't want to go back to a normal build as I LOVE UNRAID AND ALL OF ITS AMAZING FEATURES. I have read a couple articles on this very issue and it looks like the only thing that can get this to work is to patch the kernel. The only problem is the patch was written for an older version of Unraid (~4.0). Maybe since some time has passed, someone has come up with a new way to do this? I have tried adding it to the XML file - didn't work I have tried stubbing it on the sysconfig file - didn't work PCI Info [12ab:0380] 81:00.0 Non-VGA unclassified device: YUAN High-Tech Development Co., Ltd. Device 0380 (rev ff) Error message qemu-system-x86_64: -device vfio-pci,host=01:00.0,id=hostdev3,bus=pci.0,addr=0x7: vfio: Error: Failed to setup INTx fd: Device or resource busy qemu-system-x86_64: -device vfio-pci,host=01:00.0,id=hostdev3,bus=pci.0,addr=0x7: Device initialization failed qemu-system-x86_64: -device vfio-pci,host=01:00.0,id=hostdev3,bus=pci.0,addr=0x7: Device 'vfio-pci' could not be initialized My Precious: CPU: Intel Core i7 4790K Motherboard: GIGABYTE GA-Z97X-UD5H SSD: Samsung SSD 850 EVO 250GB (2x) Disk Array: Western Digital Blue 1TB (3x) UnRaid: 16GB PNY Flash Drive RAM: G.SKILL Ripjaws Series 24GB (2 x 4GB, 2 x 8GB) GPU1: EVGA GeForce GTX 1070 SC (Slot 1) GPU2: EVGA GeForce GTX 970 04G-P4-2974-RX 4GB SC GAMING (Slot 2) Case: COOLER MASTER MASTERBOX 5 PCI-E USB Controller: Rosewill RC-508 -USB Chipset: Renesas uPD720201 Any help is greatly appreciated as I don't feel complete without my Unraid server and I want to show off my Unraid server on my channel while I stream! "Help me nerdy-wan-kenobi! You're my only hope!" - Vanum

Hello unRaid! I want to create a power user account on my unRaid server that is able to manage VMs, but not manage anything else on the GUI. Is that possible? Thanks!

Bump with an update! So...I am still trying to get a second VM running that i can do some gaming on. I have turned off Hyper-V and also moved the card to different slots on the mobo. I am able to boot up Win10 after reassigning the card to the VM. My other VM isn't seeing the 550 TI still... Also, I thought maybe I'd try a different card so I stole my wife's graphics card and gave that a shot. No go. It would not boot up on the second VM either. Thank you all!

Awesome! It looks like you got farther than I got the first time. My Mobo has a Renesas USB controller and wouldn't play nice with the Oculus Rift Sensor. I ended up getting one of the recommended cards to get it to work. If I was you, I would try passing through all of the Oculus Rift USB devices to your VM first and then give it a go. If you aren't getting your Oculus rift Sensor to play nice with your VM, then purchase the Inateck card that is recommended by Oculus. USB PCIe Card: https://www.amazon.com/gp/product/B00FPIMJEW Thanks!

Hey wedge22! If you have everything up and running, I would suggest you download the Oculus Compatibility Tool and make sure Oculus Home will see all your hardware. https://ocul.us/compat-tool Post your results when you get them back!

Posting here might actually help... Good evening! I am trying to pass through my GeForce 970 to macOS 10.11, but I can't get it to boot. I keep getting an error. Next question would be...how do I pass through my mouse and keyboard with QEMU commands. I have had the awfullest luck with them. Error: internal error: process exited while connecting to monitor: 2016-11-02T23:45:17.224833Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error opening /dev/vfio/14: Operation not permitted 2016-11-02T23:45:17.224857Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 14 2016-11-02T23:45:17.224863Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed XML: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>macOS</name> <uuid>cf5aa9c4-c70c-4b00-bb27-2125bc8fcedc</uuid> <metadata> <vmtemplate xmlns="unraid" name="macOS" icon="/mnt/user/domains/macOS/OSX-10.12.png"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/358dc26b-25c9-45ed-306e-469ceccde831_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>Penryn</model> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/user/domains/macOS/sierra_usb'/> <target dev='hda' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/user/domains/macOS/vdisk1.img'/> <target dev='hdc' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:00:20:30'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </interface> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=funnystatementhere'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> PCI Devices: 00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06) 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) 00:01.2 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x4 Controller [8086:0c09] (rev 06) 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) 00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB xHCI Controller [8086:8cb1] 00:16.0 Communication controller [0780]: Intel Corporation 9 Series Chipset Family ME Interface #1 [8086:8cba] 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-V [8086:153b] 00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset Family HD Audio Controller [8086:8ca0] 00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 [8086:8c90] (rev d0) 00:1c.2 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 3 [8086:8c94] (rev d0) 00:1c.3 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 [8086:8c96] (rev d0) 00:1c.6 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 7 [8086:8c9c] (rev d0) 00:1f.0 ISA bridge [0601]: Intel Corporation 9 Series Chipset Family Z97 LPC Controller [8086:8cc4] 00:1f.2 SATA controller [0106]: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] [8086:8c82] 00:1f.3 SMBus [0c05]: Intel Corporation 9 Series Chipset Family SMBus Controller [8086:8ca2] 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GM204 High Definition Audio Controller [10de:0fbb] (rev a1) 02:00.0 USB controller [0c03]: Fresco Logic FL1100 USB 3.0 Host Controller [1b73:1100] (rev 10) 04:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller [1969:e091] (rev 10) 05:00.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 41) 07:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller [1b4b:9172] (rev 12) IOMMU Groups: /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/2/devices/0000:00:01.2 /sys/kernel/iommu_groups/3/devices/0000:00:02.0 /sys/kernel/iommu_groups/4/devices/0000:00:03.0 /sys/kernel/iommu_groups/5/devices/0000:00:14.0 /sys/kernel/iommu_groups/6/devices/0000:00:16.0 /sys/kernel/iommu_groups/7/devices/0000:00:19.0 /sys/kernel/iommu_groups/8/devices/0000:00:1b.0 /sys/kernel/iommu_groups/9/devices/0000:00:1c.0 /sys/kernel/iommu_groups/10/devices/0000:00:1c.2 /sys/kernel/iommu_groups/11/devices/0000:00:1c.3 /sys/kernel/iommu_groups/12/devices/0000:00:1c.6 /sys/kernel/iommu_groups/13/devices/0000:00:1f.0 /sys/kernel/iommu_groups/13/devices/0000:00:1f.2 /sys/kernel/iommu_groups/13/devices/0000:00:1f.3 /sys/kernel/iommu_groups/14/devices/0000:01:00.0 /sys/kernel/iommu_groups/14/devices/0000:01:00.1 /sys/kernel/iommu_groups/15/devices/0000:02:00.0 /sys/kernel/iommu_groups/16/devices/0000:04:00.0 /sys/kernel/iommu_groups/17/devices/0000:05:00.0 /sys/kernel/iommu_groups/18/devices/0000:07:00.0 Thank you so much!

Hey pmuk, Just wanting to give you my two cents on this topic. I have an Oculus Rift that is working inside a Windows 10 VM. Inateck KT4005: This card uses the Renesas chipset and as you might have found out by now, that is "not supported" by Oculus Home even on a bare metal setup or at least that is what others have reported. My Solution: I ended up passing through my onboard USB Controller and using my extra PCIe USB 3.0 card for the unRaid thumb drive; this is a little cumbersome, but effective. Another Solution: You can try the Inateck card that is recommended by Oculus on their forums: https://www.amazon.com/Inateck-Superspeed-Ports-PCI-E-Expansion/dp/B00FPIMICA Let me know if I can help with getting this working for ya! Thanks!

Good evening! I am trying to pass through my GeForce 970 to macOS 10.11, but I can't get it to boot. I keep getting an error. Next question would be...how do I pass through my mouse and keyboard with QEMU commands. I have had the awfullest luck with them. Error: internal error: process exited while connecting to monitor: 2016-11-02T23:45:17.224833Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error opening /dev/vfio/14: Operation not permitted 2016-11-02T23:45:17.224857Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 14 2016-11-02T23:45:17.224863Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed XML: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>macOS</name> <uuid>cf5aa9c4-c70c-4b00-bb27-2125bc8fcedc</uuid> <metadata> <vmtemplate xmlns="unraid" name="macOS" icon="/mnt/user/domains/macOS/OSX-10.12.png"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/358dc26b-25c9-45ed-306e-469ceccde831_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>Penryn</model> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/user/domains/macOS/sierra_usb'/> <target dev='hda' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/user/domains/macOS/vdisk1.img'/> <target dev='hdc' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:00:20:30'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </interface> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=funnystatementhere'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> PCI Devices: 00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06) 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) 00:01.2 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x4 Controller [8086:0c09] (rev 06) 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) 00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB xHCI Controller [8086:8cb1] 00:16.0 Communication controller [0780]: Intel Corporation 9 Series Chipset Family ME Interface #1 [8086:8cba] 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-V [8086:153b] 00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset Family HD Audio Controller [8086:8ca0] 00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 [8086:8c90] (rev d0) 00:1c.2 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 3 [8086:8c94] (rev d0) 00:1c.3 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 [8086:8c96] (rev d0) 00:1c.6 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 7 [8086:8c9c] (rev d0) 00:1f.0 ISA bridge [0601]: Intel Corporation 9 Series Chipset Family Z97 LPC Controller [8086:8cc4] 00:1f.2 SATA controller [0106]: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] [8086:8c82] 00:1f.3 SMBus [0c05]: Intel Corporation 9 Series Chipset Family SMBus Controller [8086:8ca2] 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GM204 High Definition Audio Controller [10de:0fbb] (rev a1) 02:00.0 USB controller [0c03]: Fresco Logic FL1100 USB 3.0 Host Controller [1b73:1100] (rev 10) 04:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller [1969:e091] (rev 10) 05:00.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 41) 07:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller [1b4b:9172] (rev 12) IOMMU Groups: /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/2/devices/0000:00:01.2 /sys/kernel/iommu_groups/3/devices/0000:00:02.0 /sys/kernel/iommu_groups/4/devices/0000:00:03.0 /sys/kernel/iommu_groups/5/devices/0000:00:14.0 /sys/kernel/iommu_groups/6/devices/0000:00:16.0 /sys/kernel/iommu_groups/7/devices/0000:00:19.0 /sys/kernel/iommu_groups/8/devices/0000:00:1b.0 /sys/kernel/iommu_groups/9/devices/0000:00:1c.0 /sys/kernel/iommu_groups/10/devices/0000:00:1c.2 /sys/kernel/iommu_groups/11/devices/0000:00:1c.3 /sys/kernel/iommu_groups/12/devices/0000:00:1c.6 /sys/kernel/iommu_groups/13/devices/0000:00:1f.0 /sys/kernel/iommu_groups/13/devices/0000:00:1f.2 /sys/kernel/iommu_groups/13/devices/0000:00:1f.3 /sys/kernel/iommu_groups/14/devices/0000:01:00.0 /sys/kernel/iommu_groups/14/devices/0000:01:00.1 /sys/kernel/iommu_groups/15/devices/0000:02:00.0 /sys/kernel/iommu_groups/16/devices/0000:04:00.0 /sys/kernel/iommu_groups/17/devices/0000:05:00.0 /sys/kernel/iommu_groups/18/devices/0000:07:00.0 Thank you so much!

My disk utility can't erase the virtual disk. It shows up as "Apple read/write media," Clicking erase defaults to format unknown in the drop down, but no matter what format I choose it says Erase process has failed. Click Done to continue. Further investigation shows the error could not unmount disk, but the disk was never mounted in the first place... Move the image to Desktop and format it from there. I was unable to format my image file on the root drive as well. Thanks!

Q35 did not work either. Before I brought out my spare hard drive and attempted to install Windows 10 bare metal, I decided to pass through one of my motherboard's built USB controllers and leave the USB 3.0 card for unRaid. I booted successfully into unRaid and brought up my Windows 10 and reran the Oculus Setup. Everything installed without fail! Oculus Rift Sensor is running at USB 3.0. Now, the only issue I seem to be having is a very, very, very slight judder when I turn my head too fast, which is abnormal compared to the bare metal build. I have a couple errors in my Event Viewer I am going to sort through that may help identify the culprit. I will link them to this ticket for the next me.

Oculus Home: Yes, Oculus home says the sensor is experiencing high latency and the USB type indicator shows USB 2.0 as the type. USB Assignment: Also, I have tried directing passing each of the devices through to the VM, but the Oculus is a tricky piece of equipment. When you try to pass the Oculus Rift (headset) through with it is dormant or not in use, some of the USB devices within the unRaid GUI don't show up and the Oculus Rift Sensor is not even picked up by Oculus Home. I have Drivers: I have tried the Windows 10 drivers that are assigned when the card was first registered and also the stock drivers from the manufacturer's website. Windows 10 drivers has poor tracking and the Manufacturer's drivers has no tracking. I'll try Q35 on a test VM and see if it works. I might also try to use the USB Card on a vanilla Win10 with bare metal just to go a step farther. If it fails there, I can say it has to the card HA! I'll keep that in mind. If I don't return to the forum for a while, you will know what happened! Thanks, Vanum