reluctantflux

Boot from a Live CD for some flavor of Linux you're familiar with and check to see if they ports are working in there. Mine are working fine. I am having issues with hard boots messing up my graphics card so bad, that I have to re-seat it. Just unplugging the power to the machine and discharging static power doesn't fix the issue. Seems like more of a graphics card issue than a Unraid issue, though. That was a fun one to troubleshoot. I'm on RC4 now.

I was concerned about creating a cache pool, but you guys are easing my mind on it. I have a 500GB Samsung PRO Evo 4, a 120GB Corsair, and a 120GB Silicon Power. Would this limit me to a cache pool of only 240GB?

Cool, I'm looking to get rid of my main HTPC VM, and go with a straight up Nvidia Shield Android TV front end with Kodi. Then put my Windows 7 Server WMC VM on with my gaming rig VM SSD, and point recordedTV to a separate SSD (previously occupied by HTPC VM), as that's where the high data write will happen. I don't think putting the tiny 25GB Win7 with my gaming rig is going to affect anything on gaming or tv performance as long as the Recorded TV virtual disk is on a separate SSD. Thanks for the input guys! Any recommendations on qcow2 vs raw for the Recorded TV virtual disk?

Hey, just curious on how people are setting up their VM's in regard to the image files. I currently have two SSD's out of my array, mounted with SNAP, and I have one VM per SSD. Is anyone running multiple VM's off of a single SSD? How is the performance? Is anyone running VM's off of their array? I would think this would be a major degradation in performance with having to keep parity, and obviously, working off HDD since SSD's aren't supported in the array yet..

I think I may have lost power this morning. The only clock that doesn't just keep going on with business if power blips under 5 seconds is in my son's room, and when I was putting him down tonight, he was flashing. I think that was why it went down initially, and caused some weird issue with the graphics card, even though I did a whole power discharge on the computer. the 09:00:00 is the address of the card I had to reseat.

Oddly, one of my two graphic cards had to be reseated. Crisis averted!

Go file: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & /boot/unmenu/uu /usr/local/sbin/vfio-bind 0000:01:00.0 0000:01:00.1 0000:02:00.0 0000:02:00.1 0000:09:00.0 0000:04:00.0 0000:0c:00.0 cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c Tried with and without the vfio-bind

Ha, yeah, that was back when I was an idiot and allowed external access to Unraid. That's been fixed. Here's two pictures of what's going on. First is right where it hangs for 2ish seconds before it goes nuts. Second pic is where it goes nuts. http://imgur.com/kHBujxG,6rITH5S#1 http://imgur.com/kHBujxG,6rITH5S#0

disregard syslog. I think it's just an old one. I can't ssh in to get a current one. It never loads ssh.

System crashed sometime last night. Now I can't get it to boot. Never had it crash before. Gets to the choose unraid screen. Select regular option and after a bit of regular booting stuff, just massive scrolling on the screen. Here is the syslog.txt. Oddly, the date is sometime in October. syslog.zip

Life got in the way. Furthest I got was working with VNC into it. Havne't tried hardware passthrough. Goodluck! Hoping to try more this weekend.

Does the new VM Manager allow USB hot plugging? I remember dmcias working on that. Very excited about it.

Just wanted to put this out there. This would be a fantastic match with Unraid. I don't think any work would need to be done from Lime Tech, as they're going to release Linux version of the software, so I imagine a docker will get released pretty quickly once released. Just want to get the word out so people can contribute. I'm not affiliated with Silicondust. I just love their products and find it relevant to other users that enjoy their Unraid.

You could use unraid as your cell phone! But really, it's more of a "cause I can" thing. My end goal is to get Android TV working in a VM with GPU passthrough so I don't need to buy a physical Android TV. As much as I like Kodi, the lack of official apps for it like Netflix and HBO GO/Now, really kill the WAF. Having an Android TV with native apps for those services, plus Emby as my personal media hub and live tv would finally provide me an all-in-one front end for media conception in front of the TV. So I used Android Lollipop as a jumping off point since that seemed the easiest to prove it could work, and I'll go from there trying to get Android TV to work.

Barebones Android Lollipop 5.0.2 is running on Unraid! No hardware passthrough or anything. Here is the xml: <domain type='kvm' id='57'> <name>Android</name> <uuid>fc6b55c8-b219-49c2-368d-40bdb0076cdb</uuid> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static'>1</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='i686' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='yes'/> </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'/> <source file='/mnt/disk/samsungvms/Android/Android.img'/> <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/cache/iso/android_x86-5.0.2.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:cf:91:6d'/> <source bridge='br0'/> <target dev='vnet2'/> <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/3'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/3'> <source path='/dev/pts/3'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <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='16384' 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> In order for it to boot properly, I needed to remove the input devices, otherwise, I pretty much made a stock image with VMman. <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> I used the Android x86 image from here: https://drive.google.com/file/d/0B4VR-WNTOX0qVnkyWExEZHdLTms/view I was directed there from guides, I did not upload that. I also had to select Raw for the HD type. The "Android is upgrading # of 66 apps" took over an hour to complete, and going through initial setup is terribly slow. Trying to create a new vm with different settings to see if it performs better. First one I used was with 32-bit settings, as I believe it is necessary. Secondary one is 64-bit. Thought I'd post an update. ETA: First boot after install, make sure to select Debug mode. It'll hang at a few spots during loading. Type "exit" to get past it. Basically, you can't remove Mouse and Keyboard from the XML and it can't load those drivers so it hangs. If you type "exit" after it hangs, it bypasses the driver and continues! Android is Upgrading now on 64-bit!

I started here, but I haven't seen much about Android TV. http://www.android-x86.org/ Youtube video. Lollipop, non-tv version, but still proof of concept. 4.4 install instructions, but probably still pretty similar. http://forum.xda-developers.com/showthread.php?t=2703270 I have qemu-img files from the Android SDK, which you can get from here. (Also where I got the screenshot) https://developer.android.com/sdk/index.html I do have the Android SDK emulator running Android TV in a VM, but no google play services just cause I don't know how to integrate them. I'm very green on this Android Developer stuff. But I was able to get the new Emby app for Android TV working in it (minus video playback for obvious reasons). I found the API 21 was running better than the API 22, so I'd probably start with API 21.

Maybe not as difficult as it used to be since they've been releasing intel x86 system images. I know people have been using these in emulators and even to dual boot machines to get intel hardware acceleration, particularly with KVM. I'm just not sure if all the pieces/versions line up.

Just wondering if anyone has tried getting Android TV to work in KVM. I think I'm going to start dabbling with this, but if anyone made any good headway prior, I'd like to join their work in progress. Considering the Android SDK emulator uses qemu, I think this is possible. Biggest concern would be vid card and infrared receiver drivers.

For existing image files, you can use it this way, but if you're starting a new VM, you're going to want to use Virtio type. You'll then need to attach the virtio-drivers disc to the VM and pull the drivers off of it at OS install, otherwise it won't be able to see the install. Virtio will have better performance than straight sata. You can change this once the VM is created by adding a different image file using virtio, then booting up and loading the drivers for the drive. Then shut down, change the OS to virtio, and boot back up. Make a backup of the image file and xml before you do this, though, just in case. It can be a bit finicky sometimes.

I'm not 100% sure, but I'm pretty sure it would still take that long in a VM, as when you mount it, it would still have to transfer through the VM nic to the VM's ram, and then back out of the VM nic to the new hard drive space. It'll probably be faster than doing it from a physical machine, but not much. Fastest way to do it would be directly through Unraid CLI. If it were me, I would make sure that Screen is installed. Then mount the iso to a folder, use a screen session to use with Midnight Commando (mc), and copy it over that way. I do believe you might be able to get decent speeds if you use 9p sharing with a linux VM, but I have no experience with that.

I would just use a different machine to mount the ISO from the appdata share, and copy the files directly to the other directory. Unless these are Blu-Rays, it shouldn't take too long.

Yeah, basically, I have two VM XML's. One with <qemu:commandline> section, and one without. Other than that, they are identical. The one without is so I can remotely access the VM at a bios/boot level to troubleshoot issues. I booted the one without, and it failed to boot once, but went into System Startup failure in Windows, instead of just the "Problem with your PC" error message and auto reboot. I looked around but wasn't able to make any actual changes from CLI or and the auto startup repair failed. But sometime during all of that, it must've installed the driver because then I rebooted it and it took me to the OS. I checked Device Manger, and the hard drive was now listed as a Red Hat SCSI device instead of QEMU Harddrive. I shut it down, booted up my VM with the <qemu:commandline> lines, and it booted up successfully. I then shut it down, made the changes to incorporate your XML SSD Performance tweaks, and booted it back up successfully. The items that I have for passthrough are a USB controller, and an ATI HD7770 GPU.

I got it working! Thanks for your help! I tried it with leaving the device as vdc, but it still wouldn't boot. I booted with no device passthrough (removed all qemu commands) and was able to get it to boot successfully. Then added the passthrough items back and it worked! Then I was able to successfully apply jonp's SSD XML performance tweaks. Thanks everyone!

Worked great on my Gaming VM on Virtio bus. I could not get it to work on my HTPC with Sata bus. I figured that'd be the case, but figured I'd post so others knew. ETA: I successfully converted my Sata bus vm over to Virtio!

Unless you set it up weird, yes, it'll be accessible. If you are running it on your cache drive, just go to your cache share.