![]() That said, what hardware platform does the 'clean' MacOS 10.13 template copy? Does it make sense to coerce the VM into reporting the host CPU, such as my I7-3820QM, for example? What about a particular 'least common denominator' Mac model (Macbook7,1, iMac14,1, Macmini6,2, etc.) DSMOS should propagate from the host to the client, right? ![]() (and a LOT of time waiting on DSMOS) I want to stay away from hacks and patches to ensure a valid test run. I have Parallels and VMware Fusion but VirtualBox is the common platform for my work on Windows, Linux and Mac.Īs I focus on MacOS on MacOS, I spend a lot of time trying to get a VM to work. Often the security testing is destructive, so operating in VMs is key. I have many security issues to test for work and need to test on several releases of MacOS. The laptop is fine and is just used to run VirtualBox. I am running the latest VirtualBox 6.1.2 on MacOS Mojave on a MacBookPro9,1 2.7 GHz Intel Core i7 with 16 GB RAM and 1 TB of SSD. (My browser filled in the Subject: line for me.)
0 Comments
Leave a Reply. |