[Unraid OS version 6.9.0-beta29 available]

Sorry if this isn’t the best place to ask but I have a Kernel question. Kernel 5.8 to my knowledge is supposed to include code for amd_energy to be monitored by hwmon. Do you know if this code is included in the unraid kernel?

 

I got hwmon working via prom/node-exporter and Prometheus but can’t find anything related to amd_energy. Trying to determine if it’s the kernel lacking or the exporter.

[Unraid OS version 6.9.0-beta25 available]

On 7/20/2020 at 11:29 PM, 5hurb said:

Not sure if its been raised but I'm still having to do this mod to xml to get windows 10 vm to boot without a BSOD kernal error. Found a random thread with a solution to the BSOD.

I don't know what this does or why its needed? Seems like it might be a ZEN 2 issue? has been there since beta22

 

From This

 <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' dies='1' cores='4' threads='2'/>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
  </cpu>

 

 

To This

 <cpu mode='host-model' check='none'>
    <topology sockets='1' dies='1' cores='4' threads='2'/>
    <feature policy='require' name='topoext'/>
  </cpu>

 

OMG you're a saint.  My Windows 10 VM would not start.  VM log was just reporting the below.  Is this a bug?  Wonder what the change did that allowed the to VM boot.  Those groupings below were all in there own IOMMU grouping and not bound to the new VFIO-PCI plugin integration.

 

 

2020-08-19T18:56:34.641854Z qemu-system-x86_64: vfio: Cannot reset device 0000:02:00.0, depends on group 19 which is not owned.
2020-08-19T18:56:34.651819Z qemu-system-x86_64: vfio: Cannot reset device 0000:0f:00.1, depends on group 40 which is not owned.
2020-08-19T18:56:34.656829Z qemu-system-x86_64: vfio: Cannot reset device 0000:11:00.4, depends on group 43 which is not owned.
2020-08-19T18:56:34.770052Z qemu-system-x86_64: vfio: Cannot reset device 0000:02:00.0, depends on group 19 which is not owned.
2020-08-19T18:56:34.770192Z qemu-system-x86_64: vfio: Cannot reset device 0000:11:00.4, depends on group 43 which is not owned.

 

Edit:  Adding I was on latest stable build before updating to Beta 25.  The above were the main SATA controller for my motherboard that the array is on, a USB device that's part of my NVIDIA 2060 and some random Non-Essential Instrumentation.

[[6.8.3] docker image huge amount of unnecessary writes on cache]

On 7/7/2020 at 10:05 PM, limetech said:

Added several options for dealing with this issue in 6.9.0-beta24.

I read through the beta 24 release notes.  Is the option do help deal with this related to editing the config/docker.cfg and having the docker image in a directory and not loopback?  Just trying to see what I need to implement from the beta in order to deal with the excessive writes.