breakline

Members
  • Posts

    36
  • Joined

  • Last visited

Everything posted by breakline

  1. yeah hyper-v always disabled , I've re-installed windows many times on my 660 Ti . what I'm doing now is creating a base image for windows 10 and windows 8 cuz I really don't wanna do the virtio drivers install anymore lol. I decided to simplify things even more so I removed all but one hdmi output from the 970 and I still get the same results. I really don't understand what's happening but after I update the drivers the image gets worse with drivers from Nvidia site or via device manager like it goes from 720p(Microsoft display adapter) to 640x840 or worse. my next step is try a different OS and see what the results are, I saw a lot of arch in the confirmed working doc for 970 but don't know much about it. I have until the 24th to return this card so I'm going to keep trying until the weekend unless I figure out it for sure wont work. and THANKS for the help seriously much appreciated!!!
  2. I tried that today and there were 4 different rom files for my card so I downloaded all of them and renamed them rom1 - rom4 and I tried .bin and .rom and tried again with all steps in my first post. When I add the code to the xml I get no output at all. any other tricks or should I just go back to my 660 Ti ? or maybe a similar card that would work ? I'm just afraid to get another card and go through the same steps again to have it still not work.
  3. So I upgraded from an MSI twin frozr gtx 660 Ti to an asus gtx 970 strix and when I boot into windows with the 970 it only detects 1 of 3 monitors and in device manager it's the dreaded code 43 again. One weird thing I notice is that when I shut down or force stop the VM's with this card is the monitor stays active like it doesn't go to power save mode. everything works great with the 660Ti all 3 monitors & latest drivers and has for months. heres the steps I have tried: and the ONLY difference is the video card. win 8.1 x64 or win 10 x64 new and existing VM's older nvidia drivers . fresh unraid install. with and with out pcie_acs_override=downstream with and without amd_iommu=on iommu=pt iommu=1 vfio_iommu_type1.allow_unsafe_interrupts=1 checked xml's with diff > https://www.diffchecker.com/hdz5w3pz asus bios update checker said up to date for the video card. motherboard bios up to date. q35 and I440fx seabios and ovmf different PCIe slots and 660 Ti works fine in both. with and without the 660 Ti installed. here is my build: motherboard : ASRock Fatal1ty 990FX Killer cpu: fx8350 ram:32GB trident x ddr3 2400 gpu:MSI twin Frozr gtx 660 Ti gpu: ASUS strix gtx970 any help would be appreciated , I'm stuck .
  4. I use deluge vpn docker from binhex and the scheduler seems to work great , I never used it before today but decided to try when I read this post. I have included some screen shots of the different states set in the scheduler and the speeds with each state. I thought I would have to install scheduler but all I had to do was enable it in the preferences . If you don't have a vpn or have other routes set then there is a non vpn one also.
  5. np xxredxpandaxx your noobie docker guide helped me out quite a bit when I started ,its not much but glad to have it come back around a little !
  6. there might be a way to add them after install, but my guess would be time and effort figuring out how might prove more time and effort than just starting freshmy personal opinion anyways, but yeah the screeen where you select browse to find the driver for the virtual disk to show up you just repeat the process for each driver.
  7. When I very first started trying to passthrough my gtx 660 I was having pretty much the same results as you and the ONLY way I found out how to get it to work was adding a 2nd video card for unraid console to latch onto ( no integrated graphics ). I added a cheap gt 210 and unraid console picks that graphics card first so that my 660 is free for the vm's and its working awesome with windows 8.1 and nvidia drivers up to date . granted I have not tried the new steps listed in the wiki ,I'll be doing that here in the next week or 2 so that I can hopefully free that pcie slot for another card/machine. I need a way to tell unraid not to attach the console to the first card or maybe tell unraid that its headless and so I can test it out , but idk if thats possible. anyways if you have another card to test might be worth a shot. my hardware asrock 990fx fatality fx8350 msi gtx660 msi gtx 660TI pe
  8. Did you install the virtio network drivers during windows 8.1 install ? here's the wiki guide : http://lime-technology.com/wiki/index.php/UnRAID_Manual_6#Installing_a_Windows_VM
  9. this might help : jonp ( I think ) has been adding a lot to the wiki lately especially for vm's and passthrough , a lot of good info in here >>> http://lime-technology.com/wiki/index.php/UnRAID_Manual_6#Assigning_Graphics_Devices_to_Virtual_Machines_.28GPU_Pass_Through.29 Warning: Passing through a GPU to a SeaBIOS-based VM will disable console VGA access If you rely upon a locally-attached monitor and keyboard to interact with the unRAID terminal directly, you will lose this ability once you create a SeaBIOS VM with a GPU assigned. This is due to a bug with VGA arbitration and cannot be solved. This does NOT affect your ability to access the console using a telnet or SSH session, but local console access directly will appear to be frozen (blinking cursor, but no visible response to keyboard input). It does not matter if you are using on-board graphics for the console compared to a discrete GPU for the pass through to a VM or not. With OVMF, however, VGA isn't utilized, therefore arbitration isn't needed and therefore your console graphics will remain intact. Note that not all GPUs support OVMF as OVMF requires UEFI support on your GPU.
  10. I already have a synergy license and use it often , for some reason in my brain I was thinking that since I was passing kb and mouse through that I wouldn't be able to do that,momentary lapse of reason i guess , but yes i have it all set up windows 8.1 vm thats always on and set up as the synergy server and then another linux vm as client and my seperate windows 8.1 work machine as client and its working beautifully with all machines and a backup kb and mouse for my work machine in case i need to reboot unraid. Thanks for the reply ghunter . P.S. I'm so psyched about my new setup, I have eliminated 2 machines so far and working on 2 more! unraid + docker + kvm + synergy FTW seriously my vision over the past couple years for what I wanted unraid to become is now a reality - an all in one one super machine ! Thank you limetech!
  11. I totally understand that this may not be possible and I don't really care about the kvm switch , but really just looking for a solution to be able to use only one mouse and keyboard throughout the whole system simultaneously without switching cables or anything. my setup right now for the content of this post is 2 systems #1 is unraid has windows 8.1 passthrough with gtx 660ti 8gb ram and kvm switch passed through (showing as my keyboard model) and keyboard works but have to pass through seperate mouse for mouse functionality, #2 my work system with same keyboard and mouse connected to switch and works flawless,but plan on moving this to unraid as well in the near future. is there a way to get my kvm switch working properly with both mouse and keyboard ? or is there another solution out there that I may not know of that would work better to do what I need to achieve?
  12. Hauppauge WinTV-HVR-2250 Dual TV Tuner 0a:00.0 Multimedia controller: Philips Semiconductors SAA7164 (rev 81)
  13. everything looks right hopefully someone with more experience can chime in ,sorry ajgoyt I got nothing maybe something in this thread will help ? http://lime-technology.com/forum/index.php?topic=38381.0
  14. did you check and make sure the docker img got created? like I have mine set to mnt/cache/docker/docker and so when i go to my network shares and go to Tower2/cache/docker I have the docker img in there.
  15. not sure if this is your issue or not but you need to add the template repositories first before it will show you any templates to choose from and make sure that the repositories actually show in your repository list after you save, and there are many posts and information here on the forums check the stickies first but I hope these help ,some very informative posts to help you from the start. http://lime-technology.com/docker-guide/ and http://lime-technology.com/forum/index.php?topic=37732.0
  16. Thanks net2wire , I had set it up and was able to access it before reading your post but was not too sure or comfortable that it was correct or secure I have no experience with sql or database software at all. I deleted mariadb and owncloud dockers/shares and folders and started fresh following your guide and feel better about it. one question I have though is I set up a share called owncloud and set : /var/www/owncloud/data to /mnt/user/owncloud/ and all owncloud files are in there including my owncloud user folder ,is that how it should be or should I point /var/www/owncloud/data to mnt/cache/docker/apps/owncloud for config and other app files and then set another container volume as /data and point to host path: /mnt/user/owncloud where all my user folders for owncloud would be ? sorry dont even know if that makes sense still trying to wrap my head around how some dockers have seperate container volume and host paths and and what it means and how they work and how that is determined.
  17. I think the answer to your question may be in this thread http://lime-technology.com/forum/index.php?topic=37734.msg348955#msg348955 and like stottle said, you are using the disk image not the actual disk itself so no need to make the disk bootable in bios
  18. ok ive now updated the dockerfile to do a symlink to the db in the teamspeak container to the db on host volume map for /config. so there is a one off operation your now going to have to do if you want to maintain your current db, if you dont care about it then simply update, otherwise do the following:- 1. start the docker container binhex-teamspeak 2. start putty and connect to unraid via ssh 3. type docker exec -it binhex-teamspeak /bin/bash 4. type cp /usr/share/teamspeak3-server/sql/ts3server.sqlitedb /config 5. type exit 6. update the docker container for the new build that should be it, it should now pick up your db and carry on as before, the only thing i dont know is whether it will create a new auto generated admin password, so check the supervisord.log file just incase it does. Works perfect binhex , also showed me how to exec into a docker so double thanks ! I hadn't really set up the ts3 server on unraid 6 yet,just verified that I could connect. All I had to do was transfer my existing ts3server.sqlitedb from unraid 5 to my teamspeak config folder on unraid 6 , I didn't have admin rights at first so tried to copy token from log but said it had been used so I just rebooted server and everythings perfect , admin with all my settings intact as far as I can see so far. thanks for all your work on the containers, currently using TS3,PLEX and delugevpn all great
  19. OK cool thanks , yeah I was trying to add more space but it doesn't work like that, it created raid 1 as its supposed to. so then when I tried to remove it ,the array was broken and it couldn't find it. I did get my disks back though and it was because although I had removed it from the array I still had to set the cache disk back to 1 slot and completely missed that.
  20. I had a great working system ,docker, kvm, gpu passthrough everything was awesome until I tried to add a 2nd cache drive. When I tried to add a 2nd drive to the cache it said both cache drives needed to be formatted so I cancelled and tried to remove new cache drive, it still said my previous cache drive that was working needed to be formatted, SO then I tried new config and re added my drives as they were and was still getting the drive needed to be formatted message, so since this was a test server and I made backups of my vms i said ok format but it is still not letting me add my drive back for cache I click format and it says Started, formatting... but I wait forever and it does not finish so I refresh the page and still no cache or drive showing that was supposed to be cache, I'll start over if I have to but was trying to avoid that
  21. +1 Zoneminder and +1 PXE server
  22. I have been working at this every chance I can and I finally have passthrough working(ish) and can replicate it but windows is still very slow for me , here is my system and steps that I took to get it going: my setup : unraid versions 6b12-14b motherboard : ASRock Fatal1ty 990FX Killer, with IOMMU enabled cpu: fx8350 ram:16GB trident x ddr3 2400 passthrough gpu:msi 660 twin frozr for passthrough unraid gpu: geforce 210 windows 8.1 and windows 10 both with msi 660 twin frozr for passthrough q35 4 vCPU and 8192 (8gb) RAM for both my device list from tools>system devices in unraid webgui : color coding doesnt work in code I guess so I spaced the relevant video card that im passing through 00:00.0 Host bridge: AMD/ATI [Advanced Micro Devices, Inc.] RD890 PCI to PCI bridge (external gfx0 port B) (rev 02) 00:00.2 IOMMU: AMD/ATI [Advanced Micro Devices, Inc.] RD990 I/O Memory Management Unit (IOMMU) 00:02.0 PCI bridge: AMD/ATI [Advanced Micro Devices, Inc.] RD890 PCI to PCI bridge (PCI express gpp port B) 00:09.0 PCI bridge: AMD/ATI [Advanced Micro Devices, Inc.] RD890 PCI to PCI bridge (PCI express gpp port H) 00:0a.0 PCI bridge: AMD/ATI [Advanced Micro Devices, Inc.] RD890 PCI to PCI bridge (external gfx1 port A) 00:0b.0 PCI bridge: AMD/ATI [Advanced Micro Devices, Inc.] RD890 PCI to PCI bridge (NB-SB link) 00:0d.0 PCI bridge: AMD/ATI [Advanced Micro Devices, Inc.] RD890 PCI to PCI bridge (external gfx1 port B) 00:11.0 SATA controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40) 00:12.0 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.2 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.2 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: AMD/ATI [Advanced Micro Devices, Inc.] SBx00 SMBus Controller (rev 42) 00:14.2 Audio device: AMD/ATI [Advanced Micro Devices, Inc.] SBx00 Azalia (Intel HDA) (rev 40) 00:14.3 ISA bridge: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40) 00:14.4 PCI bridge: AMD/ATI [Advanced Micro Devices, Inc.] SBx00 PCI to PCI Bridge (rev 40) 00:14.5 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller 00:16.0 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:16.2 USB controller: AMD/ATI [Advanced Micro Devices, Inc.] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:18.0 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h Processor Function 0 00:18.1 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h Processor Function 1 00:18.2 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h Processor Function 2 00:18.3 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h Processor Function 3 00:18.4 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h Processor Function 4 00:18.5 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h Processor Function 5 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) 01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1) 02:00.0 USB controller: Etron Technology, Inc. EJ188/EJ198 USB 3.0 Host Controller 03:00.0 Ethernet controller: Qualcomm Atheros Killer E2200 Gigabit Ethernet Controller (rev 10) 04:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 660] (rev a1) 04:00.1 Audio device: NVIDIA Corporation Device 0e0b (rev a1) 05:00.0 PCI bridge: Integrated Device Technology, Inc. [iDT] PES12N3A PCI Express Switch (rev 04) 06:00.0 PCI bridge: Integrated Device Technology, Inc. [iDT] PES12N3A PCI Express Switch (rev 04) 06:01.0 PCI bridge: Integrated Device Technology, Inc. [iDT] PES12N3A PCI Express Switch (rev 04) 07:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) 07:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) 08:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) 08:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) #1. add: pcie_acs_override=downstream to syslinux.cfg #2. replace: <vcpu placement='static'>4</vcpu> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> with: <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='cdrom'/> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='2' cores='2' threads='1'/> </cpu> still boots fine in vnc #3. add: <driver name='qemu' type='qcow2' cache='none' io='native'/> between : <disk type='file' device='disk'> <source file='/mnt/cache/kvm/vms/windows 10/windows 10.qcow2'/> still boots in vnc and performance seems improved. #4. add: <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=04:00.1,bus=pcie.0'/>/> </qemu:commandline> between </devices> and </domain> get this error: Warning: libvirt_domain_create(): internal error: early end of file from monitor: possible problem: 2015-02-28T00:29:13.839414Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error opening /dev/vfio/18: No such file or directory 2015-02-28T00:29:13.839447Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 18 2015-02-28T00:29:13.839459Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed. 2015-02-28T00:29:13.839475Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized in /usr/local/emhttp/plugins/dynamix.kvm.manager/classes/libvirt.php on line 838 #5. run: vfio-bind 0000:04:00.0 0000:04:00.1 via command line black screen in vnc and mouse not in sync (passthrough may have been working at this point) had to force shutdown #6. reboot server #7. run vfio-bind 0000:04:00.0 0000:04:00.1 via command line start windows 10 kvm and wants new windows install (good thing i backed it up to another folder) paste backup into vms folder. #8. remove : <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> #10. success working passthrough #11. add: /usr/local/sbin/vfio-bind 0000:04:00.0 0000:04:00.1 to go file #12. add mouse : <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x046d'/> <product id='0xc018'/> </source> </hostdev> #13. reboot server #14. success !!!! passthrough working with mouse but wants to reinstall windows again windows repair says disk is locked #15. copy fully updated vm from back ups and start vm and it worked: passthrough with fully updated windows 10 and mouse working but... very sluggish. #16. to be continued ... my current xml after all tweaks: <domain type='kvm' id='4' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>windows 10</name> <uuid>f564e480-bfca-7981-ec4c-8f74268ec9cf</uuid> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='cdrom'/> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='2' cores='2' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none' io='native'/> <source file='/mnt/cache/kvm/vms/windows 10/windows 10.qcow2'/> <backingStore/> <target dev='hda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/kvm/isos/Windows10_TechnicalPreview_x64_EN-US_9926.iso'/> <backingStore/> <target dev='hdc' bus='sata'/> <readonly/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb0'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:26:b0:57'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc018'/> <address bus='6' device='2'/> </source> <alias name='hostdev0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=04:00.1,bus=pcie.0'/> </qemu:commandline> </domain>
  23. jonp thank you for the quick reply , and yeah I have seen that on a lot of 8.1 machines as well and usually found it to be the windows antimalware service if I remember correctly. Thank you for the info , I'll try those suggestions and look into the libvirt docs and post back. EDIT: ok so i have not checked out the libvirt docs yet but disabling index made a huge improvement so far and made windows useable ,also disabled page file but i dont know how much improvement that made yet. Thank You will post more upon trying your other suggestions
  24. Trying to figure out why it does this and how to fix it or if I am doing something wrong . Long story short : every time I install windows via kvm (many times already) windows is very slow and task manager shows %100 disk . This is my test server so I've reformatted all disks and flash and re-install unraid and same issue , all latest versions. my setup : unraid versions 6b12-14b motherboard : ASRock Fatal1ty 990FX Killer, with IOMMU enabled cpu: fx8350 ram:16GB trident x ddr3 2400 passthrough gpu:msi 660 twin frozr for passthrough unraid gpu: geforce 210 windows 8.1 and windows 10 both with msi 660 twin frozr for passthrough q35 4 vCPU and 8192 (8gb) RAM for both I tried adding this with no improvement: <driver name='qemu' type='qcow2' cache='none' io='native'/> after passthrough it does not seem as bad but still very sluggish. here's my xml's before and after tweaks/passthrough untouched xml: <domain type='kvm'> <name>windows 10</name> <uuid>f564e480-bfca-7981-ec4c-8f74268ec9cf</uuid> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <vcpu placement='static'>4</vcpu> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/mnt/cache/kvm/vms/windows 10/windows 10.qcow2'/> <target dev='hda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/kvm/isos/Windows10_TechnicalPreview_x64_EN-US_9926.iso'/> <target dev='hdc' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </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='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:26:b0:57'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> </domain> and here's my xml with tweaks and passthrough: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>windows 10</name> <uuid>f564e480-bfca-7981-ec4c-8f74268ec9cf</uuid> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='cdrom'/> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='2' cores='2' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none' io='native'/> <source file='/mnt/cache/kvm/vms/windows 10/windows 10.qcow2'/> <target dev='hda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/kvm/isos/Windows10_TechnicalPreview_x64_EN-US_9926.iso'/> <target dev='hdc' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </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='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:26:b0:57'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=04:00.1,bus=pcie.0'/> </qemu:commandline> </domain> not really sure where to go from here so any input would be appreciated.
  25. ok so after many weeks reading many posts in the kvm thread I finally got passthrough working but I need some clarification on a few things and I'm hoping some of you guru's can help , the only way i can get passthrough to work so far is with 2 video cards installed - 1 for unraid and 1 for passthrough ,is that the only way to do it or am i missing something? and further on that same issue, it will only work if the unraid card (gtx 210) is installed to the first pcie slot before my gtx 660 that I am passing through on the 2nd pcie slot, is that how it has to work or is it my hardware ? when I have just the 660 installed or the the 660 in the 1st pcie slot I see the unraid console and when I start the vm the unraid console disappears and my screen just goes to no signal . ok so first I want to post my hardware because I never knew what anyone elses hardware was while going through xml's posted and thought maybe that was the issue but it was not, so : asrock 990fx killer motherboard AMD FX8350 processor GTX 210 video card for unraid ? MSI GTX 660 video card for passthrough and next my go, syslinux and xml files: go #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & #bind pci /usr/local/sbin/vfio-bind 0000:04:00.0 0000:04:00.1 syslinux.cfg default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest label Xen/unRAID OS kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot label Xen/unRAID OS Safe Mode (no plugins) kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot unraidsafemode and my xml with passthrough working and logitech wheel mouse passed through : <domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>window8_2</name> <uuid>b623fc02-b4b9-53e5-b120-0557c45e6d2a</uuid> <metadata> <snapshot1423446187>passthrough working and logitech mouse passed through</snapshot1423446187> <snapshots/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static'>4</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/mnt/cache/kvm/vms/windows8_2/windows8_2.qcow2'/> <backingStore/> <target dev='hda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/kvm/isos/en_windows_8.1_pro_vl_with_update_x64_dvd_6050880.iso'/> <backingStore/> <target dev='hdc' bus='sata'/> <readonly/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb0'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:49:78:59'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc018'/> <address bus='4' device='2'/> </source> <alias name='hostdev0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=04:00.1,bus=pcie.0'/> </qemu:commandline> </domain> I have more questions but these are the main things I would like to try and figure out for now so if anyone has answers I would be very grateful, and this thread seemed to be my go to through out this process thats why im posting it here but im going to list a few other posts that were helpful in my journey here. many thank yous to all who posted in this thread and the ones below. [PLUGIN] VM Manager http://lime-technology.com/forum/index.php?topic=35858.0 First Pass-through attempt http://lime-technology.com/forum/index.php?topic=37733.0 there are more but they're on my other machine ill edit when im at work