Issue starting VM
Hi! I am following the setup instructions, and am running into a roadblock.
I seem to be missing dockerbridge, and am getting the error BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found. The process appears to die after waiting for a response 1-3 times. I waited for 30 minutes to make sure it wasn't just working in the background, but no luck.
Below are screenshots of how far I get with this command: ./run-local.sh --use-kvm false --browser-port 8000 --prepare-image true
Terminal:
Browser localhost:
Let me know if I'm missing a step.
You can ignore that log based on this comment. I don’t see any errors in the log. However, it’s important that you don’t manually exit the process; let it continue running until it exits automatically. You can use this video as a reference.
That video link is broken for me. Okay, so even if the process appears to stop (see 2nd screenshot), then I should just wait?
I removed the contents of storage/ and restarted the process, but it seems to stop quickly:
❯ Windows has started successfully. You can connect using either a web browser or RDP, both accessible at localhost on the specified ports...
BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found
BdsDxe: loading Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)
BdsDxe: starting Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)
(winarena) [beaker] piperw /data/piperw/projects/WindowsAgentArena/scripts $ channel 3: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
In this section, you’ll find the preparation walkthrough video. The error in your later attempt is different from your previous run.
I recommend restarting the Docker daemon and ensuring that no other processes are using the browser port 8000. Keep in mind that performance of the agent with use-kvm false may not be ideal. We recommend using this option only for preparing the image and then copying the storage folder image to run the benchmark on an Azure D-series VM or another system that supports nested virtualization.
I started from scratch with a new port and the installation seems to just stop (see screenshot below). The video suggests that the process stopping for me is incorrect. I do not see anything running in the background.
We're working to support KVM Acceleration in our docker containers, but for now trying to prepare the image without it. Maybe this setup is not working due to the nature of our containers.
It seems the process is being terminated halfway through the image preparation. A quick check you could try is:
- Start with a plain dockur Docker image:
docker run -it --rm -p 8006:8006 -e KVM=N --cap-add NET_ADMIN --stop-timeout 120 dockurr/windows
- Ensure that the Windows 11 VM has started successfully at port 8006.
If the issue persists, please file an issue on dockur and reference this one. We're constantly working to improve our setup, and contributions are always welcome. Thanks in advance!
./run-local.sh --prepare-image true --ram-size 4G --cpu-cores 4
Terminal
Browser
Windows installation is blocked, Please give me some advice.
I am running in WSL2 Ubuntu 24.04.1 LTS:
./run-local.sh --prepare-image true --ram-size 4G --cpu-cores 4
Terminal
Browser
Windows installation is blocked, Please give me some advice.
same issue here, get stuck on the same exact screen in windows: Install driver to show hardware
I am running in WSL2 debian: Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye
Any help would be highly appreciated!
I'm also having this issue; I've had it happen on my desktop while trying to install UEFI GPT/MBR 's conflicting with my system- happened while trying to make bootable windows iso's from linux/mac. Will have to take a further look int it.
I've got a, hopefully, working win10e version here: https://github.com/matbee-eth/WindowsAgentArena/tree/win10e-support
It does seem like the issue is related to GPT/MBR or VirtIO drivers, but I'm unable to figure out why. Probably fixable via: https://github.com/quickemu-project/quickemu/issues/927#issuecomment-2079527171
Having the same issue as well! Process gets stuck on "Install driver to show hardware"
This problem has troubled me for a long time, and it is the same when I change a server. Have you solved it?-------"Install driver to show hardware"