Screen Resolution in Ubuntu with VirtualBox 4.0.8

[zanechua]

I've googled about this but can't find a fix for it, at least not an updated one.

I would like to fix the Screen Resolution sizes in VirtualBox. I've looked at the xorg.conf and kinda screwed my ubuntu installation up.

Before Guest Additions, i could go up to 600x800 or the other way round, can't remember. After Guest Additions i'm up to 1280x960 but i would like my native resolution which is 1920x1080. Anyone have any ideas?

Regards
Zane

[Perryg]

Once the guest additions are install. you use the mouse click & drag or the host+F toggle to go in and out of full screen. If the host+F does not work you need to use the host+G toggle to turn the auto-resize on.

[zanechua]

I'll try that when my host is back up again.

However, if that does work. Why do i not see a "boot" screen until my actual desktop loads?

[Perryg]

Could be a lot of things, hard to say. Ubuntu has had issues since the switched to plymouth. Something to do with framebuffers and which they choose not being the best for a virtual environment. You can take VGA (something) out of the black list but it has not been a big enough issue for me to troubleshoot.

[zanechua]

Alright. As long as it works, i don't really mind. Thanks Perry. Will update on what happens. ^^

EDIT: Awesome it works! Thanks for the tip and sorry for posting without trying.

[james_turton]

Hi guys, I've been battling to increase my screen resolution in an Ubuntu guest beyond 1024x768 without installing guest additions. Is this possible? The reason I can't install guest additions is that my guest is actually a live USB installation that sometimes boots up physical, sometimes virtualised. If guest additions are installed when the OS boots up physical then the kernel modules fail to load and crash the kernel. As an aside, is it possible to stop the guest addition kernel modules from crashing the OS when the OS boots up physical (i.e. VirtualBOX VMM is not present)? Why can't the kernel modules log a warning and fail to load themselves without crashing the whole kernel in this scenario?

The other (ugly) option I'm looking at is adding startup/shutdown scripts to the guest to look for the guest additions ISO being mounted and automatically install guest additions and remove them again every time the machine is booted and the guest additions ISO is visible.

Thanks
James

[james_turton]

Don't worry, I gave up on having an environment that can boot both physical and virtual. My VMDK now lives on the ExFAT formatted stick and includes installers for VirtualBox - the environment will not run without it.