macOS Monterey V 12.0.1
Chip Apple M1
When I was trying to install
(1).
VMware-Fusion-e.x.p-18656771_arm64.dmg,
I got this error message
This virtual machine cannot be powered on because it requires the X86 machine architecture, which is incompatible with this Arm machine architecture host. (See KB-84273.)
(2) Next,
VMware-Fusion-12.2.1-18811640_x86
I got this error message.
This version of VMware Fusion is for Intel-based Macs, but is being run on an Apple silicon based Mac via Rosetta-2.
(See KB-84273)
Could you please anyone help me to install this in my M1 MacBook.
@jhuertaNU1996 I just downloaded UTM and installed Windows 11 ARM VM in virtualization mode. I didn't follow the instructions in the video exactly - I created a new VM and installed iWindows 11 ARM from an ISO that I'd used successfully with the Fusion Tech Preview. I did have to disable the TPM check and Secure Boot check in the installer (documented registry keys are the same as used for the Fusion TP), but otherwise it installed smoothly. If installing from an ISO, you still need to make sure you have 4GB memory, a 64GB disk and 2 cores minimum otherwise Windows still complain that you're not meeting requirements.
I downloaded the SPICE tools and installed them with no ill effects. I can resize the screen just fine, and the shared folder and networking work fine as well. (no need to hack the kernel debug NIC).
It seems to run pretty nicely. I haven't beat on it much, but so far so good. (This makes the VMware experience for Windows even more disappointing)
I still find that you can't run the Microsoft Store from the VM - this is the same issue I found with running Windows 11 on the TP.
thanks for the update Technogeezer. I also did the registry keys, as well as creating the ISO installer with Rufus to exclude the TPM and Security Boot checks. I still can't get the ISO installer to get past the TPM and Security Boot.
same problem. help, please
@jhuertaNU1996 At what point in the installer process did you drop into regedit? I've had best success when hitting shift-F10 at the very first screen where it asks you about keyboard layout. If you try it on the next screen, Setup may already be running and it's already read the registry.
Also make sure that the key you created was HKLM\System\Setup\LabConfig, and the two DWORD values are associated with that key.
I run into the issue with the TPM and Secutrity Boot checks when running the ISO from within Windows 11, to do and upgrade to a non-Eval copy. It doesn't even get to the keyboard layout screen. It does the checking for updates and then runs the compatibility check.
I had also already created the registry keys, but it doesn't seem to acknowledge them.
I had tried UTM (2.4.1) earlier. I upgraded to 3.1.5 and tried again. I already had Windows11_InsiderPreview_Client_ARM64_en-us_22499.qcow2, so I tried it. It worked almost perfect. I made no regedit changes, started with no internet per the video. I have not played with it for very long, but shared folders, cut and paste between host and VM, and video resolution changes all work. The only problem I have encountered so far is inability to pause the VM. I get same problem for W11 as reported here. I have tried other adapters (ie SCSI, IDE), but none work. Not bad, just have to reboot on each use.
I just now tried installing via the ISO installer, and it seems to have gotten past the TPM and Security Boot Check. Looks like it will be fine after all.
Give the new 22H2 Fusion Tech Preview that runs on Apple Silicon a try. It moves the needle on Windows 11 support by introducing a TPM device that allows Windows 11 ARM to install without disabling Microsoft checks. It also contains a subset of VMware Tools for video and network device drivers. Unfortunately no cut/paste/drag/drop between guest and host and shared folders - yet. (They hint about filling in the gaps in the upcoming Fusion GA release)
But it’s notable that VMware has finally decided not to let Microsoft’s vague statements on Windows 11 get in the way of delivering Windows 11 ARM support in Fusion.
We have the same issue (using a lot of VM machines based on VMware Fusion). We are now testing instead Parallels 18 on M1 and M2, and looks good so far.
@ABuss wrote:We have the same issue (using a lot of VM machines based on VMware Fusion.
There are a few issues being discussed in this thread. Can you clarify what you mean by “same issue”?
@Technogeezer, do you have a direct link to where 22H2 fusion can be downloaded?
If you're reading this message in the forum, you see the following at the top of the page:
Click on the "Fusion TP 22H2" and you then will see this page
Toward the bottom of the page, you'll see links to download both the Tech Preview and the Tech Preview Testing Guide (required reading):
You will need a VMware account to sign up (free and it'll prompt you to create one) and download the Tech Preview installer.
You should also download and read the unofficial Tips and Techniques document for the Apple Silicon 22H2 Tech Preview
I was just about to respond to say that I found exactly that way.
https://communities.vmware.com/t5/Fusion-Tech-Preview-22H2/ct-p/3022
Thanks @Technogeezer !
For me it looks like vmware is just a scam. You are advertising this product as Apple Silicon ready but it can't run x64.
Contacting support (tech and non tech) is total crap. You will be navigated to bot.
@MiKo3 wrote:
For me it looks like vmware is just a scam. You are advertising this product as Apple Silicon ready but it can't run x64.
Contacting support (tech and non tech) is total crap. You will be navigated to bot.
Not sure what you expect, exactly. The product (especially the release version, since this tech preview is now closed) IS Apple Silicon ready... it virtualizes the CPU accurately, to run any other ARM-based OS. VMware does NOT have emulation products, where you could run an x86/x86-64-based OS.
Do you expect a diesel truck to run on gasoline?
Because that's what you're asking - it's a fundamentally different "fuel". The marketing and release information is very clear as to what's supported and what's not possible.
I think the disconnect here is that the users are looking for a way forward. They understand that you can't run an Intel-based VM on an ARM M1 machine and are looking for a way around this problem, not through it.
Ideally there should be a way to transfer the data from an old VM that won't launch to a freshly-created VM that's compatible with the underlying hardware. For each guest operating system, one would have to write a tool that attaches to the old image and knows where to find the data and where to put it in the new VM. Not sure how much development work this would take but it might be worth the effort in the case of popular guest operating systems with millions of customers.
[soapbox]
Given the number of questions I’ve answered here, there are a significant number of people that do not understand that they simply can’t take their old VMs and run it on their brand new Apple Silicon Mac. The expectation is “It’s a Mac, it runs Fusion, therefore I can take my VM over to my new Mac and it should run”.
VMware could have explained the whole Apple Silicon upheaval to Fusion users in a white paper prominently promoted in their web site and documentation to make sure users knew what they were up against when they bought a new shiny M1 Mac. They didn’t and user expectations were shattered. It got left to the community to fill in the gaps.
The way forward IMO is to treat this as if you bought a new computer and had to transfer your data. Many of those techniques still work, and you also have the additional capability of attaching your old VM’s virtual disks to the new VM and copying data.
The move to Windows 11 ARM is more complicated because you have to verify that the application you want to run is available in native ARM code or runs under Windows 11 ARM’x x86_64 translator.
[end soapbox]
I always appreciate Technogeezer's obviously authoritative opinions, But for those of us are only techno-consumers, authoritative about other things but only half-savvy about what lurks under the hoods of these machines we must toil on, wouldn't it be nice if someone explained to us how to "attach your old VM’s virtual disks [whatever those are] to the new VM and copying data [ok: how?].
And also: "The move to Windows 11 ARM is more complicated because you have to verify that the application you want to run is available in native ARM code [whatever that is] or runs under Windows 11 ARM’x x86_64 translator [at the risk of repeating myself, whatever that is.]" You may snicker, but doofuses like me are still the masses whose purchases support the existence of software companies, and all we want is a new VMWare version that works on what Apple now makes. If this is Microsoft's fault and not VMWare's, tell me that. But if Parallels can do it, why can't VMWare (especially as I'd just renewed my annual subscription when this happened)? Why is VMWare ghosting its Mac customers, hiding behind all the jargon that keeps us hanging on, waiting to upgrade to the M1-ready version they sort of hint at? Me, I've been using Macs for so long that all I want is to be able to access my old WordPerfect Windows files that for years VMWare has let me read on -- ready -- Windows XP, the last version of Windows I ever needed (and I often hear, the best). That's all. Help, already.
@RDPetruska wrote:
@MiKo3 wrote:For me it looks like vmware is just a scam. You are advertising this product as Apple Silicon ready but it can't run x64.
Contacting support (tech and non tech) is total crap. You will be navigated to bot.
Not sure what you expect, exactly. The product (especially the release version, since this tech preview is now closed) IS Apple Silicon ready... it virtualizes the CPU accurately, to run any other ARM-based OS. VMware does NOT have emulation products, where you could run an x86/x86-64-based OS.
I was expecting product to be advertised in non misleading way.
Additionally support is just a joke - I was unable to find help and my mail is still not answered.
