Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

UTM M1 crash - Windows 10 #3701

Closed
AlessandroCordella opened this issue Feb 28, 2022 · 5 comments
Closed

UTM M1 crash - Windows 10 #3701

AlessandroCordella opened this issue Feb 28, 2022 · 5 comments

Comments

@AlessandroCordella
Copy link

Last April I downloaded the Windows 10 Arm VHDX file (it seems not available anymore, only Windows 11 Arm VHDX). I tried running it with Parallels and it worked fine.

Now I need to create a Win10 virtual machine using UTM. I converted the VHDX file to a qcow2 file using the following qemu command:
qemu-img convert -p -O qcow2 Windows10_InsiderPreview_Client_ARM64_en-us_21354.VHDX Windows10.qcow2

Then I created a VM using UTM with the following settings:

immagine
immagine

but during the boot process I get this error INACCESSIBLE_BOOT_DEVICE:
immagine

Then, I tried to convert the VHDX file to a qcow2 file from a Windows machine using StarWind V2V Converter (the qcow2 converted file was different that the one created with qemu). I create a VM in UTM using the same configuration, but I got the same error during the boot process.

I read what is written here #2646, but I have already set the hardisk as a NVMe.

What configuration am I doing wrong? I report that I tried the same process using the Windows 11 VHDX file and the qcow2 generated using StarWind V2V Converter, and the Windows 11 machine is running correctly in UTM in my MAC M1.

@osy
Copy link
Contributor

osy commented Mar 1, 2022

Please provide the following:

**Configuration**
* UTM Version: 
* OS Version: 
* Intel or Apple Silicon? 

@AlessandroCordella
Copy link
Author

UTM 3.0.4 (46)
macOS Monterey 12.2.1
Apple Silicon

@osy
Copy link
Contributor

osy commented Mar 1, 2022

Did you use the wizard? If so you should use the VHDX directly and not a converted qcow2 since it will convert it for you.

@AlessandroCordella
Copy link
Author

AlessandroCordella commented Mar 1, 2022

I tried using the wizard and selecting directly the VHDX, but I got the same error

@osy
Copy link
Contributor

osy commented Mar 1, 2022

Oh I just realized you said “ Windows10_InsiderPreview_Client_ARM64_en-us_21354.VHDX Windows10.qcow2” that’s too old and doesn’t support M1 at all. You need 21390 or higher. I recommend using https://mac.getutm.app/gallery/windows-10

@utmapp utmapp locked and limited conversation to collaborators Mar 1, 2022
@osy osy converted this issue into discussion #3706 Mar 1, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants