New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows 10 StandaloneVM not booting #4352

Open
Simon-Davies opened this Issue Sep 28, 2018 · 9 comments

Comments

Projects
None yet
4 participants
@Simon-Davies
Copy link

Simon-Davies commented Sep 28, 2018

Qubes OS version:

Qubes 4.0 (R4.0)

Affected component(s):

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.

Expected behavior:

Windows 10 StandaloneVM boots (With GUI)

Actual behavior:

Windows 10 StandaloneVM doesn't boot (No GUI) State is Yellow.

General notes:


Related issues:

@unman

This comment has been minimized.

Copy link
Member

unman commented Sep 28, 2018

A little more information might be useful - any errors reported?
Does window open and close again?
If you run qvm-start from dom0 konsole, do you see any more detail?
Anything reported in logs? (You can access these from Qube Manager)

@Simon-Davies

This comment has been minimized.

Copy link

Simon-Davies commented Sep 28, 2018

The GUI doesn't open at all

If I run qvm-start Windows-10 from dom0 I see no errors and it completes.

Logs:

/var/log/qubes/guid.Windows-10.log

Icon size: 128x128
domain dead
Failed to connect to gui-agent

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

@taradiddles

This comment has been minimized.

Copy link

taradiddles commented Oct 1, 2018

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

Do you mean that you can consistently boot your VM without problem (withwithout QWT installed) until you change the memory setting, or did booting fail just after you installed QWT ?

Did you try to enable debug to get an early gui console ? (qvm-prefs win10 debug true)

[edit- typo - with QWT -> without QWT]

@Simon-Davies

This comment has been minimized.

Copy link

Simon-Davies commented Oct 1, 2018

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.

/var/log/qubes/qrexec.Windows-10.log

domain dead
cannot connect to qrexec agent: No such process

@taradiddles

This comment has been minimized.

Copy link

taradiddles commented Oct 1, 2018

I have tried enabling qvm-prefs Windows-10 debug true with a fresh VM but I still get the issue.

That's strange, with debug=true you should see a gui console of the VM - eg. the windows boot entry, windows boot logo, ..., until:

  • QWT's display driver is enabled when windows loads the system drivers: the "main" windows appears and the "debug" one goes dark or stays with the windows logo
  • or the VM crashes (the so called "blue screen of death"), which is most of the time the reason that qrexec didn't start

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)

@Simon-Davies

This comment has been minimized.

Copy link

Simon-Davies commented Oct 1, 2018

I enabled debug before installing QWT and the output above is from that.

Why file a new issue when I've already filed this one?

I have all the updates from qubes-dom0-current-testing installed.

@taradiddles

This comment has been minimized.

Copy link

taradiddles commented Oct 1, 2018

Why file a new issue when I've already filed this one?

Because it looked like you had two unrelated problems::

  1. QWT breaks an otherwise functional VM - this issue.
  2. the early gui console doesn't appear

I assumed 1. because you wrote:

Steps to reproduce the behavior:
Create a Windows 10 StandaloneVM. Update the VM and install Qubes Windows Tools.

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.

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.

Which seemed to confirm my assumption. But you then replied:

I enabled debug before installing QWT and the output above is from that.

So, did you mange to have a functional VM without QWT installed ?

Anyway, what do /var/log/xen/console/guest-Windows-10.log and /var/log/xen/console/guest-Windows-10-dm.log show ?

@Simon-Davies

This comment has been minimized.

Copy link

Simon-Davies commented Oct 1, 2018

Before installing QWT the VM is functional.

I can't check the logs now as I'm seeing if increasing the timeout to 600 instead of 300 helps aswell as setting debug to true.

If it does the same again with no GUI I'll edit this comment and post the logs.

@Simon-Davies

This comment has been minimized.

Copy link

Simon-Davies commented Oct 1, 2018

After Installing QWT again on a new Windows 10 Pro N for Workstations StandaloneVM.

unnamed

unnamed2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment