You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So for a little background, because of the way QEMU handles VHDX files, it has a tendency to corrupt them, causing errors. For me the two that I have experienced (on Windows 10) is a process initialization BSOD and an error with the sign-in service, but the corruption can cause many others. This is an issue because Windows 10 for ARM gets distributed in the form of a pre-made VHDX disk, and manually converting is a pain.
My request is, if you try to launch a virtual machine with a VHDX file loaded as a boot drive, UTM will display a pop-up asking if you would like to convert the VHDX to QCOW2 automatically.
The text was updated successfully, but these errors were encountered:
My feature request for UTM is simple:
So for a little background, because of the way QEMU handles VHDX files, it has a tendency to corrupt them, causing errors. For me the two that I have experienced (on Windows 10) is a process initialization BSOD and an error with the sign-in service, but the corruption can cause many others. This is an issue because Windows 10 for ARM gets distributed in the form of a pre-made VHDX disk, and manually converting is a pain.
My request is, if you try to launch a virtual machine with a VHDX file loaded as a boot drive, UTM will display a pop-up asking if you would like to convert the VHDX to QCOW2 automatically.
The text was updated successfully, but these errors were encountered: