Devs are gonna LOVE having to optimise games for all those different Xbox devices...
Expect poorly optimised games on all of them.
You haven't been paying attention. All those variants would be running Magnus AT2. And maybe Medusa Point AT3 for the lower SKU.
Devs will only need to target one or two profiles. Maybe three max. Up to 1080/120, 1440/120, and 4k/120.
But the baseline to optimize toward is Magnus AT2 built by MS, aka Xbox Prime. OEMs building higher spec SKUs would still be using the same APU, just more storage, ram, or higher clocking with better cooling. Same with Xbox PCs, they will use Magnus AT2 also. And if any Xbox PCs use AT1 or AT0, that just means the AT2 optimized games would perform more smoother on more powerful hardware.
That's the entire point of using the same Magnus APUs across the board, only thing devs need to build toward.
I never said "full windows". There is no need for that on a console. But you have answered the need for virtualization yourself. In order to make quick resume seamlessly work for PC games, a hypervisor driven approach seems to make the most sense from a security, abstraction and ease of management standpoint. In any case, we are both speculating here and won't know until MS reveals what is it that they are really making. So I'll leave it there.
Ok, I see what your saying but I guess that's where we disagree. I don't think PC unpackaged games will get Quick Resume. That will likely remain a benefit of native Xbox ecosystem games.
MS will want to run the PC games securely regardless, to prevent piracy. Best way to do that is to remove Desktop mode, and file system access. Secondly, run all those games in a secure container that could be wiped/reset easily.
Containerization is MS preferred way to secure things. XDK created Xbox One games were put into the XVC container (Xbox virtual container).
UWP was naturally sandboxed via the appX container. GDK and GDKX containerize games via MSIXVC. And MSIX containerizes other Win32 apps on MS Store.
xCloud runs on Kubernetes containers, running Series S profiles on custom Series X server blades.
MS plan with Windows 10X for the cancelled Surface Neo was to run three types of containers, appX, MSIX, and a large universal container for all unpackaged Win32 apps. Those principles were all added to Windows 11, before UWP was deprecated.
My point is, think containers, not virtualization of unpackaged Win32 games.
And yes, we're all speculating here. But I do think even the Consoles will run full windows, Magnus seems to have three CPU cores dedicated to OS. A converged Windows 12/Xbox OS would likely be provided to the OEMs to run on the entire Xbox family of devices, the full platform. But features unlock based on form factor.
I expect desktop mode, filesystem access to be blocked for consoles, and odds are only the consoles get the Xbox OS shell. The full windows would be extremely locked down on consoles and lie dormant until invoked. The PC games would run inside a large container. They may do separate containers for each storefront or just one big container for all PC stores.
No containers on Xbox PCs, and Console BC/FC delivered via Smart Delivery. Let's see how things play out.