So, until recently I had a 1920x1200 monitor at the office, and a 3440x1440 monitor at home. I finally sprung for a 3440x1440 monitor to use at work, so that I can scale my vnc/nomachine sessions up. (I'm doing system software development; I just need a bunch of emacs frames on a nice big persistent desktop that I can reach from home and the office.)
As I mentioned a few months ago in this thread, it's a big help to connect to the office VPN from a VM, because only the VM gets fenced out of the home network. I can connect at 3440x1440 from my physical mac, but I have failed so far to get a VM working with this resolution.
Per "3.14.1 Video modes in EFI" (
https://www.virtualbox.org/manual/ch03.html#efividmode) I was able to get a mac VM working at 2560x1440
- Code: Select all Expand viewCollapse view
BigDog:~ jmg$ vboxmanage getextradata jmac1 VBoxInternal2/EfiGraphicsResolution
Value: 2560x1440
...but 3440x1440 is not on the list.
According to 9.8.1. Custom VESA resolutions (
https://www.virtualbox.org/manual/ch09.html#customvesa) it looks like I should be able to set 3440x1440 as a custom resolution - but I haven't had success (vms boot at 640x480, or some other tiny resolution).
- Code: Select all Expand viewCollapse view
BigDog:~ jmg$ vboxmanage setextradata jmac2 VBoxInternal2/EfiGraphicsResolution
BigDog:~ jmg$ vboxmanage getextradata jmac2 VBoxInternal2/EfiGraphicsResolution
No value set!
(reverse-i-search)`cu': cd Documents/Zoom
BigDog:~ jmg$ vboxmanage getextradata jmac2 CustomVideoModel
No value set!
BigDog:~ jmg$ vboxmanage setextradata jmac2 CustomVideoModel 3440x1440x16
BigDog:~ jmg$ vboxmanage getextradata jmac2 CustomVideoModel
Value: 3440x1440x16
But the vm "jmac2" (which is just a copy of jmac1) boots up in tiny resolution.
So it appears that VBoxInternal2/EfiGraphicsResolution is recognized by osx, but CustomVideoModel is not.
Any illumination would be appreciated.
Edit: I'm running vbox 5.2.8 (latest as of now) and the vm is osx El Capitan (10.11.6). I suppose I should try High Sierra in the VM.
Thanks,
John