"Despite my earlier prediction that VMWare was the way to go, there also seems to be a network issue with VMWare on macOS 15 Sequoia (the latest macOS). After about 5 minutes the network in ArcaOS drops then might come back 15 mins or so later, then goes again. It's not an IP or MAC address clash which was my first thought. This does not happen with macOS 14 Sonoma, the previous version - it seems rock solid."
Hmmm ... shouldn't have worked at all, as the guest OS is AOS, and there are no "full" guest additions for VMware as the Type-2 hypervisor. AOS will run in a VMware vm, but unless AN is now providing a set of VMware guest additions in their AOS, it can't comm with the outside world. In other words:
1. have a host OS (windows, linux, max)
2. install a Type-2 hypervisor (VMware, Virtualbox)
3. create a VM (and give it a network conn type, utilizing the host's ethernet adapter)
4a. install a guest OS into the vm
- on VMware, the only supported guests are those which have VMware guest additions, typically these are modern Win or Linux OS's
4b. inside the guest OS, install a "full" set of Guest additions (this is where it gets tricky):
- Windows OS (both VMware & Vbox have full guest additions to install; this turns on networking)
- Linux (both VMware & Vbox have full guest additions to install; this turns on networking)
- AOS:
- Vbox has some older versions of a full set of guest additions (and Valery has a version)
- AOS has something in it that turns on, when in a vbox vm
So, even though a VMware vm has a network adapter defined in it's vm settings, this doesn't come to life all the way in the Guest OS until a full set of supported guest additions gets installed into the vm; there aren't any for AOS for VMware, although the find of a Github drivers set, with mouse and clipboard support is interesting ... this find gives us some partial support.
This limits AOS to vbox, if you want full "guest additions" support. Hyper-V is a Type-1 hypervisor, but the same issues apply ... there is no full guest additions support for os/2 (obviously, as MS could care less) in Hyper-V.
If you think you got full network support, or full video support, etc., out of your AOS under VMware, then that warrants some further exploring (as to how you got it to work).
Hope this clears things up ... please advise if yours (or anyone's) experiences are different ...