On Jan 23, 2023, at 7:09 AM, Dr Eberhard Lisse <nos...@lisse.na> wrote: > Why would I try and install a VM on an M1 (ie an EMULATOR for a > different processor)
Virtualization is not emulation. An emulator (like WINE) makes use of a software bridge to simulate a different hardware environment, with a high cost in performance; software running on an emulator interacts with the bridge, not directly with the hardware. Software running in a Parallels VM runs directly on the native hardware at native, or near native, speeds. On a Mac running Apple Silicon, you create an native Arm VM with Parallels and you install an Arm version of Linux in the VM. There is no emulation. > and install Linux, of which most distributions do > not have the latest and greatest LyX and or TeX(live) So you find one that does (e.g., Kali and, soon, Fedora), easy-peasy. It’s also super easy to compile the latest and greatest source yourself under Linux (not that that’s everyone’s cup o’ tea). > to fix a bug that > is almost certainly going to be fixed soon and can be reasonably easily > circumvented until then? Well, I admit that I didn’t say so explicitly, but I wasn’t really suggesting that one purchase and install Parallels just to fix the bug (which hopefully is going to be fixed soon — though if it isn’t, it won’t be Stephan’s fault, it will be due to some deeper problem with MacOS). I was assuming that one might have Parallels installed already or have independent reasons for purchasing it. For such folks, the VM solution (even if temporary) seems to me to be a reasonable one. > Makes no sense to me, whatsoever. Hope it makes at least a bit of sense to you now. ;-) -chris > On 22/01/2023 20:21, Christopher Menzel wrote: > [...] >>> The alternative proposed here makes not sense whatsoever to me, >>> especially on an M1. The (speed) limiting factor is LaTeX (in >>> particular LuLaTeX). >> >> I /guess/ you are talking about my suggested alternative of running >> LyX in a Linux VM under Parallels? How does it "make no sense >> whatever" to you to have a fast, fully-functional version of LyX that >> does not exhibit the bug in question? (Just to note, I’ve also had LyX >> 2.3.7 simply crash on me a couple of times under Ventura in random >> situations, so there are apparently further problems and, hence, >> reasons independent of this bug to run LyX in a VM.) > [...] >>> Universal binary in any case means that on the M1 the M1 binary runs >>> and on the Intel the Intel binary. However, even running the Intel >>> binary on the M1 under Rosetta makes no real difference, other than >>> that it loads slower. But since LyX is set up to open at login I >>> would not even care. >> >> Are you saying that the bug doesn’t occur if you use a LyX Intel >> (i.e., non-universal) binary under Ventura via Rosetta? That is not >> the case, for either version 2.3.6.2 or 2.3.7. You can’t insert a >> graphic via the file browser in either one. > [...]
-- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users
