That seems to be a great question! I have no idea what the answer is. :-)
I can only say that I experienced the same problem symptoms that several people before me did - that Windows setup hung at the initial boot screen with glowing logo. Following the same steps that helped many others also helped me (changing to Cirrus driver). All the details to the how are summarised nicely here: https://github.com/QubesOS/qubes-issues/issues/2488. I don't recall any mention of the why, though. I guess I can also say that my system is a standard Intel Skylake Core M7 utilising the on-processor Intel HD graphics, and that my BIOS is a combination of Coreboot and Tianocore, purely UEFI. Just some fundamental driver incompatibility maybe. Incidentally, in case it might help anybody that comes after me and reads this thread... I upgraded from the previous build of QWT to the latest (3.2.2-3) since the previous version didn't work particularly better for me. Since then I was able to run Windows apps at least twice in seamless mode, no debug! It's pretty random, though. It fails to display a window at all most times, and the VM has to be killed. I will try to find time to look deeper, maybe increase the loglevel of some of the components and see more of what's happening when it fails vs. when it succeeds. Not sure on when I can find the time for that, but I'll try to remember to report back if I find anything that allows me to get it working consistently all the time. For now I've accepted running it always in debug mode for the stability. On Thu, Aug 17, 2017 at 6:44 PM, Drew White <drew.qu...@gmail.com> wrote: > On Tuesday, 15 August 2017 03:19:03 UTC+10, Daniel Nelson wrote: > > Thanks for all the additional notes. Everything you did perfectly > matched what I've done except that I also had to copy the win7.conf and > edit it to change the video from "xen" to "cirrus," which is also pretty > well documented in various places. I had to do this both during Windows > install, and then again during QWT install, but it worked as advertised. > > The one thing I've not done too much fiddling with is the resolution. > I've tried 1024x768 without joy. I will continue to investigate further > with different resolutions, and I will try also to more permanently change > the video driver in use. > > > > Thanks again! > > Why do you all have to change from Xen to Cirrus in the config? > > I use XEN as my video. And I have no issue with many graphical things now. > > Only time I have issues is when I try to start the Windows Guest when I'm > running 5 monitors. As long as I start it with only 1, then proceed to add > the rest, it's fine. But I've said all this before so I swill not repeat it > all over again. > > But that's the only real issue I have with the video side of it. > > So I am just curious as to why so many people I see are having to change > to Cirrus from XEN? > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAB-xJPfnDNZsCNdBnViyiYjr7Qo2jH%3DrfPf%2B4B1tw3RqdKJ1LQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
