Display output is not active

[daxil34]

now work all and log in to the novnc

[kroese]

I have no idea what you mean. Please provide a more detailed description of your problem, and include the Docker log and compose file.

[daxil34]

❯ Starting Windows for Docker v2.04... ❯ For support visit https://github.com/dockur/windows ❯ Booting Windows using QEMU emulator version 8.2.1 ... KVM internal error. Suberror: 1 extra data[0]: 0x0000000000000000 extra data[1]: 0x0000000000000400 extra data[2]: 0x0000000100000014 extra data[3]: 0x00000000000a0000 extra data[4]: 0x0000000000000000 extra data[5]: 0x0000000000000000 emulation failure RAX=00000000fffd4f94 RBX=000000000081fd20 RCX=000000000081fd20 RDX=00000000fffd4f54 RSI=0000000000000000 RDI=00000000ffe01390 RBP=000000000081fca0 RSP=000000000081fb78 R8 =8000000000000003 R9 =0000000000000010 R10=0000000000000000 R11=0000000000000004 R12=00000000fffcc094 R13=00000000ffc84090 R14=00000000ffc84000 R15=000000000081fbc8 RIP=00000000000a0000 RFL=00000082 [--S----] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] CS =0038 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] DS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] FS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] GS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] LDT=0000 0000000000000000 0000ffff 00008200 DPL=0 LDT TR =0000 0000000000000000 0000ffff 00008b00 DPL=0 TSS64-busy GDT= 00000000fffffed0 0000003f IDT= 000000000081fd70 0000021f CR0=80000033 CR2=0000000000000000 CR3=0000000000800000 CR4=00000660 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000500 Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[kroese]

Never seen this KVM internal error. Suberror: 1 error before. Might be some incompatiblity between your CPU or kernel with KVM.

[fowlmanor]

win10LOG.txt I'm also having this issue but I also did just recently launch this so maybe it needs time?

Here are my logs and a screen shot of what I'm getting

3932160K ........ ........ ........ ........ 97% 109M 1s 3964928K ........ ........ ........ ........ 98% 104M 1s 3997696K ........ ........ ........ ........ 99% 103M 0s 4030464K ........ ........ ........ ........ 99% 112M 0s 4063232K ... 100% 113M=38s ❯ Extracting Windows 10 bootdisk... ❯ Extracting Windows 10 environment... ❯ Extracting Windows 10 setup... ❯ Extracting Windows 10 image... ❯ Adding XML file for automatic installation... ❯ Building Windows 10 image... ❯ Booting Windows using QEMU emulator version 8.2.1 ...

[daxil34]

at my place docker worked for a week and then it died kvm is compatible with the system and processor

[kroese]

Try with a clean container using the latest version (v2.16). Maybe it is fixed now, because I disabled a lot of features (secure boot, tpm, some hyper-v enlightments) by default now for fresh installs.

[DenisBessa]

I’m facing this issue as well. The container starts, but it freezes after some time. Moving the mouse or pressing some key in the VNC connection briefly shows this message, and then it starts again.

This started a few days ago. Before that it was working perfectly.

[DenisBessa]

Here's a few more info about my experience:

• I'm 100% sure my CPU is compatible. It was working a few days ago, and the problem seems to happen even if I use other VM.
• It was working a few days ago.
• Only teste Windows 10 Pro.
• I'm using it in an Azure Kubernetes environment.
• I think the problem might be related to Windows going to sleep, though I'm not 100% sure. I'll make some tests and report the results here.

[kroese]

@DenisBessa Do you happen to know if you upgraded to a new version of the container (for example from v2.14 to v2.16) around the time the problem started? Or did the problem appear while still using the same version of the image you had before?

[DenisBessa]

I use the container with the latest tag, so every time it restarts I have the updated version.

I've tested with the 2.16 and 2.14 versions and both of them seem to have trouble.

I have manually disabled the "sleep" timeout in Windows 10, and so far it's working (for 2 hours now). I really think it's related to Windows going to sleep.

[kroese]

@DenisBessa The automatic installation disables sleep/hibernation/screensaver. So sleep should not happen unless you did a manual installation?

[DenisBessa]

@DenisBessa The automatic installation disables sleep/hibernation/screensaver. So sleep should not happen unless you did a manual installation?

I did an installation with a custom autounattend.xml file, but everything I did was add a custom script. Didn't deactivate the other ones.

The commands used for disabling the sleep mode are the ones in lines 337 to 396 and 357 to 361, right?

Am I missing something?

[DenisBessa]

I think I just found the issue.

It seems that Windows enable the sleep mode by default.

The autounattend.xml file has 2 commands to disallow the computer into sleep mode:

        <SynchronousCommand wcm:action="add">
          <Order>5</Order>
          <CommandLine>cmd /C POWERCFG -H OFF</CommandLine>
          <Description>Disable Hibernation</Description>
        </SynchronousCommand>
        <SynchronousCommand wcm:action="add">
          <Order>6</Order>
          <CommandLine>cmd /C POWERCFG -X -monitor-timeout-ac 0</CommandLine>
          <Description>Disable monitor blanking</Description>
        </SynchronousCommand>

(lines 357 to 366)

But these 2 commands does not affect the When plugged in, PC goes to sleep after option in the settings app.

Executing cmd /C POWERCFG -X -standby-timeout-ac 0 does the trick.

[kroese]

Thanks!! I will add that command to the default XML's now, so that for all future installations it will be solved.

[51anygo]

Same issue, android 13.1, termux 0.118.0, QEMU Virtual CPU version 2 5 using QEMU v8.2.1, winxp