windows icon indicating copy to clipboard operation
windows copied to clipboard

Windows stuck at installer starting

Open youcannotseemeagain opened this issue 11 months ago • 3 comments

I've tried Microsoft iso and custom iso but both get stuck here.

Snipaste_2024-

I've waited for several hours and it's still like this.

yml file

version: "3"
services:
  windows:
    image: dockurr/windows:latest
    container_name: windows
    devices:
      - /dev/kvm
    cap_add:
      - NET_ADMIN
    ports:
      - 8006:8006
      - 3389:3389/tcp
      - 3389:3389/udp
      - 48080:8080
      - 48000:80
      - 44443:443
    stop_grace_period: 2m
    restart: on-failure
    environment:
      MANUAL: "N"
      VERSION: "2008"
      RAM_SIZE: "8G"
      CPU_CORES: "4"
      DISK_SIZE: "500G"
    volumes:
      - /home/win:/storage

youcannotseemeagain avatar Feb 28 '24 08:02 youcannotseemeagain

Do you only have this with Server 2008 or also with other versions?

kroese avatar Feb 28 '24 08:02 kroese

Do you only have this with Server 2008 or also with other versions?

I tried win10 and the same problem occurred.

youcannotseemeagain avatar Feb 28 '24 08:02 youcannotseemeagain

same problem

ggdd2008 avatar Feb 28 '24 09:02 ggdd2008

Maybe both of you can share some info about your system, so we can see if you have something in common. For example the same CPU, or the same OS, or certain kernel.

Because it would be a lot easier to find a solution as soon as we know under what circumstances it occurs.

kroese avatar Feb 29 '24 01:02 kroese

Maybe both of you can share some info about your system, so we can see if you have something in common. For example the same CPU, or the same OS, or certain kernel.

Because it would be a lot easier to find a solution as soon as we know under what circumstances it occurs.

CPU: Intel(R) Xeon(R) CPU E5-2630 v2 OS: CentOS 7.5.1804 Kernel: 3.10.0-862.el7.x86_64 Docker: 23.0.6

I appreciate it.

youcannotseemeagain avatar Feb 29 '24 02:02 youcannotseemeagain

My guess is that it has something to do with that Xeon CPU. Because the last time someone had strange failure during install was also with a Xeon CPU E5-2680 v4

It might be some CPU instruction that is missing (as that CPU was released 10 years ago) or some obscure bug in QEMU/KVM.

Things to try:

Disable emulation for the TPM module:

environment:
  TPM: "N"

Disable Hyper-V enlightments:

environment:
  HV: "N"

You can even disable KVM completely:

environment:
  KVM: "N"

(Expect very low performance, but at least we know if it makes a difference or not)

kroese avatar Feb 29 '24 02:02 kroese

CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz OS: CentOS 7.5.1804 Kernel: 3.10.0-862.el7.x86_64 Docker: 25.0.3

ggdd2008 avatar Feb 29 '24 02:02 ggdd2008

Okay, you both have CentOS 7.5.1804 and exactly the same kernel. That is a pretty big co-incidence, so then I think its not the CPU but something related to this version of CentOS.

However, its extremely difficult to figure out why QEMU does not work on that CentOS kernel. So my only suggestion would be to check if disabling Hyper-V in the compose file helps, otherwise I dont have many suggestions anymore.

kroese avatar Feb 29 '24 03:02 kroese

I think this may be fixed now in v2.06

kroese avatar Mar 12 '24 11:03 kroese