On Feb 14, 2025, at 00:05, Søren Schmidt <soren.schm...@gmail.com> wrote:
> >> On 14 Feb 2025, at 01.50, Mark Millard <mark...@yahoo.com> wrote: >> >> I've no clue if the issue is specific to just Parallels >> or not: I've really only used Hyper-V (only getting >> it working for FreeBSD as a guest OS on amd64) and >> Parallels (aarch64 currently). So I do not know if >> it would be worth a tunable to, say, set the >> vd_priority offset from VD_PRIORITY_GENERIC, such >> that it could end up not replacing efifb. (I looked >> in the source code a little bit for this message.) > > I’m using UTM on my M4 Macs, and it works just fine (so does VMware / > Virtualbox in my experience) > However in UTM you can choose your display device as to fx use a simple ram > buffer console, maybe there is something similar I parallels ? > I've not done anything with virtio_gpu before, so I may simply have not figured out some functionality (or even how to find the documentation). It may be something that works for a "real" Other Linux. When I tried the non-Linux plain Other, FreeBSD panicked while trying to support the virtio code. As stands, I'm booting my own kernel that omits virtio_gpu (so that it does not replace efifb). efifb seems to work just fine for my limited range of use. Parallels allows me to operate my normal boot media as the as the storage for a VM. It is the same media that I use on the Windows Dev Kit 2023 and that I sometimes use on a RPi5 as well. Software for Apple Store distribution was not allowed to do such last I knew: It involved privilege escalation. See: https://github.com/utmapp/UTM/issues/5346 That is one of the reasons that I'm using Parallels. (I already had a license as context as well.) === Mark Millard marklmi at yahoo.com
