I was running VMWare with Mac OS X 10.11 El Capitan for over a year. Also installed Xcode into the El Cap environment. I’m running Windows 10. During the course of the year both the OS & Xcode were upgraded. Last night I was prompted for another upgrade. Didn’t pay all that much attention to it.
I'm using VMware Fusion 7.1.1 to run both Windows 8.1 and Windows 10 on a mid 2014 15-inch retina Mac. I've heard it is possible to run VMware in such a way that the screen's native resolution (in my case, 2880x1800) is displayed without any scaling. After lots of trial and error, I discovered this works fine using the default desktop scaling in OSX.
However, I normally run OSX in a scaled display setting (the default scaling makes everything too big to my tastes), where it actually renders everything at 3360x2100 and then downscales that to 2880x1800. It seems this also happens when using VMware Fusion, which means the perfect 2880x1800 picture from Windows gets stretched to 3360x2100, only to get scaled down to 2880x1800 again, leaving me with edges and text being blurrier than they should be. Is there any way to prevent this from happening? I'd rather not change back to default desktop scaling in OSX every time I want to use VMware Fusion. From:. Install the VMware Tools by selecting Virtual Machine → Install VMware Tools in the menubar. Follow the on-screen instructions.
Set Use full resolution for Retina display in VMware Fusion’s Settings → Display preferences panel. Run this command in Terminal on your OS X guest VM and enter your password when requested: sudo defaults write /Library/Preferences/com.apple.windowserver.plist DisplayResolutionEnabled -bool true.
Log out of your OS X guest VM and then re-login. Resize your OS X guest VM window to your preferred dimensions.
In System Preferences → Displays, set the resolution to Scaled and then select the HiDPI setting. Note: If you resize your guest VM, it will revert to the non-HiDPI resolution. Simply re-select the HiDPI resolution in the System Preferences → Displays preferences panel.
Apple has made some changes to Disk Utility in OS X 10.11 El Capitan. One of the biggest changes is how the partition tab looks and functions. I recently grew my MacPro VM’s virtual disks from 128G to 256G, and ran ‘sudo diskutil resizeVolume / R’ to try to make the space available, but it told me ‘MediaKit reports partition (map) too small’. I downloaded gparted-live-0.27.0-1-i686.iso and put it into datastore1, added it ‘at power up’ to the VM’s CD, changed the VM type to Other 2.6.x LInux 32 bit, booted the VM and held C down from the VMWare screen until it reached the GRUB screen, but while I could select the GRUB options, most of the resulting systems either didn’t recognise the keyboard in character mode, or the mouse in GUI mode. Every so often, the default GRUB option worked but while I got through language selection I found I needed to selected menu option 2 to enter shell mode, then quit it without doing anything to enter the GUI, but had to drum on the keyboard’s arrow keys for a while before the GUI system recognised the keyboard or mouse clicks.
I told it to fix the partition table – the ‘do you want to fix this’ that came up automatically. I saw a small /dev/sda1, the EFI system partition, at 200M, /dev/sda2 the Mac HD, at 127G, /dev/sda3 the recovery HD at 620M, and 128G of unallocated space.
I asked to move the recovery partition to the very end of the free space, and it said that might be bad, so I just quit and rebooted. I turned the guest OS back to Mac (I had to log in to the host as root to shut down the VM, for some reason: VMWare Fusion didn’t give me the shutdown option), and now it’s back in OSX. Now resizeVolumes / R doesn’t show the ‘Note: Your partition map does not use the entire space of your whole-disk’ warning, and completes without ‘MediaKit reports partition map too small’.
And my HD is at 274G. Not quite the whole 128G, but certainly better than 127.