meep

I currently use the TVHeadEnd PlugIn (https://lime-technology.com/forum/index.php?topic=40704.90;topicseen) If I wanted to migrate to the Docker, is there a way for me to preserve all my settings, recordings tec. I really don't want to start setting the whole thing up again. Thanks

Thanks. Got it working with Apache and proxy pass. Turns out I don't need to ssl node-red at all as Apache can look after certs for all proxies services. Loving node-red though, thanks for the docker.

Yes please. Am currently looking at OpenEnergyMonitor and while I can easily set up a Pi, it would be cool to try to emulate the emonbase in unRaid . (one less device)

I've just set up Node-RED docker to serve HTTPS. Took me a while to do something that should be quick so I've put together the steps; http://mediaserver8.blogspot.ie/2016/10/unraid-node-red-docker-with-https.html Hopefully it will help someone, sometime.

Thanks. Will do that over the weekend. Another step towards a super smooth unRAID. Sorry now, this didn't work.... My data directory is set to /mnt/cache/tvheadend/.htsconfig in the settings UI I SSH'd in there and nano'd the config file. I added this to the bottom, following the format of the existing entries... "script": "" I disabled TVHeadEnd in the settings UI and removed YES from the script field. However, on hitting 'Apply', it popped right back in. Is there another step to force the plugin to read the updated config? Is this even the correct config file? (the entry format is different to that which you outline). Help appreciated.

Thanks. Will do that over the weekend. Another step towards a super smooth unRAID.

Hi That field won't empty for me. I stop the plug in, remove the 'yes' from the script filed and hit apply. As soon as I do, the 'yes' reappears. I simply cannot get rid of it!! Thanks

Please ignore. I fixed it. I had an update share set up and mover was obviously moving my config files to the array but my container config was set to the direct pitch to the cache folder. Set the share to cache only and all is well with the world again.

I had installed and set up this Emby docker and it was working fine. However, I've noticed that if I have occasion to restart the app, docker or unraid system, it loses it's config. I behaves as if the config is on non-permanent storage but as I understand it, the mappings (attached) point it to my cache drive. Whenever I access the UI after a restart I get the settings screen (also attached). I'm missing something obvious, but what? Thanks

Cool, you know you got me back into this DVB stuff don't you, I was looking at your blog and even bought you a coffee! The one and only coffee received on that blog! Very much appreciated Must start writing there again. I'd slipped into a 'it's all working' mode but must update with these tvheadend changes. Keep up the good work!!

I've got Yes in the script field as well. Even if I stop the service, remove 'Yes' and restart, it pops back in there all by itself! Anyway, installed this at the weekend as I was fed up with MediaPortal TV Server crashing my Win7 VM. It works great with by Digital Devices Octopus tuners (enabled by CHBMB's DVD build). One gotcha if you use Kodi.... DONT set any recordings with a frequency of 'forever'. They will record and save to your storage but will not show up in the TVHeadEnd completed recordings or Kodi UI. It's a bug with v 4.0.x (fixed in 4.1, apparently). You can set any frequency up to and including 3 years. Drove me nuts trying to figure out whey some recordings were showing up and some now, even though all were saved.

I installed this last night and had a play around. It's nicely organised and, as already noted, the help is fantastic. As a first time user, I had one point of confusion. (apologies, this his from memory as I'm not in front of unRAID); For a couple of the tweaks, the help indicates that lower values could be better 'if your VM is used fro streaming and/or gaming' (or words to that effect. This gave me pause for thought. I run multiple VMs, some of which are used for gaming/streaming, some of which are general purpose workstations. The phrasing here suggests the possibility of setting these values on a per-VM basis but I gather these are global settings? An improvement in language here might offer better clarity. Also, the links on the tips page could open in a new tab/window. Right now the seem to replace the unRAID interface? Thanks again.

Actually, I linked to the incorrect guide - the point I was trying to make was that it's important that you install the VIRTIO drivers in a specified order. Here's the case relevant to our situation (specify drivers during Windows install process); http://lime-technology.com/wiki/index.php/UnRAID_Manual_6#Loading_the_VirtIO_Drivers_During_Installation Peter

A couple of things.... Are you following the driver installation sequence described here; http://lime-technology.com/wiki/index.php/UnRAID_6/VM_Management#Step_5:_Install_the_VirtIO_drivers_from_inside_the_VM_.28Windows_Guests_Only.29 That page specifically indicates that the viostor drivers should be installed last. It's not clear from your post if you've done the others, but if not, maybe try Balloon, NetKVM and vioserial drivers first? The second thing is, I recently set up a Win 8.1 VM and used the Win 8.1 drivers from the ISO. I subsequently implemented the Windows 10 upgrade and attempted to update the virtio drivers from device manager using the Win10 folders on the ISO. In all cases, windows reported that I already had the most up to date drivers which would lead me to believe that there's no difference between the 8.1 and 10 versions on the ISO. You could try installing the 8.1 versions during Win 10 installation to see if that gets you past this screen?

Superhandy, washed over me completely! Will check that out when I get home!

That's interesting indeed as I'm trying to improve performance of a specific VM for gaming. Is there a reference or technique for determining which pairs match? I have an AMD FX Piledriver and a quick google didn't reveal much of use. Thanks

Bungy Many thanks of Mochad. I'd started rolling my own CM15 solution under a windows VM but this is altogether more efficient. Great work. Peter

0e:00.0 Multimedia controller: Digital Devices GmbH Octopus DVB Adapter Octopus PCIe bridge http://www.digitaldevices.de/english/Octopus_PCIe_Bridge.html 10:04.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02) m-audio delta 410 PCI audio interface 07:06.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02) m-audio delta 1010lt PCI audio interface

So I did that and rebooted and the VM now boots and passthrough works. Got to read up a bit more on the risk. Gettingthere...

Oh Dear Just read this; http://vfio.blogspot.ie/2014/08/iommu-groups-inside-and-out.html and did this; $ find /sys/kernel/iommu_groups/ -type l which resulted in this; /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:02.0 /sys/kernel/iommu_groups/2/devices/0000:00:09.0 /sys/kernel/iommu_groups/3/devices/0000:00:0a.0 /sys/kernel/iommu_groups/4/devices/0000:00:0b.0 /sys/kernel/iommu_groups/5/devices/0000:00:0c.0 /sys/kernel/iommu_groups/6/devices/0000:00:0d.0 /sys/kernel/iommu_groups/7/devices/0000:00:11.0 /sys/kernel/iommu_groups/8/devices/0000:00:12.0 /sys/kernel/iommu_groups/8/devices/0000:00:12.2 /sys/kernel/iommu_groups/9/devices/0000:00:13.0 /sys/kernel/iommu_groups/9/devices/0000:00:13.2 /sys/kernel/iommu_groups/10/devices/0000:00:14.0 /sys/kernel/iommu_groups/11/devices/0000:00:14.3 /sys/kernel/iommu_groups/12/devices/0000:00:14.4 /sys/kernel/iommu_groups/12/devices/0000:07:06.0 /sys/kernel/iommu_groups/12/devices/0000:07:0e.0 /sys/kernel/iommu_groups/13/devices/0000:00:14.5 /sys/kernel/iommu_groups/14/devices/0000:00:15.0 /sys/kernel/iommu_groups/14/devices/0000:00:15.1 /sys/kernel/iommu_groups/14/devices/0000:00:15.2 /sys/kernel/iommu_groups/14/devices/0000:00:15.3 /sys/kernel/iommu_groups/14/devices/0000:08:00.0 /sys/kernel/iommu_groups/14/devices/0000:09:00.0 /sys/kernel/iommu_groups/14/devices/0000:10:04.0 /sys/kernel/iommu_groups/14/devices/0000:0a:00.0 /sys/kernel/iommu_groups/14/devices/0000:0b:00.0 /sys/kernel/iommu_groups/14/devices/0000:0c:00.0 /sys/kernel/iommu_groups/14/devices/0000:0c:01.0 /sys/kernel/iommu_groups/14/devices/0000:0c:02.0 /sys/kernel/iommu_groups/14/devices/0000:0e:00.0 /sys/kernel/iommu_groups/14/devices/0000:0f:00.0 /sys/kernel/iommu_groups/15/devices/0000:00:16.0 /sys/kernel/iommu_groups/15/devices/0000:00:16.2 /sys/kernel/iommu_groups/16/devices/0000:01:00.0 /sys/kernel/iommu_groups/16/devices/0000:01:00.1 /sys/kernel/iommu_groups/17/devices/0000:02:00.0 /sys/kernel/iommu_groups/18/devices/0000:03:00.0 /sys/kernel/iommu_groups/19/devices/0000:04:00.0 /sys/kernel/iommu_groups/19/devices/0000:04:00.1 /sys/kernel/iommu_groups/20/devices/0000:05:00.0 /sys/kernel/iommu_groups/20/devices/0000:05:00.1 /sys/kernel/iommu_groups/21/devices/0000:06:00.0 /sys/kernel/iommu_groups/21/devices/0000:06:00.1 and when compared to my PCI devices list, shows I'm in a world of hurt :-( 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) (rev 02) 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD/ATI] RD990 I/O Memory Management Unit (IOMMU) 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B) 00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port H) 00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port A) 00:0b.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (NB-SB link) 00:0c.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890S PCI Express bridge for GPP2 port 1 00:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port B) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40) 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40) 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40) 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller 00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) 00:15.1 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1) 00:15.2 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 2) 00:15.3 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 3) 00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series] 02:00.0 USB controller: Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01) 03:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 12) 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series] 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] 06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 06:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] (Secondary) 07:06.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02) 07:0e.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0) 08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 09:00.0 USB controller: Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01) 0a:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 12) 0b:00.0 PCI bridge: Texas Instruments XIO3130 PCI Express Switch (Upstream) (rev 02) 0c:00.0 PCI bridge: Texas Instruments XIO3130 PCI Express Switch (Downstream) (rev 02) 0c:01.0 PCI bridge: Texas Instruments XIO3130 PCI Express Switch (Downstream) (rev 02) 0c:02.0 PCI bridge: Texas Instruments XIO3130 PCI Express Switch (Downstream) (rev 02) 0e:00.0 Multimedia controller: Digital Devices GmbH Octopus DVB Adapter 0f:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200A PCI Express-to-PCI Bridge (rev 03) 10:04.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02) Group 14 contains a bunch of stuff along with the device I want to pass through including SATA controllers, USB controllers, main ethernet etc. - stuff I don't want to be passing through anywhere.

All done, extended errors now... root@UnRaid:~# virsh start MediaServer error: Failed to start domain MediaServer error: internal error: early end of file from monitor: possible problem: 2015-04-25T18:34:34.898771Z qemu-system-x86_64: -device vfio-pci,host=0e:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: error, group 14 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2015-04-25T18:34:34.898805Z qemu-system-x86_64: -device vfio-pci,host=0e:00.0,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to get group 14 2015-04-25T18:34:34.898820Z qemu-system-x86_64: -device vfio-pci,host=0e:00.0,id=hostdev0,bus=pci.0,addr=0x6: Device initialization failed. 2015-04-25T18:34:34.898835Z qemu-system-x86_64: -device vfio-pci,host=0e:00.0,id=hostdev0,bus=pci.0,addr=0x6: Device 'vfio-pci' could not be initialized This would be a good juncture to point out that this device is on a PCI/PCIe expansion board. I can try moving it into the system proper and seeing what happens? (goes without saying this hardware config worked OK with Xen). Thanks

Here you go; Linux 3.19.4-unRAID. root@UnRaid:~# virsh start MediaServer error: Failed to start domain MediaServer error: Requested operation is not valid: PCI device 0000:0e:00.0 is not assignable

Attempting passthrough but no joy. Here's my base XML which works; <domain type='kvm'> <name>MediaServer</name> <uuid>52774a80-94bc-1c66-8317-bffa1cda7c86</uuid> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</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-i440fx-2.2'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </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='none' io='native'/> <source file='/mnt/cache/domains/TVserver/TVserver.img'/> <target dev='hda' 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/cache/domains/virtio-win-0.1-100.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <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> <interface type='bridge'> <mac address='52:54:00:f9:a5:e0'/> <source bridge='virbr0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 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='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> here's my PCIe device; 0e:00.0 Multimedia controller: Digital Devices GmbH Octopus DVB Adapter here's the XML I added; <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0e' slot='0x00' function='0x0'/> </source> </hostdev> And the resulting XML file, but when I try to launch the VM, nothing happens (no entries in log file, no errors displayed on screen); <domain type='kvm'> <name>MediaServer</name> <uuid>52774a80-94bc-1c66-8317-bffa1cda7c86</uuid> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</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-i440fx-2.2'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </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='none' io='native'/> <source file='/mnt/cache/domains/TVserver/TVserver.img'/> <target dev='hda' 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/cache/domains/virtio-win-0.1-100.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <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> <interface type='bridge'> <mac address='52:54:00:f9:a5:e0'/> <source bridge='virbr0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 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='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0e' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain>

Hi I would be interested in the read/write speeds you're seeing to your unRaid storage drives. Also, can you get the drives to spin down? When I tried this 12 months ago, I found disk i/o in VirtualBox to be a real bottleneck making the setup unusable. Peter