Console resolution.

[DavyJohnes]

Hello!
I have installed Ubuntu 10.10 Server as guest system. Everything alright, but console resolution is very small, something like 640x480, and when I go to full-screen mode, it doesn't change. What I have to do to change console resolution ?

[Perryg]

http://ubuntuforums.org/showpost.php?p= ... stcount=10

You will need to adapt to your version

[DavyJohnes]

http://ubuntuforums.org/showpost.php?p= ... stcount=10

You will need to adapt to your version

I now this way, but hwinfo --framebuffer, that gives vga modes, dooesn't give mode that i neeed (1366x768). What I have to do?

[Perryg]

Does sudo hwinfo --framebuffer show that resolution?
If not you can't use it. Besides 1366x768 is not a standard resolution.

This really has nothing to do with VirtualBox. If you had X installed and could install the guest additions you would not have this issue. Since it is a server without X you must rely on the OS for the framebuffers.

[akaspin]

Check this link http://idyllictux.wordpress.com/2010/04 ... ed-driver/

[hartman.rh]

There does seem to be an issue with console resolution in VBox 4.1.
I'm running a CentOS 5 and a CentOS 6 client in 1280x1024 (console) resolution (VGA=775), and since VBox 4.1 I lost my high console resolution in both clients.
I downgraded VBox to 4.0.12 again, and found this is an issue with the VBoxLinuxAdditions; only after also downgrading the Additions to 4.0.12 I had my high console resolution back again.

[levk]

I there a specific reason you prefer the actual vbox window with the console? Because you can do everything you can with a console and more (like scrolling up, copy/paste) with SSH.

[qkb]

I have a Debian-testing guest (and Ubuntu must be similar) so my solution for full-screen full-resolution console screen may also work in Ubuntu:
1. add your host resolution as a 'custom VESA resolution' to VBox (see section 9.6.1 in VBox User's Manual for details)
2. add a line like:

Code: Select all

GRUB_GFXPAYLOAD_LINUX="1280x800x32,1280x800"

to /etc/default/grub in the host (use your host resolution here, 1280x800 is mine). The 'update-grub' is needed for the changes to take effect after next guest reboot. You need to be root orl sudoer to be able to apply these changes in the guest.

Keep in mind that since 4.1 terminal consoles are invisible anyway (see another thread).

[pvoigt]

Hi qbk,

could you please give me the link to the thread dealing with "invisible terminal consoles". I've come to this issue after upgrading from VB 4.0.10 to 4.1.4. After the upgrade I cannot change anymore to the virtual consoles with ALT+CTRL+Fx of my Linux guest. They simply remain black. I figured out that downgrading the Linux Guest Additions to 4.0.10 provides a workaround. I would like to know, if it is a bug or a configuration issue.

[Sasquatch]

Hi qbk,

could you please give me the link to the thread dealing with "invisible terminal consoles". I've come to this issue after upgrading from VB 4.0.10 to 4.1.4. After the upgrade I cannot change anymore to the virtual consoles with ALT+CTRL+Fx of my Linux guest. They simply remain black. I figured out that downgrading the Linux Guest Additions to 4.0.10 provides a workaround. I would like to know, if it is a bug or a configuration issue.

It's a problem with Linux picking the wrong framebuffer to show the console after the GA are installed. There are some features in the GA that cause Linux to misinterpret it's true capabilities. To avoid this, use "text" instead of a resolution. Your terminal will show, but in the default 80x25 characters. You can't have both, unless, as you found out, use older guest additions or none at all (but I've read various posts that had no text even without GA).

[pvoigt]

Hi qbk,

could you please give me the link to the thread dealing with "invisible terminal consoles". I've come to this issue after upgrading from VB 4.0.10 to 4.1.4. After the upgrade I cannot change anymore to the virtual consoles with ALT+CTRL+Fx of my Linux guest. They simply remain black. I figured out that downgrading the Linux Guest Additions to 4.0.10 provides a workaround. I would like to know, if it is a bug or a configuration issue.

It's a problem with Linux picking the wrong framebuffer to show the console after the GA are installed. There are some features in the GA that cause Linux to misinterpret it's true capabilities. To avoid this, use "text" instead of a resolution. Your terminal will show, but in the default 80x25 characters. You can't have both, unless, as you found out, use older guest additions or none at all (but I've read various posts that had no text even without GA).

Thanks for the quick reply. Directly after my post in this thread I've addressed this issue to the "Discuss the 4.1.4 release" with some more details given. Still remaining to me is the anser to the question: Is the GA misinterpretation a bug or a feature, e.g. should I open a bug report or not? The current situation is very annoying and makes Linux guests close to unusable.