archedraft

Wow that's intense! Are all your cache drives in a pool or can you set them to be individual caches?

I have the same setup and mostly I find it easiest to just click to the page ever so often as I have 1 main VM that uses the GPU. That said you could make a script that you run that shutdown the current VM, waits xx amount of seconds and starts the next VM. It would look something like this: virsh shutdown win10vm sleep 30 virsh start win7vm

My VM was also a Windows 10 VM. I went back to 6.1.9 as I have limited time currently. I will probably try again once the next beta is released.

Thought I would try my luck with 6.2. Trying to get my VM's back up and working but it would seem that with 6.2 it doesn't like the VM's hosted on the unassigned devices plugin. Is this correct? I keep getting the following when I create a VM located on a mounted disk: Warning: libvirt_domain_xml_xpath(): namespace warning : xmlns: URI unraid is not absolute in /usr/local/emhttp/plugins/dynamix.vm.manager/classes/libvirt.php on line 936 Warning: libvirt_domain_xml_xpath(): EDIT: hmm, even If I try to create a new VM in the /mnt/user/system/ location I get error. Diagnostics attached. Any ideas?

You haven't had to click that button since June 2015. (Part of the reason it says "Don't Click Me - Why Are You Clicking Me?" on its pop up) Unless you're talking about Plugins - Check For Updates, in which case, yes you will now have lots of spare time on your hands to spend with your better-half. Hmmm, well in that case I would like a feature request to blow up the auto update feature into oblivion... The better-half always has something for me to accomplish [emoji51]

Whooo I don't have to click the community app update button daily!! I'm not sure what I will do with all my newly found free time... ?

If you read through the user comments on the other guides you will find someone who gave instructions on how they accomplished that. I have no plans to make another guide with OVMF as I am not currently running my VM that way.

Looking at your config, I would suspect 2 things and the first being the most likely. A system log may shed some more light on what is going on. 1. Amount of assigned memory, if unRAID needs more it will kill the VMs (unRAID did this to me many times until I backed off the memory I gave to my VMs) 2. Amount of CPU cores assigned. This is less likely but if you take away some memory from the VM and it is still crashing I would try less cores.

Definitely Tito Puente!

So what does it feel like to be a rockstar?

You're welcome, glad the guide was helpful.

I forget the excatly how but you need to add "rcp2" to the end. *I think* something like this: No user name or password is needed. You may need to change it to http: at the beginning though scgi://localhost:5000/rpc2

I would say give it a shot. A lot of other users with AMD boards have the VM up and running.

Could you elaborate more on this? Do we need to remove our /transcode location in our docker and then Plex manages it?

Why not just install it in your dads machine and format then?

Could you check and see if the 2016.03.26 (2.20) update breaks the Sxx and Kxx scripts? My Sxx scripts were working fine with 2016.02.14a (2.19) but do not seem to load with 2.20. EDIT: Disregard, error is in my end.

Yeah, I believe the .plist file has some weird characters in it and isn't working properly. You either need to create a new one or use a special text editor (text wrangler) to clean it up.

Basically if someone is randomly scanning all the external IP addresses in the world and is trying to find open ports they would start with commonly open ports to speed up their random search. So to be extra safe it is best to use an uncommon port to make their life harder.

I believe it is because of this line in the XML <model fallback='allow'>core2duo</model> I tired messing with other models but nothing would boot on my machine. Maybe with unRAID 6.2 it will work but I haven't updated my server yet. Here is a list of some models you can try. It might be an older list: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/ch03s02.html If you get one to work post back with how you accomplished it.

Definitely keep plugin updates in the footer (and preferably have a way to disable plugin footer notifications). Major unRAID OS updates could be a big in your face banner or footer and I wouldn't give an option to disable that notification.

Looks good to me, I know that alone would motivate me to update. I always update to the latest regardless but if I didn't that certainly would drive me crazy!

That's a good idea. I know the Plex banner drives me crazy so I update very regularly just to stop seeing it. Just make sure it shows back up every time you reload the page like Plex does, if the X permanently closes the notification I wouldn't be as motivated to update.

That is a lousy thing to say. It's as perfectly fine a thing to say as is posting about the history. History does not always dictate the future. That's all I was conveying. Past performance may not always indicate the future performance but the best way to predict future performance is by using past performance.

I like the idea of making it less clicks to verify data. Another idea based on johnnie's post. It would be pretty awesome to add a row for each disk on the dashboard that had a green check or whatever symbol stating that all data on that disk was good and a red X if it found that data was corrupt.

Same here. It has happened with with all 6.1 and 6.2 versions I have used All my VMs say the same thing in 6.1, my understanding is that it is because the VMs have root privileges . The interwebs left me believing that this message wasn't a big deal. what isn't normal though is my VM totally freezing, that just happens to be the last entry in the log. Agreed, freezing VMs is a pretty big deal.