This error wasn't descrided: Image format was not specified for 'QEMU_EFI.img'/'QEMU_VARS.img'/'woa_17134.img' and probing guessed raw.....

Question

This error wasn't descrided: Image format was not specified for 'QEMU_EFI.img'/'QEMU_VARS.img'/'woa_17134.img' and probing guessed raw.....

Max-RM opened this issue 3 months ago · comments

C:\Users\Max\Desktop\M\WinARM\vm>arm.bat
WARNING: Image format was not specified for 'QEMU_EFI.img' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
WARNING: Image format was not specified for 'QEMU_VARS.img' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
WARNING: Image format was not specified for 'woa_17134.img' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.
C:\Program Files\qemu\qemu-system-aarch64.exe: -drive file=virtio-win-0.1.185.iso,media=cdrom,if=none,id=drivercdrom: Could not open 'virtio-win-0.1.185.iso': ╨Э╨╡ ╤Г╨┤╨░╨╡╤В╤Б╤П ╨╜╨░╨╣╤В╨╕ ╤Г╨║╨░╨╖╨░╨╜╨╜╤Л╨╣ ╤Д╨░╨╣╨╗.

The repository does not tell how to solve such a problem

Max-RM · Answer 1 · Tue Apr 16 2024 18:31:53 GMT+0800 (China Standard Time)

ChatGPT helped with this:

Now code in bat is:

@echo off
title WOA
"C:\Program Files\qemu\qemu-system-aarch64.exe" ^
-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 ^
-drive file="QEMU_VARS.img",format=raw ^
-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.240.iso",media=cdrom,if=none,id=drivercdrom

But next problem in console is:

I waited 10 minutes for it to start, but nothing literally changed. I even gave the highest priority through the task manager.

(qemu:12776): Gtk-WARNING **: Could not load a pixbuf from /org/gtk/libgtk/theme/Adwaita/assets/bullet-symbolic.svg.
This may indicate that pixbuf loaders or the mime database could not be found.

After installing "gtk3-runtime-3.24.31-2022-01-04-ts-win64.exe" nothing happens in cmd but nothing appears on the screen:

Sergey · Answer 2 · Tue Apr 16 2024 21:01:25 GMT+0800 (China Standard Time)

-drive file="QEMU_EFI.img",format=raw ^
-drive file="QEMU_VARS.img",format=raw ^

This is not correct. Should be:

-pflash QEMU_EFI.img ^
-pflash QEMU_VARS.img ^

You can ignore these warnings:

WARNING: Image format was not specified for 'QEMU_EFI.img' and probing guessed raw.

EFI shell appears in a few seconds, you don't have to wait 10 minutes.

╨Э╨╡ ╤Г╨┤╨░╨╡╤В╤Б╤П ╨╜╨░╨╣╤В╨╕ ╤Г╨║╨░╨╖╨░╨╜╨╜╤Л╨╣ ╤Д╨░╨╣╨╗

Это всего лишь говорит о том, что файл virtio-win-0.1.185.iso не найден :-)
Вижу, что вы исправили.

Но работать эта виртуалка будет безумно неторопливо даже на хорошем железе.
Надо запастись терпением.

gvl610 · Answer 3 · Tue Apr 16 2024 22:21:51 GMT+0800 (China Standard Time)

Hello. -pflash should be the correct option.

Max-RM · Answer 4 · Wed Apr 17 2024 17:48:35 GMT+0800 (China Standard Time)

-drive file="QEMU_EFI.img",format=raw ^
-drive file="QEMU_VARS.img",format=raw ^

This is not correct. Should be:
-pflash QEMU_EFI.img ^
-pflash QEMU_VARS.img ^
You can ignore these warnings:
WARNING: Image format was not specified for 'QEMU_EFI.img' and probing guessed raw.
EFI shell appears in a few seconds, you don't have to wait 10 minutes.
╨Э╨╡ ╤Г╨┤╨░╨╡╤В╤Б╤П ╨╜╨░╨╣╤В╨╕ ╤Г╨║╨░╨╖╨░╨╜╨╜╤Л╨╣ ╤Д╨░╨╣╨╗
Это всего лишь говорит о том, что файл virtio-win-0.1.185.iso не найден :-) Вижу, что вы исправили.

Но работать эта виртуалка будет безумно неторопливо даже на хорошем железе. Надо запастись терпением.

Max-RM · Answer 5 · Wed Apr 17 2024 17:48:44 GMT+0800 (China Standard Time)

Hello. -pflash should be the correct option.

Doesnt work

Max-RM · Answer 6 · Wed Apr 17 2024 17:51:42 GMT+0800 (China Standard Time)

oh wait. I was should use:
-pflash QEMU_EFI.img ^
-pflash QEMU_VARS.img ^

Instread of:
-pflash file="QEMU_EFI.img",format=raw ^
-pflash file="QEMU_VARS.img",format=raw ^

Max-RM · Answer 7 · Wed Apr 17 2024 17:56:44 GMT+0800 (China Standard Time)

here was BSOD related wit drivers then I disabled driver signature checking.
And then got this BSOD:

then this screen appear but now without UEFI shell. Now just infinite load:

Max-RM · Answer 8 · Wed Apr 17 2024 18:20:02 GMT+0800 (China Standard Time)

I cant disable driver signature because OS will reboot into another BSOD and then OS will forgot that Driver sig was disabled

Stop code: ACPI BIOS ERROR

Max-RM · Answer 9 · Thu Apr 18 2024 02:48:25 GMT+0800 (China Standard Time)

@raspiduino @zenden2k

gvl610 · Answer 10 · Thu Apr 18 2024 09:38:35 GMT+0800 (China Standard Time)

@raspiduino @zenden2k

Try -M virt-2.12. Also, this repo is outdated, please refer to readme.md for more info

Max-RM · Answer 11 · Thu Apr 18 2024 15:06:01 GMT+0800 (China Standard Time)

@raspiduino @zenden2k

Try -M virt-2.12. Also, this repo is outdated, please refer to readme.md for more info

MANY THANKSFOR YOU!

I will leave my bat code here for everyone who will got same error:

@echo off
title WOA
"C:\Program Files\qemu\qemu-system-aarch64.exe" ^
-name "Windows 10 on ARM64" ^
-M virt-2.12 ^
-cpu cortex-a72 ^
-smp 3 ^
--accel tcg,thread=multi ^
-m 3072 ^
-pflash QEMU_EFI.img ^
-pflash QEMU_VARS.img ^
-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.240.iso",media=cdrom,if=none,id=drivercdrom

gvl610 · Answer 12 · Thu Apr 18 2024 15:23:28 GMT+0800 (China Standard Time)

@raspiduino @zenden2k

Try -M virt-2.12. Also, this repo is outdated, please refer to readme.md for more info

MANY THANKSFOR YOU!

I will leave my bat code here for everyone who will got same error:

@echo off title WOA "C:\Program Files\qemu\qemu-system-aarch64.exe" ^ -name "Windows 10 on ARM64" ^ -M virt-2.12 ^ -cpu cortex-a72 ^ -smp 3 ^ --accel tcg,thread=multi ^ -m 3072 ^ -pflash QEMU_EFI.img ^ -pflash QEMU_VARS.img ^ -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.240.iso",media=cdrom,if=none,id=drivercdrom

Glad it works for you. I just randomly remembered the flag and didn't expect it to work but yeah, it works.

Max-RM · Answer 13 · Thu Apr 18 2024 15:33:07 GMT+0800 (China Standard Time)

Glad it works for you. I just randomly remembered the flag and didn't expect it to work but yeah, it works.

Btw why keyboard doesnt work correctly?

gvl610 · Answer 14 · Thu Apr 18 2024 15:35:00 GMT+0800 (China Standard Time)

Btw why keyboard doesnt work correctly?

Wdym?

Max-RM · Answer 15 · Thu Apr 18 2024 15:37:24 GMT+0800 (China Standard Time)

Btw why keyboard doesnt work correctly?

Wdym?

When I pressed buttons, nothing happen in WinARM

Max-RM · Answer 16 · Thu Apr 18 2024 15:38:22 GMT+0800 (China Standard Time)

Also need to search how to make shared folder

gvl610 · Answer 17 · Thu Apr 18 2024 15:40:17 GMT+0800 (China Standard Time)

Btw why keyboard doesnt work correctly?

Wdym?

When I pressed buttons, nothing happen in WinARM

IDK, it worked the last time I tested it (several years ago)

Max-RM · Answer 18 · Thu Apr 18 2024 15:41:55 GMT+0800 (China Standard Time)

IDK, it worked the last time I tested it (several years ago)

It worked now. Idk why didnt work before

gvl610 · Answer 19 · Thu Apr 18 2024 15:43:26 GMT+0800 (China Standard Time)

IDK, it worked the last time I tested it (several years ago)

It worked now. Idk why didnt work before

Bruh, instead of logging your tries here in realtime, you can try yourself and then comment later.

Max-RM · Answer 20 · Thu Apr 18 2024 15:45:53 GMT+0800 (China Standard Time)

IDK, it worked the last time I tested it (several years ago)

It worked now. Idk why didnt work before

Bruh, instead of logging your tries here in realtime, you can try yourself and then comment later.

ok

Max-RM · Answer 21 · Fri Apr 19 2024 19:17:09 GMT+0800 (China Standard Time)

IDK, it worked the last time I tested it (several years ago)

It worked now. Idk why didnt work before

Bruh, instead of logging your tries here in realtime, you can try yourself and then comment later.

Do you have pre-installed .iso with working PowerShell? Because in this iso, which is provided in this repository, PowerShell does not work (all 4 PowerShell doesnt work).

gvl610 · Answer 22 · Sat Apr 20 2024 00:33:19 GMT+0800 (China Standard Time)

IDK, it worked the last time I tested it (several years ago)

It worked now. Idk why didnt work before

Bruh, instead of logging your tries here in realtime, you can try yourself and then comment later.

Do you have pre-installed .iso with working PowerShell? Because in this iso, which is provided in this repository, PowerShell does not work (all 4 PowerShell doesnt work).

I don't think so. But you can try install on your own, there is a link to a gist in the readme. You may have better luck trying that.