T0a

January 18, 2020

Hi, I also own a Fujitsu d3644-b board and found this thread while searching for fan control with unRaid.

I bought two NF-A12x25 fans (4 pin pwm) as I wanted to move my unRaid build from the hall to my living room. Unfortunately, the mainboard bios fan control has no silent mode (full, auto and enhanced). Thus, I was trying to control the fans via unRaid - finding it lacking the driver support.

There are a lot of people owning this mainboard, because it was highly recommended in c't and this NAS build guide.

@limetech Could you please consider adding the driver to unRaid 6.9.0?

January 15, 2020

On 1/14/2020 at 2:42 AM, 702Pilgrim said:

Just so different users can have their own files but it's fine if not.

So I'm guessing there's no way to send an email for the users to sign up?

I'm sorry, I think this is not possible ATM. However, you can search in the projects issue tracker for this. If you don't find something similar, feel free to open a feature request and describe your use-case. Maybe someone from the community will pick it up and implement it.

14 hours ago, hpka said:

Sort of adjacent question: What scanners are people using with Paperless and, importantly, which are the least nonsense to use day to day. I'd like something that I can carelessly throw paper into and press one button to scan and upload if I can. Home budget.

I do see the recomendations in the Paperless docs and in the OP, but there is a slight dating issue now. That said, if those are still the reliable working options, I'd happily consider it.

If you are not aiming to implement this workflow for your business, you might run well with an app for your phone like ScanBot or ScannerPro (Make sure to disable the build-in OCR since it is either bad or runs in the cloud). Otherwise, as already pointed out by @ice pube, the Fujitsu ScanSnap is really popular in business like environments.

January 13, 2020

10 hours ago, 702Pilgrim said:

Thank you @T0a.

I'm sorry if someone already posted this question.

Is the "./manage.py createsuperuser" the only way to create users? Can users have there own documents?

This is the only way as far as I know. Is this a problem for you? There is also no multi-user feature. Can you describe your use case for multi-user support? As a workaround you can start multiple Paperless instances - one per user.

January 11, 2020

1 hour ago, dockerPolice said:

Shouldn't the paperless template be updated with this URL?

Thanks for your reply. I already changed the link in the template. We are waiting for the testing branch getting merged into master. See https://github.com/selfhosters/unRAID-CA-templates/pull/75 👍

January 10, 2020

Quote

From reading your guide, it sounds like you are saying that you need two instances of paperless, one specially for the consumer? is that correct?

You are right. The first container runs `runserver 0.0.0.0:8000 --insecure --noreload` (webserver) and the second one `document_consumer --no-inotify --loop-time 60` (consumer) in „Post Arguments“. Both containers have the /consume folder shared. I will update the install instructions with pictures and making it more precise once I find the time. If you stick to smb shares you might omit the `--no-inotify --loop-time 60` .

Thanks for the additional configuration variables. We plan to update the template and I will consider these too.

January 10, 2020

On 1/8/2020 at 1:45 AM, l3gion said:

Thanks mate, this was GOLD

Glad, I could help!

3 hours ago, hpka said:

Sort of adjacent question: What scanners are people using with Paperless and, importantly, which are the least nonsense to use day to day. I'd like something that I can carelessly throw paper into and press one button to scan and upload if I can. Home budget.

Do you mind asking this question in the new paperless docker template support thread again? I already added a section for scanner. I also created a pull request for changing the support thread in the docker template.

January 10, 2020

Reserved Space

January 10, 2020

------------------------------

Dear paperless user,

paperless hasn't received a lot of updates and bug fixes in the past. Even pull requests are not merged for some time now. Though, paperless runs rocks solid and gets the job done! For some time now, there is a well-maintained fork of paperless out there. It's called paperless-ng and I'm happy to announce that paperless-ng is officially available via Unraids community application store (CA store). Go check it out!

----------------------------

Overview: Support for Docker paperless template in the selfhosters/unRAID-CA-templates repository.

Docker Hub: https://hub.docker.com/r/thepaperlessproject/paperless/

Documentation: https://paperless.readthedocs.io/en/latest/

This is the official Paperless Docker support thread. Feel free to ask questions and share information or your experience. I try to update this main post regularly and also incorporate your shares. I also started to contribute features to the Paperless project. You are welcome to help to improve Paperless too as it is a community-driven project.

You might also find this old question about Paperless helpful: https://forums.unraid.net/topic/71733-help-with-paperless-dockerhub-unraid/

1. How to Install

Paperless uses a two container setup: (1) a webserver serving your files via the browser and (2) a consumer service that checks for new files in the input directory, doing the parsing and importing the documents to the database. Because unRaid does not support docker-compose, you need to create those two containers from the same template with manual adjustments:

1. Create a "Paperless" share on your array with subfolders for media, consume, and export

2. Install the Paperless webserver

2.1 From the Apps tab, search for "Paperless"

2.2 Configure the Media, Consumption, and Export paths to point at the folders you created in step 1

2.3 Accept the defaults for the remaining variables or adjust as needed. As you get more familiar with Paperless, you may wish to add additional variables that are defined here: https://github.com/the-paperless-project/paperless/blob/master/paperless.conf.example

2.4 Hit Apply to start the container.

3. Create the Paperless superuser

3.1 From the Unraid Docker UI, click the Paperless icon and choose Console. At the prompt, type "./manage.py createsuperuser". Follow the instructions to create the paperless user

4. Install paperless as consumer service to process documents in your /consume folder

4.1 From the Unraid Docker UI, click Add Container and select the paperless template from the [ User templates ] section

4.2 Rename the container to "paperless-consumer"

4.3 Remove the port to avoid port conflicts with the webserver

4.4 Switch to Advanced mode and change the "Post Arguments" parameter to "document_consumer". If you are using NFS, also add "--loop-time 60 --no-inotify" (See FAQ)

Now, you should be able to place a document in your /consume folder of your "Paperless" share and recognize it being imported to paperless.

2. Paperless Scan Workflows

2.1 WebDav Scan App with Nextcloud

I also want to share my scanning workflow with Paperless and Nextcloud (See https://blog.kilian.io/paperless/ as reference). With the app ScannerPro, I can upload my scanned files to a Nextcloud folder via WebDav from my mobile device. This folder functions as Paperless consume folder and grabs the files and imports them to Paperless. Following steps required for the setup:

1. Mount the paperless /consume folder in the Nextcloud docker container via unRaids Docker template editor

2. Enable the external storage app as Nextcloud admin. The app can be found in the apps dropdown hidden in disabled apps.

3. Add the mounted consume/ folder as local storage for your Nextcloud user with name paperless-consume (Settings -> External Storage)

4. Configure the Nextcloud paperless-consume folder as WebDav target in your scan app

Quote

An added bonus is that the Nextcloud desktop client also syncs the consume directory to my computer, so I also have a directory there where I can drop PDF files to be added to paperless (https://blog.kilian.io/paperless/)

3. FAQ

3.1 Why does the consumer not pick up my files?

The consumer service uses `inotify` to detect new documents in the consume folder. This subsystem, however, does not support NFS shares. Thus, you need to start your consumer with "Post Arguments" defined as `document_consumer --no-inotify --loop-time 60`.
The document file type might not be supported. Check the consumer logs using the unRaid docker section for warnings and issues.

3.2 How to customize Paperless?

All variables from paperless.conf.example can be passed as Docker environment variable to the container.

3.3 What scanner do you use for your paperless home?

Paperless user recommendations
iPhone with ScannerPro App; one time purchase (@T0a)

3.4 Can I use Paperless on a mobile device?

There is a mobile app in pretty early development stage

January 7, 2020

On 1/6/2020 at 7:39 PM, ljm42 said:

I haven't fully decided if I will use paperless, but I have some suggestions for the template to help people get started faster. I could submit a PR, but I figured the people who have been using this more might be in a better position to decide if this would be helpful:

In the 'Overview', include a link to the documentation:
https://paperless.readthedocs.io/en/latest/

For the 'Data' path, set a default of /mnt/user/appdata/paperless/data with the following description:
Container Path: /usr/src/paperless/data .
This contains the paperless database. Should be in appdata.

For the 'Media' path, set a default of /mnt/user/appdata/paperless/media with the following description:
Container Path: /usr/src/paperless/media .
Once consumed, files will be stored here. You may wish to place this on the array instead of in appdata.

For the 'Consumption' path, set a default of /mnt/user/appdata/paperless/consume with the following description:
Container Path: /consume .
Files placed here will be consumed by paperless.

For the 'Export' path, set a default of /mnt/user/appdata/paperless/export with the following description:
Container Path: /export .
Location for files used by the exporter utility.
See https://paperless.readthedocs.io/en/latest/utilities.html#the-exporter

For PAPERLESS_OCR_LANGUAGES, set a default value of "eng" and include the following description:
Container Variable: PAPERLESS_OCR_LANGUAGES.
Space-separated list of 3-letter language codes used for OCR. List of valid codes available here: https://www.loc.gov/standards/iso639-2/php/code_list.php

How about adding the PAPERLESS_TIME_ZONE variable, defaulted to "UTC", with the following description:
Container Variable: PAPERLESS_TIME_ZONE.
Override the default UTC time zone. For details see: https://docs.djangoproject.com/en/1.10/ref/settings/#std:setting-TIME_ZONE

How about adding the PAPERLESS_INLINE_DOC variable, defaulted to "false", with the following description:
Container Variable: PAPERLESS_INLINE_DOC.
When true, PDF files will be viewed in the browser.
When false, PDF files will be downloaded.

I would love to see this as a pull request for the docker template. A few minor remarks from my side:

I wouldn't add defaults for Media, Consumption and Export paths, since this may mislead people placing it in their appdata. Though, I like the comment!
I suggest to add `PAPERLESS_OCR_LANGUAGE`, defaulted to "eng" with the following description or similar: "Override the language that tesseract will attempt to use when parsing documents. Use a 3-letter language code consistent with ISO 639: https://www.loc.gov/standards/iso639-2/php/code_list.php".
Maybe add a short explanation about the unRaid docker template installation i.e. paperless-webserver docker and paperless-consumer docker instances.
Maybe add a warning about NFS and inotify issues to the 'Consumption' path such as:
"If you are using NFS mounts for the consume directory you also need to change the command to turn off inotify as it doesn’t work with NFS command: ["document_consumer", "--no-inotify"]". Maybe shorter?

January 5, 2020

@smittyuk Glad I could give something back. The `paperless` image referenced in the official CA template is BTW outdated (also mentioned by @spacecops). The project is now driven by its community (See: https://github.com/the-paperless-project/paperless/issues/470). Use the up-to-date image `thepaperlessproject/paperless` instead. I already proposed the change for the docker template in the UnRaid repository. Change should be on the way. In the meantime you can just stop your container and replace the image and click apply.

January 4, 2020

With the information from this thread I successfully installed paperless today on my unRaid server. Thanks to @speedyg213 for the wrap-up. Let me briefly summarize the steps to install paperless with the new paperless CA template from 9th Nov 2019. I decided to use NFS mounts also for the consumer folder. So I had to adapt the commands slightly:

1. Create a NFS share with subfolder (e.g. media/ consume/ and data/)

2. Install paperless as web server from CA

2.1. Configure the NFS mounts for media/ consume/ and data/ created in step 1

2.2 Define PAPERLESS_OCR_LANGUAGES (in my case: "eng deu")

3. Login to the paperless container via the unRaid web-interface and issue the following command: "./manage.py createsuperuser". Follow the instructions to create the paperless user

4. Install paperless as consumer service in order to process documents in your /consume folder

4.1 Go to the docker UI, click add container and select the paperless template

4.2 Rename the container to "paperless-consumer"

4.3 Remove the port

4.4 Change the parameter "postargument" to "document_consumer --no-inotify --loop-time 60". This will start the consumer service with a 60 seconds time loop. It also disables the inotify feature, which does not work with consumer/ folders represented as NFS shares.

Now you should be also to place a document in your /consume folder of your NFS share and recognize it being imported to paperless.

Have a nice weekend everybody! Questions are welcome.

----- Edit ----

I also want to share my scanning workflow with Paperless and Nextcloud with you guys (See https://blog.kilian.io/paperless/ as reference). With the app ScannerPro, I can upload my scanned files to a Nextcloud folder via WebDav. This folder functions as paperless consume folder and grabs the files and imports them to paperless. Following steps required for the setup:

1. Mount the paperless /consume folder in the Nextcloud docker container via unRaids Docker template editor

2. Enable the external storage app as Nextcloud admin. The app can be found in the apps dropdown hidden in disabled apps.

3. Add the mounted consume/ folder as local storage for your Nextcloud user with name paperless-consume (Settings -> External Storage)

4. Configure the Nextcloud paperless-consume folder as WebDav target in your scan app

Quote

An added bonus is that the Nextcloud desktop client also syncs the consume directory to my computer, so I also have a directory there where I can drop PDF files to be added to paperless (https://blog.kilian.io/paperless/)

December 13, 2019

Hi,

check out Home-Assistant (HA). I recently started using it. There is a weather-card and you can configure custom sensors for e.g traffic monitoring (Maybe with Google travel api or Waze api?). Not everything is possible to configure via the Web-Interface. Thus, if you want to have full-control about the lovelance UI, you can enable yaml mode. This site might also be a good source.

I also stumbled about this thread a few days ago showing a custom component for UnRaid. However, it is not a public available component.

November 17, 2019

On 11/16/2019 at 3:00 PM, saarg said:

No issues here. Try following the guide to update using the command line in the link in the first post.

I have a similar problem. When clicking on the WebUI Button the attached screen appears. By clicking on "agree", I receive the following error after a while:

Internal Server Error
The server encountered an internal error and was unable to complete your request.

The nginx `access.log` contains the following while the `error.log` is empty:

192.168.178.25 - - [17/Nov/2019:19:54:27 +0100] "GET / HTTP/2.0" 500 289 "http://192.168.178.21/Docker" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/2010010
1 Firefox/70.0"
192.168.178.25 - - [17/Nov/2019:19:55:18 +0100] "GET / HTTP/2.0" 500 289 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
192.168.178.25 - - [17/Nov/2019:19:55:55 +0100] "GET /favicon.ico HTTP/2.0" 500 289 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0

Accessing the WebUI via `http://192.168.178.21:443/` as I did before the upgrade, causes the error "The plain HTTP request was sent to HTTPS port". I am sure that my nginx `default` file contains the latest changes from the commit update nginx site conf due to CVE. Any help?

November 3, 2019

Thank you. Looks like this mailing list post describes my current problem despite me having also (maybe unrelated) strange hardware errors. I tried the recommendations from this thread getting still the "Input/output error" error.

Can somebody provide me a VGA BIOS ROM for Intel core i3-8100 or UHD 630 IDG? I think this is my last option worth trying.

$ echo 1 > /sys/devices/pci0000:00/your-i3-integrated-graphics/rom
$ cat /sys/devices/pci0000:00/your-i3-integrated-graphics/rom > vbios.dump
$ echo 0 > /sys/devices/pci0000:00/your-i3-integrated-graphics/rom

I think about buying a ZOTAC GeForce® GT 710 ZONE Edition 2GB DDR3 (or GT730 since ROM is attached here) as a fallback, when I cannot get IDG pass-through with the i3-8100 working. According to @1812 (reference), these cards have native driver support for OSX and should work well with pass-through via UnRaid.

November 2, 2019

On 11/2/2019 at 10:49 PM, SpaceInvaderOne said:

If you can get the passthrough to work with other vms it should work.

Please try this xml in place of what you have. This xml has your gpu passed through in it.

However when you start the vm you will have no keyboard or mouse as I couldnt put that in for you but that should be easy to do.

Just use this as is to see if it boots with the gpu and gets to the desktop.

Remember to put both your uuid and osk key back into the xml

Thanks for this quick response. When you answered I already stumbled across Advanced OSX VM techniques for KVM in unRAID, which helped me to come up with a similar hostdev section as yours. I think you mixed slot and bus values in your snippet causing "Device 0000:02:00.0 not found" error.

Quote

<hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
      </source>
      <alias name='hostdev0'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </hostdev>

I can save the template with this definition above without errors. However, when starting the VM the log gives me the following errors - UnRaid indicates the VM as started though:

2019-11-02 22:04:38.934+0000: Domain id=5 is tainted: high-privileges
2019-11-02 22:04:38.934+0000: Domain id=5 is tainted: custom-argv
2019-11-02 22:04:38.934+0000: Domain id=5 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2019-11-02T22:04:39.467427Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,id=hostdev0,bus=pci.4,addr=0x0: Failed to mmap 0000:00:02.0 BAR 2. Performance may be slow
2019-11-02T22:04:40.089368Z qemu-system-x86_64: vfio-pci: Cannot read device rom at 0000:00:02.0
Device option ROM contents are probably invalid (check dmesg).

I checked with a monitor connected to the DP on my hardware, but got no signal. Not able to dump the VGA BIOS ROM either:

$ echo 1 > /sys/bus/pci/devices/0000\:00\:02.0/enable
$ echo 1 > /sys/bus/pci/devices/0000\:00\:02.0/rom
$ sudo cat /sys/bus/pci/devices/0000\:00\:02.0/rom > /tmp/myigpu.rom
cat: '/sys/bus/pci/devices/0000:00:02.0/rom': Input/output error

Also found hardware errors in "dmesg":

[    0.189137] TSC deadline timer enabled
[    0.189148] smpboot: CPU0: Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz (family: 0x6, model: 0x9e, stepping: 0xb)
[    0.189191] mce: [Hardware Error]: Machine check events logged
[    0.189194] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee00000000801136
[    0.189195] mce: [Hardware Error]: TSC 0 ADDR 8cc3ff00 MISC 43040000086 
[    0.189197] mce: [Hardware Error]: PROCESSOR 0:906eb TIME 1572729386 SOCKET 0 APIC 0 microcode b4
[    0.189199] mce: [Hardware Error]: Machine check events logged
[    0.189200] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee00000000801136
[    0.189201] mce: [Hardware Error]: TSC 0 ADDR 8cc3ff40 MISC 43040000086 
[    0.189204] mce: [Hardware Error]: PROCESSOR 0:906eb TIME 1572729386 SOCKET 0 APIC 0 microcode b4
[    0.189205] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 8: ee00000000801136
[    0.189206] mce: [Hardware Error]: TSC 0 ADDR 8cc3ff80 MISC 43040000086 
[    0.189208] mce: [Hardware Error]: PROCESSOR 0:906eb TIME 1572729386 SOCKET 0 APIC 0 microcode b4
[    0.189210] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 9: ee00000000801136
[    0.189211] mce: [Hardware Error]: TSC 0 ADDR 8cc3ffc0 MISC 43040000086 
[    0.189213] mce: [Hardware Error]: PROCESSOR 0:906eb TIME 1572729386 SOCKET 0 APIC 0 microcode b4
[    0.189232] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
[...]
[ 1709.638052] DMAR: DRHD: handling fault status reg 3
[ 1709.638056] DMAR: [DMA Read] Request device [00:02.0] fault addr 8b8c0000 [fault reason 06] PTE Read access is not set
[ 1709.639210] DMAR: DRHD: handling fault status reg 3
[ 1709.639214] DMAR: [DMA Read] Request device [00:02.0] fault addr 8b8c0000 [fault reason 06] PTE Read access is not set
[ 1709.640368] DMAR: DRHD: handling fault status reg 3
[ 1709.640372] DMAR: [DMA Read] Request device [00:02.0] fault addr 8b8e6000 [fault reason 06] PTE Read access is not set
[ 1709.641531] DMAR: DRHD: handling fault status reg 3
[ 1710.114661] vfio_ecap_init: 0000:00:02.0 hiding ecap 0x1b@0x100
[ 1710.115413] vfio-pci 0000:00:02.0: BAR 2: can't reserve [mem 0x4000000000-0x400fffffff 64bit pref]
[ 1710.743259] resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000c3fff window]
[ 1710.743263] caller pci_map_rom+0x7a/0x15e mapping multiple BARs
[ 1710.743277] vfio-pci 0000:00:02.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
[ 1757.150276] br0: port 2(vnet0) entered disabled state
[ 1757.151237] device vnet0 left promiscuous mode

cat syslog | grep "mcelog"
Nov  3 10:41:12 Zeus nerdpack: Installing mcelog-161 package...
Nov  3 10:41:12 Zeus root: Installing mcelog-161 package... 
Nov  3 10:43:10 Zeus sudo:     root : TTY=pts/1 ; PWD=/var/log ; USER=root ; COMMAND=/usr/sbin/mcelog --client
Nov  3 10:44:21 Zeus mcelog: failed to prefill DIMM database from DMI data
Nov  3 10:44:21 Zeus mcelog: Kernel does not support page offline interface
Nov  3 10:46:16 Zeus sudo:     root : TTY=pts/1 ; PWD=/var/log ; USER=root ; COMMAND=/usr/sbin/mcelog --client
root@Zeus:/var/log# mcelog --client
root@Zeus:/var/log# #EMPTY#
root@Zeus:/var/log# cat /var/log/mcelog
root@Zeus:/var/log# #EMPTY#

Seems like mcelog does not work on my System due to lack of kernel support? Also, mcelog never outputs anything so I suspect it is not functional.

Am I missing something @SpaceInvaderOne? Looks like "Fix Common Problems" Plugin also reports these hardware issues. So I attached my diagnostics too. Not sure, if the hardware errors are related to the non-working iGPU pass-through. Just bought my UnRaid Licence today and installed it to my new assembled server

Maybe it is a good idea to put this issue in its own thread, since it has nothing to do with MacInABox anymore.

Update:

- Got rid of "vfio-pci 0000:00:02.0: BAR 2: can't reserve [mem 0x4000000000-0x400fffffff 64bit pref]" with "append initrd=/bzroot video=efifb:off" (debugged with /proc/iomem). Still get "vfio-pci: Cannot read device rom at 0000:00:02.0
Device option ROM contents are probably invalid"

November 2, 2019

I struggle with passing the iGPU of my Intel Core i3-8100 CPU to a Catalina VM, created via Macinabox. In order to do so, I changed the selection under graphics card of my VM template from "VNC" to "Intel 8th Gen Core Processor Gaussian Mixture Model (00:02:0)". Once I click apply, the error "XML error: Attempted double use of PCI Address 0000:00:02.0" pops up.

The following shows my so far working XML definition for the Catalina VM (OSK clean) with VNC as selected graphics card. The VM boots as expected. However, I cannot change the display resolution in the OSX settings due to the missing iGPU pass-through.

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>MacinaboxCatalina</name>
  <uuid>a-uuid-here</uuid>
  <description>MacOS Catalina</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="MacOS" icon="/mnt/user/domains/MacinaboxCatalina/icon/catalina.png" os="Catalina"/>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>2</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-3.1'>hvm</type>
    <loader readonly='yes' type='pflash'>/mnt/user/domains/MacinaboxCatalina/ovmf/OVMF_CODE.fd</loader>
    <nvram>/mnt/user/domains/MacinaboxCatalina/ovmf/OVMF_VARS.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='2' threads='1'/>
  </cpu>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/Clover.qcow2'/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/Catalina-install.img'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/MacinaboxCatalina/macos_disk.img'/>
      <target dev='hde' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='4'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </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='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:2c:45:1e'/>
      <source bridge='br0'/>
      <model type='vmxnet3'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-usb'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='usb-kbd,bus=usb-bus.0'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='isa-applesmc,osk=clean'/>
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/>
  </qemu:commandline>
</domain>

Further my system device output from the Tools section:

IOMMU group 0:	[8086:3e1f] 00:00.0 Host bridge: Intel Corporation 8th Gen Core 4-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S] (rev 08)
IOMMU group 1:	[8086:3e91] 00:02.0 VGA compatible controller: Intel Corporation 8th Gen Core Processor Gaussian Mixture Model
IOMMU group 2:	[8086:a379] 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
IOMMU group 3:	[8086:a36d] 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
		[8086:a36f] 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
IOMMU group 4:	[8086:a360] 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
IOMMU group 5:	[8086:a352] 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10)
IOMMU group 6:	[8086:a309] 00:1f.0 ISA bridge: Intel Corporation Device a309 (rev 10)
		[8086:a348] 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
		[8086:a323] 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
		[8086:a324] 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
		[8086:15bb] 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM (rev 10)

I already had a look at this thread. But I cannot identify duplicate lines, since the template is not changed after clicking apply due to the mentioned error. Does someone has a similar problem or know how to solve it? Maybe someone owns the same CPU having similar problems in the past? And follow-up question: Is it even possible to use the integrated graphics with OSX (reference)?

-----

@SpaceInvaderOne: Thank you so much for this docker container. I just spotted a small typo in the log output of the container:

Quote

The reference /image below refers to where you mapped that folder in the docker template on your server
(normally to /mnt/user/doamins

T0a

Posts

Joined

Last visited

Content Type

Profiles

Forums

Downloads

Store

Gallery

Bug Reports

Documentation

Landing

Posts posted by T0a

Kernel Module "Teutates" chip from Fujitsu

[Support] Paperless Docker

[Support] Paperless Docker

[Support] Paperless Docker

[Support] Paperless Docker

Help with Paperless DockerHub -> Unraid

[Support] Paperless Docker

[Support] Paperless Docker

Help with Paperless DockerHub -> Unraid

Help with Paperless DockerHub -> Unraid

Help with Paperless DockerHub -> Unraid

Smart Home Dashboard (Photos, Calendar, Weather, etc)

[Support] Linuxserver.io - Nextcloud

[SOLVED] Non-working IGD pass-through with i3-8100 for VM

[SOLVED] Non-working IGD pass-through with i3-8100 for VM

[SOLVED] Non-working IGD pass-through with i3-8100 for VM