[Bug 39416] New: Many settings should be per VM host

https://bugs.winehq.org/show_bug.cgi?id=39416

Bug ID: 39416
           Summary: Many settings should be per VM host
           Product: Wine-Testbot
           Version: unspecified
          Hardware: x86
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

The following global settings should in fact be customizable on a per VM host
basis:
* $MaxRevertingVMs - Hosts with SSDs may be able to handle multiple reverts in
parallel.
* $MaxRevertsWhileRunningVMs - Again this may depend on disk speed and QEmu
version.
* $MaxActiveVMs - Depends on disk and CPU speed, number of cores, etc.
* $SuiteTimeout & $SingleTimeout - Might need to be adjusted based on the CPU
speed.
* $BuildTimeout & $ReconfigTimeout - Might need to be adjusted based on the CPU
speed. Fortunately we can currently only have one build VM so that's not too
much of an issue.

One way to do so would be to introduce a VMHosts table storing the settings for
each VM host (see the schema attachment of bug 39412). VMs (VMInstances really)
would then be linked to the relevant VM host so to indicate which set of
constraints apply.

Note that this would be different from the handling of the truly global
settings described in bug 39415.

[Bug 39416] Many settings should be per VM host

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=39416

--- Comment #1 from François Gouget  ---
I think it is both possible and desirable to use the same mechanism as for the
global settings (see bug 39415).