VIrtualBox graphics unable to determine correct screen size to use in some cases

Closing as part of EE RC2

OK, docs updated slightly and pull request created on github.

Please update the QEMU documentation at http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/machines/qemu.html

So, here's where things reside at this point. The latest version of VirtualBox is 5.2.0. With VirtualBox 5.2.0 and macOS 'El Capitan' (10.11) as well as macOS 'Mavericks' (10.9), VirtualBox is able to provide a functional DRM guest video driver and with weston using the drm-backend backend, things work as expected. The first hiccup here is that we do not see a cursor (as ivi-shell doesn't have that option?) and unlike QEMU there is no option to force a cursor. This is a problem if you aren't using a touchcreen laptop. The second hiccup is that VirtualBox 5.1.30 and macOS Sierra (10.12) has been functional the whole time. It however does not provide a functional DRM guest driver, but does have the host-OS cursor visible.

There are two problems in Dab as shipped. The first is addressed with and is a metadata issue and impacts all QEMU and VMWare as well, as by default none of these have a DRM driver enabled in Dab.

The second is only found in VirtualBox, and is that VBox insists on providing an 800x600 display despite the fact that uvesafb is running at 1024x768 (or, if you modify the kernel command line to pass in another size such as 1600x900, same thing). This is what causes the screen to be all distorted, with the first problem resolved.