MikeW Posted August 27, 2015 Share Posted August 27, 2015 I'm trying to run an OpenELEC VM, but I get a kernel panic which I think might be related to an IRQ, but I'm not sure. This is the end of the UnRAID syslog: Aug 27 15:49:23 unraid kernel: device vnet0 entered promiscuous mode Aug 27 15:49:23 unraid kernel: br0: topology change detected, sending tcn bpdu Aug 27 15:49:23 unraid kernel: br0: port 3(vnet0) entered forwarding state Aug 27 15:49:23 unraid kernel: br0: port 3(vnet0) entered forwarding state Aug 27 15:49:24 unraid kernel: vfio-pci 0000:0b:00.1: enabling device (0400 -> 0402) Aug 27 15:49:24 unraid kernel: irq 17: nobody cared (try booting with the "irqpoll" option) Aug 27 15:49:24 unraid kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.1.5-unRAID #3 Aug 27 15:49:24 unraid kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Extreme6, BIOS P2.30 05/26/2015 Aug 27 15:49:24 unraid kernel: 0000000000000000 ffff88084fa03e18 ffffffff816105e3 0000000000040001 Aug 27 15:49:24 unraid kernel: ffff88082baeea00 ffff88084fa03e48 ffffffff8107afcb 000000010513ec23 Aug 27 15:49:24 unraid kernel: ffff88082baeea00 0000000000000000 0000000000000011 ffff88084fa03e88 Aug 27 15:49:24 unraid kernel: Call Trace: Aug 27 15:49:24 unraid kernel: [] dump_stack+0x4c/0x6e Aug 27 15:49:24 unraid kernel: [] __report_bad_irq+0x2b/0xbe Aug 27 15:49:24 unraid kernel: [] note_interrupt+0x19d/0x227 Aug 27 15:49:24 unraid kernel: [] handle_irq_event_percpu+0xe0/0xf2 Aug 27 15:49:24 unraid kernel: [] handle_irq_event+0x3c/0x5e Aug 27 15:49:24 unraid kernel: [] handle_fasteoi_irq+0x7a/0xdb Aug 27 15:49:24 unraid kernel: [] handle_irq+0x1a/0x24 Aug 27 15:49:24 unraid kernel: [] ? __tick_nohz_idle_enter+0x27e/0x308 Aug 27 15:49:24 unraid kernel: [] do_IRQ+0x49/0xcd Aug 27 15:49:24 unraid kernel: [] common_interrupt+0x6e/0x6e Aug 27 15:49:24 unraid kernel: [] ? cpuidle_enter_state+0xb9/0x114 Aug 27 15:49:24 unraid kernel: [] ? cpuidle_enter_state+0x4f/0x114 Aug 27 15:49:24 unraid kernel: [] cpuidle_enter+0x12/0x14 Aug 27 15:49:24 unraid kernel: [] cpu_startup_entry+0x1e2/0x2b2 Aug 27 15:49:24 unraid kernel: [] rest_init+0x85/0x89 Aug 27 15:49:24 unraid kernel: [] start_kernel+0x415/0x422 Aug 27 15:49:24 unraid kernel: [] ? set_init_arg+0x56/0x56 Aug 27 15:49:24 unraid kernel: [] ? early_idt_handler_array+0x120/0x120 Aug 27 15:49:24 unraid kernel: [] x86_64_start_reservations+0x2a/0x2c Aug 27 15:49:24 unraid kernel: [] x86_64_start_kernel+0xe6/0xf5 Aug 27 15:49:24 unraid kernel: handlers: Aug 27 15:49:24 unraid kernel: [] vfio_intx_handler Aug 27 15:49:24 unraid kernel: Disabling IRQ #17 Aug 27 15:49:26 unraid kernel: kvm: zapping shadow pages for mmio generation wraparound Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x1c9 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored wrmsr: 0x1c9 data 3 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x1c9 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x1a6 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored wrmsr: 0x1a6 data 1ff Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x1a6 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x1a7 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored wrmsr: 0x1a7 data 1ff Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x1a7 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x3f6 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored wrmsr: 0x3f6 data 1ff Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x3f6 Aug 27 15:49:28 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x606 Aug 27 15:49:28 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x570 Aug 27 15:50:01 unraid crond[1700]: exit status 127 from user root /usr/local/sbin/monitor &> /dev/null Aug 27 15:50:16 unraid emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log libvirt/qemu/OpenELEC Radeon 6450.log And in my terminal window where I ssh into my unRAID box I get the following message: Message from syslogd@unraid at Aug 27 15:49:24 ... kernel:Disabling IRQ #17 I'm not sure what the problem is. If there's a better log file somewhere please let me know and I'll look at it. Also, the Radeon 6450 is plugged into a PCIe slot which connects to the PCH on an ASRock Z97 Extreme6 motherboard. The other PCIe slots are used. The strange thing is that I've had this working in the past. But for some reason it's not working now. I'm stuck so any help would be greatly appreciated. Thanks. Link to comment
jonp Posted August 27, 2015 Share Posted August 27, 2015 I'm trying to run an OpenELEC VM, but I get a kernel panic which I think might be related to an IRQ, but I'm not sure. This is the end of the UnRAID syslog: Aug 27 15:49:23 unraid kernel: device vnet0 entered promiscuous mode Aug 27 15:49:23 unraid kernel: br0: topology change detected, sending tcn bpdu Aug 27 15:49:23 unraid kernel: br0: port 3(vnet0) entered forwarding state Aug 27 15:49:23 unraid kernel: br0: port 3(vnet0) entered forwarding state Aug 27 15:49:24 unraid kernel: vfio-pci 0000:0b:00.1: enabling device (0400 -> 0402) Aug 27 15:49:24 unraid kernel: irq 17: nobody cared (try booting with the "irqpoll" option) Aug 27 15:49:24 unraid kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.1.5-unRAID #3 Aug 27 15:49:24 unraid kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Extreme6, BIOS P2.30 05/26/2015 Aug 27 15:49:24 unraid kernel: 0000000000000000 ffff88084fa03e18 ffffffff816105e3 0000000000040001 Aug 27 15:49:24 unraid kernel: ffff88082baeea00 ffff88084fa03e48 ffffffff8107afcb 000000010513ec23 Aug 27 15:49:24 unraid kernel: ffff88082baeea00 0000000000000000 0000000000000011 ffff88084fa03e88 Aug 27 15:49:24 unraid kernel: Call Trace: Aug 27 15:49:24 unraid kernel: [] dump_stack+0x4c/0x6e Aug 27 15:49:24 unraid kernel: [] __report_bad_irq+0x2b/0xbe Aug 27 15:49:24 unraid kernel: [] note_interrupt+0x19d/0x227 Aug 27 15:49:24 unraid kernel: [] handle_irq_event_percpu+0xe0/0xf2 Aug 27 15:49:24 unraid kernel: [] handle_irq_event+0x3c/0x5e Aug 27 15:49:24 unraid kernel: [] handle_fasteoi_irq+0x7a/0xdb Aug 27 15:49:24 unraid kernel: [] handle_irq+0x1a/0x24 Aug 27 15:49:24 unraid kernel: [] ? __tick_nohz_idle_enter+0x27e/0x308 Aug 27 15:49:24 unraid kernel: [] do_IRQ+0x49/0xcd Aug 27 15:49:24 unraid kernel: [] common_interrupt+0x6e/0x6e Aug 27 15:49:24 unraid kernel: [] ? cpuidle_enter_state+0xb9/0x114 Aug 27 15:49:24 unraid kernel: [] ? cpuidle_enter_state+0x4f/0x114 Aug 27 15:49:24 unraid kernel: [] cpuidle_enter+0x12/0x14 Aug 27 15:49:24 unraid kernel: [] cpu_startup_entry+0x1e2/0x2b2 Aug 27 15:49:24 unraid kernel: [] rest_init+0x85/0x89 Aug 27 15:49:24 unraid kernel: [] start_kernel+0x415/0x422 Aug 27 15:49:24 unraid kernel: [] ? set_init_arg+0x56/0x56 Aug 27 15:49:24 unraid kernel: [] ? early_idt_handler_array+0x120/0x120 Aug 27 15:49:24 unraid kernel: [] x86_64_start_reservations+0x2a/0x2c Aug 27 15:49:24 unraid kernel: [] x86_64_start_kernel+0xe6/0xf5 Aug 27 15:49:24 unraid kernel: handlers: Aug 27 15:49:24 unraid kernel: [] vfio_intx_handler Aug 27 15:49:24 unraid kernel: Disabling IRQ #17 Aug 27 15:49:26 unraid kernel: kvm: zapping shadow pages for mmio generation wraparound Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x1c9 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored wrmsr: 0x1c9 data 3 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x1c9 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x1a6 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored wrmsr: 0x1a6 data 1ff Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x1a6 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x1a7 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored wrmsr: 0x1a7 data 1ff Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x1a7 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x3f6 Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored wrmsr: 0x3f6 data 1ff Aug 27 15:49:27 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x3f6 Aug 27 15:49:28 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x606 Aug 27 15:49:28 unraid kernel: kvm [32069]: vcpu0 ignored rdmsr: 0x570 Aug 27 15:50:01 unraid crond[1700]: exit status 127 from user root /usr/local/sbin/monitor &> /dev/null Aug 27 15:50:16 unraid emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log libvirt/qemu/OpenELEC Radeon 6450.log And in my terminal window where I ssh into my unRAID box I get the following message: Message from syslogd@unraid at Aug 27 15:49:24 ... kernel:Disabling IRQ #17 I'm not sure what the problem is. If there's a better log file somewhere please let me know and I'll look at it. Also, the Radeon 6450 is plugged into a PCIe slot which connects to the PCH on an ASRock Z97 Extreme6 motherboard. The other PCIe slots are used. The strange thing is that I've had this working in the past. But for some reason it's not working now. I'm stuck so any help would be greatly appreciated. Thanks. There is actually a thread for support on this VM under the VM Templates subforum. That said, have you tried changing the machine type / bios type under advanced view? Link to comment
MikeW Posted August 27, 2015 Author Share Posted August 27, 2015 Yes, I tried OVMF and SeaBIOS with both Q35 and i44fx. It doesn't seem to matter which combination I used. Link to comment
jonp Posted August 27, 2015 Share Posted August 27, 2015 Yes, I tried OVMF and SeaBIOS with both Q35 and i44fx. It doesn't seem to matter which combination I used. Ok, a few things: 1 - Click "info" in the top right of the webGui. Does IOMMU say Enabled? 2 - Reboot into your motherboard BIOS and look for a setting for graphics and make sure it is set to integrated graphics (not PCIe) 3 - Do other VMs work with GPU pass through for you ok? 4 - Last option, review this section of the wiki and try passing the ROM file through the VM (will require you to edit the XML of the VM) Link to comment
MikeW Posted August 27, 2015 Author Share Posted August 27, 2015 Yes, I tried OVMF and SeaBIOS with both Q35 and i44fx. It doesn't seem to matter which combination I used. Ok, a few things: 1 - Click "info" in the top right of the webGui. Does IOMMU say Enabled? 2 - Reboot into your motherboard BIOS and look for a setting for graphics and make sure it is set to integrated graphics (not PCIe) 3 - Do other VMs work with GPU pass through for you ok? 4 - Last option, review this section of the wiki and try passing the ROM file through the VM (will require you to edit the XML of the VM) 1. Yes. 2. Confirmed. 3. Yes, multiple other VMs work fine. I have a Win8 VM with a GTX 680 working as well as a OE VM with a GTX 730. 4. I haven't tried this yet, but I have successfully passed this GPU to an OE VM in the past. The firmware on the Radeon 6450 has been flashed with a UEFI image. I'm wondering if when using enough resources concurrently if this is causing an IRQ resource allocation issue. Is that possible? Link to comment
jonp Posted August 28, 2015 Share Posted August 28, 2015 Yes, I tried OVMF and SeaBIOS with both Q35 and i44fx. It doesn't seem to matter which combination I used. Ok, a few things: 1 - Click "info" in the top right of the webGui. Does IOMMU say Enabled? 2 - Reboot into your motherboard BIOS and look for a setting for graphics and make sure it is set to integrated graphics (not PCIe) 3 - Do other VMs work with GPU pass through for you ok? 4 - Last option, review this section of the wiki and try passing the ROM file through the VM (will require you to edit the XML of the VM) 4. I haven't tried this yet, but I have successfully passed this GPU to an OE VM in the past. The firmware on the Radeon 6450 has been flashed with a UEFI image. Which "version" of the OE VM are you using (Beta 3 or Beta 2)? Which OE VM worked in the past? You mean 6.1-rc1 or what? I'm wondering if when using enough resources concurrently if this is causing an IRQ resource allocation issue. Is that possible? That shouldn't be a problem, but honestly can't say for sure. I can tell you that OVMF + AMD usually requires the ROM file to be specified for some reason. Link to comment
RobJ Posted August 28, 2015 Share Posted August 28, 2015 In my view, an "irq #: nobody cared" error is a software bug in something, but may be hard to know for sure which piece of software. The general advice would be to make sure the BIOS, all firmwares, all drivers/modules are fully up-to-date. I don't remember the command just now, but there's a way to identify all IRQ assignments, which can help isolate the potential modules at fault (plus the associated lower level drivers and firmware), plus the BIOS itself. Link to comment
MikeW Posted August 28, 2015 Author Share Posted August 28, 2015 In my view, an "irq #: nobody cared" error is a software bug in something, but may be hard to know for sure which piece of software. The general advice would be to make sure the BIOS, all firmwares, all drivers/modules are fully up-to-date. I don't remember the command just now, but there's a way to identify all IRQ assignments, which can help isolate the potential modules at fault (plus the associated lower level drivers and firmware), plus the BIOS itself. I ran the following command, but I'm not sure if this is what you were thinking of: root@unraid:~# cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 0: 32 0 0 0 0 0 0 0 IR-IO-APIC-edge timer 1: 3 0 0 0 0 0 0 0 IR-IO-APIC-edge i8042 7: 21 0 0 0 0 0 0 0 IR-IO-APIC-edge 8: 65 0 0 0 0 0 0 0 IR-IO-APIC-edge rtc0 9: 0 0 0 0 0 0 0 0 IR-IO-APIC-fasteoi acpi 12: 3 0 0 0 0 0 0 0 IR-IO-APIC-edge i8042 16: 115929756 0 0 0 0 0 0 0 IR-IO-APIC 16-fasteoi ehci_hcd:usb7, vfio-intx(0000:01:00.0) 17: 13146550 0 0 0 0 0 0 0 IR-IO-APIC 17-fasteoi vfio-intx(0000:01:00.1) 18: 7991 0 0 0 0 0 0 0 IR-IO-APIC 18-fasteoi 23: 33 0 0 0 0 0 0 0 IR-IO-APIC 23-fasteoi ehci_hcd:usb8 24: 0 0 0 0 0 0 0 0 DMAR_MSI-edge dmar0 25: 0 0 0 0 0 0 0 0 DMAR_MSI-edge dmar1 33: 581163 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd 34: 19 0 0 0 0 0 0 0 IR-PCI-MSI-edge vfio-msix[0](0000:09:00.0) 35: 446009 0 0 0 0 0 0 0 IR-PCI-MSI-edge vfio-msix[1](0000:09:00.0) 36: 66 0 0 0 0 0 0 0 IR-PCI-MSI-edge vfio-msix[2](0000:09:00.0) 37: 33 0 0 0 0 0 0 0 IR-PCI-MSI-edge vfio-msix[3](0000:09:00.0) 38: 34 0 0 0 0 0 0 0 IR-PCI-MSI-edge vfio-msix[4](0000:09:00.0) 39: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge vfio-msix[5](0000:09:00.0) 40: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge vfio-msix[6](0000:09:00.0) 41: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge vfio-msix[7](0000:09:00.0) 42: 13488 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd 43: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd 44: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd 45: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd 46: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd 47: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd 48: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd 49: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge xhci_hcd 50: 37289601 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth0 51: 10214141 0 0 0 0 0 0 0 IR-PCI-MSI-edge 0000:00:1f.2 52: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge 0000:08:00.0 53: 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge 0000:0a:00.0 54: 83334 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth1 55: 62230 0 0 0 0 0 0 0 IR-PCI-MSI-edge vfio-msi[0](0000:02:00.1) 56: 741467 0 0 0 0 0 0 0 IR-PCI-MSI-edge vfio-msi[0](0000:02:00.0) NMI: 4229 0 0 0 179 167 110 105 Non-maskable interrupts LOC: 69273006 108770121 87396232 91945305 90660055 71625115 66464587 63278298 Local timer interrupts SPU: 0 0 0 0 0 0 0 0 Spurious interrupts PMI: 4229 0 0 0 179 167 110 105 Performance monitoring interrupts IWI: 385 0 0 0 17 8 3 2 IRQ work interrupts RTR: 7 0 0 0 0 0 0 0 APIC ICR read retries RES: 18640635 15666419 12174127 11550390 113816994 119578607 114226137 103097481 Rescheduling interrupts CAL: 10480 26736 29720 25345 22701 22795 22342 22632 Function call interrupts TLB: 21520 15019 19146 16603 10067 4914 7053 7133 TLB shootdowns TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts MCE: 0 0 0 0 0 0 0 0 Machine check exceptions MCP: 557 557 557 557 557 557 557 557 Machine check polls HYP: 0 0 0 0 0 0 0 0 Hypervisor callback interrupts ERR: 21 MIS: 0 Link to comment
MikeW Posted August 28, 2015 Author Share Posted August 28, 2015 Just wanted to add another piece of data. When I try to start my OE with the Radeon interrupt 17 is assigned to: 17: 13568606 0 0 0 0 0 0 0 IR-IO-APIC 17-fasteoi vfio-intx(0000:01:00.1), vfio-intx(0000:0b:00.1) The relevant devices are: 01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 680] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1) 0b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 0b:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] Again, I'm not sure what to make of this, if anything. The Nvidia GPU is currently passed through to another OE VM which is working fine. Link to comment
jonp Posted August 28, 2015 Share Posted August 28, 2015 Just wanted to add another piece of data. When I try to start my OE with the Radeon interrupt 17 is assigned to: 17: 13568606 0 0 0 0 0 0 0 IR-IO-APIC 17-fasteoi vfio-intx(0000:01:00.1), vfio-intx(0000:0b:00.1) The relevant devices are: 01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 680] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1) 0b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 0b:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] Again, I'm not sure what to make of this, if anything. The Nvidia GPU is currently passed through to another OE VM which is working fine. What version of OpenELEC and how did you get it on unRAID? Link to comment
MikeW Posted August 29, 2015 Author Share Posted August 29, 2015 It's OE version 6.0.0 Beta3 and unRAID version 6.1-rc6. I used the VM template for OE during the VM creation. The same thing happened with 6.0.0 Beta2. Link to comment
jonp Posted August 29, 2015 Share Posted August 29, 2015 In your first post, you mention having gotten this to work in the past. Was that with the same GPU? What version of OE worked with this GPU previously? Link to comment
MikeW Posted August 29, 2015 Author Share Posted August 29, 2015 In your first post, you mention having gotten this to work in the past. Was that with the same GPU? What version of OE worked with this GPU previously? I was using 6.0.0. Beta2 last time with unRAID version 6.1-rc2 (I think). I think I had it working with the latest version as well. There is a test I want to run. I have three VMs with GPU passthrough: 1. Windows 8 with a GTX 680 2. OE with a GTX 730 3. OE with a Radeon 6450 I want to test this with the Win8 VM turned off. Right now it's on and my son is using it so I need to wait to test it, but that's the only thing I can think of that might be different from when the OE/Radeon was working. And the GTX 680 and the Radeon are both assigned to IRQ 17. I should be able to test this in a couple hours. Link to comment
jonp Posted August 29, 2015 Share Posted August 29, 2015 In your first post, you mention having gotten this to work in the past. Was that with the same GPU? What version of OE worked with this GPU previously? I was using 6.0.0. Beta2 last time with unRAID version 6.1-rc2 (I think). I think I had it working with the latest version as well. There is a test I want to run. I have three VMs with GPU passthrough: 1. Windows 8 with a GTX 680 2. OE with a GTX 730 3. OE with a Radeon 6450 I want to test this with the Win8 VM turned off. Right now it's on and my son is using it so I need to wait to test it, but that's the only thing I can think of that might be different from when the OE/Radeon was working. And the GTX 680 and the Radeon are both assigned to IRQ 17. I should be able to test this in a couple hours. Ok, let me know how that test goes!! Link to comment
MikeW Posted August 29, 2015 Author Share Posted August 29, 2015 OK, I shut down the Win8 VM and I still have the problem. In fact, I shut down all VMs and even added the enable_msi=1 setting to the OE VM and it still wouldn't boot. The OE VM would give a panic during boot. But I didn't see the same IRQ 17 issue. I then rebooted the unRAID server and started the OE(Radeon) VM followed by the OE(GTX730) VM then the Win8 VM. I'm playing two movies at the same time and running a 3DMark 11 benchmark on the Win8 VM and everything is working right now. So, I have no idea what the previous problem was, but it seems like something got hosed in the unRAID kernel which required a reboot. I probably won't spend any more time on this and I'll just hope that it doesn't happen very often, but if it does then I'll just reboot the system. ***UPDATE*** Sometimes when I shut down the OE (Radeon) VM then I can't restart it again without rebooting the unRAID server. I haven't been able to 100% reproduce this, but once it gets hosed only an unRAID reboot will fix it. Link to comment
MikeW Posted August 29, 2015 Author Share Posted August 29, 2015 And to add another piece of data.... When the OE (Radeon) VM fails to start I can't even stop the unRAID array. When I check the box to stop the array I keep getting the following messages across the bottom of the screen: "Unmounting disks...Retry unmounting disk share(s)..." I have to run "shutdown -r now" in an ssh window to get it to reboot. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.