Page 1 of 1

Ubuntu VM screen size stuck after upgrade

Posted: 14. Jun 2013, 14:15
by jshardlo
I'm sure this is something of an FAQ but I have read the other posts and followed the instructions and I'm still quite stuck.

I have an Ubuntu VM running under VB 4.2.12. The Ubuntu version is 12.04.2 LTS.

I just applied some package updates that upgraded the kernel to 3.2.0-48-generic.

Normally after kernel upgrades I noticed that I had to rebuild the guest additions to use larger monitor sizes.

I followed the same procedure but this time it doesn't seem to work and I am stuck with only 1024x768 or 800x600.

The log file from the module build looks OK to me...

Any other ideas on how to fix it?

:?

Re: Ubuntu VM screen size stuck after upgrade

Posted: 14. Jun 2013, 15:08
by Perryg
Depends on the procedure that you mention but not explain what it in fact is.

Re: Ubuntu VM screen size stuck after upgrade

Posted: 15. Jun 2013, 04:43
by jshardlo
Hello Perry,

After kernel upgrade I've always mounted the Guest Additions CD/DVD image and then done this:

cd <path to image>

sh ./VBoxLinuxAdditions.run

But after this upgrade and after rebuilding the guest additions the GUI starts with a dialog that says:

The System is Running in Low Graphics mode.

I select the option to run in that mode for one session and I can see in the System Settings -> Displays that I only have the two options mentioned (1024x768 and 800x600).

Pressing "Detect Displays" has no effect.

I can see the vboxvideo module is loaded using "lsmod".

The xorg.conf file lists the Driver as "vboxvideo".

Any other details that would be useful?

Thanks

Re: Ubuntu VM screen size stuck after upgrade

Posted: 15. Jun 2013, 13:10
by stefan.becker
Known problems. You need a fix available in this Guest Additions ISO: http://www.virtualbox.org/download/test ... -86264.iso

Re: Ubuntu VM screen size stuck after upgrade

Posted: 15. Jun 2013, 15:13
by jshardlo
Thanks Stefan. I downloaded this and tried it but I still have the same problem.

I've booted from the previous kernel 3.2.0-38-generic instead of 3.2.0-48-generic and that completely solves the problem and also fixed an issue with the system not powering off cleanly.

So for now I'll stick with the older kernel.