I've described most of these settings/features extensively here:

 

However, it would be great if these were added to the image by default:

 

1. Add

  <timer name='hypervclock' present='yes'/>

along with the reset of prerequisites to Windows 10/11 VMs by default. This will dramatically reduce idle CPU usage of these VMs

 

2. Add "ksmtuned" daemon to the image for controlling KSM (kernel samepage merging) to reduce RAM usage for those with multiple similar VMs and enable it by default. It only gets triggered at 80% RAM utilization by default. It's really just a shell script.

 

3. Add ability to limit maximum number of cores for a VM without actually pinning the cores to physical cores to let the host kernel distribute the load.

Edited April 21, 20233 yr by m00nman

On 2/28/2023 at 5:16 AM, m00nman said:

I've described most of these settings/features extensively here:

 

However, it would be great if these were added to the image by default:

 

1. Add

  <timer name='hypervclock' present='yes'/>

along with the reset of prerequisites to Windows 10/11 VMs by default. This will dramatically reduce idle CPU usage of these VMs

 

2. Add "ksmtuned" daemon to the image for controlling KSM (kernel samepage merging) to reduce RAM usage for those with multiple similar VMs and enable it by default. It only gets triggered at 80% RAM utilization by default. It's really just a shell script.

 

3. Add ability to have maximum number of cores for a VM without actually pinning the cores to physical cores to let the host kernel distribute the load.

Hi I will review and look to see if we can add to next release after 6.12. Do you need hyperv as you can disable that also.

On 3/26/2023 at 6:13 AM, SimonF said:

Hi I will review and look to see if we can add to next release after 6.12. Do you need hyperv as you can disable that also.

 Thank you for looking into this. Yes, hyperv enligtenments need to be on for hypervclock to work

 

+1 vote for this feature!

+1 vote from me.

+1 as well

On 2/28/2023 at 5:16 AM, m00nman said:

I've described most of these settings/features extensively here:

 

However, it would be great if these were added to the image by default:

 

1. Add

  <timer name='hypervclock' present='yes'/>

along with the reset of prerequisites to Windows 10/11 VMs by default. This will dramatically reduce idle CPU usage of these VMs

 

2. Add "ksmtuned" daemon to the image for controlling KSM (kernel samepage merging) to reduce RAM usage for those with multiple similar VMs and enable it by default. It only gets triggered at 80% RAM utilization by default. It's really just a shell script.

 

3. Add ability to limit maximum number of cores for a VM without actually pinning the cores to physical cores to let the host kernel distribute the load.

Hi mOOnman,

 

I have looked at the code and point 1 should already be there. Which version where you running the tests on?

 

            if ($domain['hyperv'] == 1 && $os_type == "windows") {

                $hyperv = "<hyperv>

                            <relaxed state='on'/>

                            <vapic state='on'/>

                            <spinlocks state='on' retries='8191'/>

                            <vendor_id state='on' value='none'/>

                        </hyperv>";

 

                $clock = "<clock offset='" . $domain['clock'] . "'>

                            <timer name='hypervclock' present='yes'/>

                            <timer name='hpet' present='no'/>

                        </clock>";

            }

 

Do these need to be added also?

 

<vpindex state='on'/> <synic state='on'/> <stimer state='on'/>

+1

 

On 8/28/2023 at 6:25 AM, SimonF said:

Hi mOOnman,

 

I have looked at the code and point 1 should already be there. Which version where you running the tests on?

 

            if ($domain['hyperv'] == 1 && $os_type == "windows") {

                $hyperv = "<hyperv>

                            <relaxed state='on'/>

                            <vapic state='on'/>

                            <spinlocks state='on' retries='8191'/>

                            <vendor_id state='on' value='none'/>

                        </hyperv>";

 

                $clock = "<clock offset='" . $domain['clock'] . "'>

                            <timer name='hypervclock' present='yes'/>

                            <timer name='hpet' present='no'/>

                        </clock>";

            }

 

Do these need to be added also?

 

<vpindex state='on'/> <synic state='on'/> <stimer state='on'/>

Hi SimonF, I believe it was version 6.11.x, the version that was current at the time of writing OP.

 

Yes, it is my understanding that that you need all of the following options <vpindex state='on'/> <synic state='on'/> <stimer state='on'/>, additionally some people reported settings migratable='off' resolved issues with GPU PCIe passthrough stutter. migratable='on' is only useful when miograting VM from one host to another, and unraid does not support it anyway so it's safe to turn it off for everyone.

 

 

Edited August 29, 20232 yr by m00nman

On 8/29/2023 at 7:05 PM, m00nman said:

Hi SimonF, I believe it was version 6.11.x, the version that was current at the time of writing OP.

 

Yes, it is my understanding that that you need all of the following options <vpindex state='on'/> <synic state='on'/> <stimer state='on'/>, additionally some people reported settings migratable='off' resolved issues with GPU PCIe passthrough stutter. migratable='on' is only useful when miograting VM from one host to another, and unraid does not support it anyway so it's safe to turn it off for everyone.

 

 

I have created a PR to address these and make timers available from the GUI to change. https://github.com/unraid/webgui/pull/1494

 

migratable is on PR https://github.com/unraid/webgui/pull/1474

I just found this post through google search but I couldn't find the settings on the GUI. @SimonF Are these changes in the official release of 6.12.8?

3 hours ago, aarontry said:

I just found this post through google search but I couldn't find the settings on the GUI. @SimonF Are these changes in the official release of 6.12.8?

Next release i.e. 6.13

Oh ok thanks. I thought the next release will be the 7. 

2 hours ago, aarontry said:

Oh ok thanks. I thought the next release will be the 7. 

Yes it maybe release as 7.

Has this been implemented, as of Unraid 7 beta 4??

Edited October 21, 20241 yr by MILDEW

6 minutes ago, MILDEW said:

Has this been implemented, as of Unraid 7 beta 3??

The timer part is in betas now its beta 4

4 minutes ago, SimonF said:

The timer part is in betas now its beta 4

I just came back to edit my comment after noticing the update. Thank you.

On 2/28/2023 at 6:16 AM, m00nman said:

2. Add "ksmtuned" daemon to the image for controlling KSM (kernel samepage merging) to reduce RAM usage for those with multiple similar VMs and enable it by default. It only gets triggered at 80% RAM utilization by default. It's really just a shell script.

+1 for the KSM feature, which can greatly reduce the RAM consumption of the host through deduplication if there are several similar VMs or even a single VM running many similar processes.