xioustic

Members
  • Posts

    22
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

xioustic's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. Marv, Yes, I think this can be just done on the syslinux.cfg file in the USB drive at /syslinux/syslinux.cfg. Find the line that says "append" for your boot menu option, and add ",acpi=debug" to the end of it. Thanks for the reply, I'll be trying this solution later. Had abandoned unRAID up to this point.
  2. Any image should work I think; the binary is built static which means it's an entirely self-contained 64-bit executable. The original release was not by default. Ionly used Debian Jessie because that's what op did and I already have that image on my system (so it doesn't take up additional room for me). Try building with the FROM line changed and let me know if you have any issues. If you point me at documentation or a guide to create an unRAID template I can probably put that together.
  3. Hey guys, I've just randomly taken up this project because I just dug my PS3 out of storage. Repo is here (directly forked from latest webman-MOD): https://github.com/xioustic/ps3netsrv It includes a pre-built static binary and Dockerfile to pull the latest binary and create the image exactly like OPs repo/Dockerfile. Cheers. FROM debian:jessie ADD https://github.com/xioustic/ps3netsrv/raw/master/bin/ps3netsrv64 / RUN chmod +x ps3netsrv64 && mkdir /games VOLUME ["/games"] EXPOSE 38008 CMD ["/ps3netsrv64", "/games"]
  4. So I've given up on fixing this and rolled back to the Clover version gridrunner supplies in his YouTube videos. I tried isolcpus, pinning CPUs and EmulatorPins per the thread I linked in EDIT2 but no luck there with QEMU enabled or off in the Clover settings. Will keep an eye out for other solutions posted here or elsewhere; the only other success I've seen from others in the thread are manually patching and building Clover, which is a bit more work than I'd want to tackle. I assume this is something gridrunner did to the files in the "EFI" folder?
  5. gridrunner: Thanks a ton for your work. I've been able to get Xcode installed on 10.12.2 which is my bare minimum to compile what I need for my work, so now I don't have to use my underspecced MacBook Air anymore. I have one issue (which I can easily rollback with a qemu snapshot, but I still want to resolve): I'm trying to update Clover to maybe get FileVault2 working (since that's something supported later than the version you give us in your "sierra kvm unraid" folder.) I downloaded the latest clover pkg installer, hit continue up until I could hit "customize", then I set the settings per the image below (only checking "Install for UEFI booting only" and "Install Clover in the ESP". Everything seems to boot fine, the bootloader shows the new version number (3961), but now lots of things are in "slow motion". For example, if I right click the desktop and then unclick the context menu, it fades out veeeeeery slowly. Most transition effects like that are unbearably slow. Not sure how else to describe it. In advance of questions, I used kdiff3 to compare the EFI partition contents to the "EFI" folder you give us in your "sierra kvm unraid" package to show the difference. Below is the diff of file contents (+ for added, - for removed, U for updated): + EFI/CLOVER/drivers32/FSInject-32.efi + EFI/CLOVER/drivers32/Ps2MouseAbsolutePointerDxe-32.efi + EFI/CLOVER/drivers64UEFI/AppleImageCodec-64.efi + EFI/CLOVER/drivers64UEFI/AppleKeyAggregator-64.efi + EFI/CLOVER/drivers64UEFI/AppleUITheme-64.efi U EFI/CLOVER/drivers64UEFI/DataHubDxe-64.efi + EFI/CLOVER/drivers64UEFI/FirmwareVolume-64.efi U EFI/CLOVER/drivers64UEFI/FSInject-64.efi U EFI/CLOVER/drivers64UEFI/OsxFatBinaryDrv-64.efi + EFI/CLOVER/drivers64UEFI/SMCHelper-64.efi U EFI/CLOVER/tools/bdmesg.efi U EFI/CLOVER/tools/Shell64U.efi U EFI/CLOVER/CLOVERX64.efi Did I do something wrong? Can I roll back one or remove some of those files (since I am assuming maybe you had a special patched version in your pack)? Is this a known issue in r3961? Is there more information I can provide to help diagnose this? My XML file hasn't changed, but perhaps there's a Clover or macOS bootlog that I can provide a before and after copy of? Has anyone successfully updated Clover to a newer version than what's in the "sierra kvm unraid" EFI folder? Thanks again! EDIT: I guess one more thing; I'm only using VNC to use the system at this point, so no unique hardware constraints AFAIK. EDIT2: Following the rabbit hole of this thread, still no luck though. I did notice if I untoggle the QEMU setting under Clover Configurator -> CPU that the machine now runs at super speed (unusable) instead of slow motion (slightly usable), so the issue must be related.
  6. You beautiful human being! I just started working on this again (after preparing for a wipe) and yours was the last ditch change I attempted (switching to USB Mode: 3.0 (XHCI)). My Dell keyboard now works at the password bootloader! I can stay encrypted and not have to change SeaBIOS/re-create the VM/stay on 6.1. The 0.1 Bitcoin bounty is yours if you want (now worth closer to $80), just post a Bitcoin address via PM to me or on this post. Cheers!
  7. Booting with VNC worked; I was able to type the password and disable the encrypted bootloader from within windows. From there I tried an identical VM but with OVMF with Nvidia passthrough, no luck (no video output to screen). Tried toggling the Hyper-V option to Off, still no dice. Tried switching back the Hyper-V setting to On and using VNC without Nvidia, got video output but it pushes me to the EFI Shell. I booted the Windows disk (fs0:/efi/boot/bootx64.efi) and tried Startup Repair from there. No luck. Moved to the repair Command Prompt. Tried to enter "C:", drive not found. Tried "diskpart" and "list disk", but no disks found. Tried booting to the UEFI menu to see any boot devices listed; I only saw the EFI Shell and the Windows disk. And then there's some BLK devices but I couldn't "ls" or "dir" from within them. Then I had a genius idea: The repair command prompt can't see the boot drive because it doesn't have viostor drivers installed. So I followed this tutorial for the most part, using "drvload" command: https://eastbaytechservice.com/loading-kvmvirtio-storage-drivers-windows-server-2012-recovery/ Sure enough, now I could access C:. I backed out of the command prompt and tried startup repair, but no luck. Explored C: but found no EFI directory. Figured out F: was the actual main disk partition for my Windows install. Went to F:\Windows and used "bootrec /fixboot". Rebooted the VM. No luck. Booted to repair again, moved to command line, used drvload on viostor drivers. Tried "bootrec /rebuildbcd". It found F:\Windows, asked me to add it to boot list, and upon confirmation it says "The requested system device cannot be found." So from here I tried "bootrec /fixboot", and then "bcdboot F:\Windows /l en-us /s C: /f ALL" with F being the drive containing my old files and C being the EFI partition (apparently). Then a reboot. No dice, still pushes me to EFI Shell. At this point I believe it's an issue with the bootloader not having what it needs to "see" or "load" the boot partition and/or windows partition (eg virtio drivers?) so... At this point I'm giving up on converting to OVMF outside of doing a backup and fresh install. I'm worried switching back to the SeaBIOS VM would be broken, but it still boots fine! Phew. So my next trick is trying to have VNC *and* Nvidia passthrough co-exist. It seems to get past the bootloader just fine with VNC as the primary display (so if encrypted, I'd use VNC to type in the password without issue as before when I removed the bootloader). However, in Windows the video card isn't outputting. Checking device manager shows the GTX 970 being passed through, but with an error "Windows has stopped this device because it has reported problems. (Code 43)". So I try to reinstall Nvidia drivers (fresh), still Code 43. Try toggling the Hyper-V option to "Yes". Still boots with VNC but Nvidia card reports Code 43. At this point I give up and go back to raw Nvidia passthrough with no VNC and no fancy encrypted bootloader. After a few bootloops, automatic driver updates, and reinstalling the Nvidia drivers things appear back to normal. The 0.1 Bitcoin bounty stands if anyone else has any ideas that would allow me to use my keyboard to get to the BIOS menu at boot (and thus be able to enter a bootloader password). I also am open to any suggestions to convert my Windows 10 VM to OVMF/UEFI from its current setup, but I feel like I've tried just about everything per above. I'll probably give up in a few days, back up the machine, and do a fresh W10 install on a nuked drive with OVMF. I suspect the UEFI encrypted bootloader won't have too much trouble recognizing a keyboard. Bummer.
  8. That's a good lead and I tried it, unfortunately no luck. I tried detaching/reattaching when it was assigned at boot, and tried attaching/detaching/reattaching when it wasn't assigned at boot. The bootloader nor the BIOS seems to still not recognize any keypresses. I'll give that a try, although if memory serves this caused nothing to display on boot at all. Might try it with VNC enabled instead of video card to see if that makes any difference.
  9. Hi, I have a somewhat unique setup. I directly pass my Windows 10 VM (under SeaBIOS) directly to my SSD disk (using /dev/disk/by-id). I also directly pass-through a USB 3.0 PCI-E as well. Finally, I also encrypt my drive (TrueCrypt, and now, VeraCrypt). As a result, it's important that at the earliest point during boot that a keyboard is available. In 6.1, the keyboard I plugged into the USB 3 hub would not be recognized at boot so I couldn't type in a password. I then manually added a USB 2 Dell Keyboard plugged into a USB 2 port outside of the USB 3 hub and added it to the VM through the unRAID GUI. This worked; at boot, I had to use a different keyboard to type in my password but after that I could use everything else as normal after Windows booted. Now, in 6.2, the Dell keyboard does not work at boot and neither does the USB 3 hub keyboard. I cannot boot my machine past the encryption bootloader because I cannot type in a password. I know encrypted boot (or even VeraCrypt) is not supported by unRAID, so let's put this another way. I have no keyboard at boot so I cannot get into the SeaBIOS BIOS menu by hitting escape or F12 at boot. If that problem is solved, I highly suspect my real problem can be solved. So please don't dismiss this plea for help! Here's what I've tried: - Deselecting, update, and reselecting + update the VM for the Dell Keyboard from the unRAID GUI. - Same steps above after changing the Dell Keyboard to a USB 3 port. - Tried plugging Dell Keyboard directly into the USB 3 hub passthrough, no luck. - Rolling back to 6.1; this worked but then I'm stuck on 6.1. - Removing the encryption in 6.1, upgrading to 6.2, and ensuring Windows boots without that bootloader (it does). - Re-adding the encryption in 6.2 to see if I can get past the bootloader again (I can't, and this is where I am now) So I'm not totally without options: - Search around for a similar problem/solution for anyone else using KVM / VirtIO / etc or unRAID. I've spent a few hours at this but so far, no luck. - Post here to see if anyone else has had this problem and/or resolution. This is where I am now. - Use VNC to hopefully bypass the bootloader once and then remove it. Continue using machine unencrypted. - Finally, if VNC doesn't work, rollback to 6.1 to remain encrypted. I may do this even if VNC works; having full disk encryption in an audited open-source implementation is of high value to me. My final solution might be to backup everything, nuke the VM and drive, and then recreate/reinstall the Windows 10 VM using OVMF which will likely be able to detect the USB 3 hub and devices plugged in at boot. This wasn't an option before because TrueCrypt/VeraCrypt did not support UEFI boot, but now it does. However, this is the "nuclear" option and would result in the most time & work, and still may not even be a solution in the end. Here's the things I think you might need to help diagnose: VM XML Before 6.2 Upgrade: http://pastebin.com/raw/piAntJ8t VM XML After 6.2 Upgrade: http://pastebin.com/raw/xaipiALw lspci: login as: root root@192.168.86.38's password: Last login: Thu Dec 8 12:04:11 2016 from 192.168.86.222 Linux 4.4.30-unRAID. root@unRAID:~# lspci 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4) 00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4) 00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 (rev d4) 00:1c.7 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 (rev d4) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) 04:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11) 05:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller (rev 03) 06:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01) lsusb: login as: root root@192.168.86.38's password: Linux 4.4.30-unRAID. root@unRAID:~# lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 0781:5583 SanDisk Corp. Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer Bus 003 Device 005: ID 413c:2112 Dell Computer Corp. Bus 003 Device 004: ID 0cf3:e004 Atheros Communications, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Specific to each device, I'm passing through USB device 413c:2112 (Dell Keyboard) through the GUI, and passing through 1912:xxxx which is the USB hub, also manually stubbed in syslinux. The drive passthrough has been the /dev/disk/by-id/*SSD* device. All of this was the case before and after 6.2, although 6.2 actually makes some of this stuff visible in the GUI and prior I had to do it manually via XML editing. I see a number of things I could also provide under the Tools menu, but I'm not sure what would be critical for this type of problem. I hope that I've provided enough to solve the problem as I suspect any solution will require a direct edit to the VM XML file related to VM settings and/or devices. Thanks for any help anyone can provide. P.S. Optionally, I'll give 0.1 Bitcoin (about $75 of value today) to the first person who gives me a lead that results in the working solution that: - doesn't require me to reformat or reinstall Windows 10 - doesn't require me to stay on 6.1 - allows me to continue using VeraCrypt's full-disk encryption - doesn't require me to purchase additional hardware - ie. a solution (which may not exist) that requires only a few configuration edits
  10. PsyCrow, Glad to hear it helped! Couple of questions just out of pure curiosity: 1. What sort of computer / motherboard do you have? This is some model of Dell XPS, so I was expecting weird stuff like this. 2. Now that you have the onboard hooked up to a monitor, can you confirm if you switch to the monitor input to view the UnRAID console and then back to your GPU input and back again, if that triggers the IRQ issue? If (2) is not an issue for you, perhaps I should try killing my onboard USB 3 ports. I have a USB 3 PCI-E card passthrough to the VM which is plenty for me; unRAID needs no USB 3 devices. Overall though, I'm pretty happy with my setup. I never switch the monitor input so the machine has been smooth sailing. Even played a few games on it! Granted, they're indie games and have nearly no business being put through a GTX 970, lol.
  11. I've actually been smooth sailing with over a week uptime on both the W10 VM and the unRAID box. There's not a ton of reason I'd be flipping monitor channels to view the unRAID box anyway unless it was a recovery procedure, in which case the W10 VM should be off anyway. 0.109 device drivers wouldn't fix it; as mentioned in a previous post the bug is actually having to do with unRAID using the on-board video plugged into a monitor, and my monitor flipping away and back to the HDMI channel. unRAID is then the one that throws the IRQ error whether there's a VM running or not.
  12. So I popped into the BIOS and changed "Intel Multi Display" to Off. This disables On-Board graphics and the Motherboard forces you to disconnect any onboard graphics connections. So I did that, and now unRAID bound itself to the video card. When I try to start the VM with the GPU passed thru, all monitors go blank. When I stop the VM, the unRAID terminal never comes back. So, next up, I'll try pci.stubing the videocard to hopefully boot unRAID headless. At this point it seems the workaround solution is to leave Intel Multi Display "On", leave an HDMI plugged in to the onboard graphics, and never ever switch to that channel on whatever monitor it's plugged in with less every thing in unRAID get poisoned by the IRQ error state. UPDATE: So stubbing the videocard didn't keep unRAID from binding to it. The VM still won't start. I think I'm going to find the most elegant solution to leaving the onboard graphics on, keeping the HDMI plugged in, and preventing the channel from ever being enabled. What a wonky solution. Final solution unless someone comes in to look at this with other recommendations: - Leave "Intel Multi Display" enabled in BIOS - Leave onboard HDMI plugged into 3rd monitor - Leave 3rd monitor on DVI-D channel (for the discrete graphics card) - Never ever ever change the 3rd monitor input while unRAID is running - Boot unRAID and wait about 10 minutes; should be accessible from local network by now - Pretend the 3rd monitor has no input switch button and that unRAID is actually running headless - Profit
  13. More information on this error: - The full error on a fully logged in SSH client is: Message from syslogd@unRAID at Jan 19 17:38:13 ... kernel:Disabling IRQ #16 - The error occurs at the exact moment the monitor switches over to the HDMI channel (not when it is switched off). - The error seems to completely poison the unRAID run-time so that it runs ultra slow; it cannot be fixed without shutting down and powering back on the system - Dumping /var/log/syslog immediately after a reboot and then triggering this error: http://hastebin.com/raw/odizowinew - Interesting stuff starts here: ... Jan 19 17:37:19 unRAID kernel: br0: port 1(eth0) entered listening state Jan 19 17:37:19 unRAID kernel: br0: port 1(eth0) entered listening state Jan 19 17:37:20 unRAID avahi-daemon[1790]: Server startup complete. Host name is unRAID.local. Local service cookie is 3857780728. Jan 19 17:37:21 unRAID avahi-daemon[1790]: Service "unRAID" (/services/ssh.service) successfully established. Jan 19 17:37:21 unRAID avahi-daemon[1790]: Service "unRAID" (/services/smb.service) successfully established. Jan 19 17:37:21 unRAID avahi-daemon[1790]: Service "unRAID" (/services/sftp-ssh.service) successfully established. Jan 19 17:37:34 unRAID kernel: br0: port 1(eth0) entered learning state Jan 19 17:37:49 unRAID kernel: br0: topology change detected, propagating Jan 19 17:37:49 unRAID kernel: br0: port 1(eth0) entered forwarding state Jan 19 17:37:51 unRAID sshd[1868]: error: Received disconnect from 192.168.1.202: 3: com.jcraft.jsch.JSchException: Auth cancel [preauth] Jan 19 17:37:51 unRAID ntpd[1648]: Listen normally on 2 br0 192.168.1.138:123 Jan 19 17:37:51 unRAID ntpd[1648]: new interface(s) found: waking up resolver Jan 19 17:37:58 unRAID sshd[1888]: Accepted password for root from 192.168.1.202 port 49507 ssh2 Jan 19 17:38:13 unRAID kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Jan 19 17:38:13 unRAID kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.1.13-unRAID #1 Jan 19 17:38:13 unRAID kernel: Hardware name: Dell Inc. XPS 8700/0KWVT8, BIOS A10 12/08/2014 Jan 19 17:38:13 unRAID kernel: 0000000000000000 ffff88062fa03e18 ffffffff815f12b0 0000000000000001 Jan 19 17:38:13 unRAID kernel: ffff88061359e400 ffff88062fa03e48 ffffffff8107b05f 00000000fffc86af Jan 19 17:38:13 unRAID kernel: ffff88061359e400 0000000000000000 0000000000000010 ffff88062fa03e88 Jan 19 17:38:13 unRAID kernel: Call Trace: Jan 19 17:38:13 unRAID kernel: <IRQ> [<ffffffff815f12b0>] dump_stack+0x4c/0x6e Jan 19 17:38:13 unRAID kernel: [<ffffffff8107b05f>] __report_bad_irq+0x2b/0xbe Jan 19 17:38:13 unRAID kernel: [<ffffffff8107b46a>] note_interrupt+0x19d/0x227 Jan 19 17:38:13 unRAID kernel: [<ffffffff81079460>] handle_irq_event_percpu+0xe0/0xf2 Jan 19 17:38:13 unRAID kernel: [<ffffffff810794ae>] handle_irq_event+0x3c/0x5e Jan 19 17:38:13 unRAID kernel: [<ffffffff8107bcc7>] handle_fasteoi_irq+0x7a/0xdb Jan 19 17:38:13 unRAID kernel: [<ffffffff8100cf66>] handle_irq+0x1a/0x24 Jan 19 17:38:13 unRAID kernel: [<ffffffff8108f5ca>] ? __tick_nohz_idle_enter+0x15a/0x308 Jan 19 17:38:13 unRAID kernel: [<ffffffff8100c9f8>] do_IRQ+0x49/0xcd Jan 19 17:38:13 unRAID kernel: [<ffffffff815f74ae>] common_interrupt+0x6e/0x6e Jan 19 17:38:13 unRAID kernel: <EOI> [<ffffffff814dd3ad>] ? cpuidle_enter_state+0xb9/0x114 Jan 19 17:38:13 unRAID kernel: [<ffffffff814dd343>] ? cpuidle_enter_state+0x4f/0x114 Jan 19 17:38:13 unRAID kernel: [<ffffffff814dd42a>] cpuidle_enter+0x12/0x14 Jan 19 17:38:13 unRAID kernel: [<ffffffff810728ac>] cpu_startup_entry+0x1e2/0x2b2 Jan 19 17:38:13 unRAID kernel: [<ffffffff815e4581>] rest_init+0x85/0x89 Jan 19 17:38:13 unRAID kernel: [<ffffffff818a3ed4>] start_kernel+0x415/0x422 Jan 19 17:38:13 unRAID kernel: [<ffffffff818a38b5>] ? set_init_arg+0x56/0x56 Jan 19 17:38:13 unRAID kernel: [<ffffffff818a3120>] ? early_idt_handler_array+0x120/0x120 Jan 19 17:38:13 unRAID kernel: [<ffffffff818a34c6>] x86_64_start_reservations+0x2a/0x2c Jan 19 17:38:13 unRAID kernel: [<ffffffff818a35ae>] x86_64_start_kernel+0xe6/0xf5 Jan 19 17:38:13 unRAID kernel: handlers: Jan 19 17:38:13 unRAID kernel: [<ffffffff81491d40>] usb_hcd_irq Jan 19 17:38:13 unRAID kernel: Disabling IRQ #16 Jan 19 17:39:53 unRAID sshd[2129]: Accepted password for root from 192.168.1.148 port 5116 ssh2 Jan 19 17:41:47 unRAID emhttp: shcmd (17): rmmod md-mod |& logger Jan 19 17:41:47 unRAID kernel: md: unRAID driver removed Jan 19 17:41:47 unRAID emhttp: shcmd (18): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Jan 19 17:41:47 unRAID kernel: md: unRAID driver 2.5.3 installed Jan 19 17:41:47 unRAID emhttp: Plus key detected, GUID: 0781-5583-1001-371024111592 FILE: /boot/config/Plus.key Jan 19 17:41:47 unRAID emhttp: Device inventory: Jan 19 17:41:47 unRAID emhttp: shcmd (19): udevadm settle Jan 19 17:41:47 unRAID emhttp: get_device_size: open: No medium found Jan 19 17:41:47 unRAID emhttp: device /dev/sdb problem getting size Jan 19 17:41:47 unRAID emhttp: get_device_size: open: No medium found Jan 19 17:41:47 unRAID emhttp: device /dev/sdc problem getting size Jan 19 17:41:47 unRAID emhttp: get_device_size: open: No medium found Jan 19 17:41:47 unRAID emhttp: device /dev/sdd problem getting size Jan 19 17:41:47 unRAID emhttp: get_device_size: open: No medium found Jan 19 17:41:47 unRAID emhttp: device /dev/sde problem getting size Jan 19 17:41:47 unRAID emhttp: WDC_WD30EZRX-00SPEB0_WD-WCC4EC6HJN7F (sdf) 2930266584 Jan 19 17:41:47 unRAID emhttp: Samsung_SSD_840_EVO_1TB_S1D9NEADB04236N (sdg) 976762584 Jan 19 17:41:47 unRAID emhttp: SAMSUNG_HD204UI_S2H7JD2ZA11042 (sdh) 1953514584 Jan 19 17:41:47 unRAID emhttp: SAMSUNG_HD204UI_S2H7JD2ZA11032 (sdi) 1953514584 Jan 19 17:41:47 unRAID emhttp: ST3000DM001-1ER166_W500QGLN (sdj) 2930266584 Jan 19 17:41:47 unRAID emhttp: BP4_mSATA_SSD_270E073C021900037977 (sdk) 234431064 Jan 19 17:41:47 unRAID emhttp: ST9500325AS_6VEXE0CY (sdl) 488386584 Jan 19 17:41:47 unRAID emhttp: ST1000LM024_HN-M101MBB_S2TBJ90C240302 (sdm) 976762584 Jan 19 17:41:47 unRAID emhttp: ST1000DM003-1CH162_Z1D60704 (sdn) 976762584 Jan 19 17:41:47 unRAID emhttp: ST3000DM001-1ER166_Z500LYLZ (sdo) 2930266584 Jan 19 17:41:47 unRAID emhttp: array slots: 24 ...
  14. So I went thru the following: - Boot Windows VM - Cycle Monitor from unRAID to VM to unRAID - IRQ Error is raised - VM is massively slow - Shutdown VM - After 8 minutes of waiting, force shutdown VM - Stop Array, PowerOff unRAID - PowerOn unRAID, Start Array - Start VM - VM Won't Boot (Goes Straight to UEFI Shell After "Press Any Key...." Installer Prompt) - Restart VM, Boot to Installer - Go Thru to Load Drivers, Load VioStor - Quit & Go to Repair Windows - Click "Continue to Windows" - Massive number of quick successive bootloops occur - Force Stop VM - Decide to start fresh - Epiphany occurs So, here's the epiphany; what if this isn't VM related? So I boot unRAID, don't even start the array or VM. Its terminal is on the main monitor via onboard HDMI. I cycle off that monitor channel and then back to the unRAID terminal HDMI channel, and bam, the IRQ error occurs. This means that the IRQ error is occuring when the monitor channel for the unRAID terminal is moved off and on again, and it's unRAID itself that is having this issue completely unrelated to KVM. I wonder why? This narrows the troubleshooting window a bit though; it's either a BIOS setting or it's a pci.stubs entry I need to do. Here's my current syslinux.cfg: default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append initrd=/bzroot label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest
  15. Here's the last lspci -v output, after the Nvidia driver install. Everything is up-to-date driver-wise and Windows-wise; no MSI tweaks applied, all instructions followed in the unRaid 6 Manual for driver / guest-agent install. 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) Subsystem: Dell Device 05b7 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0c <?> Kernel driver in use: hsw_uncore 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000e000-0000efff Memory behind bridge: f6000000-f70fffff Prefetchable memory behind bridge: 00000000e0000000-00000000f1ffffff Capabilities: [88] Subsystem: Dell Device 05b7 Capabilities: [80] Power Management version 3 Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [a0] Express Root Port (Slot+), MSI 00 Capabilities: [100] Virtual Channel Capabilities: [140] Root Complex Link Capabilities: [d94] #19 Kernel driver in use: pcieport 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device 05b7 Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f7400000 (64-bit, non-prefetchable) [size=4M] Memory at d0000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Subsystem: Dell Device 05b7 Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f7c14000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) (prog-if 30 [XHCI]) Subsystem: Dell Device 05b7 Flags: bus master, medium devsel, latency 0, IRQ 27 Memory at f7c00000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Dell Device 05b7 Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f7c1e000 (64-bit, non-prefetchable) [size=16] Capabilities: [50] Power Management version 3 Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+ 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04) (prog-if 20 [EHCI]) Subsystem: Dell Device 05b7 Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at f7c1c000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) Subsystem: Dell Device 05b7 Flags: bus master, fast devsel, latency 0, IRQ 3 Memory at f7c10000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 Capabilities: [40] Express Root Port (Slot-), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell Device 05b7 Capabilities: [a0] Power Management version 3 Kernel driver in use: pcieport 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 0000d000-0000dfff Memory behind bridge: f7b00000-f7bfffff Prefetchable memory behind bridge: 00000000f2100000-00000000f21fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell Device 05b7 Capabilities: [a0] Power Management version 3 Kernel driver in use: pcieport 00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: 0000c000-0000cfff Memory behind bridge: f7a00000-f7afffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell Device 05b7 Capabilities: [a0] Power Management version 3 Kernel driver in use: pcieport 00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 (rev d4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=05, subordinate=05, sec-latency=0 Memory behind bridge: f7900000-f79fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell Device 05b7 Capabilities: [a0] Power Management version 3 Kernel driver in use: pcieport 00:1c.7 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 (rev d4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=06, subordinate=06, sec-latency=0 Memory behind bridge: f7800000-f78fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell Device 05b7 Capabilities: [a0] Power Management version 3 Kernel driver in use: pcieport 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04) (prog-if 20 [EHCI]) Subsystem: Dell Device 05b7 Flags: bus master, medium devsel, latency 0, IRQ 23 Memory at f7c1b000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 04) Subsystem: Dell Device 05b7 Flags: bus master, medium devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0c <?> 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0]) Subsystem: Dell Device 05b7 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 36 I/O ports at f0b0 [size=8] I/O ports at f0a0 [size=4] I/O ports at f090 [size=8] I/O ports at f080 [size=4] I/O ports at f060 [size=32] Memory at f7c1a000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA v1.0 Kernel driver in use: ahci Kernel modules: ahci 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04) Subsystem: Dell Device 05b7 Flags: medium devsel, IRQ 18 Memory at f7c19000 (64-bit, non-prefetchable) [size=256] I/O ports at f040 [size=32] Kernel modules: i2c_i801 01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device 2974 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f6000000 (32-bit, non-prefetchable) [size=16M] Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f0000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at f7000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [258] #1e Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 Kernel driver in use: vfio-pci 01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1) Subsystem: eVga.com. Corp. Device 2974 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at f7080000 (32-bit, non-prefetchable) [size=16K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Kernel driver in use: vfio-pci 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) Subsystem: Dell Device 05b7 Flags: bus master, fast devsel, latency 0, IRQ 37 I/O ports at d000 [size=256] Memory at f7b00000 (64-bit, non-prefetchable) [size=4K] Memory at f2100000 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-00-00-00-00 Capabilities: [170] Latency Tolerance Reporting Kernel driver in use: r8169 Kernel modules: r8169 04:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11) (prog-if 01 [AHCI 1.0]) Subsystem: Marvell Technology Group Ltd. Device 9215 Flags: bus master, fast devsel, latency 0, IRQ 38 I/O ports at c050 [size=8] I/O ports at c040 [size=4] I/O ports at c030 [size=8] I/O ports at c020 [size=4] I/O ports at c000 [size=32] Memory at f7a10000 (32-bit, non-prefetchable) [size=2K] Expansion ROM at f7a00000 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Express Legacy Endpoint, MSI 00 Capabilities: [e0] SATA HBA v0.0 Capabilities: [100] Advanced Error Reporting Kernel driver in use: ahci Kernel modules: ahci 05:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller (rev 03) (prog-if 30 [XHCI]) Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at f7900000 (64-bit, non-prefetchable) [size=8K] Capabilities: [50] Power Management version 3 Capabilities: [70] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [90] MSI-X: Enable+ Count=8 Masked- Capabilities: [a0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [150] Latency Tolerance Reporting Kernel driver in use: vfio-pci 06:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01) Subsystem: Dell Device 0209 Flags: bus master, fast devsel, latency 0, IRQ 5 Memory at f7800000 (64-bit, non-prefetchable) [size=512K] Expansion ROM at f7880000 [disabled] [size=64K] Capabilities: [40] Power Management version 2 Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00 Diffing all three lspci -v outputs using this utility shows that there's no difference between any of the three outputs. So it's safe to say MSI enabling / disabling is independent of the driver / update installs. At this point I'm going to play with trying to trigger that IRQ error again and seeing if enabling MSI devices keeps it from happening. Candidates for MSI enabling include: - High Definition Audio Controller - VirtIO Balloon Driver - Intel® 823371SB PCI to USB Universal Host Controller