Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Windows 10 StandaloneVM not booting #4352
Qubes OS version:
Qubes 4.0 (R4.0)
Windows 10 StandaloneVM
Steps to reproduce the behavior:
Create a Windows 10 StandaloneVM. Update the VM and install Qubes Windows Tools. Everything works at this point.
Close down the VM and increase the memory and max memory to 8049 in dom0
Windows 10 StandaloneVM won't boot (No GUI) State is Yellow.
Windows 10 StandaloneVM boots (With GUI)
Windows 10 StandaloneVM doesn't boot (No GUI) State is Yellow.
The GUI doesn't open at all
If I run qvm-start Windows-10 from dom0 I see no errors and it completes.
Icon size: 128x128
The Windows-10 VM shows as State Green in Qubes Manager.
It looks like it's booted but just not connecting to the GUI from that log file and the fact that it doesn't open the GUI window at all.
I'm running the latest updates from qubes-dom0-current-testing
Do you mean that you can consistently boot your VM without problem (
Did you try to enable debug to get an early gui console ? (
[edit- typo -
I have tried enabling qvm-prefs Windows-10 debug true with a fresh VM but I still get the issue.
I'm running Windows 10 Pro N for Workstations.
I was also getting the same issue with Windows 10 Pro.
The problem is introduced as soon as I install the latest version of QWT, reboot and start the system and then try to reboot again.
This time I set up all the correct RAM parameters at the start.
That's strange, with debug=true you should see a gui console of the VM - eg. the windows boot entry, windows boot logo, ..., until:
You could try to enable debug before you install QWT and check that you see the early console. If you don't, something's not OK, try to search other issues or file a new one.
By the way QWT for R4.0 are still a work in progress - they work OK for some people, and crash for others (see issue #3585)
Because it looked like you had two unrelated problems::
I assumed 1. because you wrote:
If that's in that order, Windows being Windows, WindowsUpdate most likely rebooted the VM a zillion times. This would imply that you could reboot the VM without experiencing the 'domain dead' error.
Which seemed to confirm my assumption. But you then replied:
So, did you mange to have a functional VM without QWT installed ?
Anyway, what do