Vmware m1 macbook professional#

That's not to condone a less than professional response though. We're human too and sometimes we let the frustration get to us. It does get frustrating as most of us do this in our spare time and it does take time to have to repost the same information or ask for clarification. We have, though, seen a rash of posts recently where it doesn't look like posters have even taken the time to read the information (even within the same thread), or post simply 'me too' types of questions with no context.

We have to recognize that and as you say, draw out information so that we can guide and educate. People who post here may or may not have the experience we have in the industry and/or with Fusion as a product. We're users just like you.įrom a personal perspective, I admit from time to time I have to watch what I say for the reasons you give. Ask more information when there clearly is hardly any info and try to push them in the right direction.įirst, most of us here do not work for VMware. So please, stop making assumptions and stop being hostile towards users. There really is no excuse for the current behaviour. Instead of the current hostility one could have simply asked to provide more information. If you and your colleagues had bothered to read the topic start then one thing should have been noticed: the lack of information.

As a result the topic starter has now gone silent. It is the only one that seems to have an actual final release that works and it works perfectly you and your fellow VMware colleagues comply with the terms of use and refrain from making these kind of toxic comments. Out of all the Linux distros I tried Fedora seems to be the best.

Vmware m1 macbook install#

Older versions don't even boot the install (it returns to grub). Regarding RHEL 9.x: I tried Rocky and Alma Linux and noticed that those only seem to be working as of RHEL 9.x.

Vmware m1 macbook software#

It also has newer versions of the software but it is a rolling release. I have seen that Fusion is not detecting it as being OpenSUSE so you can immediately select the 'Other Linux' option you'll have to because it doesn't show OpenSUSE (nor its enterprise sibling).and that could be a hint. From the Linux distros I tested thus far I found these to be one of the easiest to use with the Tech Preview. I have seen that both Leap and Tumbleweed work just fine. The Tech Preview guide does not mention OpenSUSE at all so no idea if it is officially supported or not. If you then start the vm it will boot from the dvd image and let you install OpenSUSE Leap. Instead press the 'customise settings' because we need to make it boot from the downloaded dvd image: open the cd/DVD drive settings, connect it to the vm and select the downloaded dvd image with the dropdown menu. Go through the other options but don't press the 'finish' button at the end. To solve it I created a new vm again but this time select 'create custom virtual machine' (it is below the previous mentioned disc option) and in the next step choose Linux > Other Linux 5.x kernel 64-bit ARM (the bottom option). Upon saving that vm it will start it and return the KB-84273 error message. It will set the guest operating system to OpenSUSE. When you hit next you'll get an overview of the settings it made based on the dvd image. Then I added a new vm and used the 'install from disc or image', added the downloaded dvd image.

Vmware m1 macbook full#

What I did was download the aarch64 OpenSUSE Leap 15.3 version (the full dvd iso image).

Vmware m1 macbook update#

(ok a bit dramatic but you get my drift.) Update 2 fixed it and it installed cleanly 'out of the box'ĭo you have specifics on where this message popped up for you? For example, the RHEL 9 Beta Update 1 for ARM64 required a bunch of hoops to be jumped through while reciting magic incantations to install. Some things that didn't work quite right in one release I'd find fixed on the next spin. This arm64/aarch64 thingy is something where we're all on the leading edge. And it's mostly depended on how mature the arm64 distribution is. That's not to say that I haven't encountered strangeness from time to time. I've been in the business long enough, though, to know that just because many of us have never seen a problem doesn't mean a problem doesn't exist. I've installed almost a dozen various arm64 Linux distributions and have not seen this message pop up once. I don't work for VMware, but I would be interested in the situations where this occurs so we can provide more specific feedback to VMware and to other users so that they may be able to avoid the situation. Message doesn't just pop-up when you are trying to run an x86 OS on your ARM64 Mac but also when you run an ARM64 OS on your ARM64 Mac in some specific cases (aka it is a bug).