Asking a dumb question in regards to virtualization software

[ryzen4osx]

When operating Linux or Windows on AMD vs Intel CPUs with respective Virtualization support enabled in BIOS, we don't see any variation in either the virtualization software package (Virtualbox, VMWare would not ask you to download separate packages for AMD or Intel platform) or their workings post installation. I am assuming that the respective kernels of windows and linux does the mapping and translation for the underlying VM instruction sets. In past I have used docker as well as VirtualBox on hackintosh but couldn't run latest version of either docker or VirtualBox on my ryzentosh. Since Darwin hasn't been officially rolled out on AMD processors till date, the corresponding mapping/translation stuff would not be present. But two successes in getting intel wifi working as well as AMD GPUs (zen, Renoir) working kinda pushes the hope for AMD virtualization support in coming times.

Coming to the question (finally ), is there any active work going on in trying to get virtualization support on ryzentosh? I did find some links on how few people got docker running using VirtualBox 6.x edition but I am more fascinated towards possibilities of getting virtualization enablement in ryzentosh directly.

 

[Edhawk]

Have you seen this guide for VMWare on a Ryzen system.

Mac OS install on AMD Ryzen/INTEL (VMWare) Opencore - Improved Performance - Works with Tahoe / Sequoia / Sonoma / etc

*** First of all, don't make any changes to the vmware .vmx file. It is recommended that you create a new virtual machine from scratch so that it recreates this file by default and without any changes. *** Use VMWare Workstation Pro version at the link provided in the tutorial. (If you install...

forum.amd-osx.com

It probably isn't what you are after, but I think it is the latest guide for macOS as a VM.

 

[El'Xsanori Leo]

Have you seen this guide for VMWare on a Ryzen system.

Mac OS install on AMD Ryzen/INTEL (VMWare) Opencore - Improved Performance - Works with Tahoe / Sequoia / Sonoma / etc

*** First of all, don't make any changes to the vmware .vmx file. It is recommended that you create a new virtual machine from scratch so that it recreates this file by default and without any changes. *** Use VMWare Workstation Pro version at the link provided in the tutorial. (If you install...

forum.amd-osx.com

It probably isn't what you are after, but I think it is the latest guide for macOS as a VM.

I guess he's asking not about macOS as a VM, but about VM on a macOS, because the first one is much easier than the second. Speaking about VM on macOS (and answering the author's question) - as you know, AMD has no virtualization support in AppleHW (obviously, because there haven't been any Macs on AMD). VirtualBox had it's own hypervisor till ~6.x, but now they are relying on AppleHW as most other virtualization software does. As a result, all Ryzentoshes now have no virtualization support. The only option is UTM in software mode, which is almost identisch to running required OS on a separate PC with something like Atom as a CPU or even worse. As I know, there is no work been doing right now on this problem as it is not the most critical one. But it would be really nice if someone could discover the solution (a system patch or something like custom virtualization software). This is the only reason why I don't use macOS on my perfectly suitable laptop.

 

[Coaster]

I guess he's asking not about macOS as a VM, but about VM on a macOS, because the first one is much easier than the second. Speaking about VM on macOS (and answering the author's question) - as you know, AMD has no virtualization support in AppleHW (obviously, because there haven't been any Macs on AMD). VirtualBox had it's own hypervisor till ~6.x, but now they are relying on AppleHW as most other virtualization software does. As a result, all Ryzentoshes now have no virtualization support. The only option is UTM in software mode, which is almost identisch to running required OS on a separate PC with something like Atom as a CPU or even worse. As I know, there is no work been doing right now on this problem as it is not the most critical one. But it would be really nice if someone could discover the solution (a system patch or something like custom virtualization software). This is the only reason why I don't use macOS on my perfectly suitable laptop.

As an update, VirtualBox 6.1.50 (last release from that branch) runs fine on my AMD Hackintosh running Sonoma 14.6.1 (latest release as of this post). It just requires gyrations to partially disable SIP and disable AMFI before installation, which then allows the requisite VBox kexts to be loaded.

Ironically, VBox 6.1.x runs better on the locked down Sonoma than it does on Ventura.