Giters

raspiduino / waq

Run Windows 10 for ARM64 on QEMU

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Wheire is "startup.nsh"?

kunisuzaki opened this issue · comments

commented

Dear,

I run the following commd on Ubuntu 2204 amd64 and met the message.

qemu-system-aarch64 -name "Windows 10 on ARM64" -M virt -cpu cortex-a72 -smp 3 --accel tcg,thread=multi -m 2048 -drive file="QEMU_EFI.img",format=raw,if=pflash -drive file="QEMU_VARS.img",format=raw,if=pflash -device VGA -device nec-usb-xhci -device usb-kbd -device usb-mouse -device usb-storage,drive=boot -drive if=none,id=boot,file="woa_17134.img",format=raw -device usb-storage,drive=drivercdrom -drive file="virtio-win-0.1.185.iso",media=cdrom,if=none,id=drivercdrom

Wheire is "startup.nsh"?
should I change the *.img fies?
image

commented

You don't need that file. Type exit, then you should get to a menu. Select Boot Device or thing like that, then select your boot drive.

commented

Thank you for your reply. It was very useful.
I could go to the BIOS mode and change the boot device as shown the following photo.
image_1

However, I could not boot normal Win10. It went to the following. I could not contine normally and go to torubleshoot.
image

Fortunately, I could run command prompt mode.

image

Could you help me to boot normal Win10 on QEMU?

commented

WHAT? You gave it 2048 MB of RAM and it still says Not enough memory resources are available to process this command???

commented

I changed the memory size 4096 MB, but the message was same.

qemu-system-aarch64 -name "Windows 10 on ARM64" -M virt -cpu cortex-a72 -smp 3 --accel tcg,thread=multi -m 4096 -drive file="QEMU_EFI.img",format=raw,if=pflash -drive file="QEMU_VARS.img",format=raw,if=pflash -device VGA -device nec-usb-xhci -device usb-kbd -device usb-mouse -device usb-storage,drive=boot -drive if=none,id=boot,file="woa_17134.img",format=raw -device usb-storage,drive=drivercdrom -drive file="virtio-win-0.1.185.iso",media=cdrom,if=none,id=drivercdrom

The QEMU setting is as follows.

$ qemu-system-aarch64 -version
QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.21)
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers

The same messge was found on QEMU on Rasberry Pi 4. Why?

commented

Hmm, maybe you should try -M virt-2.11?

commented

Thank you for your suggestion. However, the situation has not changed.

I noticed an interesting issue: the QEMU BIOS shows "0 MB RAM". Could this be causing a problem?

image

commented

Hi, maybe try newer EDK2 firmware at https://retrage.github.io/edk2-nightly/ ?

commented

I tried to use "RELEASEAARCH64_QEMU_EFI.fd" in https://retrage.github.io/edk2-nightly/

 dd if=/dev/zero bs=1M count=64 of=flash0.img
 dd if=RELEASEAARCH64_QEMU_EFI.fd bs=1M of=flash0.img conv=notrunc

And I replaced QEMU_EFI.img with the "flash0.img"

qemu-system-aarch64 -name "Windows 10 on ARM64" -M virt-2.11 -cpu cortex-a72 -smp 3 --accel tcg,thread=multi -m 2048 -drive file="flash0.img",format=raw,if=pflash -drive file="QEMU_VARS.img",format=raw,if=pflash -device VGA -device nec-usb-xhci -device usb-kbd -device usb-mouse -device usb-storage,drive=boot -drive if=none,id=boot,file="woa_17134.img",format=raw -device usb-storage,drive=drivercdrom -drive file="virtio-win-0.1.185.iso",media=cdrom,if=none,id=drivercdrom

The QEMU tells "Guest has not initialized the dispay (yet).
image

commented

-device VGA

Replace this with -device ramfb

commented

Thank you for your quick response.
However, the sitiation is same.
The QEMU tells "Guest has not initialized the dispay (yet)."