A similar problem was observed with VirtualBox at bug #1365336. I guess the root of both problems can be the same: in recent VirtualBox versions, no framebuffer device is being exposed by the kernel "a priori" in a guest Ubuntu-daily system.
Have you tried to boot on a VMware virtual machine?
A similar problem was observed with VirtualBox at bug #1365336. I guess the root of both problems can be the same: in recent VirtualBox versions, no framebuffer device is being exposed by the kernel "a priori" in a guest Ubuntu-daily system.
Have you tried to boot on a VMware virtual machine?