Zer0Nin3r
-
Posts
160 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Zer0Nin3r
-
-
I'm definitely keeping an eye on the developments here and looking forward for this project to mature some more and come out of
betaalpha. At the moment, I have the Handbrake docker setup with thanks to SpaceInvader One. It was a little cumbersome to setup initially with tweaking here and there for my tastes and needs; it works.One thing that is lacking from the Handbrake hack is the ability to flag certain videos to not encode them and simply pass them through to Sonarr. For example, a nightly news show or late night variety show that automatically gets deleted after you watch it doesn't need to be encoded into h.265. The Handbrake workflow also doesn't check for h.265 and will re-encode the file regardless thus, being redundant with some loss to picture quality.
Another thing that I will be curious to see are the encoding customization settings for Unmanic. The Handbrake GUI is something that I am familiar and comfortable with (although, it could use a little more K.I.S.S.) and I would like to see some of those features in Unmanic. e.g., sound/surround sound encoding/downmixing, video encoder speed, etc.
-
On 11/7/2018 at 3:22 PM, 1812 said:
Pro Tip: remove the topology and you can go up to 64 cores, or down to 3 cores, or anywhere in-between. Your Mac vm will actually be faster because when you declare a topology, osx won't push all the threads to 100%, meaning you lose performance. Without topology, it has no idea what is what and uses all threads/cores to 100%.
@1812This is so clutch!! When you said to remove topology, I had no clue what you were referring to.
It's as simple as removing the line: <topology sockets='1' cores='2' threads='2'/> from the xml file after toggling the CPU's that you want to assign to the VM. So again, thank you for the pro tip!
-
1
-
-
On 11/12/2018 at 12:39 PM, scubieman said:
DelugeVPN keeps removing my plugin "simply extractor" and reverting back to "extractor"
Could the plugin version be incompatible with the version of Deluge that you're running? I recently ran into the problem of a pluggin/egg file (Copy Completed) not installing via Web GUI and the version that SpaceInvaderOne had was one version newer than the one I pulled from the Deluge site/forums.
On 11/14/2018 at 7:46 AM, wgstarks said:Plugins should be installed in appdata/binhex-delugevpn/plugins/.
In the past I’ve had issues with plugin settings reverting to defaults (I believe this is/was a Deluge issue) but never had plugins completely disappear.
@scubieman What method did you use to install the plugin?
- Not sure if this will help solve the issue, but try making your changes to the preferences using the Web GUI and Apply/OK them.
- Next, go Connection Manager > Disconnect > Reconnect > Stop Daemon > Start Daemon
- Stop/Start the Deluge docker
I was running into an issue of the Plugin's settings were not being saved after stopping and starting the Deluge docker. Doing this, seemed to help me and I got the idea from here.
Initially, I thought it might be a permissions issue as this was showing up in my log:
WARNING: file 'credentials.conf' is group or others accessibleSo, I deleted the perms.txt file thinking that would solve the issue.
I also, understood not to run the New Permissions (Located under Tools > New Permissions) on the /appdata directory as it will have a negative impact on any Docker containers — so, I didn't run New Permissions.
QuoteNote that this tool may negatively affect any docker containers if you allow your appdata share to be included.
-
1
-
On 11/29/2018 at 12:25 PM, Dazog said:
Maybe AMD knows something we don't?
Just posted:
https://www.phoronix.com/scan.php?page=news_item&px=AMD-Zen-November-Microcode
To fix threadripper issues?
On 11/29/2018 at 3:19 PM, limetech said:Thanks for the "heads up". We'll keep an eye on the kernel git repo:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
Would this fix the Zen states warning in Fix Common Problems app?
Honestly, I haven't experienced any perceivable performance issues with the Zen states warning that the Fix Common Problems plugin reports; the corresponding thread that the plugin links to doesn't seem to pertain to Threadrippers per say.
-
On 11/29/2018 at 4:04 PM, John_M said:
The k10temp module only reads the processor's onboard sensor. Hence Tdie. Tctl is the same as Tdie but with an offset of +27 degrees C for some processors. If you want to read motherboard temperature and fan speed sensors you need a module for your particular Super I/O chip.
Is there a benefit to the ~+27 C for some processors?
I thought I shared a screenshot from the terminal showing the "four" temperature readings.
Regardless, thank you for the informative response @John_M
-
Report Findings:
- Dynamix Auto Fan Control is incompatible with the Threadripper 1950x running on a Gigabyte Designare X399.
-
Only the CPU Temperatures are detected by Sensors command.
- This is after performing sensors-detect command and saying YES to all the prompts.
-
Testing with a 1950x on a Desginare X399
On 11/12/2018 at 11:34 AM, John_M said:You can type 'k10temp' manually, then click Save, then Load drivers. Worth a try?
So initially clicking on Detect didn't do anything.
typing Sensors or k10temp into the field allows the plugin to pull in the temps. But, only two sensor readings.
On 11/12/2018 at 3:32 AM, sjaak said:1950X on a Gigabyte X399 Aorus gaming 7 motherboard with latest BIOS
I have the latest bios installed for the Desginare X399.
On 11/12/2018 at 3:36 AM, bastl said:This command worked.
Output:
But I do not know what those sensors reading from.
I do have three (3) wire temperature sensors that I attached to the motherboard that come with the Designare X399. Loading into the bios when I have a monitor attached, you can see all the temperature readings and fan readings. Just wished there was a way to get all of this data inside Unraid since I am running headless.
Also is this relevant?:
source: https://github.com/groeck/k10temp
Kernel driver k10temp ===================== Supported chips: * AMD Family 10h processors: Socket F: Quad-Core/Six-Core/Embedded Opteron (but see below) Socket AM2+: Quad-Core Opteron, Phenom (II) X3/X4, Athlon X2 (but see below) Socket AM3: Quad-Core Opteron, Athlon/Phenom II X2/X3/X4, Sempron II Socket S1G3: Athlon II, Sempron, Turion II * AMD Family 11h processors: Socket S1G2: Athlon (X2), Sempron (X2), Turion X2 (Ultra) * AMD Family 12h processors: "Llano" (E2/A4/A6/A8-Series) * AMD Family 14h processors: "Brazos" (C/E/G/Z-Series) * AMD Family 15h processors: "Bulldozer" (FX-Series), "Trinity", "Kaveri", "Carrizo" * AMD Family 16h processors: "Kabini", "Mullins" * AMD Family 17h processors: "Ryzen", "Threadripper" Prefix: 'k10temp' Addresses scanned: PCI space Datasheets: BIOS and Kernel Developer's Guide (BKDG) For AMD Family 10h Processors: http://support.amd.com/us/Processor_TechDocs/31116.pdf BIOS and Kernel Developer's Guide (BKDG) for AMD Family 11h Processors: http://support.amd.com/us/Processor_TechDocs/41256.pdf BIOS and Kernel Developer's Guide (BKDG) for AMD Family 12h Processors: http://support.amd.com/us/Processor_TechDocs/41131.pdf BIOS and Kernel Developer's Guide (BKDG) for AMD Family 14h Models 00h-0Fh Processors: http://support.amd.com/us/Processor_TechDocs/43170.pdf Revision Guide for AMD Family 10h Processors: http://support.amd.com/us/Processor_TechDocs/41322.pdf Revision Guide for AMD Family 11h Processors: http://support.amd.com/us/Processor_TechDocs/41788.pdf Revision Guide for AMD Family 12h Processors: http://support.amd.com/us/Processor_TechDocs/44739.pdf Revision Guide for AMD Family 14h Models 00h-0Fh Processors: http://support.amd.com/us/Processor_TechDocs/47534.pdf AMD Family 11h Processor Power and Thermal Data Sheet for Notebooks: http://support.amd.com/us/Processor_TechDocs/43373.pdf AMD Family 10h Server and Workstation Processor Power and Thermal Data Sheet: http://support.amd.com/us/Processor_TechDocs/43374.pdf AMD Family 10h Desktop Processor Power and Thermal Data Sheet: http://support.amd.com/us/Processor_TechDocs/43375.pdf Author: Clemens Ladisch <clemens@ladisch.de> Description ----------- This driver permits reading of the internal temperature sensor of AMD Family 10h/11h/12h/14h/15h/16h/17h processors. All these processors have a sensor, but on those for Socket F or AM2+, the sensor may return inconsistent values (erratum 319). The driver will refuse to load on these revisions unless you specify the "force=1" module parameter. Due to technical reasons, the driver can detect only the mainboard's socket type, not the processor's actual capabilities. Therefore, if you are using an AM3 processor on an AM2+ mainboard, you can safely use the "force=1" parameter. There is one temperature measurement value, available as temp1_input in sysfs. It is measured in degrees Celsius with a resolution of 1/8th degree. Please note that it is defined as a relative value; to quote the AMD manual: Tctl is the processor temperature control value, used by the platform to control cooling systems. Tctl is a non-physical temperature on an arbitrary scale measured in degrees. It does _not_ represent an actual physical temperature like die or case temperature. Instead, it specifies the processor temperature relative to the point at which the system must supply the maximum cooling for the processor's specified maximum case temperature and maximum thermal power dissipation. The maximum value for Tctl is available in the file temp1_max. If the BIOS has enabled hardware temperature control, the threshold at which the processor will throttle itself to avoid damage is available in temp1_crit and temp1_crit_hyst.
-
General rule of thumb is to leave CPU 0 and its corresponding hyperthread open to Unraid. All other CPU & HT are free game.
Try moving your VM's to CPU 1&2. Dockers can go later.
There is a thread somewhere in the forums that go into further details on how to discover which CPU's are on which particular die.
Also, subscribe to @spaceinvaderone's YouTube channel, as he has a video on CPU pinning and VM's.
Good luck and share with us your discoveries!
P.S. - If you don't like the forum's search engine, use the syntax:
site:forums.unraid.net search terms
Into a search engine such as DuckDuckGo, StartPage, or Google, replacing search terms with your intended query.
I'm sure that you'll find what you are looking for in the forums as many have asked similar questions in the past.
-
The Hide button simply became a mystery that only the Invision Community devs know about.
-
8 hours ago, BRiT said:
Have you found the Seek Button yet?
Deja-Vu.
LoLz. No I haven't.
6 hours ago, trurl said:But I don't see why a user would want to hide their own post, especially if they can't see it or unhide it, instead of just deleting it. Can normal users delete their own posts?
I can see a use wherein a forum user will want to post to the forum and yet, they don't want it fully and readily accessible by a search engine such as Google. e.g. information that the user deems as sensitive in nature; limit meta-data
-
Weird. Using the Hide button works, but a complete refresh of the page...the poof...the post is gone even for me.
Does anyone know what the Hide Button does?
-
1
-
-
Test II
-
This is a test for what the 'hide' button does when you reply to a thread.
I've searched the Invision Community's website, but they don't have anything in their documentation. My assumption is that it allows you to reply to a thread without search engines crawling your reply and storing it on their servers yet, registered forum users can still read your reply.
-
4 hours ago, Squid said:
What you're missing is that Docker is part of unRaid, so by default your handbrake container also only has access to CPU 0 and 1. You can pin Handbrake by editing it to one of the other isolated cores, but you cannot pin it to multiple isolated cores and have it execute correctly on those multiple cores.
IE: Isolating cores is generally only done when you want a VM to have exclusive access to cores.
Okay, I think I have a better understanding now. Thank you. I found the thread on in-depth CPU pinning, and will have to go over that in finer detail at some point.
So, CPU Isolation is good when you want to run Docker applications in parallel to running VM's in order to keep the shared system resources tidy. In the case of Handbrake, this is counter intuitive because you will only be limited to a single core as CPU Isolation will not allow Handbrake access to multiple pinned cores. CPU Isolation will work great with applications that are not CPU/multi-thread intensive.
-
So, if I want to keep CPU: 0 and its Hyperthread: 1 for Unraid, it would look like this?
Am I understanding the help tip correctly? At first I thought I would just pin CPU 0/1 and that would reserve it for Unraid.
**Update**
Yes, this is how CPU pinning for Unraid should look like if you want to pin Unraid to Core 0/1 (Threadripper 1950x). I was able to verify by launching terminal after a reboot and running htop from the command line.**Update**
@Jcloud I was wrong with my previous update to this post.
Now, I'm totally confused. With the settings set above in the screenshot, I thought CPU 0/1 would only be reserved for Unraid. Come to find out that, CPU 2–31 weren't being used at all when I ran a test with Handbrake. Instead, Handbrake was confined only to CPU 0/1 along with Unraid. Everything else was reading 0%.
Now that I enabled CPU pinning on CPU 0/1 with everything else untoggled, Handbrake is now being confined only to CPU 0. Very strange.
-
1
-
-
SUNDAY!! SUNDAY!! SUNDAY!!
Come witness the Battle of the VM's live in 3-D!
Chaos and Mayhem guaranteed!
Greetings @everyone! I am curious to know your thoughts on which OS running inside a VM will give me the best performance. I edit photos in Lightroom, Photoshop, and Lumen. Video editing is also something I do with FCP X. While my primary workflow has been macOS based, I am open to the idea of installing my Adobe programs on a Windows VM if that means I will get better performance.
My thoughts and assumptions:
-
Windows is "VM friendly"
- Meaning, it knows when it is being ran as a VM. I would imagine that Windows will optimize itself automatically under these conditions.
- Windows will make better, more efficient use of the resources available to the VM.
-
macOS
- Thinks it's running on Apple hardware, but because we are using "magic" to trick the OS into working for a hypervisor as a guest VM, we will take a hit in performance.
- While we are able to pass an Nvidia GPU onto the macOS VM, this will increase performance, but because we are hacking the OS, we are susceptible to degraded performance.
- It's well known that Apple isn't bleeding edge technology. That being said, performance will/may lag behind that of Windows workstations when compared in performing tasks such as rendering.
-
Windows is "VM friendly"
-
I bought a Windows 10 Pro license, but haven't tried to activate it yet with my VMs.
-
Is there any disadvantage of not activating your key on a Windows VM?
- Is there an advantage to activating?
- Is there a way to assign the activation key to more than one VM?
I don't use a Windows VM as a daily driver. Only to edit photos and game.
-
Is there any disadvantage of not activating your key on a Windows VM?
-
4 minutes ago, 1812 said:
Pro Tip: remove the topology and you can go up to 64 cores, or down to 3 cores, or anywhere in-between. Your Mac vm will actually be faster because when you declare a topology, osx won't push all the threads to 100%, meaning you lose performance. Without topology, it has no idea what is what and uses all threads/cores to 100%.
Is this covered in SPO's video on how to tweak macOS VM performance? Because I haven't watched it yet. LoL.
@1812 Would you mind sharing your current settings? Or recommended settings?
I'm setting up FCP X in my High Sierra VM and am trying to take full advantage of my Threadripper 1950x and Nvidia GPU; I'm also contemplating installing my photo editing software in the macOS VM instead of a Windows 10 VM.
-
On 10/29/2018 at 1:32 PM, IanB said:
I'm trying to setup a High Sierra VM on my 6.6.3 Unraid Server. I've followed the video multiple times to verify i'm doing everything. However, after Force Stopping my VM (after updating the BIOS resolution) and trying to first boot into the OSX installer things start to go wrong. I'm initially presented with an Apple logo for ~5 seconds (no progress bar). After this, the VM appears to reboot back into Clover. This will then repeat a number of times until finally Clover gives up and i'm displayed with a large X.
Does anyone have any useful tips to get additional information from Clover as to what is failing?
Thanks in advance
It is important to use the correct number of cores when creating a macOS VM. In the video from @SpaceInvaderOne, his guide works with 4 cores all the way up to 8 cores. I just tried 10/12/14 cores and that's where, I ran into problems.
While I am new to Clover, I am curious to see if an updated Clover and a change to a profile like, iMac Pro, will allow me to assign more processors to the VM. Also, I noticed that we are using the Penryn designator in the XML, is this hindering us from assigning more cores/CPUs to the VM? The Mac Pro goes up to 8 cores. iMac Pro goes up to 18 cores.
-
9 hours ago, John_M said:
I'm curious as to why you want to run parity checks as often as every week. I'd say it's unnecessary and once a month is fine but you may well have a good reason.
Not sure who you are addressing, but I will say this. I have my parity checks scheduled for once a quarter. In order to do this, you have to set each individual field. There is no option to schedule on a quarterly or bi-monthly, etc. basis.
So, I'm not trying to schedule a parity check each week, it just so happens that I set the schedule for Sundays which just so happens is affected by the bug.
Perhaps, @plantsandbinary is whom your question is for?
-
11 minutes ago, plantsandbinary said:
Oh wow, it's a bug, just for Sunday? Haha.
I guess Unraid wants to adhere to the Sabbath; maybe computers are sentient after all.
-
1
-
1
-
-
@plantsandbinary It's a known issue and will be fixed — hopefully, in the next patch. In the meantime, change your day to any other day than Sunday.
-
On 5/20/2018 at 1:58 AM, Fireball3 said:
Especially for recurring problems it's very useful.
It takes a lot of time to repeat things again and again and the forum search is of no help unfortunately.
It took me some time to figure out the forum's search and it's quirks, but it works. #tapeandglue
I would've been happy to update the Wiki with the knowledge that I am gaining from SpaceInvaderOne's videos and raiding (pun intended) the Unraid forum, but logging in with my forum credentials simply doesn't work as stated before.
I see a lot of reoccurring threads, but I suppose that is human nature. Either A) humans are lazy to make the effort to find the information they are looking for or B) humans are making the effort and the back-end is hindering the person's ability to find what they are looking for.
Pro Tip #31: Using the search operator site:forums.unraid.net and your search term(s) with DuckDuckGo/StartPage/Google makes finding the information that you are looking for WAY more easier.
-
20 hours ago, trurl said:
Since the Unraid OS is in RAM, installed plugins are taking up RAM even when not invoked. Depending on the specific plugin, it may or may not have background processes that also take CPU.
That makes total sense now. I was thinking that they live on the array.
Thank you.
I will up vote you when I get more reactions — just wished we'd get more of them.P.S. - Wouldn't be great if we could toggle plugins on and off?
Improving Windows VM performance for gaming
in VM Engine (KVM)
Posted · Edited by Zer0Nin3r
Threw in another question about CPU pinning to 0/1
Are you noticing any performance improvements after switching to Q35-3.0.0? I've been happy so far with the gaming performance on i440fx-3.0 running BFV, R6, and PUBG.
Maybe, I'll give it a try and report back.
Also, I was trying to search on the forum, but is it imperative that we don't pin anything to CPU 0/1? I'm running a Threadripper and I think I would get better performance if isolating VM's to a single chip versus spreading the workload of the VM across the Infinity Fabric.
===
I also, want to link back to another thread that discusses Q35 and gaming performance so we have a cross-reference here.