After enabling 3D acceleration in Mac OS 11 Big Sur guest VMs Apple Vision no longer works to do optical character recognition (OCR). I've created a test application in the hopes that a VMWare Fusion...
See more...
After enabling 3D acceleration in Mac OS 11 Big Sur guest VMs Apple Vision no longer works to do optical character recognition (OCR). I've created a test application in the hopes that a VMWare Fusion engineer will see this and be able to dupe it. Using a Big Sur host, create a Big Sur VM. Run the example Apple Vision application (attached) and click "Do OCR". After a few seconds the OCR finishes and you see the resulting text. Shut down the VM and follow the instructions at https://kb.vmware.com/s/article/81657 to enable 3D acceleration in the VM. Launch the VM and repeat step 2. RESULT: The OCR doesn't work. Nothing happens. Is there a workaround besides turning off 3D acceleration. I love how smooth the VM is with it enabled but AppleVision must work for my purpose. I've put two attachments on this post: A built test application, zipped. (not sure if the forum will even allow that) The Xcode project for the application. I'm building with Xcode 12.4 on Big Sur 11.2.2
I've put the utility up where anyone can access it. It's available at: http://www.zackswagon.com/random/VMWareFusionSetScreenResolutionPack.zip Good luck!
Sure, send me your email address and I'll send you the compiled application. If you want the code I can send that too but you'll need to compile it yourself. Zack
I've had intermittent problems with the shared folder facility on VMWare Fusion so I just avoid it completely and move files around via the network using command line tools and shell scripts. rs...
See more...
I've had intermittent problems with the shared folder facility on VMWare Fusion so I just avoid it completely and move files around via the network using command line tools and shell scripts. rsync has all the options necessary to keep/transform symlinks and you should be able to get a clean, build-able copy of your source using it. Zack
Building in a VM and regressing on the hardware will probably work fine. Unless you're compiling millions of lines of code your build should be pretty snappy. You should consider spooling up th...
See more...
Building in a VM and regressing on the hardware will probably work fine. Unless you're compiling millions of lines of code your build should be pretty snappy. You should consider spooling up the VM specifically for building and shutting it down afterwards so that all hardware can be dedicated to regression most of the time. Build servers and QA labs are like pets: you have to raise them from infancy and learn their individual quirks. No amount of reading or preparation can stand in for what you will learn actually doing it. Set up the machine the way you think it should be and try it out. If it's rubbish then try again until you get it right. Even once you've gotten it right things will evolve over time until today's solution looks terrible and it's time to build a new one. Good luck!
I have a variety of VMs running simultaneously. They are launched headless by vmrun with the nogui option (I wrote some shell scripts that launch the VMs when the system boots up) and then I acc...
See more...
I have a variety of VMs running simultaneously. They are launched headless by vmrun with the nogui option (I wrote some shell scripts that launch the VMs when the system boots up) and then I access them remotely using Apple Remote Desktop (ARD). ARD allows you to observe multiple computers in a single window like you describe. This setup works great for me. Apple Remote Desktop is US $79.99 on the AppStore. There may be other VNC clients that are cheaper and that allow observing multiple computers.
Your configuration will work fine. I regularly run similar configurations (mid-2011 Mini with 4 GB RAM running one Mac OS X Guest VM with 2 GB RAM allocated). If you have both the host and gues...
See more...
Your configuration will work fine. I regularly run similar configurations (mid-2011 Mini with 4 GB RAM running one Mac OS X Guest VM with 2 GB RAM allocated). If you have both the host and guest doing processor or disk intensive work then things will slow down a bit, but if you are only taxing one or the other things should stay snappy.
HPReg, Thank you for the solution. I've put together a little program based on your code that does exactly what you described. That program is invoked by launchd at login and works like a char...
See more...
HPReg, Thank you for the solution. I've put together a little program based on your code that does exactly what you described. That program is invoked by launchd at login and works like a charm. It's definitely a viable workaround for the issue and I appreciate your willingness to share it with me. A thousand thanks.
Thanks for the detailed explanation. Your proposed solution would work fine for me. I was curious if there is any way for me to talk to the VMware Tools directly in the VM. If I could simula...
See more...
Thanks for the detailed explanation. Your proposed solution would work fine for me. I was curious if there is any way for me to talk to the VMware Tools directly in the VM. If I could simulate whatever the Fusion UI says to VMware Tools to make steps a through c happen that would be a fine solution too. Thanks again.
Thanks spb2011. I've tried those settings in the vmx for this VM but they did not help. With those settings I still only see the one available resolution in System Preferences (1024x768). Sinc...
See more...
Thanks spb2011. I've tried those settings in the vmx for this VM but they did not help. With those settings I still only see the one available resolution in System Preferences (1024x768). Since I can't stretch the window to resize the resolution when running in nogui mode I can't change the resolution in Mavericks VMs running that way at all.
Yes, I've seen your AppleScript solution. Unfortunately since I run exclusively in nogui mode that solution is not appropriate in my case. Thanks. One solution I'm looking into is writing an...
See more...
Yes, I've seen your AppleScript solution. Unfortunately since I run exclusively in nogui mode that solution is not appropriate in my case. Thanks. One solution I'm looking into is writing an application that uses the Core Graphics API to set the resolution. Unfortunately the only display mode that Core Graphics shows available for the VM display is 1024x768. I'm playing around with an undocumented call in that API to see if maybe I can build up a display mode out of whole cloth and then apply it. Still seeking solutions, of course. The best solution would be from VMWare, of course, with a fix to make this feature work in Mavericks guests like it does in non Mavericks ones. If I find something I'll post it but hopefully somebody here has a solution already.
I run a virtualized automation lab via VMWare Fusion. This lab is used to QA test Mac software. I have dozens of VMs running on a variety of Mac hardware using VMWare Fusion 6.0.2. The problem...
See more...
I run a virtualized automation lab via VMWare Fusion. This lab is used to QA test Mac software. I have dozens of VMs running on a variety of Mac hardware using VMWare Fusion 6.0.2. The problem I am seeing is that the Mavericks VMs have their screen resolution reset to 1024x768 upon every reboot and that is the only resolution available in the System Preferences Display panel. The way I set up VMs is like so: 1. Using the VMWare Fusion app create a new VM and install the operating system. 2. Install VMWare Tools in the guest. Restart the VM. 3. Configure the guest OS with my settings. This always includes setting the screen resolution to something above 1400x1050. I do this by stretching the window in the VMWare Fusion application or by setting the resolution via System Preferences. 4. Shutdown the VM and make a copy of it. This copy is my default state. In actual use after that the VMs are run headless using vmrun with the nogui argument. For all versions of OS X VMs the resolution stays the same when the VM is restarted. For Mavericks VMs the resolution is changed to 1024x768. For all other OSes multiple resolutions show up in the System Preferences Display panel. For Mavericks only that one resolution appears in the Scaled options. I have tried the steps in KB 1003: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1003&sliceId=1&docTypeID=DT_KB… but that did not fix the problem. I have tried turning 3d acceleration on and off and the problem exists in both cases. Changing the resolution by resizing the window while using VMWare Fusion app works fine but that is not possible when running headless. Tech support via phone suggested I post this problem to the community and see if there are any answers here. Thanks in advance. Message was edited by: AzironaZack to add more details.
