SpaceInvaderOne

Community Developer
  • Posts

    1726
  • Joined

  • Days Won

    29

Everything posted by SpaceInvaderOne

  1. 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
  2. Yes i think thats a great idea. Awesome score 16883 makes me want to upgrade my card!!!
  3. Ok. You dont need to passthrough a sata card for what you want to do. You use a virtual disk as the harddrive. You can use an ssd as an unassigned device in unraid, then create your vdisk on that (of whatever size you want, or multiple vdisks if you want more than 1) However you dont use a cache drive why not use the ssd as cache drive and create the vdisk on the cache. That way you will get a bit more bang for buck on the ssd as it will serve 2 purposes. You can use a virtual cd for disk images. If you dont want to do that i would just use a usb cd drive and pass that through. To backup. What i do is have my os on a 40 gig vdisk and my game data on a 500 gig vdisk. I backup the 40 gig vdisk just by copying and pasting it onto my main array now and then. Then if i need to i could just replace the os vdisk with my backup and get system up. best of luck
  4. 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
  5. This could be very useful to plug a usb device on our machines accessing an unraid vm and have the vm be able to use them!! http://www.usb-over-network.com/usb-over-network.html shame its expensive for a licence!
  6. Looking at your iommu groups both your graphics cards are in the same iommu group /sys/kernel/iommu_groups/1/devices/0000:00:01.0 (Host bridge: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller) /sys/kernel/iommu_groups/1/devices/0000:00:01.1 (00:01.0 PCI bridge: Intel Corporation Xeon E3-1200) /sys/kernel/iommu_groups/1/devices/0000:01:00.0 (01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTX 550 Ti) /sys/kernel/iommu_groups/1/devices/0000:01:00.1 (01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller) /sys/kernel/iommu_groups/1/devices/0000:02:00.0 (02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]) /sys/kernel/iommu_groups/1/devices/0000:02:00.1 (02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV610 HDMI Audio) This will cause problems. You must split them up. Have you tried PCIe ACS Override set to yes?
  7. Problem looks like your gpu not alone in its own iommu group /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.1 Try the PCIe ACS Override set to yes and see if that sets the gpu in its owm iommu group. hope that helps
  8. 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.
  9. 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>
  10. It sounds like when you shutdown the vm its not releasing the graphics card, so when you start it again the screen is black. restarting the server releases the card hence the vm works again. best to post your pci devices iommu groups and xml so we can see that
  11. Just setup a win 10 vm same specs but with ovmf bios i7 6700, ASRock - Z170M Extreme4, EVGA gtx 960 ovmf i440fx 2.3, 8 cpu cores, 24 gigs ram test score graphics physics combined fire strike 1.1 6975 8072 10770 2738.............all better than my seabios vm skydiver 1.0 20629 26176 10061 20353...........all slightly lower than my seabios vm cloudgate 1.1 22476 49975 7682..........................higher graphics slightly lower physics each test i ran 3 times and got similar results. Overall it would seem for me anyway i get better 3d performance using an ovmf vm
  12. Sorry can you also post your pci devices and iommu groups from the tools, system devices. Please post it using the insert code button on the tool bar # just makes it easier to read than a file attachment. so your xml would look like this <domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows Rig</name> <uuid>9e4bbedc-f281-a0d5-4129-c2589968ed39</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='6' threads='1'/> </cpu> <clock offset='localtime'> <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/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Domains/Windows Rig/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/en_windows_10_multiple_editions_version_1511_x64_dvd_7223712.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/virtio-win-0.1.112.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:41:26:73'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows Rig.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x14' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <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=01: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=00.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:03.0,bus=root.1,addr=01.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1b.0,bus=root.1,addr=02.0'/> </qemu:commandline> </domain>
  13. yes the first specs is from the server hosting my vm. i7 6700, ASRock - Z170M Extreme4, EVGA gtx 960 The second is from the vm itself seabios i440fx 2.3, 8 cpu cores, 24 gigs ram you can download the 3dmark basic from http://www.techpowerup.com/downloads/2497/futuremark-3dmark-2013-v1-5-915/
  14. ah yeah the unraid 6.2 "soon™" edition, I want the unraid 6.2 "now" edition!!!!!!!!!! ....but i was never patient
  15. To get started mine is win 10 vm i7 6700, ASRock - Z170M Extreme4, EVGA gtx 960 seabios i440fx 2.3, 8 cpu cores, 24 gigs ram test score graphics physics combined fire strike 1.1 6804 7873 10619 2661 skydiver 1.0 20769 26255 10140 20881 cloudgate 1.1 22187 47923 7705
  16. Hi Thought i'd make a post where we can post some benchmarks of our gaming vms using 3d mark. Post your cpu, motherboard, and graphics card in your unraid box. Then type of bios seabios or ovmf. Amount of cpu cores and ram assigned.
  17. disconnect your harddrives you use for your windows computer. pop in a spare drive if you have one. Then boot it off a usb. that way you can do some proper testing. I have never virtualised unraid so couldnt help you with that.
  18. Yes sleep hibernation causes probs. Follow through Jon Panozzo's guide especially from 15:20 onwards there are a few post install things to do to on a win 10 vm.
  19. I had a similar issue with my onkyo amp. I cant remember quite what i did but it was into do with the hdmi setting within the amp. Also you must have the amp set to the correct hdmi channel before you start the vm. If you dont the graphics card doesnt see its plugged into an hdmi and the display on card defaults to the dvi port. Once the vm has started it you can switch hdmi channels on the amp with no probs but you must start the vm with amp on the correct hdmi channel hope this helps
  20. Best thing you can do is passthrough a whole usb controller. Then anything you plug into it will work plus you will have the benefit of usb hot swap. Guide is here http://lime-technology.com/forum/index.php?topic=36768.0
  21. more info on msi interupts here http://lime-technology.com/wiki/index.php/UnRAID_6/VM_Guest_Support#Enable_MSI_for_Interrupts_to_Fix_HDMI_Audio_Support
  22. Try enabling msi interupts for the nvidea card. i had some probs with my gtx 960 until i did use this prog https://www.dropbox.com/s/gymaipg6vprd508/MSI_util.zip?dl=0 run it as admin on windows and tick the nvidea stuff enable it for the video and audio parts of card
  23. Probably a long shot but try changing the position of the card in different slots without the acs override setting turned on. Maybe in slot 3 and sas cards in 1 and 2 without acs overide. I would try all combinations possible of slots and acs overide on and off