praaphorst

Thanks Ghost, guess my information was pretty old, actually makes sense to separate that. Alright, let see if I can get this done.

When attempting to create a ZFS storage pool: virsh pool-define-as zfs_pool zfs error: Failed to define pool zfs_pool error: internal error: missing backend for pool type 12 (zfs) Can we get a libvrt compiled with ZFS backend support, needs a few switches flipped? Background: Creating a VM which is intended to run on a ZFS Volume, my device snippet would look like this: <disk type='volume' device='disk'> <source pool='zfs_pool' volume='winvolume'/> <target dev='vdb' bus='virtio'/> </disk> Unfortunately the backend support is not compiled in libvrt. I know there are other ways to get a ZFS volume mounted in a VM but prefer to use the excellent support and performance for ZFS pool.

Sure but remember this is highly experimental, you might wreck your pool for all I know, I've got everything backup-ed, so you are warned here. For each block device used in your zpool add it to your VM using the following XML fragment under the <devices> section: <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/sdb'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> can also use /dev/by-id just be sure

So I did something either very stupid or very genius, feel free to comment: - Installed the unraid ZFS plugin - got familiar with the command line operations and ZFS in general - Tuned using fio for large file storage, went for ashift 12 and recordsize 1M - Created a raidz pool with 4 pieces of rust and a bunch of datasets (mounted at root, not /mnt/user) - Configured docker for directory on ZFS, reinstalled my docker apps, tweaked some paths and everything up and running ok - Limited arc size to 2 Gb of memory (sorry need my memory for docker/vm) - Happily rsyncing terrabytes of data back so far so good, but my fingers are getting blue, time to get some GUI, lets do something crazy .... - installed a freebsd VM with truenas latest version, 10G virtio image and 4 Gb of Ram - After It was up running shutdown and modified the XML to pass through my ZFS block devices (not the whole controller) - Started the truenas VM, pretended a nose bleed and just imported the ZPOOL which is also imported and in use on unraid - During import I got one warning: To my utter surprise it imported and I got the nice truenas gui available for managing my snapshots. Seems to work so far, any objections anybody?

Same problem here, the server list is empty.

8 Gb of ECC ram, usage indicates 4 Gb should have been more then enough. I am not running any VM's.

Part of one at the fitness club, nothing more

I am using Kodi on a rpi3 with PlexKodiConnect which synchronizes Kodi's media libray with Plex. . I've set it to use SMB shares. Updates from the plexmediaserver seem to arrive pretty quick, i can not force it on the Kodi though (through the update library button). The only issue I've seen so far is that opening the same file for the second time in a short period of time (seconds) seems to "hang"on busy. Stop playing and retry solves it. All in all i am content with this solution.