Zer0Nin3r

@Jagadguru Thank you for taking the time to respond. I'll keep an eye open. The thing is, the VM will even hang with no applications open. What I have been observing yesterday is that the system will become extremely sluggish. If I step away for a while or some time and come back to the VM later, it corrects itself and is operational again. I will also check what's happening at the HDD level and monitor the write speeds on which drives. I'm wondering if there is some I/O that is causing the VM to lag. There are no overlapping of CPU pinning with regards to the VM + Docker. RAM usage on Unraid is at: 28.7/31.4 GB I have a high amount allocated towards the VM for Avid **Update** I am not noticing anything about the HDD activity that would warrant concern.

Not sure what the heck is going on, but macOS will lag like a mofo. Booting up and logging in, the VM works great and then out of nowhere, the system will lag heavily making it unusable. Input still works and all, it just takes an eternity to see the actions happen. After a while, the lag goes away and I can use the VM normally again. I use Apple's Screen Sharing primarily and have Splashtop as a backup or for when I need audio; I notice this lag issue on both instances. When the lag happens on Splashtop, the connection will drop and then reconnect. Upon reconnect, the lag is still there. VM's are on an SSD cache. macOS: High Sierra Clover: 4674 Happens on Q35 3.1 & 3.0 Using iMac 18.3 profile in Clover Never had any issues until upgrading Unraid to 6.7.0 <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='31' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>macOS - Avid</name> <uuid>d15d58e2-d8f1-e392-9892-64a64d3c586d</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="default.png" os="linux"/> </metadata> <memory unit='KiB'>27262976</memory> <currentMemory unit='KiB'>27262976</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='17'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='19'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='21'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='23'/> <vcpupin vcpu='8' cpuset='9'/> <vcpupin vcpu='9' cpuset='25'/> <vcpupin vcpu='10' cpuset='11'/> <vcpupin vcpu='11' cpuset='27'/> <vcpupin vcpu='12' cpuset='13'/> <vcpupin vcpu='13' cpuset='29'/> <vcpupin vcpu='14' cpuset='15'/> <vcpupin vcpu='15' cpuset='31'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/d15d58e2-d8f1-e392-9892-64a64d3c586d_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='16' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/macOS - Avid/vdisk3.img'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:61:0f:9f'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='vmxnet3'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-31-macOS - Avid/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x41' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x41' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel,kvm=on,+invtsc,+avx,+avx2,+aes,+xsave,+xsaveopt,+ssse3,+sse4_2,+popcnt,vmware-cpuid-freq=on,'/> </qemu:commandline> </domain>

I'm definitely keeping an eye on the developments here and looking forward for this project to mature some more and come out of beta alpha. 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.

@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!

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. 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 accessible So, 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.

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 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. I have the latest bios installed for the Desginare X399. 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 <[email protected]> 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.

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.

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.

I've ignored this warning since my thread searches hasn't turned up anything critical or relevant to Zenstates + Threadripper. Plus, the Unraid OS has been running just fine *knock on wood*. I didn't see anything in the 6.6.3 announcement when I used the "Search This Topic" function in the forum search. Ditto with a search in the 6.6.2 topic

Thank you for this. It's weird because in SpaceInvaderOne's video, the template allows the changing of Raw –> Qcow2 but when I went to make this change, it wasn't an option. I believe you have to change Raw > Qcow2 before you select/specify the location of the clover boot loader. Because I didn't do this beforehand, the drop-down disappeared which then means you need to edit the XML file directly. @RSQtechThank you for posting, I had the same issue as well. I was able to get Clover to boot after making the change directly in the XML template. @everyone: For what it's worth make sure that when you are creating the DMG/IMG in Disk Utility, that you give yourself enough room i.e., 8GB as specified in SIO's video. I tried 5.56GB (I was trying to save space) which is about the size of the High Sierra installer in the Application folder and Clover wouldn't post the installation img so I could boot. Going back and re-creating the installation img file as specified, solved this problem of being stuck at the Clover boot loader.

In case any new users stumble upon this thread. The option to hide .DS_Store files is available in the GUI. Settings > Network Settings > SMB > Hide "dot" files I ran the terminal command (I don't remember it off the top of my head), rebooted the computer, but the files are still being made on the array. From my understanding, Apple is slowly phasing out AFP and SAMBA will be the way to go; sticking with SAMBA for now.

Is the Ryzen Zenstates warning still relevant to v. 6.6.3? To Threadripper?

32GB (16x2 Non-ECC. Corsair Vengance RGB Pro. 2666 MHz.)

Thank you for the reply and for the insight Squid! I appreciate it. Q: If I specify a specific drive for a particular share to use, then later change my mind and specify a different drive, will Unraid move the files to the new location I specified? Or do the files live in the old location and generate "Share is outside the list of designated disks"? Just trying to better understand how Unraid and shares work.

I did something similar. I had setup Time Machine user share to disk4 which was a 250GB drive. Now, that I am grasping how Unraid works, I removed the 250GB drive, replaced it with a larger drive, added a few more drives and changed the Time Machine share to disk5. After doing a Compute on the user share, I see the message: Share is outside the list of designated disks What are the implications of this?