1812

Members
  • Content count

    1587
  • Joined

  • Last visited

  • Days Won

    4

1812 last won the day on January 10

1812 had the most liked content!

Community Reputation

110 Very Good

2 Followers

About 1812

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

1232 profile views
  1. Access my unRaid tower externally?

    Tonido docker app and done.
  2. unsafe interrupts is now working, which allows us to unmask your real problem, that being: vfio-pci 0000:09:00.0: Device is ineligible for IOMMU domain attach due to platform RMRR requirement. Contact your platform vendor. This thread has some information regarding it. Some in the first post which may not be applicable on a G7 (using older bios vs updated-works on G6 servers...) On the second page, another user posted their steps using a custom kernel they made to bypass the RMRR issue with a patch via proxmox users. Currently these are the only 2 options that I know of to work around the issue. I have not attempted to use the custom compiled kernel.
  3. it's not booting allowing unsafe interrupts (per the log.) delete all that you have in the syslinux and replace with the following: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot label unRAID OS GUI Mode kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot unraidsafemode label unRAID OS GUI Safe Mode (no plugins) kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest once done verify the sound card is in it's iommu group by itself and try again with the vm. if it fails, post your new diagnostics immediately after.
  4. post your diagnostics zip file (tools>diagnostics)
  5. Data Balancing

    lots of folks like unBalance
  6. Restoring Virtual Machines

    i'm on 6.5 rc3 and run 2 osx vm's no problem using pc-q35-2.11
  7. the xml you posted shows topology defined and shows 8 sockets with 2 threads.... you can try adding an emulator pin on cpu 0, but with 16 cpu's, I don't think it'll make that much of a difference. What else is running off the NVME drive? downloaders/dockers? Something is bogging it down and I don't believe it is cpu related since you're throwing 16 threads at it (at the moment of typing, I'm running 2 osx vm's on a W3520, with each vm on it's own ssd and only 4-6 gb of ram, using gtx 710's, so way less power but runs smooth)
  8. afaik you can pool them on a single vcpu and the system will choose which to run the thread on. I don't believe you can combine their output to fake a higher mhz. But I'd like to be wrong about the second part.
  9. New HP H220 (LSI 9207-8i)

    what does the LSI firmware give you (besides zfs) that the hp firmware doesn't?
  10. shot in the dark time: if sr-iov is enabled in the bios, turn it off and try again if that doesn't work, since it's a z600, you could try the options outlined for passthrough detailed in the link in my sig for proliants. I run 2 vm's with 2 gpus on a z400 and needed a few of the modifications to the syslinux.cfg to get it going.
  11. My server rack with that particular setup is currently torn down and packed for moving. It will be about 2 months before I'll have it back up and running. I can try to do this at that point, if I can remember!
  12. You need to start with VM passthrough problems on the previous page dealing with unsafe interrupts. Without allowing unsafe interrupts (append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot) , you will not get any closer to your goal of a working vm.
  13. Can't get to Dockers

    its curious because i lost access today to my dockers on the dashboard and docker tab and I too recently installed pihole.... dockers are functional, just not listed in the unRaid web gui.... also getting this error Apr 4 17:03:44 Brahms1 nginx: 2018/04/04 17:03:44 [error] 5110#5110: *1602274 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.181, server: , request: "POST /webGui/include/DashboardApps.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.253", referrer: "http://192.168.1.253/Dashboard" Apr 4 17:05:53 Brahms1 nginx: 2018/04/04 17:05:53 [error] 5110#5110: *1602274 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.181, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.253", referrer: "http://192.168.1.253/Docker" Apr 4 17:05:53 Brahms1 nginx: 2018/04/04 17:05:53 [error] 5110#5110: *1602464 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.181, server: , request: "POST /plugins/ca.docker.autostart/include/exec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.253", referrer: "http://192.168.1.253/Docker" Apr 4 20:25:36 Brahms1 nginx: 2018/04/04 20:25:36 [error] 5110#5110: *1618384 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.203, server: , request: "POST /webGui/include/DashboardApps.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "brahms1.local", referrer: "http://brahms1.local/Dashboard" Apr 4 20:29:01 Brahms1 ool www[67689]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update
  14. fix is also in the first post here under ACPI: https://lime-technology.com/forums/topic/59375-hp-proliant-unraid-information-thread/

Copyright © 2005-2018 Lime Technology, Inc.
unRAID® is a registered trademark of Lime Technology, Inc.