Comment 12 for bug 1270656

The apport data from comment #11 shows a virtual machine on VMWare. Looking at the first dmesg log, there seems to be some kind of resource conflict between the simple-framebuffer driver and vmwgfx. For testing you could probably try to create a file like /etc/modprobe.d/blacklist-testing.conf with a line "blacklist vmwgfx" in it. That should give some console (maybe not the most performant).

[ 0.782125] simple-framebuffer simple-framebuffer.0: framebuffer at 0xe8000000, 0x1d5000 bytes, mapped to 0xffffc90008380000
[ 0.782128] simple-framebuffer simple-framebuffer.0: format=a8r8g8b8, mode=800x600x32, linelength=3200
[ 0.784093] Console: switching to colour frame buffer device 100x37
[ 0.785022] simple-framebuffer simple-framebuffer.0: fb0: simplefb registered!
...
[ 21.258191] vmwgfx 0000:00:0f.0: BAR 1: can't reserve [mem 0xe8000000-0xefffffff pref]
[ 21.258193] [drm] It appears like vesafb is loaded. Ignore above error if any.
[ 21.258469] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 21.258471] [drm] No driver support for vblank timestamp query.
[ 21.259320] [drm] Screen objects system initialized
[ 21.259325] [drm] Initialized vmwgfx 2.4.0 20120209 for 0000:00:0f.0 on minor 0