windows
windows copied to clipboard
dockur
QEMU harddisk fail
windows | ❯ Extracting Windows 10 bootdisk... windows | ❯ Extracting Windows 10 environment... windows | ❯ Extracting Windows 10 setup... windows | ❯ Extracting Windows 10 image... windows | ❯ Adding XML file for automatic installation... windows | ❯ Building Windows 10 image... windows | ❯ Creating a 64G growable disk image in raw format... windows | ❯ Booting Windows using QEMU emulator version 8.2.1 ... windows | BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found windows | BdsDxe: loading Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0) windows | BdsDxe: starting Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0) windows | ❯ ERROR: Forcefully terminating Windows, reason: 0... windows | ❯ Shutdown completed!
Trying to start the container on M1, this is my YAML: version: "3" services: windows: image: dockurr/windows container_name: windows cap_add: - NET_ADMIN ports: - 8006:8006 - 3389:3389/tcp - 3389:3389/udp stop_grace_period: 2m restart: on-failure environment: VERSION: "win10"
It has nothing to do with the harddisk. QEMU quits for some reason and somehow it doesnt tell why.
But since the Apple M1 is an ARM chip you might have better luck with https://github.com/dockur/windows-arm because that one is made for ARM.
I get the same error running on linux with both Windows-arm and Windows11
@roadkingvrod Do you also have an Apple M1 cpu? Are you using MacOS or Linux? It would be helpful to have some more info.
@kroese sorry, was trying to respond between meetings. I am running on an x86 chip with Ubuntu running on a VM. I did set up the storage on an external volume (which could be the problem), so I'll try running without that before commenting more.
UPDATE: Changing to original compose without external volumes did NOT help.
Did you enable "Nested Virtualization" for the VM? Its always a bit tricky to run a VM inside a VM, so that might be the cause of this problem.
I now created a new release (v2.05) which should provide more error info in your case. Can you please try and see if it reports more info? And if not, can you try setting:
environment:
CONSOLE: "Y"
in your compose file, and see if outputs more info?