CHBMB

Community Developer
  • Posts

    10620
  • Joined

  • Days Won

    51

Posts posted by CHBMB

  1. I agree, Smithwicks is an awesome beer, unfortunately you can't get it in the UK and when I enquired why at the brewery tour in Kilkenny I was told because England has enough ales already, so they only export to the USA, you lucky lot.  Although having said that we do have a huge selection of craft ales in the UK.

  2. I was attempting to do the same thing (passing the GPU) and tried to follow along with the conversation modifying as I thought I needed to.  What I ended up with was UNRAID booting up find but the VM fails to start.  Attached are my go, xml, syslinux. Any thoughts on what I am doing wrong would be much appreciated.  I really thought I was following along really well ;)

     

    I'm pretty new to all this myself but have spent a long time poring over a lot of the xmls posted in this forum and elsewhere trying to figure things out, so I might be wrong but I think that you're trying to passthrough the integrated GPU, which as I understand it, isn't working at the moment.  I think the current advice is to buy a discrete PCI GPU if you want to passthrough graphics.

     

    But like I said I'm new so I might be completely wrong and I'm sure someone with a bit more knowledge will post here if that's the case.  :)

     

    Here's a quote from jonp, who definitely knows what he's talking about in this thread here

    We haven't gotten iGPU pass through to work yet

    Not saying this is impossible, but we haven't been able to get this to work on any of our test systems as of yet.  For those wondering, iGPU means integrated graphics or "on-board" graphics as in the graphics device is not installed into a PCI/e slot on the server, but a part of the motherboard itself.

     

    The challenges relating to iGPU pass through are not easy to solve, but some may be able to get this to work.  We can confirm that none of our test systems have had success with this yet.  We have tried numerous patches of various types into our kernel with no success.  Even Alex Williamson of Red Hat who wrote the patches even said there is limited success in using them at this time.

     

    If anyone gets this working on their system, please share!

  3. I'm in the process of doing just what you are.

     

    I've got one empty drive that I've added to an Unraid pool. Then I've used unmenu to mount my Flexraid NTFS disks. That's as far as I've got at the moment, but next step is SSH and run mc, copy data from 1st flexraid disk, then add that disk to the Unraid pool, copy data from 2nd flexraid disk and so on.

     

    Rsync would be a better way to migrate the data from one drive to another.

     

    I did look at rsync but I wasn't too sure what advantage it offered over mc.  Perhaps I'll have another look..

  4. Thats a great idea! I'll have to try that myself. Thanks bud

     

    No problem mate,  just remember that you'll have no parity protection until all your data has been copied across and you've added a parity drive and done your first parity check.

     

    I've mounted and shared all my NTFS drives using unmenu and then added each disk as a source in Kodi so I can still watch my media during the migration.  Seems to be working pretty well and the wife hasn't noticed any difference which is a good sign!

  5. So, I've successfully managed to mount my 2TB drives in SNAP and can access the shares.  However my 4TB NTFS drives, connected via SATA to either the motherboard or a M1015 card (with flashed firmware) are showing up in SNAP as no fs

     

    Is there any way to mount this in SNAP? Would be happy as a READ only FS as it's pretty much just to keep access to things going whilst I migrate.

     

    Thanks for any help fellas.

     

    So, I figured the problem out in the end.  On my 4TB drives the NTFS partition is actually the second partition, so SNAP cannot mount it. 

     

    My workaround is to use Unmenu to mount and share the partitions, which seems to be working fine.

     

    Although I'm sure I will use SNAP once my array is up and running for a few things!

  6. I'm in the process of doing just what you are.

     

    I've got one empty drive that I've added to an Unraid pool. Then I've used unmenu to mount my Flexraid NTFS disks. That's as far as I've got at the moment, but next step is SSH and run mc, copy data from 1st flexraid disk, then add that disk to the Unraid pool, copy data from 2nd flexraid disk and so on.

  7. OK, so like the title said I'm a novice,

     

    Tried a few things to sort this out, changing a variable at a time and finally managed to see my card in Windows 7.

     

    I think where I was going wrong was in a couple of areas.

     

    Turns out this was the config that managed to get the card seen in Windows for anyone else who is trying to achieve a similar thing.

     

    My go file

    #!/bin/bash
    # Start the Management Utility
    /usr/local/sbin/emhttp &
    
    #bindpci
    /usr/local/sbin/vfio-bind 0000:00:1c.4
    /usr/local/sbin/vfio-bind 0000:02:00.0

     

    My syslinux.cfg {Relevant bit only)

    label unRAID OS
      menu default
      kernel /bzimage
      append intel_iommu=on pcie_acs_override=downstream initrd=/bzroot

     

    My XML file

      <domain type='kvm' id='12' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
      <name>Win7VM</name>
      <uuid>2287f5d8-6c0d-b595-4cb2-43eba3234d99</uuid>
      <memory unit='KiB'>4194304</memory>
      <currentMemory unit='KiB'>4194304</currentMemory>
      <vcpu placement='static'>3</vcpu>
      <resource>
        <partition>/machine</partition>
      </resource>
      <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/VM/Win7VM/Win7VM.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/user/KVM/Media/Win7AIO.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:04:f1:33'/>
          <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/1'/>
          <target port='0'/>
          <alias name='serial0'/>
        </serial>
        <console type='pty' tty='/dev/pts/1'>
          <source path='/dev/pts/1'/>
          <target type='serial' port='0'/>
          <alias name='serial0'/>
        </console>
        <input type='tablet' bus='usb'>
          <alias name='input0'/>
        </input>
        <input type='mouse' bus='ps2'/>
        <input type='keyboard' bus='ps2'/>
        <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0'>
          <listen type='address' address='0.0.0.0'/>
        </graphics>
        <video>
          <model type='vmvga' vram='9216' heads='1'/>
          <alias name='video0'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
        </video>
        <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='vfio-pci,host=02:00.0,bus=pcie.0'/>
      </qemu:commandline>
    </domain>
    

     

    Haven't yet tried it for stability but at least I can see it in Windows!  :D

     

    I think I was trying to pass the pci-e slot through to windows not the actual device, then I tried with both the slot and device, which also didn't work.  In the end loading the vfio-pci driver to both slot and device and then only passing through the device in the xml seemed to crack it.

  8. Well I think that a MAC address is hardware bound and not dependent on whether an IP address is allocated or not.  So Unraid boots, sees three NICs, randomly chooses one as the primary Ethernet whether it has an IP address or not, hence you're seeing a change in the MAC address you expect and not able to access the server as it's not on the LAN and doesn't have a IP address.

  9. I noticed something similar when I tried a dual-nic card on my UnRAID machine.  Didn't really mess around with anything and all three Ethernet cables were plugged in and I would find that although I have a reserved address in my router for the onboard NIC sometimes Unraid was using one of the dual NICs as it's primary Ethernet adapter and therefore my MAC and IP address of my Unraid box would change. 

     

    I didn't get any further investigating the issue as all I really wanted to know was that the card was working.  I do intend at some point to run a VM with PFSense to experiment with, but it'll be a good while before I get to trying that.

     

    I know that hasn't helped solve your problem at all, but sometimes it's nice to know you're not the only one!

     

    My observation led me to believe that Unraid randomly selects a NIC on boot to use, my plan was to try and bind a specific controller at boot time, but I don't yet know how to go about it.

     

    Good Luck though!

  10. One thing I just noticed is that with the Sharkoon case and 5in3 cages, there isn't enough clearance between the motherboard and the back of the cages.  Had to get myself a new case when I was rebuilding because of that. 

     

    Ended up buying a Zalman MS800plus which is a fair bit deeper.

     

    I bought a Rebel12 and got 4 5in3s in there. I didn't have depth issues, just a little problem with the top slot that took some work.

     

    Overall, I am happy with it.

     

    I liked the Sharkoon case, don't get me wrong, but with sata ports coming straight out of the motherboards edge towards the drive cages I couldn't fit the cables in, it was only a problem with my new motherboard, my previous supermicro board with the sata ports coming up from the motherboard in the same direction as the CPU cooler was fine.

     

    I'm not sure how much sense that makes, but I know what I'm trying to say!

  11. Tried the above suggestion and this was my xml file, couldn't get it to work so tried from scratch

     

    <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
      <name>Win7VMTest</name>
      <uuid>e2624501-9cf5-2767-fdbb-b3b5510bb166</uuid>
      <memory unit='KiB'>2097152</memory>
      <currentMemory unit='KiB'>2097152</currentMemory>
      <vcpu placement='static'>2</vcpu>
      <os>
        <type arch='x86_64' machine='pc-q35-2.1'>hvm</type>
        <boot dev='hd'/>
      </os>
      <features>
        <acpi/>
        <apic/>
        <hyperv>
          <relaxed state='on'/>
          <vapic state='on'/>
          <spinlocks state='on' retries='8191'/>
        </hyperv>
      </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/VM/Win7VMTest/Win7VMTest.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/user/KVM/Media/Win7AIO.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:76:f1:13'/>
          <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='9216' 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>
      <qemu:commandline>
        <qemu:arg value='-device'/>
        <qemu:arg value='vfio-pci,host=00:1c.4,bus=pcie.0'/>
      </qemu:commandline>
    </domain>
    

     

    With debugging running got the following error code:

     

    Warning: libvirt_domain_create(): internal error: early end of file from monitor: possible problem: 2015-01-21T22:44:01.402946Z qemu-system-x86_64: -device vfio-pci,host=00:1c.4,bus=pcie.0: vfio: Assignment of PCIe type 0x4 devices is not currently supported 2015-01-21T22:44:01.402989Z qemu-system-x86_64: -device vfio-pci,host=00:1c.4,bus=pcie.0: vfio: 0000:00:1c.4 Error adding PCI capability 0x10[0x40]@0x40: -22 2015-01-21T22:44:01.635794Z qemu-system-x86_64: -device vfio-pci,host=00:1c.4,bus=pcie.0: Device initialization failed. 2015-01-21T22:44:01.635823Z qemu-system-x86_64: -device vfio-pci,host=00:1c.4,bus=pcie.0: Device 'vfio-pci' could not be initialized in /usr/local/emhttp/plugins/dynamix.kvm.manager/classes/libvirt.php on line 896

     

    Any ideas?  Still finding my feet here a bit...

     

    EDIT: Do I need to add some lines to my syslinux.cfg

     

    Tried

    append intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 pcie_acs_override=downstream initrd=/bzroot

     

    Same error thrown up

  12. You also need to add this to the top of your xml

    <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
    

    Your xml is being saved but libvirt removes invalid syntax.

     

    Thanks, I'll give it a try as soon as the wife stops watching TV.  Never would have got there without that pointer. Much appreciated for the help and all your work with the plugin dmacias.

  13. Just on a sidenote: If you want tvheadend you could also setup an ubuntu VM and install tvheadends repository. Should be more compatible than windows.

     

    I'm not really too bothered what OS or TV Backend I run, from reading around I think my TV card has a few problems in Linux depending on the kernel as the drivers aren't built in, what I intend to do is get a VM up and running then start playing around with different options.  Have to say though the Argus TV tuner is rock solid, keep coming back to it since around 2009 I think. (Was previously called For The Record)

  14. Hi, can't believe the progress made in UnRAID since I migrated to WHS2011 about a year ago.  Am looking to migrate back  :-[ Yeah, I know, grass is always greener....

     

    Apart from some messing around with VirtualBox in Windows I'm new to all this virtualisation business so please forgive the wall of text as I wanted to put all my steps down so I others could follow the ramblings of my disturbed mind!

     

    Managed to get a Win7VM up and running using dmacias' excellent plugin, here is the xml file that was created.

     

    <domain type='kvm' id='3'>
      <name>Win7VM</name>
      <uuid>16423bf2-47b7-0c00-2cb3-0c000b16ea8a</uuid>
      <memory unit='KiB'>4194304</memory>
      <currentMemory unit='KiB'>2097152</currentMemory>
      <vcpu placement='static'>1</vcpu>
      <resource>
        <partition>/machine</partition>
      </resource>
      <os>
        <type arch='x86_64' machine='pc-q35-2.1'>hvm</type>
        <boot dev='hd'/>
      </os>
      <features>
        <acpi/>
        <apic/>
        <hyperv>
          <relaxed state='on'/>
          <vapic state='on'/>
          <spinlocks state='on' retries='8191'/>
        </hyperv>
      </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/VM/Win7VM/Win7VM.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/user/KVM/Media/Win7AIO.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:40:3f:e1'/>
          <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>
        <input type='mouse' bus='ps2'/>
        <input type='keyboard' bus='ps2'/>
        <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0'>
          <listen type='address' address='0.0.0.0'/>
        </graphics>
        <video>
          <model type='vmvga' vram='9216' heads='1'/>
          <alias name='video0'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
        </video>
        <memballoon model='virtio'>
          <alias name='balloon0'/>
          <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
        </memballoon>
      </devices>
    </domain>

     

    I want to passthough my PCI-E Quad Tuner DVB-T2 card which is a TBS6285, the alternative is to use the TVHeadEnd plugin which I used before but it is a bit of a pain bothering piotrasd for media builds with TBS drivers every time there's a new release!

     

    Here's the output of lspci -knn without my TV Card installed in the machine.

     

    00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09)
            Subsystem: ASRock Incorporation Device [1849:0150]
    00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09)
            Subsystem: ASRock Incorporation Device [1849:0152]
    00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e31]
            Kernel driver in use: xhci_hcd
    00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e3a]
    00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e2d]
            Kernel driver in use: ehci-pci
    00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:8892]
    00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
            Kernel driver in use: pcieport
    00:1c.5 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 [8086:1e1a] (rev c4)
            Kernel driver in use: pcieport
    00:1c.7 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 [8086:1e1e] (rev c4)
            Kernel driver in use: pcieport
    00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e26]
            Kernel driver in use: ehci-pci
    00:1f.0 ISA bridge [0601]: Intel Corporation H77 Express Chipset LPC Controller [8086:1e4a] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e4a]
    00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e02]
            Kernel driver in use: ahci
            Kernel modules: ahci
    00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e22]
            Kernel modules: i2c_i801
    01:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03)
            Subsystem: LSI Logic / Symbios Logic Device [1000:3020]
            Kernel driver in use: mpt2sas
            Kernel modules: mpt2sas
    02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
            Subsystem: ASRock Incorporation Motherboard (one of many) [1849:8168]
            Kernel driver in use: r8169
            Kernel modules: r8169
    03:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 01)
            Subsystem: ASRock Incorporation Device [1849:0612]
            Kernel driver in use: ahci
            Kernel modules: ahci
    

     

    Once installed I get this output.

     

    00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09)
            Subsystem: ASRock Incorporation Device [1849:0150]
    00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09)
            Subsystem: ASRock Incorporation Device [1849:0152]
    00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e31]
            Kernel driver in use: xhci_hcd
    00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e3a]
    00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e2d]
            Kernel driver in use: ehci-pci
    00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:8892]
    00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
            Kernel driver in use: pcieport
    00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 [8086:1e18] (rev c4)
            Kernel driver in use: pcieport
    00:1c.5 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 6 [8086:1e1a] (rev c4)
            Kernel driver in use: pcieport
    00:1c.7 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 [8086:1e1e] (rev c4)
            Kernel driver in use: pcieport
    00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e26]
            Kernel driver in use: ehci-pci
    00:1f.0 ISA bridge [0601]: Intel Corporation H77 Express Chipset LPC Controller [8086:1e4a] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e4a]
    00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e02]
            Kernel driver in use: ahci
            Kernel modules: ahci
    00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04)
            Subsystem: ASRock Incorporation Device [1849:1e22]
            Kernel modules: i2c_i801
    01:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03)
            Subsystem: LSI Logic / Symbios Logic Device [1000:3020]
            Kernel driver in use: mpt2sas
            Kernel modules: mpt2sas
    02:00.0 Multimedia controller [0480]: Philips Semiconductors SAA7160 [1131:7160] (rev 02)
            Subsystem: Device [6285:0001]
    03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
            Subsystem: ASRock Incorporation Motherboard (one of many) [1849:8168]
            Kernel driver in use: r8169
            Kernel modules: r8169
    04:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 01)
            Subsystem: ASRock Incorporation Device [1849:0612]
            Kernel driver in use: ahci
            Kernel modules: ahci
    

     

    So if I'm correct in my assumptions that means that these two entries are the ones I need to be looking at.

     

    00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 [8086:1e18] (rev c4)
            Kernel driver in use: pcieport
    02:00.0 Multimedia controller [0480]: Philips Semiconductors SAA7160 [1131:7160] (rev 02)
            Subsystem: Device [6285:0001]

     

    Editing my go file to this should allow for passthrough of the slot right?

     

    #!/bin/bash
    # Start the Management Utility
    /usr/local/sbin/emhttp &
    
    #bindpci
    /usr/local/sbin/vfio-bind 0000:00:1c.4

     

    This then give me  these lines when I run lspci -knn so my PCI-E slot is using the virtuo driver right?

     

    00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 [8086:1e18] (rev c4)
            Kernel driver in use: vfio-pci
    02:00.0 Multimedia controller [0480]: Philips Semiconductors SAA7160 [1131:7160] (rev 02)
            Subsystem: Device [6285:0001]

     

    Now am I correct in thinking I now need to add something along the lines of this to my VM xml file?

    <qemu:commandline>
    <qemu:arg value='-device'/>
        <qemu:arg value='vfio-pci,host=00:1c.4,bus=pcie.0'/>
    </qemu:commandline>

     

    However once I've done all that, (I edited the xml file for the VM I'd already created rather than create a new one - if that's relevant) but nothing appears in device manager within Windows to indicate that my Tuner card is present.

     

    If someone could point out whereabouts I'm going wrong I'd be most grateful.

     

    EDIT:  It would appear that when I edit the xml file with the VM stopped the changes aren't being saved. 

  15. So, I've successfully managed to mount my 2TB drives in SNAP and can access the shares.  However my 4TB NTFS drives, connected via SATA to either the motherboard or a M1015 card (with flashed firmware) are showing up in SNAP as no fs

     

    It seems that I have theses drives as "Advanced Format or 512E" drives

     

    In my WHS2011 running

     

    Fsutil fsinfo ntfsinfo d:

     

    Gives me

     

    Version :                         3.1
    Number Sectors :                  0x00000001d1bcafff
    Total Clusters :                  0x000000003a3795ff
    Free Clusters  :                  0x0000000000b20a65
    Total Reserved :                  0x0000000000000000
    Bytes Per Sector  :               512
    Bytes Per Physical Sector :       4096
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 1024
    Clusters Per FileRecord Segment : 0
    Mft Valid Data Length :           0x0000000001540000
    Mft Start Lcn  :                  0x00000000000c0000
    Mft2 Start Lcn :                  0x0000000000000002
    Mft Zone Start :                  0x00000000000c1540
    Mft Zone End   :                  0x00000000000cc820
    RM Identifier:        01DFFC80-673C-11E3-822B-BC5FF49F0C1D
    

     

    Is there any way to mount this in SNAP? Would be happy as a READ only FS as it's pretty much just to keep access to things going whilst I migrate.

     

    Thanks for any help fellas.

  16. I'm wondering if I could use this plugin to migrate an array from WHS and Flexraid to an Unraid array.

     

    I have ten disks with pooled shares (TV Shows & Movies) and two spare drives to kick off the Unraid array

     

    What I'd like to do is boot up Unraid and mount all 10 NTFS disks and share them over my network so the wife can continue to watch whatever she is choosing to watch, oblivious to the migration happening upstairs.

     

    If I could pool the SNAP shares that would be brilliant, but I could work round it if that's not possible, I understand my data wouldn't be protected whilst I'm doing all this but that's a risk I'm prepared to take as my only two alternatives are buying a lot of extra hardware or telling the wife she can't watch a lot of stuff for a while.

     

    Anybody got any ideas or thoughts on my musings then I'd be grateful to hear them.

     

  17. Thanks for your reply and wise words.  Think I'll start with KVM as my general impression has been that is the way things seem to be going. 

     

    I'll give the tuner card a shot, I have been giving things some thought and an alternative plan might be to build a small ITX system just for a MythTV back end or possibly Argus and accept that I can't do everything on one box.  The benefit to that would be that if I have a problems with my array the wife can still watch Live TV and vice versa.

     

    I'll keep looking for some info on virtualising PFsense on Unraid and I've just got a dual Intel NIC to add to the native realtek on my MB to play around with.

     

    Excited about getting back into UnRAID, been playing more and more with Linux systems and finding Windows just a bit too much and overly complicated.

     

    Thanks Jon, appreciated.

  18. So, I stopped using Unraid after a sever rebuild over a year ago onto WHS2011, due to not having much int he way of time and being way more familiar with the Windows Environment.  I've been using FlexRAID which works, but is rather complicated in it's setup and I'd really like to start using UnRAID again.

     

    My server started off on UnRAID as a simple NAS but has evolved over time to become a very multifunctional device.

     

    Before I get stuck in with trying to get UnRAID setup I do have a few questions.

     

    I've been using VMs more and more in VirtualBox, but would love to try either Xen or KVM. 

     

    An essential for me would be the ability to passthrough my quad tuner DVB-T2 card (TBS6285) into either Windows 7/8/WHS2011 and run ArgusTV or alternatively into Mythbuntu or some other Linux distro to provide PVR functionality.

     

    I'd also like to use pfsense or some other router VM to provide an OpenVPN client gateway to my VPN provider.

     

    Other tasks I think I can use with various Docker Containers such as web serving.

     

    MY questions are:

     

    What have been people's experiences with DVB hardware in VMs?

    What direction is UnRAID taking in terms of virtualisation?  Is Xen or KVM going to be the hypervisor of choice?  I don't have any experience in either at the moment, but if I'm going to invest time into it then I'd rather know which one to invest my efforts in.

     

    Thanks Guys.