SpaceInvaderOne

64 gig

sure heres my dropbox link https://www.dropbox.com/s/gymaipg6vprd508/MSI_util.zip?dl=0

Yes should be stickied! Yes dockers can be pinned aswell. click the advanced view then add to extra parameters cpuset-cpus= The cpus can be pinned if you have or havent used isolcpus. I dont pin to isolcpus cores myself just to the ones used by unraid, i just avoid pinning dockers to the first pair of threads as i have heard the linux os prefers these itself. Edit.....oops sorry squid see you just replied before me!!

Thankyou dlandon for that excellent info. I have isolcpu 8 cores for my vms and left the rest for unraid and dockers and pinned emulator tasks to 2 of those cores. Wow i get an extra 1000 score running geek bench3 on my osx vm. And i get no latency on my windows 10 vm. What a difference..... great info thanks so much for sharing

So can they be pinned to dockers or only vms after isolocpus I don't know. I've not tried. I emailed the limetech guys about this and thought i would post what they replied in case others are interested. isolcpus prevents the host OS from assigning the logical CPUs specified in the parameter to any processes (kernel or user space) at boot. Users can manually assign processes back to those CPUs using Linux's cpuset capabilities. Docker and virtual machines both support this. So you can use isolcpus to reserve a set of logical CPUs and then assign docker containers to some and VMs to others and leave the unisolated CPUs for host-based tasks, if you so desire. There may be some advantages to this, there may be some disadvantages to this. With respect to adding isolcpus capability post-boot, so that you can toggle its usage on and off, that is an interesting concept that we have been investigating, but it's not something that's built into Linux's capability set today just yet. We could manually manipulate some things in the user space for this, but it's not something we're tackling as a project right now.

So can they be pinned to dockers or only vms after isolocpus

Thats interesting. I did some testing a few days ago pinning hyperthreaded pairs then pinning none hyperthreaded pairs and running passmark cpu benchmark software afterwards this is my results using a 12 core xeon @ 2.4ghz Using 8 threads or 4 cpu cores firstly 8 threads with paired hyperthreads the passmark score is 7256 next 8 threads all from non paired separate so one thread from different core passmark score is 10417 I as the threads were all on separate cores the speed was faster but i guess wouldnt have been if the other thread on each core was being used by another process. I know this is a bit off topic but thought it interesting as i never expected this result

Lol Sent from Winterfell using a raven

you can passthrough whole disk or specify the partition. eg. whole disk would be <source dev='/dev/disk/by-id/ata-ST3500312CS_9VVERKB1'/> whilst for partion 1 would be <source dev='/dev/disk/by-id/ata-ST3500312CS_9VVERKB1-part1'/> the ata-ST3500312CS_9VVERKB1 part change that to ata-yourdeviceid The problem with using sdx is that they can change on reboot

Just relating to the power consumption of both methods. i agree with a small number of drives it would be negligible. Because as well remember the data is written to the cache first, then at a later time written to the array, so it uses power twice to do its writes.

Thanks for advise. I will keep an eye on it

Hi , How serious is having a Reallocated sector count raw value of 1. I just got this warning on the smart. Should i replace the drive asap or could i just acknowledge the error and see if it gets worse?? # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 079 063 044 Pre-fail Always Never 84007277 3 Spin up time 0x0003 092 089 070 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 020 Old age Always Never 412 5 Reallocated sector count 0x0033 100 100 036 Pre-fail Always Never 1

I removed the option to move the apps tab down to settings because as a general rule it is a very bad idea to be modifying system files (which is what I was doing). This was always going to be a temporary fix. Starting with 6.1.7, you can go into display settings, and move the User's tab to settings which will fix those display aberrations Ah thanks thats working great now

I have just updated the community applications plugin and now i cant find how to not have the tab "apps" added to the top bar of the gui. As i use Dynamix System Buttons plugin the gui is messed up when this extra app tab is at the top of gui. How can i get this back to how it was? Thanks

Interesting, but doesn't change our recommendations. When Linus did the gaming + NAS video (not 2 gamers or 7), he had a skylake system and the ACS override didn't work for him. Luck of the draw on the hardware I guess. Certainly doesn't change anything with respect to igd pass through support. @JonP Yeah bit the he got the gpu passed through(it was only the onboard sound he couldnt pass through). I think if you say skylake isnt compatable with unraid, or not recommended for gpu passthrough, it may put alot of people off choosing to try or purchase unraid, as many people may not want to buy older hardware when building a new rig. There have been quite a few of us who have built our unraid rigs with skylake, and many people using kvm with passthough on other linux distros. Why dont you make a section with pros and cons of each main type of cpu. I realise that its hard for you to test everything and expensive, but this would help people deceide what to buy and what to expect. You guys official online manual on the wiki is for 4.7! I know it takes time updating the website (and i would far rather have you guys improving unraid and getting us our 6.2 soon!) Anyway thanks for all your hardwork you do for us.

Are you sure ACS overide not supported in Skylake CPUs, Jon? I have Skylake (hardware in sig) and ACS works for me This is my iommu groups with ACS override. Note my 2 gpus in separate groups 11 and 12 PCI Devices 00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07) 00:01.1 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x8) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 06) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Device a102 (rev 31) 00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) 01:00.1 Audio device: NVIDIA Corporation Device 0fba (rev a1) 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] 04:00.0 USB controller: ASMedia Technology Inc. Device 1242 IOMMU Groups Warning: Your system has booted with the PCIe ACS Override setting enabled. The below list doesn't not reflect the way IOMMU would naturally group devices. To see natural IOMMU groups for your hardware, go to the VM Settings page and set the PCIe ACS Override setting to No. /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/2/devices/0000:00:01.1 /sys/kernel/iommu_groups/3/devices/0000:00:02.0 /sys/kernel/iommu_groups/4/devices/0000:00:14.0 /sys/kernel/iommu_groups/4/devices/0000:00:14.2 /sys/kernel/iommu_groups/5/devices/0000:00:16.0 /sys/kernel/iommu_groups/6/devices/0000:00:17.0 /sys/kernel/iommu_groups/7/devices/0000:00:1b.0 /sys/kernel/iommu_groups/8/devices/0000:00:1c.0 /sys/kernel/iommu_groups/8/devices/0000:04:00.0 /sys/kernel/iommu_groups/9/devices/0000:00:1d.0 /sys/kernel/iommu_groups/10/devices/0000:00:1f.0 /sys/kernel/iommu_groups/10/devices/0000:00:1f.2 /sys/kernel/iommu_groups/10/devices/0000:00:1f.3 /sys/kernel/iommu_groups/10/devices/0000:00:1f.4 /sys/kernel/iommu_groups/10/devices/0000:00:1f.6 /sys/kernel/iommu_groups/11/devices/0000:01:00.0 /sys/kernel/iommu_groups/11/devices/0000:01:00.1 /sys/kernel/iommu_groups/12/devices/0000:02:00.0 /sys/kernel/iommu_groups/12/devices/0000:02:00.1 now this is my iommu groups wothout acs override. Note my 2 gpus now in group 1 PCI Devices 00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07) 00:01.1 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x8) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 06) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Device a102 (rev 31) 00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) 01:00.1 Audio device: NVIDIA Corporation Device 0fba (rev a1) 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] 04:00.0 USB controller: ASMedia Technology Inc. Device 1242 IOMMU Groups /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.1 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.1 /sys/kernel/iommu_groups/1/devices/0000:02:00.0 /sys/kernel/iommu_groups/1/devices/0000:02:00.1 /sys/kernel/iommu_groups/2/devices/0000:00:02.0 /sys/kernel/iommu_groups/3/devices/0000:00:14.0 /sys/kernel/iommu_groups/3/devices/0000:00:14.2 /sys/kernel/iommu_groups/4/devices/0000:00:16.0 /sys/kernel/iommu_groups/5/devices/0000:00:17.0 /sys/kernel/iommu_groups/6/devices/0000:00:1b.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.0 /sys/kernel/iommu_groups/7/devices/0000:04:00.0 /sys/kernel/iommu_groups/8/devices/0000:00:1d.0 /sys/kernel/iommu_groups/9/devices/0000:00:1f.0 /sys/kernel/iommu_groups/9/devices/0000:00:1f.2 /sys/kernel/iommu_groups/9/devices/0000:00:1f.3 /sys/kernel/iommu_groups/9/devices/0000:00:1f.4 /sys/kernel/iommu_groups/9/devices/0000:00:1f.6

I think this is a great idea. But what you can do right now.What i do is to use a "wake on lan" app on my android phone and tablet. This used with the VM Wake On Lan plugin means you can start a vm easily from the phone. My girlfriend does this to start openelec. Then once any vm has started, well its not too hard to shutdown!!!!! but a dedicated app.....yes please

Looks like the edit no longer in your xml. After you edited it and took out the Creative device in vm manager it gets rid of the xml edit. You must edit the xml then leave it, if you gointo vm manager and change anything it will get rid of anything manually added to the xml

Try using the usb driver for that controller(via) from the driver cd for your motherbaord. Or if you dont have it goto motherboard manufacturers website and dl the driver from there.

when checking the lsusb are you plugging a usb 2.0 device or usb 3 device in to check it. Maybe try a usb 3.0 device if you have one. (maybe worth a try) If you are sure that device 02:00.0 USB controller: VIA Technologies, Inc. Device 3483 (rev 01) isnt the controller your unraid key is on(please double check) then you could just pass it through and see in windows if it is the usb 3 ports on front. add to xml <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=02:00.0,bus=root.1,addr=00.2'/> so end of your xml file would look like this <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=06:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=01.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=06:00.1,bus=root.1,addr=00.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=02:00.0,bus=root.1,addr=00.2'/> </qemu:commandline> </domain>

for now ive removed this and building a new image right now Thanks for all your work you do for us Binhex. Much appreciated

edit2: It seems my PIA password is getting changed in my credentials.conf file. Everytime I correct it and restart the docker the password gets changed and I get an AUTH FAIL.... My password aswell. It had an ! (in it ie password!) then in credentials.conf had / infront of ! (ie password/!) Changed my pia password on the site to not have ! and all is fine now

What i do is to have multiple versions of the xml file. I will create a vm using vnc and call it for example windows 10 vnc. This is my base vm template for that machine. After i have that working i will click add vm and choose template .xml expert. I copy the xml from the vm i first created and paste it into the new template, but change two parts. <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>windows 10 vnc</name> <uuid>f2d2787d-25a1-e509-3b7f-c2fd11fa88ea</uuid> <description>windows 10 </description> <metadata> You must change the name to something different to original template say for example <name>windows 10 gpu passthrough</name> then delete the line <uuid>f2d2787d-25a1-e509-3b7f-c2fd11fa88ea</uuid> A new uuid will be automatically added when you first start the vm. This way you can test many different vm configs. i have vms with vnc, gpu passthrough, usb contoller passthrough all in separate xml files

Hi guys. Rebuilt my unraid this weekend from a xeon 1240v2 and socket 1155 motherboard to an i7 6700 and ASRock - Z170M Extreme4 (socket 1151) motherboard. I noticed that the board had 2 usb controllers. The motherboard has only usb3 with usb 2.0 legacy support that can be enabled disabled in bios. root@Prime:~# lspci | grep USB 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 04:00.0 USB controller: ASMedia Technology Inc. Device 1242 So my unraid flash drive would definately be on one controller and i can passthrough the other. I noticed some interesting things. Any usb device i plugged into the intel controller if usb 2.0 would be assigned bus 001. Any usb 3.0 would be assigned bus 002. root@Prime:~# lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0781:5583 SanDisk Corp 64gig usb3.0 flash Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 006: ID 0f30:0001 Jess Technology Co., Ltd Bus 001 Device 002: ID 0781:556b SanDisk Corp UNRAID flash Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Swapping the devices in different usb ports gives same result usb 3.0 always bus 002 and usb 2.0 always bus 001 same on the other contoller. Usb 3.0 is bus 004 and usb 2.0 is bus 003. so looking at the device numbers root@Prime:~# readlink /sys/bus/usb/devices/usb1 ../../../devices/pci0000:00/0000:00:14.0/usb1 root@Prime:~# readlink /sys/bus/usb/devices/usb2 ../../../devices/pci0000:00/0000:00:14.0/usb2 root@Prime:~# readlink /sys/bus/usb/devices/usb3 ../../../devices/pci0000:00/0000:00:1c.0/0000:04:00.0/usb3 root@Prime:~# readlink /sys/bus/usb/devices/usb4 ../../../devices/pci0000:00/0000:00:1c.0/0000:04:00.0/usb4 I assume the usb2.0 legacy of the board just assigns a different bus to usb 2.0 devices. The reason im posting this is just to let others know that your bus can change and always test each port with a usb 2.0 and 3.0 device when checking the bus. I could have checked all my spare usb ports with my usb 3.0 flash and it would have given me a different bus to my unraid flash (which is usb 2.0) and i could have passed that controller by mistake.

thanks for the link. I now have my cirrus graphics and network all working. Still have to boot with step by step which is fine, just a pain.