dlandon

Correct.

I have cloned and updated the linuxservio.io beta ownCloud docker. I have been using it for over a year and it works very well. I know that NextCloud is the in thing, but I am committed to ownCloud in my business and have over 200GB of media, calendars, contacts, and tasks on ownCloud. I do not want to invest time and take the risk trying to move to NextCloud. The thing I really like about this docker is that mariadb is installed in the docker so a separate docker for the database is not required. I also found other implementations of ownCloud dockers were lacking when it comes to updating ownCloud. ownCloud cannot be downgraded, so one has to be careful to always go forward, and not backwards. If a person manually updated ownCloud and then had to reinstall with the original docker, the manual upgrade got written over in other implementations. This docker prevents that situation because the ownCloud version is persistent in the appdata/owncloud folder. Anyway, the docker is available to install from CA. If you have the linuxserver.io docker installed, this is a drop in replacement for that docker. Be sure to back up your data before installing this docker. To replace the linuxserver.io ownCloud docker, remove that docker and then install this new docker from CA. Be sure to change any custom settings you made to the original docker template. Installing ownCloud from scratch will install the latest version (Currently 10.0.9 - called ownCloud X). If you've already installed the docker, your current ownCloud version will not be changed. To install the docker from scratch: Install docker and then go to the WebUI. Enter an administration user and password. Change the data folder to /data. Because the database is built into the container, the database host is localhost. The database user and the database itself are both 'owncloud'. If you do not change the default DB_PASS variable, the default database password is 'owncloud'. Once in the ownCloud WebUI, go to 'Settings->General' and click the 'Cron' method for the cron.php task. A cron to perform this is built into the docker. If you use your own certificate keys name them cert.key and cert.crt, and place them in config/keys folder. It is recommended to install the 'OwnBackup' app to backup your databases on a schedule. ownCloud can be updated from the WebUI, but it requires a certificate that is not self-signed and some other requirements that will be difficult for a self hosted server. I will post some manual update instructions so ownCloud can be updated and be persistent. I will be working on updates that can be done by updating the docker, but I have to put some time into how to do that without breaking things. I recommend you install some security apps for better security: OAuth2 - This app is for remote access to the ownCloud server and uses tokens rather than passwords to log into the server. Passwords are not stored locally by any clients or third party apps. Brute-Force Protection - Offers brute force login protection. Password Policy - Allows you to set password complexity rules.

The ownCloud docker was developed to be as secure as possible for those not experienced with security and wanting ownCloud access on the net. Feel free to fork the Docker and make your own if it's such a problem. It is easier to manage ownCloud access if it is on it's own IP address. If you don't do this and you don't have a static IP address on Unraid, you can't port forward because the IP address changes.

You probably would be better off getting support from traefik support forum. What is it you are trying to accomplish with traefik? Seems like a lot of work.

The ownCloud certificate is self signed and traefik does not like it. You need to get a valid certificate. Try Lets Encrypt. They offer valid certificates for free.

Unassigned Devices Plugin Unassigned Devices (UD) includes a lot of functionality and has become a bit complex. Please be aware of the following before you start using UD. Hover your mouse over an any active area on the UD page and a tool tip will show you what clicking that area does. UD has a destructive mode that allows deleting disk partitions and formatting disks. If Destructive Mode is not turned on in the UD Settings, you WILL NOT be able to format a disk. Go the the Settings page and scroll to the bottom to see the UD settings. To format a disk: Destructive mode must be enabled. Disk must have all partitions removed. Unmount the disk, click on the '+' icon next to the serial number, and click on all red-X to delete partitions. If the disk has been precelared and shows a grayed 'Format' button, click on the '+ icon next to the disk serial number, then click on the red-X to delete the preclear status file. There are different operations in various active areas (especially the disk serial number) based on whether or not the disk drive is mounted. If the disk is not mounted, click on the '+ icon by the serial number, click on the partition name, then you can type a new mount point name. Press Enter for the name change to be applied. This will now become the mount point and the share name when the disk is shared. In order to share any UD device, sharing needs to be enabled in the UD Settings and the switch turned on to share the particular device. Disks formatted with xfs or ext4 will be mounted with 'discard'. This enables TRIM on SSD devices. DIsks formated XFS or BTRFS will be partitioned compatible with the array disks and can be installed in the array without a re-format. An encrypted array disk can be mounted in UD with the following restrictions: The array disk passphrase has to be defined. You cannot enter the passphrase for the disk in UD. An array encrypted disk cannot be created with UD. The disk can only be mounted if the current array passphrase is the same as the UD encrypted disk. Note: There has to be at least one encrypted disk in the array. Because of security issues with samba, the mounting of remote SMB shares with CIFS has become more complicated. The default protocol is now SMB3 and not SMB1; the default security is now ntlmv2 and not ntlm. UD will try to mount SMB shares with SMB3, then SMB2, and then SMB1 to try to get the mount to use the most secure protocol it supports and the ntlmv2 protocol. If you have any issues with mounting remote SMB shares, set the in Settings->Unassigned Devices "Force all remote shares to SMB v1" to "Yes". Note: UD disks add to the total disks allowed by the Unraid license you have purchased except for a Pro license. See here for details. This plugin is a continuation of the Unassigned Devices plugin originally written by gfjardim. I have updated the plugin for unRAID 6, fixed some issues, and added new features. Unassigned Devices allows you to mount and share disk drives that are not managed as part of the array. Some users are mounting a drive specifically for Dockers and/or VMs rather than having them on a cache or array drive. You can also mount a UNC share on another system (SMB or NFS) and have it show in the unRAID shares when browsing the unRAID shares with Windows. This is called SMB Mount. The UNC path is mounted locally and shared as a \\Tower share. Access to Unassigned Devices shares defaults to Public with everyone having read/write access. User access can be enabled in the Unassigned Devices Settings. Access can be enabled by user for read/write, read only, or no access to Unassigned Devices shares. When a USB device is plugged in or mounted an event is initiated to run a user defined script. This is usefull for backing up files from the server initiated by plugging in the USB device or copying pictures from a camera to the array. Scripts are created unique for each device. You can also setup one script to run whenever any device is plugged in or mounted. Installing the plugin You can install the plugin from the Community Applications plugin or by pasting the following link in the Install Plugin tab on unARAID plugins page. https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg Mount Points and Shares There seems to ba a lot of confusion over a mount point vs. a share. The mount point is where the device is mounted locally on unRAID. A share makes the mount point available in Windows at '\\Tower' as a browseable folder. When devices and SMB Mounts are mounted, they are mounted at /mnt/disks/. They are not a part of the unRAID array and are not mounted at /mnt/disk/ which is for unRAID disk drives. As an example, you have a device named 'MyDisk'. When it is mounted, it is accessed locally at /mnt/disks/MyDisk. If you want to use 'MyDrive' in a Docker you would refer to it by '/mnt/disks/MyDrive'. It is not automatically shared at '\\Tower\MyDrive'. To share 'MyDrive', you would turn on the 'Share' switch for the drive and 'MyDrive' would be shared at '\\Tower\MyDrive'. The share 'MyDrive' is not accessed at /mnt/user/MyDrive' because it is not an unRAID user share. Mount points and shares are two separate things. Partitions and Formatting If you turn on the destructive mode in the Unassigned Devices Settings, you will be able to delete partitions and format disks. It is defaulted off as a safety measure. Scripts Here is an example script that will back up a Pictures share to a USB drive when plugged in. The USB drive is unmounted once the script completes so you just plug in the drive, wait for it to be completed, and then unplug the drive. The beeps in the script will make speaker sounds if you have a speaker to let you know when the drive is plugged in, when the backup has started, and when the backup has finished and the drive unmounted. The nice thing about this script is that all you have to do is plugin the drive and wait for it to finish. You will also be notified when it is done if you have turned on unRAID notifications. Set the drive to auto mount. Set the script to run in the background. If you mount and unmount the drive from the Unassigned Devices gui, the drive will mount and unmount but the script will not run because it has detected the 'OWNER' as 'user' and will skip the backup. #!/bin/bash PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin ## Available variables: # AVAIL : available space # USED : used space # SIZE : partition size # SERIAL : disk serial number # ACTION : if mounting, ADD; if unmounting, UNMOUNT; if unmounted, REMOVE; if error, ERROR_MOUNT, ERROR_UNMOUNT # MOUNTPOINT : where the partition is mounted # FSTYPE : partition filesystem # LABEL : partition label # DEVICE : partition device, e.g /dev/sda1 # OWNER : "udev" if executed by UDEV, otherwise "user" # PROG_NAME : program name of this script # LOGFILE : log file for this script case $ACTION in 'ADD' ) # # Beep that the device is plugged in. # beep -l 200 -f 600 -n -l 200 -f 800 sleep 2 if [ -d $MOUNTPOINT ] then if [ $OWNER = "udev" ] then beep -l 100 -f 2000 -n -l 150 -f 3000 beep -l 100 -f 2000 -n -l 150 -f 3000 logger Started -t$PROG_NAME echo "Started: `date`" > $LOGFILE logger Pictures share -t$PROG_NAME rsync -a -v /mnt/user/Pictures $MOUNTPOINT/ 2>&1 >> $LOGFILE logger Syncing -t$PROG_NAME sync beep -l 100 -f 2000 -n -l 150 -f 3000 beep -l 100 -f 2000 -n -l 150 -f 3000 beep -r 5 -l 100 -f 2000 logger Unmounting PicturesBackup -t$PROG_NAME /usr/local/sbin/rc.unassigned umount $DEVICE echo "Completed: `date`" >> $LOGFILE logger Pictures Backup drive can be removed -t$PROG_NAME /usr/local/emhttp/webGui/scripts/notify -e "unRAID Server Notice" -s "Server Backup" -d "Pictures Backup completed" -i "normal" fi else logger Pictures Backup Drive Not Mounted -t$PROG_NAME fi ;; 'REMOVE' ) # # Beep that the device is unmounted. # beep -l 200 -f 800 -n -l 200 -f 600 ;; 'ERROR_MOUNT' ) /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Server Backup" -d "Could not mount Pictures Backup" -i "normal" ;; 'ERROR_UNMOUNT' ) /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Server Backup" -d "Could not unmount Pictures Backup" -i "normal" ;; esac Here is a nice UD script for importing photos from a camera/memory card into the array: Photo Script Thanks to ljm42. Cron Task A better way of running cron scripts is the 'User Scripts' plugin. You can set up a script to run at a particular time to perform disk operations. It is best to leave the device mounted so the script can access the drive. This is a simple way to set up a cron task to run a script to copy files to a backup. This method is a little cumbersome, but does work well. You will need to set up your drive to auto mount and it has to be left mounted. You can use the default script or the following one if you want beeps when the drive is mounted and unmounted. Set the drive to auto mount. he drive has to stay mounted for the script to work. Set the script to run in the background. #!/bin/bash PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin ## Available variables: # AVAIL : available space # USED : used space # SIZE : partition size # SERIAL : disk serial number # ACTION : if mounting, ADD; if unmounting, UNMOUNT; if unmounted, REMOVE; if error, ERROR_MOUNT, ERROR_UNMOUNT # MOUNTPOINT : where the partition is mounted # FSTYPE : partition filesystem # LABEL : partition label # DEVICE : partition device, e.g /dev/sda1 # OWNER : "udev" if executed by UDEV, otherwise "user" # PROG_NAME : program name of this script # LOGFILE : log file for this script case $ACTION in 'ADD' ) # # Beep that the device is plugged in. # beep -l 200 -f 600 -n -l 200 -f 800 ;; 'REMOVE' ) # # Beep that the device is unmounted. # beep -l 200 -f 800 -n -l 200 -f 600 ;; esac Now set up a cron file in the /flash/config/plugins/dynamix/ directory. Name the file 'custom.cron' (or a name of your own choosing.cron) with the following contents. This will set up a cron task to run at 4:30 AM every day. It runs a script in the /boot/custom/ directory called DailyBackup. # Custom cron scripts: 30 4 * * * /boot/custom/DailyBackup &> /dev/null Sample Daily Backup script #!/bin/bash # # Perform daily backup. # MOUNTPOINT=/mnt/disks/DailyBackup PROG_NAME=DailyBackup logger Started -t$PROG_NAME if [ -d $MOUNTPOINT ] then logger Pictures share -t$PROG_NAME rsync -a -v /mnt/user/Pictures $MOUNTPOINT/ 2>&1 logger Completed -t$PROG_NAME /usr/local/emhttp/webGui/scripts/notify -e "unRAID Server Notice" -s "Server Backup" -d "Daily Backup completed" -i "normal" else logger Daily Backup Drive Not Mounted -t$PROG_NAME fi After you have copied your cron file to the dynamix directory you will have to load the cron file manually one time to get it started. unRAID will manage the cron file after that and insert it into the crontab for you. Use the following command to load the cron file the first time. /usr/local/sbin/update_cron Pooling Disks You can create multiple pools with UD, with some limitations, details here. Click on the 'Help' button on the main menu bar of unRAID to get some additional help. If you hover your mouse over an active area on the gui, you will see tool tips that will help you understand the operation of the active area. Verify you have the latest version installed and check the syslog for information if you are having any issues. Many questions can be answered by reading this post and checking the syslog.

This is a plugin that was inspired by the unmenu log view that highlighted certain lines in the log in color for ease in finding significant events. Each line of the log is checked for events that may be significant and they are highlighted in a color representative of that event. I used unmenu when I was on unraid V4 and really liked the highlighted log feature. The event strings that are searched were taken from the unmenu syslog configuration file. Those event strings were mostly developed in the V4 days and are not totally up to the V6 events. For example the only file system in those days was reiserfs. Now unraid includes xfs and btrfs. I expect that additional event strings will be added because of the V6 changes. This is the link to download the enhanced log plugin: https://github.com/dlandon/enhanced.log/raw/master/enhanced.log.plg The plugin can also be installed through "Community Applications". The plugin replaces the built in System Log'' to view the enhanced log. There is an icon in the 'Settings' page to configure which log events are highlighted - "Errors", "Minor Issues", etc. This allows you to highlight only the areas you want to view. You can also set the colors you want for the various log events. If you feel there are events in the log that need to be highlighted, please post a snipet of the log with those events so I can add the search strings to highlight the log event.

Update the plugin and then go to Settings->Syslog Settings and go to the Colors tab and click the Default button. This will load the new default color scheme that is more compatible with the black theme.

This is an update of the Zoneminder Docker initially created by aptalca to the latest version of Zoneminder. You can do an in place update of this Docker and your current configuration will be kept and the database updated. Note: This Docker has settings pre-configured so all you have to do is install your cameras and make your particular adjustments. Changes can be made as necessary for special needs after installation. If you need help with Zoneminder click here for the documentation and here for the forum. Search for Zoneminder in CA and install it. The Zoneminder WebUI can be accessed at https://IP:8443/zm. Only secure access is allowed. A self signed ssl certificate is generated when the Docker starts if it does not exist and it is stored at appdata/Zoneminder/keys. This certificate is used for https access to Zoneminder and for the zmNinja Event Notification Server. You can supply your own certificate and replace the auto generated certificate if you'd like. An update is performed on every startup of the Zoneminder Docker to keep patches and updates applied to Linux. Zoneminder is not updated. A new docker has to be built to update Zoneminder. This is done so I can verify the update before it is applied. PTZ Control Scripts: If you have a PTZ camera that has a custom script, put it in the '/appdata/Zoneminder/control/' folder and whenever the Zoneminder docker is started, it will copy the script to the '/usr/share/perl5/ZoneMinder/Control' folder in the docker image. Change Databases: You can change to an external database by overwriting default the zm.config database settings. Change the following settings for your particular needs and put them in the file "99-mysql.conf' in the /appdata/Zoneminder/conf/ folder. Your settings will be installed when the docker is started. # ZoneMinder database hostname or ip address ZM_DB_HOST=localhost # ZoneMinder database name ZM_DB_NAME=zm # ZoneMinder database user ZM_DB_USER=zmuser # ZoneMinder database password ZM_DB_PASS=zmpass Set up eMail Notifications: Follow the guide here. The ssmtp configuration files are at appdata/Zoneminder/ssmtp/. Note: Be sure to set up a filter for emails. These changes are kept if Zoneminder is updated or removed and re-installed. Set up zmNinja Event Norifications: The zmNinja Event Notification Server is included in the Docker. The zmNinja Notification Server pushes events to your iOS and Android devices. Enable the 'Event Server' on your iOS or Andriod device and the server will automatically connect. Be sure to forward port 9000 on your router to the Zoneminder Docker. The server is configured to run with security with the self signed certificate generated on installation of Zoneminder. The zmNinja event server is not enabled by default. Enable it in Options->System->OPT_USE_EVENTNOTIFICATION. You can configure the zmnotificationserver.pl to run with or without security. Modify the 'appdata/Zoneminder/zmeventnotification.ini' file to turn off ssl and configure other parameters like the port to listen on for events. If you change the port, you'll need to modify the port in the docker configuration. Restart the Docker after you've made changes to the zmeventnotification.ini file. There is a 'hook' feature of zmeventnotification where processing after an event can be hooked for custom processing after an event. An appdata/Zoneminder/hook folder is created where you can copy the files you need for custom event processing. When the docker is started, the files in the appdata/Zoneminder/hook folder are copied into the image at /usr/bin/. Be sure to set the proper permissions for the files in the appdata/Zoneminder/hook folder. Here is a guide on the notification server. crontab Zoneminder has the ability to change states so you can have different operation of your cameras based on the time of day and/or day of the week. To set up cron events, create a file called 'cron; and place it in the appdata/Zoneminnder/ folder. The 'cron' file contents should be the crontab entries you want created. When the Zoneminder Docker is started it will put your 'cron' file entries into the root crontab. Example 'cron' file: # Daytime camera operation 0 8 * * * /usr/bin/zmpkg.pl Daytime # Nightime camera operation 0 20 * * * /usr/bin/zmpkg.pl Nighttime Note: The default purge 'Filter' is set for 50% of the disk where the Zoneminder data is stored. On Unraid this is not a good way to manage the growth of the events. I recommend setting up a purge filter based on the age of the events. This is the way to set up a filter to purge events by age: This filter purges events older than 30 days. You can set the 'days ago' to a value that makes sense for you. User Script You can enable a custom user script. Edit the docker template xml and add a variable: ADVANCED_SCRIPT with a value of 1. This will enable your script. Put your script in the appdata/Zoneminder/ folder and name it userscript.sh. The script will be executed each time the Docker is started before Zoneminder is started. Be sure to chmod +x userscript.sh so the script is executable. Version 1.32.x update release notes: Be sure to set the display css settings. The zmNinja event server is not enabled by default. Enable it in Options->System->OPT_USE_EVENTNOTIFICATION. You can make changes to the zmeventnotification.ini file in the appdata/config/ folder. Restart the docker after making changes. You cannot change the zm.conf file in this version. You can override the zm.conf settings by creating a '.conf' file and placing it in the apdata/config/conf/ folder. The default zm.conf file is stored in the appdata/config/conf folder as well as a README on changing the default settings. For example, if you want to specify your own mysql database, copy the settings from the zm.default for the database settings and place them in a new file named '99-mysql.conf' in the appdata/config/conf folder. These settings will be used to overwrite the zm.conf default settings. Restart the docker after making your changes. You will have to redo any filter settings. The config/skins directory has been removed. The skins are not persistent across versions.

You are getting that error because the certificate is self signed. To get rid of that you will need a real certificate.

It doesn't. You just can't seem to sort out the ports, and assigning an ip to Zoneminder is an alternative. If you don't want to give it its own ip address, you'll have to sort out why port 8443 doesn't work.

That ip is Unraid's. You need to select Custom: br0 as the network and assign Zoneminder its own ip address.

This is a plugin that allows you to adjust some NIC parameters, disk caching, and other tweaks. Some users have found that these tweaks will improve media streaming and gaming performance of VMs. Feel free to experiment, but I don't recommend just cranking everything up to the maximum values. Doing that may be counterproductive. You will have an impact on RAM used, and may create a situation where Linux kills some processes to recover memory causing all sorts of problems with unRAID. Your results will depend on your NIC(s) and what features are available, the architecture of your network, your total RAM, disk drives, and your VMs. Click on the 'Help' button and read carefully before making any adjustments so you understand what each tweak does. Install the plugin using Community Applications or this link: https://github.com/dlandon/tips.and.tweaks/raw/master/tips.and.tweaks.plg Updates Added the capability to disable FTP and Telnet. Added feature to archive syslogs from the powerdown plugin. Added a feature to kill specified tasks when the array is stopped.

Try assigning a static ip address to the Zoneminder docker.

Are you using port 8443 for Unraid access?

I have made an adjustment in system parameters to improve the performance of redis. Unfortunately the only way to apply the change is through a command line parameter. This means I had to change the docker template. There are two ways to make the change: - Go to CA and search for ownCloud and apply the default settings and make any changes necessary to your situation. - Switch to the Advanced VIew and append the following to the Extra Parameters Field. --sysctl=net.core.somaxconn=511 Edit: Seems there were also a few other system settings that needed to be set to fix the Redis performance issues that can't be set this way. I'm issuing an update of the docker that will handle the settings internally, but the docker has to be run 'Privileged' in order for them to take effect. When an update shows up, edit your template and remove the '--sysctl=net.core.somaxconn=511' from the 'Extra Parameters' and turn on the 'Privilege' setting.

The diagnostics will have the history of what has been happening plus some information on your system hardware and setup.

Please post your diagnostics.

There have been several posts on the forum about VM performance improvements by adjusting CPU pinning and assignments in cases of VMs stuttering on media playback and gaming. I've put together what I think is the best of those ideas. I don't necessarily think this is the total answer, but it has helped me with a particularly latency sensitive VM. Windows VM Configuration You need to have a well configured Windows VM in order to get any improvement with CPU pinning. Have your VM configured as follows: Set machine type to the latest i440fx.. Boot in OVMF and not seaBIOS for Windows 8 and Windows 10. Your GPU must support UEFI boot if you are doing GPU passthrough. Set Hyper-V to 'yes' unless you need it off for Nvidia GPUs. Don't initially assign more that 8 GB of memory and set 'Initial' and 'Max' memory at the same value so memory ballooning is off. Don't assign more than 4 CPUs total. Assign CPUs in pairs to your VM if it supports Hyperthreading. Be sure you are using the latest GPU driver. I have had issues with virtio network drivers newer than 0.1.100 on Windows 7. Try that driver first and then update once your VM is performing properly. Get the best performance you can by adjusting the memory and CPU settings. Don't over provision CPUs and memory. You may find that the performance will decrease. More is not always better. If you have more than 8GB of memory in your unRAID system, I also suggest installing the 'Tips and Tweaks' plugin and setting the 'Disk Cache' settings to the suggested values for VMs. Click the 'Help' button for the suggestions. Also set 'Disable NIC flow control' and 'Disable NIC offload' to 'Yes'. These settings are known to cause VM performance issues in some cases. You can always go back and change them later. Once you have your VM running correctly, you can then adjust CPU pinning to possibly improve the performance. Unless you have your VM configured as above, you will probably be wasting your time with CPU pinning. What is Hyperthreading? Hyper threading is a means to share one CPU core with multiple processes. The architecture of a hyperthread core is a core and two hyperthreads. It looks like this: HT ---- core ---- HT It is not a base core and a HT: core ---- HT When isolating CPUs, the best performance is gained by isolating and assigning both pairs for a VM, not just what some think as the '"core". Why Isolate and Assign CPUs Some VMs suffer from latency because of sharing the hyperthreaded cpus. The method I have described here helps with the latency caused by cpu sharing and context switching between hyperthreads. If you have a VM that is suffering from stuttering or pauses in media playback or gaming, this procedure may help. Don't assign more cpus to a VM that has latency issues. That is generally not the issue. I also don't recommend assigning more than 4 cpus to a VM. I don't know why any VM needs that kind of horsepower. In my case I have a Xeon 4 core processor with Hyperthreading. The CPU layout is: 0,4 1,5 2,6 3,7 The Hyperthread pairs are (0,4) (1,5) (2,6) and (3,7). This means that one core is used for two Hyperthreads. When assigning CPUs to a high performance VM, CPUs should be assigned in Hyperthread pairs. I isolated some CPUs to be used by the VM from Linux with the following in the syslinux configuration on the flash drive: append isolcpus=2,3,6,7 initrd=/bzroot This tells Linux that the physical CPUs 2,3,6 and 7 are not to be managed or used by Linux. There is an additional setting for vcpus called 'emulatorpin'. The 'emulatorpin' entry puts the emulator tasks on other CPUs and off the VM CPUs. I then assigned the isolated CPUs to my VM and added the 'emulatorpin': <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> <emulatorpin cpuset='0,4'/> </cputune> What ends up happening is that the 4 logical CPUs (2,3,6,7) are not used by Linux but are available to assign to VMs. I then assigned them to the VM and pinned emulator tasks to CPUs (0,4). This is the first CPU pair. Linux tends to favor the low numbered CPUs. Make your CPU assignments in the VM editor and then edit the xml and add the emulatorpin assignment. Don't change any other CPU settings in the xml. I've seen recommendations to change the topology: <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='2'/> </cpu> Don't make any changes to this setting. The VM manager does it appropriately. There is no advantage in making changes and it can cause problems like a VM that crashes. This has greatly improved the performance of my Windows 7 Media Center VM serving Media Center Extenders. I am not a KVM expert and this may not be the best way to do this, but in reading some forum posts and searching the internet, this is the best I've found so far. I would like to see LT offer some performance tuning settings in the VM manager that would help with these settings to improve performance in a VM without all the gyrations I've done here to get the performance I need in my VM. They could at least offer some 'emulatorpin' settings. Note: I still see confusion about physical CPUs, vcpus, and hyperthreaded pairs. CPU pairs like 3,7 are two threads that share a core. It is not a core with a hyperthread. When isolating and assigning CPUs to a VM, do it in pairs. Don't isolate and assign one (3) and not its pair (7) unless you don't assign 7 to any other VM. This is not going to give you what you want. vcpus are relative to the VM only. You don't isolate vcpus, you isolate physical CPUs that are then assigned to VM vcpus.

Click on Advanced View and you can edit the WebUI link.

Https://10.0.0.7/zm

Show a screen shot when you try to access the Zoneminder WebUI. Just telling me it doesn't work is of no value.

You might have a port mapping issue. Setting the "Network Type" to "Host" allows a Docker access all ports for that ip address. Set Zoneminder to have a static ip address. Be sure you aren't using port 8443 for Unraid access.

Yes. It just configures the Docker, not Zoneminder.

Settings->Unassigned Devices->Enable SMB Security?