Skip to content
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

ERROR: Timeout while waiting for QEMU to boot the machine! #533

Open
1 task done
crookedmosquito opened this issue May 22, 2024 · 17 comments
Open
1 task done

ERROR: Timeout while waiting for QEMU to boot the machine! #533

crookedmosquito opened this issue May 22, 2024 · 17 comments

Comments

@crookedmosquito
Copy link

Is there no existing issue for this?

  • I have searched the existing issues

Machine specifications

Unraid docker

Operating system

Linux 171869390d55 6.1.64-Unraid #1 SMP PREEMPT_DYNAMIC Wed Nov 29 12:48:16 PST 2023 x86_64 GNU/Linux

Docker version

Docker version 20.10.24, build 297e128

Description

Trying to get this to work on an unraid server, running on a 730xd

Docker compose

this is done in a docker container from unraid

Docker log

❯ ERROR: Timeout while waiting for QEMU to boot the machine!
❯ Extracting Windows 10 image...
❯ Adding win10x64.xml for automatic installation...
❯ Building Windows 10 image...
❯ Booting Windows...

Screenshots (optional)

No response

@kroese
Copy link
Contributor

kroese commented May 22, 2024

There is a unRaid community app called "WindowsinDocker". Are you using that one?

@crookedmosquito
Copy link
Author

Yessir. That is the one I am using. When i first added it, it I got output on the VNC port showing it was downloading. when it finished downloading i got a "Display output is not active" on the VNC port and then in the Docker Logs I showed what I pasted in the initial ticket. I have tried windows 10 and windows 11 both same issue.

@kroese
Copy link
Contributor

kroese commented May 22, 2024

I have seen this same issue before with someone who was using a Intel Xeon (server-grade) CPU. And he happened to have multiple CPU's (not cores) in that system.

Is that also the case for you? Can you add a container variable with the key: BOOT_MODE and the value windows_secure in that case?

@crookedmosquito
Copy link
Author

Got an error on first boot so removed container and adding it back, will update shortly.

@crookedmosquito
Copy link
Author

getting this attaching picture

image

@kroese
Copy link
Contributor

kroese commented May 22, 2024

Can you try with a clean /storage folder? Because maybe there was a leftover from the previous attempts were it freezed.

@crookedmosquito
Copy link
Author

That may have done it. Thanks for the assist.

@kroese
Copy link
Contributor

kroese commented May 22, 2024

But can you tell me if your motherboard has multiple cpu's/sockets. Because if so, then I will enable windows_secure automatically for people with multiple sockets in the next version to prevent this bug.

@crookedmosquito
Copy link
Author

So I do have multiple cpu sockets on my system. I am seeing another issue now. It went through the install and then I got nothing on the VNC window, won't connect. Getting this in the log:

BdsDxe: loading Boot0003 "Windows Boot Manager" from HD(1,GPT,B4E11B75-E8BE-4394-98F5-FAA4FFD01B54,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
BdsDxe: starting Boot0003 "Windows Boot Manager" from HD(1,GPT,B4E11B75-E8BE-4394-98F5-FAA4FFD01B54,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
❯ Windows started succesfully, visit http://localhost:8006/ to view the screen...
❯ Shutdown completed!

I attempt to restart it, it tries to start up and then immediately shuts down

@kroese
Copy link
Contributor

kroese commented May 22, 2024

Can I see the full log, not only this part?

@crookedmosquito
Copy link
Author

crookedmosquito commented May 22, 2024

if I run (docker run container-name)

root@pdlstorage01:~# docker logs WindowsinDocker
❯ Starting Windows for Docker v3.10...
❯ For support visit https://github.com/dockur/windows
❯ CPU: Intel Xeon CPU E5 2698 v4 | RAM: 468/504 GB | DISK: 512 GB (btrfs) | HOST: 6.1.64-Unraid...

❯ Requesting Windows 10 from Microsoft server...
❯ ERROR: Microsoft blocked the automated download request based on your IP address.
❯ Failed to download Windows 10, will try a diferent method now...
❯ Downloading product information from Microsoft server...
❯ Downloading Windows 10...

 0K ........ ........ ........ ........  0% 67.5M 58s

32768K ........ ........ ........ ........ 1% 72.2M 56s
65536K ........ ........ ........ ........ 2% 74.7M 54s
98304K ........ ........ ........ ........ 3% 56.5M 57s
131072K ........ ........ ........ ........ 4% 36.8M 66s
163840K ........ ........ ........ ........ 4% 40.7M 70s
196608K ........ ........ ........ ........ 5% 42.5M 72s
229376K ........ ........ ........ ........ 6% 35.6M 76s
262144K ........ ........ ........ ........ 7% 2.36M 4m0s
294912K ........ ........ ........ ........ 8% 28.1M 3m47s
327680K ........ ........ ........ ........ 8% 29.5M 3m36s
360448K ........ ........ ........ ........ 9% 27.7M 3m27s
393216K ........ ........ ........ ........ 10% 25.9M 3m20s
425984K ........ ........ ........ ........ 11% 31.7M 3m12s
458752K ........ ........ ........ ........ 12% 36.5M 3m4s
491520K ........ ........ ........ ........ 12% 32.9M 2m57s
524288K ........ ........ ........ ........ 13% 34.2M 2m51s
557056K ........ ........ ........ ........ 14% 39.1M 2m45s
589824K ........ ........ ........ ........ 15% 42.0M 2m39s
622592K ........ ........ ........ ........ 16% 35.5M 2m34s
655360K ........ ........ ........ ........ 16% 27.7M 2m31s
688128K ........ ........ ........ ........ 17% 31.1M 2m28s
720896K ........ ........ ........ ........ 18% 28.6M 2m25s
753664K ........ ........ ........ ........ 19% 33.3M 2m22s
786432K ........ ........ ........ ........ 20% 39.0M 2m18s
819200K ........ ........ ........ ........ 20% 33.8M 2m15s
851968K ........ ........ ........ ........ 21% 34.1M 2m12s
884736K ........ ........ ........ ........ 22% 35.5M 2m9s
917504K ........ ........ ........ ........ 23% 34.6M 2m6s
950272K ........ ........ ........ ........ 24% 37.2M 2m3s
983040K ........ ........ ........ ........ 24% 36.1M 2m1s
1015808K ........ ........ ........ ........ 25% 28.4M 1m59s
1048576K ........ ........ ........ ........ 26% 40.3M 1m56s
1081344K ........ ........ ........ ........ 27% 27.3M 1m55s
1114112K ........ ........ ........ ........ 28% 3.69M 2m12s
1146880K ........ ........ ........ ........ 29% 33.0M 2m10s
1179648K ........ ........ ........ ........ 29% 24.1M 2m8s
1212416K ........ ........ ........ ........ 30% 22.9M 2m6s
1245184K ........ ........ ........ ........ 31% 28.9M 2m4s
1277952K ........ ........ ........ ........ 32% 33.6M 2m1s
1310720K ........ ........ ........ ........ 33% 38.6M 1m59s
1343488K ........ ........ ........ ........ 33% 42.0M 1m56s
1376256K ........ ........ ........ ........ 34% 45.6M 1m53s
1409024K ........ ........ ........ ........ 35% 34.8M 1m51s
1441792K ........ ........ ........ ........ 36% 35.4M 1m49s
1474560K ........ ........ ........ ........ 37% 44.4M 1m46s
1507328K ........ ........ ........ ........ 37% 33.2M 1m44s
1540096K ........ ........ ........ ........ 38% 35.4M 1m42s
1572864K ........ ........ ........ ........ 39% 33.2M 1m40s
1605632K ........ ........ ........ ........ 40% 34.2M 98s
1638400K ........ ........ ........ ........ 41% 39.0M 96s
1671168K ........ ........ ........ ........ 41% 42.0M 94s
1703936K ........ ........ ........ ........ 42% 41.3M 92s
1736704K ........ ........ ........ ........ 43% 45.1M 90s
1769472K ........ ........ ........ ........ 44% 31.2M 88s
1802240K ........ ........ ........ ........ 45% 32.5M 87s
1835008K ........ ........ ........ ........ 45% 32.2M 85s
1867776K ........ ........ ........ ........ 46% 38.9M 83s
1900544K ........ ........ ........ ........ 47% 44.0M 82s
1933312K ........ ........ ........ ........ 48% 43.9M 80s
1966080K ........ ........ ........ ........ 49% 36.2M 78s
1998848K ........ ........ ........ ........ 49% 39.3M 77s
2031616K ........ ........ ........ ........ 50% 44.8M 75s
2064384K ........ ........ ........ ........ 51% 45.2M 73s
2097152K ........ ........ ........ ........ 52% 37.4M 72s
2129920K ........ ........ ........ ........ 53% 3.09M 78s
2162688K ........ ........ ........ ........ 53% 26.2M 77s
2195456K ........ ........ ........ ........ 54% 29.0M 75s
2228224K ........ ........ ........ ........ 55% 26.9M 74s
2260992K ........ ........ ........ ........ 56% 31.2M 72s
2293760K ........ ........ ........ ........ 57% 34.7M 71s
2326528K ........ ........ ........ ........ 58% 30.0M 69s
2359296K ........ ........ ........ ........ 58% 32.8M 68s
2392064K ........ ........ ........ ........ 59% 39.9M 66s
2424832K ........ ........ ........ ........ 60% 39.2M 64s
2457600K ........ ........ ........ ........ 61% 42.5M 63s
2490368K ........ ........ ........ ........ 62% 41.0M 61s
2523136K ........ ........ ........ ........ 62% 36.6M 59s
2555904K ........ ........ ........ ........ 63% 30.7M 58s
2588672K ........ ........ ........ ........ 64% 34.6M 57s
2621440K ........ ........ ........ ........ 65% 27.7M 55s
2654208K ........ ........ ........ ........ 66% 32.6M 54s
2686976K ........ ........ ........ ........ 66% 31.7M 52s
2719744K ........ ........ ........ ........ 67% 31.3M 51s
2752512K ........ ........ ........ ........ 68% 35.1M 49s
2785280K ........ ........ ........ ........ 69% 37.5M 48s
2818048K ........ ........ ........ ........ 70% 44.1M 47s
2850816K ........ ........ ........ ........ 70% 29.6M 45s
2883584K ........ ........ ........ ........ 71% 21.0M 44s
2916352K ........ ........ ........ ........ 72% 27.7M 43s
2949120K ........ ........ ........ ........ 73% 32.4M 41s
2981888K ........ ........ ........ ........ 74% 3.18M 43s
BdsDxe: loading Boot0003 "Windows Boot Manager" from HD(1,GPT,B4E11B75-E8BE-4394-98F5-FAA4FFD01B54,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
BdsDxe: starting Boot0003 "Windows Boot Manager" from HD(1,GPT,B4E11B75-E8BE-4394-98F5-FAA4FFD01B54,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
❯ Windows started succesfully, visit http://localhost:8006/ to view the screen...
❯ Shutdown completed!

@kroese
Copy link
Contributor

kroese commented May 23, 2024

@crookedmosquito I know that many people have issues running this container on the BTRFS filesystem on Unraid.

Do you happen to have any other partitions (EXT4, ZFS, XFS, etc.) that you can mount /storage on? For example /mnt/cache? Because I have a suspicion that it could be related to BTRFS.

@crookedmosquito
Copy link
Author

Sorryit took me a minute to get back with you on this. I do have a couple of spare nvme's that are on the unassigned devices section. Let me format one to xfs and mount it. I will go ahead and do a re-install after and see what happens.

@crookedmosquito
Copy link
Author

@crookedmosquito I know that many people have issues running this container on the BTRFS filesystem on Unraid.

Do you happen to have any other partitions (EXT4, ZFS, XFS, etc.) that you can mount /storage on? For example /mnt/cache? Because I have a suspicion that it could be related to BTRFS.

That did work. I booted it off a newly formatted device using xfs instead of btrfs. Great call out on this. I am at the screen that starts off "Hi", so think i am good.

@crookedmosquito
Copy link
Author

booted
image

@kroese
Copy link
Contributor

kroese commented May 23, 2024

I just created a BTRFS partition on Ubuntu 24.04, and I could not reproduce this problem.

So it seems to only appear when using Unraid, maybe because of their RAID config or other specific settings that are different from Ubuntu. I added a warning now to the code, so that Unraid users who have BTRFS get notified about the issue.

But if someone reading this has some spare time and would like to help debugging this, please try if starting the container with:

environment:
  DISK_IO: "threads"
  DISK_CACHE: "writeback"

makes any difference. If it does not, remove those variables and try if setting:

environment:
  DISK_FMT: "qcow2"

or

environment:
  ALLOCATE: "Y"

or

environment:
  DISK_TYPE: "IDE"

makes any difference.

@francedot
Copy link

I just created a BTRFS partition on Ubuntu 24.04, and I could not reproduce this problem.

So it seems to only appear when using Unraid, maybe because of their RAID config or other specific settings that are different from Ubuntu. I added a warning now to the code, so that Unraid users who have BTRFS get notified about the issue.

But if someone reading this has some spare time and would like to help debugging this, please try if starting the container with:

environment:
  DISK_IO: "threads"
  DISK_CACHE: "writeback"

makes any difference. If it does not, remove those variables and try if setting:

environment:
  DISK_FMT: "qcow2"

or

environment:
  ALLOCATE: "Y"

or

environment:
  DISK_TYPE: "IDE"

makes any difference.

None of these options does the job unfortunately.. Running on Docker WSL 2 on Windows on an Azure VM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants