Hello i installed vmware fusion and download windows for arm but the vmware doesn't see the vhdx extention file which is windows 10 for arm. Does it have support for windows for arm? Thanks
Can you tell me the way to convert vhdx to vmdk with emu-img?
I entered ↓
qemu-img convert -o vmdk Windows11_InsiderPreview_Client_ARM64_en-us__22454.VHDX win11.vmdk
And it is not working😭
You already installed home-brew and QEMU?
Instruction:
yes I installed home brew and qemu
the terminal says
Could not open 'Windows11_InsiderPreview_Client_ARM64_en-us__22454.VHDX': No such file or directory
And I have my windows VHDX file in download folder
Did I entered wrong command? or do I have to move my VHDX file to another folder?
When you open terminal first you should go to download folder. Enter command cd /Users/username/Downloads. And then command to convert.
I imported the Parallels VM to VMware Fusion 12.1.2 and then created an "Other 64-bit Arm" custom VM with the Tech Preview using the virtual disk from 12.1.2. It doesn't work going straight from Parallels to Tech Preview.
qemu-img convert -f vhdx -O vmdk Windows11_InsiderPreview_Client_ARM64_en-us__22454.vdhx Windows11_Fusion.vmdk
This worked for me
qemu-img convert -f vhdx -O vmdk Windows11_InsiderPreview_Client_ARM64_en-us__22454.vdhx Windows11_Fusion.vmdk
Working as expected. The resolution in the VM “console” does not change when you change the resolution in the RDP session. You don’t work in that console session (note the console session is locked) if you are accessing via RDP session.
Ahh ok. I haven't had a chance to try it yet.
Question, can you loop back RDP inside the guest? From/to itself? Right now I'm keeping win 11 off the network.
@ColoradoMarmot wrote:Ahh ok. I haven't had a chance to try it yet.
Question, can you loop back RDP inside the guest? From/to itself? Right now I'm keeping win 11 off the network.
Sorry but no. An attempt to do so is met with the following:
Which kind of makes sense if you think about it because RDP on Windows Home/Pro closes the console session to the remote computer when you connect to it...
Windows 10 (and maybe it carries over to 11) is limited by Microsoft licensing to 1 user working on the computer from what my research is telling me. If you want multiple sessions to a system, Microsoft is encouraging you to purchase Windows Server (of which there is no ARM architecture version at the present time) if you want to do this.
There appear to be hacks for Windows 10 x86)_64 to override the default behavior and allow multiple sessions to connect to a Windows 10 system. However I doubt that it works in Windows 11 for ARM, and even trying to do this in "loop back" still won't let you change the resolution of the console session so that's not going to help you.
@Technogeezer wrote:Working as expected. The resolution in the VM “console” does not change when you change the resolution in the RDP session. You don’t work in that console session (note the console session is locked) if you are accessing via RDP session.
Also, note that you change the resolution of the RDP session by resizing the window on the Mac. You can't resize the screen from within the session via Settings / Display. Here's what you'd see:
.
You could even start the RDP session in full screen mode.
For me, only screen res in RDP changing to native, i have checked two boxes, resize and optimise for retina displays, vm screen stays on 1024x768 and logged out, so i need to work on Windows by RDP?
Yes you will need to work from the RDP session in order to use the expanded screen real estate.
Like I said, it’s a workaround if you need a bigger screen on your VM. What you are seeing is standard Windows behavior when using an RDP to the console session.
I managed to install Windows 10 ARM, but i cant get any networking to work and the installation could not connect to shared network. Alsi tried birdged but still didnt work.
https://www.youtube.com/watch?v=KsNoGPczavw we cant install those drivers like utm to get full resolution? talking about virtio drivers
Read the thread - there's tips on how to get networking working.
UTM in the demo is running the x86-64 image and emulating and thus those drivers are for x86-64 not ARM. UTM claims to also run Windows 10 ARM though.
so sadly for now only way to got full resolution is by using remote desktop?