#Azure mac os vm mac os x#
#Azure mac os vm manual#

Next time you reboot, if you made sure the RunAtLoad is set to 'true', the resolution will be set automatically.

#Azure mac os vm manual#

It should do exactly the same thing as the manual command. To test it before booting, excute: sudo launchctl load /Library/LaunchDaemons/ist Library/Application Support/VMware Tools/vmware-resolutionSet I did: sudo nano /Library/LaunchDaemons/ist In /Library/LaunchDaemons as root, create a file named whatever you like with your favorite editor, but end it with. plist file to set the resolution I want at boot. I did some searching on Launch Scripts (had done a few before) and came up with a simple Launch Daemon. In my particular application, if there is a slight performance hit, it won't matter. it might have a performance consequence, I don't know. Running that command every time you reboot is obviously not optimal, although. Just yesterday, I copied the script from my Fusion 8.1 vmware tools folder to one of my ESXi 6 OSX guests. Mark, I was just hunting for the same solution. I know our customers will greatly appreciate this workaround! Lastly, I would like to give a big thanks to Michael Udaltsov, the Engineer who is responsible for creating theВ workaround andВ providing me with some additional contextВ to this change in behavior. For example, if I want a 2880x1800 display resolution,В I would add the following: In this case, you would need to also add the following two advanced settings to the VM which can be done usingВ the vSphere Web/C# Client or the vSphere API.

One other thing to note is if you plan on using higher display resolution than 2560x1600, you may need to configure some additional VM Advanced Settings due to use of framebuffers that are larger than 16MB.

#Azure mac os vm mac os x#

Below is a screenshot of a Mac OS X 10.11 (El Capitan) running on vSphere 6.0 Update 1 configured with a 1920x1080 resolution. If weВ take a look at ourВ Mac OS X VM, we should now see that ourВ new custom display has takenВ effect. If output does not match, it most likely means you need to increase the video memory and you can refer to this VMware KB 1003 for more details. If everything was successful, you should see that both the 'Requested resolution' and the 'Effective resolution' match in the output. In the example above, I have 16MB configured for my Mac OS X VM which would give you a maxВ resolution of 2560x1600. Note:В Ensure you have sufficient video memory configured for your VM for larger display resolutions. For example, to set a 1920x1080 resolution, you would run the following command: Make sure to use 'sudo' if you want the display resolution to persist through a system reboot. The syntax for the vmware-resolutionSetВ utility is pretty straight forward, it accepts a width and height argument. One thing to note is that there is a known issue right now for VMware Fusion 8.1 related to NAT and port forwarding, you may want to hold off on upgrading if you rely on this feature. You can find it under '/Library/Application Support/VMware Tools'. UPDATE (12/11/15)- Thanks to reader it looks like the latest VMware Fusion 8.1 release now includes an updated version of VMware Tools (10.0.5) which includes the vmware-resolutionSet utility. Although this toolВ has not been officially released andВ must go through the standard release process,В theВ plan is to include it in a future update of VMware Tools and will available for use with both VMware Fusion and vSphere. You will need to ensure you have VMware Tools installed and running before you can use this utility.В As of right now, customers can get aВ hold of this utility by filing an SR with VMware Support and referencing PR 1385761.

The workaround that has been developed is a tinyВ standaloneВ command-line utility called vmware-resolutionSetВ which runs within the Mac OS X GuestВ and allows you to configure a custom display resolution. Given this is a non-trivial fix, VMware Engineering has been working hard on a providing a workaround which would still allow users to set a custom resolution from within the GuestOS. The reason for this behavior is that Apple has changed the way in which it remembers previously used modes and would automatically fall back to this versus retaining the custom mode using the Display Preferences. For customers who are running Mac OS X 10.9 (Mavericks) or newer in a Virtual Machine, you may have noticed that you can no longer set a custom display resolution beyond the default 1024x768 in eitherВ VMware Fusion and vSphere, regardless of the amount of video memory that has been allocated.