-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Comments
Please provide the following:
|
UTM 3.0.4 (46) |
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. |
I tried using the wizard and selecting directly the VHDX, but I got the same error |
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 |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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:
but during the boot process I get this error INACCESSIBLE_BOOT_DEVICE:
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.
The text was updated successfully, but these errors were encountered: