johnodon

All XFS data drives here (although I don't think it matters). The real key is lots of ECC RAM and x64. Both tests were conducted on WIN 8.1 desktop (gigabit). Reading from parity protected data drive Writing to parity protected data drive Love the fact that I can actually write to the array faster than I can read from it. John

Just wanted to provide a quick update. It has now been ~2 months since migrating all of my data disks to XFS. Since that time, I have not had a single corruption issue. Also, any hard crashes that I have experienced since that time I have been able tie directly to Docker apps (namely NZBGet or NZBDrone). About a month ago, I retired most of my Docker apps (except MariaDB and Headless Kodi) and moved the apps into VMs. My server has been purring like a kitten! John

What ended up making it boot?

If you have any success with this please let us know! I'm pretty certain that Jon and team had to create a custom build to incorporate the needed drivers and such. John

This is exactly what I experienced. I had a fully functional WIN8.1 VM using native graphics (VNC). As soon as I added the passed through GPU, I got the boot error. I thought I just had too many beers and kept trying to rebuild the same VM over and over. John

I was trying to delete some files from my cache pool and I started to see messages about failing due to out of space. How can I fix this? root@unRAID:/mnt/cache# btrfs filesystem show /dev/sdd1 Label: none uuid: f5497a6f-06d0-4702-b941-f18cd1acac53 Total devices 3 FS bytes used 64.52GiB devid 1 size 119.24GiB used 118.02GiB path /dev/sdb1 devid 2 size 3.97MiB used 0.00B path /dev/sdc1 devid 3 size 119.24GiB used 118.00GiB path /dev/sdd1 Btrfs v3.17.2 root@unRAID:~# btrfs fi df /mnt/cache Data, single: total=234.01GiB, used=63.95GiB System, single: total=4.00MiB, used=48.00KiB Metadata, single: total=2.01GiB, used=314.78MiB GlobalReserve, single: total=112.00MiB, used=0.00B Are deletes written to "garbage" and I need to empty that somehow? I just deleted a 75GB VM and it did me no good. Is the solution to run a "balance"? John

I have recently seen the same issue...numerous times. Every time it was also when attempting GPU passthrough. Whether it was passed through from the start or added after the OS install didn't matter. I was only trying to build a test VM so I gave up but I find it odd since I have never had this issue before. I'll try again today and see if it happens. Can others also try to see if we can replicate the issue? EDIT: I have even tried to use one of my existing, working XMLs and ran into the same issue. John

There is a driver for memory balloon on the virtio drivers iso. Maybe that needs to be installed. For network performance you could try turning off cpu offloading in unRAID and in the vm. For unRAID run these from the command line with eth0 as the name of your ethernet interface and br0 the name of your network bridge. In windows you'd have to go to the network device settings. ethtool -K eth0 gso off ethtool -K eth0 tso off ethtool -K eth0 sg off ethtool -K eth0 gro off ethtool -K br0 gso off ethtool -K br0 tso off ethtool -K br0 sg off ethtool -K br0 gro off This. When you create a WIN8 VM using virtio for the pcie bus, you have to load the Red Hat SCSI driver from the virtio CD/iso otherwise you will not see any available drives during the install. Once the VM is finished being built, you will notice that you have at least 2 unknown devices in Device Manager...one is the NIC and one is the memory balloon. For each of these you need to install the appropriate driver from the same windows virtio cd/iso. Just update driver and point it to the appropriate folder on that CD. If you built a WIN8 VM and your virtio driver cd is D:, the path would be D:\WIN8\AMD64 John

With Ubuntu, when I click "shut down" from the unraid web ui using the plugin, the os just brings up a screen asking for me to choose to reboot or power down. It won't just trigger the shutdown using an emulated acpi call. Hmmm...that is not my experience. When I click the "safely shutdown domain" button, it just shuts down (at least in my XBMCBuntu VMs). Is this a product of what is in the XML: <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> BTW...my WIN8 VM behaves the same way. It immediately kills my VNC session and the VM is shutdown gracefully. John

Coincidentally I was thinking the same thing but from another angle; dev chat is usually more focussed. When you introduce consumers to this chat you get good ideas but every single time you end up talking about what will come later and much wider scope at the expense of the OT. Also your Arch is well made. I say have a community dev section. Read only for all and the bar for write access would be low enough for it not to seem elitist. Love this idea. Read only for all, but invite only for posting ability. Keeps the discussion publicly visible, but more focused. I think this is the best solution but wonder if it will cause some level of PM flooding from users who can't hold their tongue. Easy enough to ignore but may cause some ill will. EDIT: Actually, jonp you should have some experience with this. Have you been inundated with PMs since the announcement forum went read-only? John

Sometimes it also takes the VM a little bit of time to shutdown nicely (especially Windows VMs). I have seen it take a few browser refreshes (which happen automatically every x seconds) before the VM was actually shutdown. However, something like the Ubuntu installer should shutdown almost immediately. John

Jon... Do you have any intent on making an OE 4.2.1 unVM available? I can only assume that you have moved onto OE v5 since it has been released. The reason I ask is that my new strategy is to use OE + PLEXBMC on all of my standalones and VMs. Unfortunately, there are just too many gaps between Helix (OE v5), PLEXBMC and the Amber skin which make it unstable. Sucks since there is some nice functionality in the newer versions Plex that have been left at the curb in PLEXBMC due to development going stale. I was hoping that you had done most dev work on OE v4 that you have a stable enough product that you can offer that would not require additional dev since OE itself has been updated. John

Has anyone had any luck installing this in needo's PMS container? https://forums.plex.tv/index.php/topic/25523-unsupported-as-in-totally-unofficial-appstore/ I tried but did not have the necessary permissions to download/extract the zip file to the appropriate folder. Unfortunately, I tried to run the newperms script again the /plexmediaserver folder and I was then unable to reach the PMS webui. I had to start from scratch a completely rebuild my PMS instance. John

I see these entries in my syslog and don't know what is being attempted by what: Dec 28 09:26:45 unRAID login[2275]: invalid password for 'UNKNOWN' on '/dev/tty1' Dec 28 09:27:24 unRAID login[2275]: invalid password for 'UNKNOWN' on '/dev/tty1' Dec 28 09:28:19 unRAID login[11795]: invalid password for 'UNKNOWN' on '/dev/tty1' Dec 28 09:29:34 unRAID login[12715]: invalid password for 'UNKNOWN' on '/dev/tty1' At the time I was playing with Plex Home Theater on a standalone Linux Mint 17.1 box (I have PMS running as a docker container). The only other containers/VMs running are my usual ones and I have never seen these messages before. Anyone have any ideas? John

I have not had a single crash since disabling docker containers and removing SNAP. I just re-enabled my NZBGet container to download a movie. Within 15 minutes my server experienced a hard crash. Nothing was written to the syslog just prior to the crash other than the entries showing the container being enabled. I'm entirely convinced at this point that either Docker and/or more specifically the NZBGet docker is the culprit. John

This is really just a "nice to have" and should get very low priority. Under the newly created Settings tab... Is it possible to have the option of configuring an external VNC viewer? Better yet...the option to configure an external viewer and if that viewer is not found on the local system, the webviewer would be launched. Call me lazy... John

If you dare do so, you can use your parity drive as the intermediary drive if you do not have a spare drive. Be warned: your data will be unprotected during the migration process. Most here would advise against this. John

FYI...I have had crashes since migrating to XFS...same CPU stall messages. But I have not seen the corrupt file system messages I was seeing before which I think led to my other crashes. I have since disabled 2 dockers (nzbget and nzbdrone) and one plugin (SNAP) and have not had a crash in 3 days. If I can go a solid week without a crash, I think my culprit was either a docker container or the SNAP plugin. John

I'm really considering making the move to Plex from XBMC. Lately it has become to hard to ignore some of the major "out of the box" benefits of Plex...shared DB, transcoding, sharing library with friends, etc. Naturally, I wanted to make sure I could run PHT on a Linux platform but I had a hell of time trying to get it to work in an Ubuntu 14.04 VM. It refused to login/authenticate to Plex. I quickly abandoned that effort and moved to Mint which worked from the very first try. The last piece is to nail down Radeon drivers/acceleration. Any pointers on which drivers (proprietary, legacy, etc.) I should run would be appreciated. John

d.... You have to be the hardest working plugin developer I have ever seen! We all greatly appreciate your hard work and especially your quick responses! not to mention making an awesome plugin. John

Same error for me.

I just created a new VM (with create new disk option) and did not see this issue. When I clicked the button to create the VM, the form came back empty. I then went to the Virtual Machines tab, the newly created VM was there. Maybe others are having permissions issue at the vm datastore location? John

Whew...thanks D. Question...why does the Create VM not add the XML namespace if it is required? John

I'm not sure what I am doing wrong or if there is a bug... I wanted to test a new VM (created using Create VM) using my passed through GPU from an existing VM (created using Add XML). For whatever reason, the new XML will not allow me to add the QEMU args. The status message at the bottom tells me that changes were made, but if I open the XML again, the changes are not there. I thought that it may be because I still had the args in the existing XML so I deleted them from that one. However, I cannot add them back to that XML either. Once again, the status message says changes were made but if I reopen the XML, they are not there. The odd thing is that I can make other changes to the XML and they are saved (like adding a passed through USB device). <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=83:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=83:00.1,bus=pcie.0'/> </qemu:commandline> Was there a change made in a recent version of virtman plugin that expects the QEMU args to be in a different format? EDIT: I just tried to Add XML with the code shown below. The VM is created but the QEMU args are being stripped out. This is the code that I am adding... <domain type='kvm'> <name>HTPCFAMRM2</name> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>rename-restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none' io='native'/> <source file='/mnt/cache/VMs/HTPCFAMRM.qcow2'/> <target dev='vdc' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Images/xbmcbuntu-13.0~gotham_amd64.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x2'/> </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> <controller type='ide' index='0'/> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/Movies'/> <target dir='movies'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/Music'/> <target dir='music'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/TV'/> <target dir='tvshows'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:94:00:d0:c0:dc'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/> </interface> <hostdev mode='subsystem' type='usb' managed='no'> <source> <address bus='2' device='6'/> </source> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=83:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=83:00.1,bus=pcie.0'/> </qemu:commandline> </domain> And this is what I end up with... <domain type='kvm'> <name>HTPCFAMRM2</name> <uuid>ae5d3169-5889-4ba9-a478-ca3f5dfd0e60</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>rename-restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none' io='native'/> <source file='/mnt/cache/VMs/HTPCFAMRM.qcow2'/> <target dev='vdc' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Images/xbmcbuntu-13.0~gotham_amd64.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x2'/> </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> <controller type='ide' index='0'/> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/Movies'/> <target dir='movies'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/Music'/> <target dir='music'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/TV'/> <target dir='tvshows'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:94:00:d0:c0:dc'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/> </interface> <hostdev mode='subsystem' type='usb' managed='no'> <source> <address bus='2' device='6'/> </source> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> </domain> John

Looks like we are having similar issue: http://lime-technology.com/forum/index.php?topic=37265.0