d.bech

Members
  • Posts

    76
  • Joined

  • Last visited

Everything posted by d.bech

  1. Probably going to get this: https://www.pccasegear.com/products/31634/draytek-vigor-2120-gigabit-router as my current router can't run a VPN server AFAIK and probably do with gigabit anyway
  2. Had a look, not seeing it in there. Router is a TL-R470T+ Emulator here: http://www.tp-link.com/resources/simulator/TL-R470T+/userRpm/Index.htm
  3. Hey guys, I'm currently looking to share my shares outside my network. Me and some friends mess about making youtube videos off and on and I want to be able to share our footage with them so anyone can edit. Currently I'm thinking I'll setup a VPN and that way they can just access the shares as if they were on their own networks. This should allow them to use the share as a source in prem pro. I've spotted and installed this plugin: http://lime-technology.com/forum/index.php?topic=35435.0 I had a look over the settings page for it and then the openVPN setup guide and immediately felt lost. Has anyone seen a guide for setting this plugin up kicking around? Also does anyone forsee any problems with my current plan? Is there a better way of doing this?
  4. Yea it seems to be asking for HDD drivers but it pops up earlier in the install than normal. IIRC in my case it didn't ask for drivers. it would ask me where i wanted to install windows to, and there would be like no hdds listed, so i'd go in and install the stor driver and only then would i see the vdisk. Yep that's what normally happens if I install the international English version.
  5. Yea it seems to be asking for HDD drivers but it pops up earlier in the install than normal.
  6. Maybe my install of unRAID is a little messed up? Or my combination of plugins? Think it's possible? Well the fact is that you are able to get the windows installer going but it just doesn't think that the driver disk contains anything valid for that install. Shouldn't be a plugin or anything that can do that. 6.2 is fairly close to a release point, so I might suggest you wait for that to try again in case it's a bug in the 6.1.6 version with QEMU/KVM. Super wigs me out that the UK version works perfectly. Is there a 6.2 beta about or anything? No publicly available version of 6.2 just yet. Bummer
  7. Maybe my install of unRAID is a little messed up? Or my combination of plugins? Think it's possible? Well the fact is that you are able to get the windows installer going but it just doesn't think that the driver disk contains anything valid for that install. Shouldn't be a plugin or anything that can do that. 6.2 is fairly close to a release point, so I might suggest you wait for that to try again in case it's a bug in the 6.1.6 version with QEMU/KVM. Super wigs me out that the UK version works perfectly. Is there a 6.2 beta about or anything?
  8. Maybe my install of unRAID is a little messed up? Or my combination of plugins? Think it's possible?
  9. Urgh, yea I have no idea what to do. I might just buy a key for the English International/UK version and be done with it. At least I know that works.
  10. Specifically it's saying a MEDIA driver your computer needs is missing. This could be a DVD, USB or Hard Disk driver.
  11. So I was trying the English International ISO while I was waiting for the EDU ISO to download. In this iso I'm not asked for drivers until I get to the partitioning section and it allows me to install the drivers. In the non international ISO it asks me for drivers right after I hit install. Small difference but maybe it means something?
  12. Gonna try out a student version of Win10 I have from uni
  13. Just gave both of those a try, getting the same results EDIT: Oh and yea I am going to viostor\w8.1\amd64 some versions have viostor\w10\amd64 which I've been trying aswell
  14. Just finished downloading 0.1.102 Yup, getting the same thing still. updated main post - also added updated XML
  15. I'm trying to install Windows 10 64bit English after previously using English International. (both ISOs are from microsofts website) This time when I get up to browsing to my virtio iso to tell windows where to find it's drivers it reports that it could not find any new drivers for the hardware installed halp? This worked fine in the past. virtio: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso - Just tried 0.1.102 (the current stable) and am getting the same results - Also tried https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.105-1/ - and https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.110-2/ - and https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.110-1/ XML: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows 10</name> <uuid>fc8280c4-7269-a6dd-ebdf-41fd12e5cf5e</uuid> <description>Windows 10 64bit</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>10485760</memory> <currentMemory unit='KiB'>10485760</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-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='off'/> <vapic state='off'/> <spinlocks state='off'/> </hyperv> <kvm> <hidden state='on'/> </kvm> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' 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/boot/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <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/Win10_1511_English_x64.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <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'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='nec-xhci'/> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:ce:26:89'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows 10.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x045e'/> <product id='0x02e6'/> <address bus='1' device='6'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x17a0'/> <product id='0x0303'/> <address bus='1' device='12'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='1' device='5'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x8087'/> <product id='0x07dc'/> <address bus='1' device='9'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='1' device='2'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='1' device='3'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='1' device='8'/> </source> </hostdev> <memballoon model='virtio'> <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=00:1b.0,bus=root.1,addr=01.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> unraid-diagnostics-20160113-2100.zip
  16. Wicked I'll switch that over. Thanks a bunch man. Waiting for windows 10 to download ATM as I had the wrong language for the key I have
  17. I recently installed unraid and a windows 10 VM. All was going fine. Stable good, performance. Then shortly after adding a new HDD to my array my GPU driver just stopped working with the following error: Windows has stopped this device because it has reported problems. (Code 43) What I've tried: - Removed all GPU drivers from the VM and reinstalled the latest from Nvidias website - Uninstalled the GPU from device manager and reinstalled - Created a fresh VM, still the same error. This makes we think I've messed up something in unRAID or my GPU is dead - Just tried a spare GPU and got the same results. (So I've tried a GTX970 and a GTX750ti) - Maybe its a plugin I've installed. I'll try disabling these. XML: <domain type='kvm' id='37' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows 10</name> <uuid>fc8280c4-7269-a6dd-ebdf-41fd12e5cf5e</uuid> <description>Windows 10 64bit</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>10485760</memory> <currentMemory unit='KiB'>10485760</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-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='off'/> <vapic state='off'/> <spinlocks state='off'/> </hyperv> <kvm> <hidden state='on'/> </kvm> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' 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='raw' cache='writeback'/> <source file='/mnt/user/boot/Windows 10/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/Win10_1511_EnglishInternational_x64.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' model='nec-xhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </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:ce:26:89'/> <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 10.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='usb' managed='yes'> <source> <vendor id='0x045e'/> <product id='0x02e6'/> <address bus='1' device='6'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x17a0'/> <product id='0x0303'/> <address bus='1' device='49'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='1' device='47'/> </source> <alias name='hostdev2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x8087'/> <product id='0x07dc'/> <address bus='1' device='9'/> </source> <alias name='hostdev3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='1' device='2'/> </source> <alias name='hostdev4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='1' device='46'/> </source> <alias name='hostdev5'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <address bus='1' device='8'/> </source> <alias name='hostdev6'/> </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=00:1b.0,bus=root.1,addr=01.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> Anyone got any ideas? unraid-diagnostics-20160113-2100.zip
  18. Hey I just tried out this menthod as I had a USB mic (ID 17a0:0303 Samson Technologies Corp. C01U Pro condenser microphone) and one of the new Xbox one wireless adapters for windows (045e:02e6 Microsoft Corp.) which were both having issues on my Z97N-Wifi motherboard from gigabyte. The USB mic would show up in unRAID but when passed through to windows the VM could not see it at all. The Xbox one adapter was recognised by windows fine but got error 10 failed to start. Switching to this new mothod has fixed both of these problems