Comment 27 for bug 1434581

I would have to do more testing, but it does not look like the simple framebuffer driver ever got fixed to release the memory resource and so, as soon as we turn on that, we will have the old issue of VMs (using cirrus default gfx) coming up with no graphical console at all.
That said, the simple framebuffer did not exist before 3.13. Reading quickly through the report I think you said you used VESA framebuffer before. That is now built into the kernel (so trying to modprobe does fail). Though maybe not. It would help to find out what framebuffer driver actually was used. Probably that info is already in one of the attached dmesg files. I need to have a look if I have more time. Things to play around would be to look at /etc/default/grub and play around with grub not enabling gfx (term == console) or pre-setting the desired resolution.