-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Comments
There is a unRaid community app called "WindowsinDocker". Are you using that one? |
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. |
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: |
Got an error on first boot so removed container and adding it back, will update shortly. |
Can you try with a clean |
That may have done it. Thanks for the assist. |
But can you tell me if your motherboard has multiple cpu's/sockets. Because if so, then I will enable |
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 I attempt to restart it, it tries to start up and then immediately shuts down |
Can I see the full log, not only this part? |
if I run (docker run container-name) root@pdlstorage01:~# docker logs WindowsinDocker ❯ Requesting Windows 10 from Microsoft server...
32768K ........ ........ ........ ........ 1% 72.2M 56s |
@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 |
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. |
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. |
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. |
Is there no existing issue for this?
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
The text was updated successfully, but these errors were encountered: