Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Tim Newsgroups: comp.sys.mac.system,uk.comp.sys.mac Subject: Re: Big Sur in a VM Date: 26 Nov 2020 22:31:14 GMT Lines: 35 Message-ID: References: <261120201308444489%nospam@nospam.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=fixed Content-Transfer-Encoding: 8bit X-Trace: individual.net TkZk4cjxgU8YfcME14gU7gZWFKxxhJZNBwgVd4B5r9cKERiphx Cancel-Lock: sha1:HWd3vjrCAgxG5s+0GQH7LYITIZI= X-No-Archive: Yes User-Agent: Usenapp/0.92.7/l for MacOS - Full License Xref: csiph.com comp.sys.mac.system:135361 uk.comp.sys.mac:148662 On 26 Nov 2020 at 18:44:34 GMT, Panthera Tigris wrote: > On 26/11/20 13:08, nospam wrote: >> In article , Panthera Tigris >> wrote: >> >>> I may attempt to run Big Sur in a VM on an Intel system, probably VMWare >>> on a Windows machine or Parallels on a Mac. In both cases, older >>> hardware, quad-core i5 or i7, 16 to 24 GB installed RAM, an SSD >>> replacing the HDD which shipped with the machine. Does anyone know if >>> this is even possible, or if Apple has put roadblocks, legal, software, >>> or otherwise in to prevent this? Or if it's even possible, whether or >>> not Apple tried/didn't try to block it? >> >> it should work fine with a mac host. be sure you have the latest >> version. > > Thanks > >> Note: Virtual Box need not apply. I have had bad experiences with VB in >>> the recent past. VB is worth every penny that you pay. Or less than that. >> >> yep. > > The only reason to use VB is that it's free. However, it's such a pain > that I, for one, will gladly pay to avoid it. I'm using VB 6.1.16 and it's working very well with my 3 VMs. So a little less bollocks wouldn't go amiss. -- Tim