[Bug 47927] New: Is the win32/win64 VM Type distinction redundant with the Missions field
https://bugs.winehq.org/show_bug.cgi?id=47927
Bug ID: 47927 Summary: Is the win32/win64 VM Type distinction redundant with the Missions field Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com Distribution: ---
Currently the TestBot has four types of VMs: build, win32, win64 and wine.
As expected the win32 and win64 VM types respectively correspond to 32 and 64 bit Windows VMs which directly correlates with their intrisic ability to run 32 and 64 bit Windows executables.
In contrast whether a wine VM can (or should) run 32 bit Windows executables, 64 bit ones or both is not indicated by its type. Instead this is determined by the VM's Missions field. A Wine VM, a NetBSD one for instance, could be able to run 64 bit executables but not 32 bit ones. Or testing the win32 build could be done on one VM and testing the wow32 and wow64 one on another to spread the load.
All VMs have this mission field, including the win32 and win64 VMs, where, like elsewhere, it will determine whether the TestBot allows running 32 and/or 64 bit executables.
In other words a win64 VM will not run 64 bit executables if exe64 is not in its Missions. That makes the win32 vs. win64 distinction somewhat redundant. So maybe the two types should be merged into a single 'windows' VM type. Or maybe it should be preserved as a way to record what the VM is capable of independently of the missions currently assigned to it.
https://bugs.winehq.org/show_bug.cgi?id=47927
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Is the win32/win64 VM Type |Is the win32/win64 VM Type |distinction redundant with |distinction redundant with |the Missions field |the Missions field?
-
WineHQ Bugzilla