3 ms·
If I am understanding correctly, it is an Xbox issue because game systems do not like virtualization / emulation / containerization functionality because of its
by lordlimecat 5y ago
If I am understanding correctly, it is an Xbox issue because game systems do not like virtualization / emulation / containerization functionality because of its potential for enabling cheats. Many test proctoring systems are the same way-- the presence of a virtualization service, driver, or hypervisor will trigger a red flag.
So again, for the huge number of people whose life involves technology there are a lot of things that can throw a wrench into that PC for gaming, and in those cases a console makes a lot of sense. It's a little odd to me that this bothers you so much; surely it is expected that consoles have a good usecase given their popularity?
- zeusk 5y agoNo the issue here is Docker creating an improperly configured network interface. xbox apps on Windows do not care about virtualization, in fact they probably can't - because xbox os is essentially a subset of windows as host and guest.
- lordlimecat 5y agoIf you are saying that a Windows application cannot tell if virtualization is in use, you are incorrect. It can both tell whether you are in a virtualized instance (e.g. if you have Hyper-V on) and if you are running a hypervisor. In the former case, a simple hardware inspection would suffice, and there are a dozen other methods to tell such as used by virt-what. None of this is relevant. Maybe Docker's interface is "improperly configured" for the gaming use case. It remains a headache, and using a console is a viable solution that allows you to work with buggy instances of Docker without disrupting your gaming.