Bug #1368784 “Vivid and Utopic Virtualbox guest gets only up to ...” : Bugs : grub-gfxpayload-lists package : Ubuntu

Revision history for this message

Daniel Holbach (dholbach) wrote on 2014-09-12:

#1

BootDmesg.txt Edit (31.4 KiB, text/plain; charset="utf-8")
BootLog.txt Edit (4.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.8 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (2.0 MiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (45.7 KiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (1.1 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (3.1 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (4.9 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (652 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (316 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (1.4 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (73.1 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (163.3 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (685 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (18.9 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (33.5 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (631 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (30.7 KiB, text/plain; charset="utf-8")
xserver.errors.txt Edit (688 bytes, text/plain; charset="utf-8")

Revision history for this message

Robert Hooker (sarvatt) wrote on 2014-09-12:

#2

[ 12.327] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo_drv.so
[ 12.327] (II) Module vboxvideo: vendor="Oracle Corporation"
[ 12.327] compiled for 10.15.0, module version = 1.0.1
[ 12.328] Module class: X.Org Video Driver
[ 12.328] ABI class: X.Org Video Driver, version 15.0
[ 12.328] (EE) module ABI major version (15) doesn't match the server's version (18)

The virtualbox driver isn't loading, and it looks like you dont have virtualbox 4.3.14-dfsg-1build1 which is the one that works with it. Is the update available to you?

affects:

xorg (Ubuntu) → virtualbox (Ubuntu)

Revision history for this message

Daniel Holbach (dholbach) wrote on 2014-09-12:

#3

That's what I have installed.

Revision history for this message

Daniel Holbach (dholbach) wrote on 2014-09-15:

#4

I tried a lot of different combinations. In the end it only worked when I had virtualbox-guest-x11 installed on the guest. -dkms and -guest-additions-iso didn't make it work.

Revision history for this message

Norbert (nrbrtx) wrote on 2014-10-03:

#5

I can confirm this on todays daily build.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-10-03:

#6

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtualbox (Ubuntu):
status:	New → Confirmed

Revision history for this message

Carla Sella (carla-sella) wrote on 2014-10-17:

#7

After rebooting a fresh Install of Utopic on Virtualbox I get resolution 640x480, no changes happen if you reinstall Virtualbox guest additions.

Revision history for this message

Ubuntu QA Website (ubuntuqa) wrote on 2014-10-17:

#8

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1368784

tags:

added: iso-testing

Revision history for this message

Otus (jan-varho) wrote on 2014-10-22:

#9

Resolution in the live session is fine, it is only after booting to the installed system that it degrades to 640x480.

Revision history for this message

Norbert (nrbrtx) wrote on 2014-11-02:

#10

Installed virtualbox-guest-x11 package in Ubuntu Utopic 14.10 final guest and got normal resolution in it.

Elfy (elfy) on 2014-11-09

tags:

added: vivid

Alberto Salvia Novella (es20490446e) on 2014-11-12

Changed in virtualbox (Ubuntu):
importance:	Undecided → High

Revision history for this message

Bruce Pieterse (octoquad) wrote on 2014-12-11:

#11

This is still present with the daily build for 11 Dec on Ubuntu Gnome.

Revision history for this message

Bruce Pieterse (octoquad) wrote on 2014-12-18:

#12

Screenshot of LVM text cut off on Vivid Alpha 1 Edit (308.0 KiB, image/png)

This is still present with the vivid alpha 1 image for Ubuntu Gnome. Additionally with LVM encryption, the text is cut off on the left and the right as well as the input box being slightly cut off at the bottom.

Revision history for this message

amjjawad  (amjjawad) wrote on 2014-12-19:

#13

Hi,

This has fixed the issue for me:
http://ubuntuforums.org/showthread.php?t=2251116&p=13158092#post13158092

Try that and let me know, please if that did help or not? :)

Revision history for this message

Tim Lunn (darkxst) wrote on 2015-01-17:

#14

The virtualbox drivers used to be included on the live CD, that doesnt seem to be the case anymore however.

Revision history for this message

Bruce Pieterse (octoquad) wrote on 2015-02-06:

#15

Also affects Ubuntu Gnome 14.04.2 with 20150203 build.

tags:

added: trusty

Revision history for this message

gravy45 (gravy45) wrote on 2015-03-27:

#16

amijawad's solution three posts up fixed the issue for me. (And https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1386005 as well).

Martin Wimpress  (flexiondotorg) on 2015-03-27

summary:

- Utopic Virtualbox guest gets only up to resolution of 640x480
+ Vivid and Utopic Virtualbox guest gets only up to resolution of 640x480

Revision history for this message

Martin Wimpress  (flexiondotorg) wrote on 2015-03-27:

#17

After discussing this with Colin Watson in #ubuntu-devel I've found a work around that is more agreeable.

Create '/usr/share/grub-gfxpayload-lists/blicklist/11_virtualbox' with the following content:

v80eedbeef.*

Run the following to update the blacklist and grub.

sudo update-grub-gfxpayload
sudo update-grub

The boot process will now be text only for Virtualbox guests and the default X resolution is 1024x768.

The other benefit of this approach is that if full disk encryption is used, you are now always able to enter your pass phrase. So this technique is also a fix for https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1386005

Colin Watson (cjwatson) on 2015-03-27

affects:	virtualbox (Ubuntu) → grub-gfxpayload-lists (Ubuntu)
Changed in grub-gfxpayload-lists (Ubuntu):
assignee:	nobody → Colin Watson (cjwatson)

Revision history for this message

Martin Wimpress  (flexiondotorg) wrote on 2015-03-27:

#18

Download full text (5.8 KiB)

Colin Watson asked that I discuss this issue in #ubuntu-kernel. A log of the IRC discussion is below, as requested by Martin Pitt, and I'll attach a debdiff for 'grub-gfxpayload-lists' in due course:

Here is what we discussed:

<flexiondotorg> I been discussing https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/ with cjwatson in #ubuntu-devel
<ubot5> Ubuntu bug 1368784 in virtualbox (Ubuntu) "Vivid and Utopic Virtualbox guest gets only up to resolution of 640x480" [High,Confirmed]
<flexiondotorg> I've got the following work around - https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/comments/17
<flexiondotorg> cjwatson is prepared to update grub-gfxpayload-lists if someone here can confirm "fixing" this issue at a kernel level is hopeless.
<flexiondotorg> So, thoughts?
<apw> flexiondotorg, "fixing" at the kernel level, do we know what the issue is ?
<apw> flexiondotorg, the implication of the (admittedly older) comments is that you need virtualbox-guest-x11
<apw> flexiondotorg, and indeed i can confirm that installing the said package does sort things out, who knows what i has in it mind
<apw> seems it has a vbox specific video drivers
<apw> i wonder if they should be being installed by jockey
<flexiondotorg> apw, So the issue is the default resolution when virtualbox-guest-x11 is not installed.
<apw> the default resolution is that offered by the vesa settings i assume ?
<flexiondotorg> apw, The vmware video devices are already blacklisted by grub-gfxpayload-lists
<apw> ok, so then it sounds like whatever this is using now is a candidate for blacklisting ?
<flexiondotorg> apw, Must be. vesa is used by vbox when the guestadditions-x11 is absent.
<apw> so that is a vbox issue really, offering stupid resolutions by default
<flexiondotorg> apw, Since 14.04. Yes.
<flexiondotorg> apw, The 640x480 thing started sometime during 14.10.
<apw> and presumably it does that because they don't care about you if you don't install their video driver
<flexiondotorg> apw, I couldn't possibly comment ;)
<apw> i wonder why i makes a difference to blacklist it in grub though, vesa must be very broken
<apw> and so i would think rather than being a fallback option to blacklist more things in grub, it might
<apw> be the appropriate option instead
<flexiondotorg> apw, It is odd because when booting from the live media, resolution is 1024x768.
<flexiondotorg> But on first install, resolution is 640x480.
<apw> right, that doesn't use grub, nor initialise the display
<apw> it uses syslinux
<flexiondotorg> apw, Indeed.
<apw> grub initialises the display, because you know the vesa modes offered should be the preferred size of your display, so setting it up early makes sense and makes things prettier
<apw> unless your vesa config is spam
<apw> and has "1 1024x768 2 640x480 (default)" in it ... or equiv
<flexiondotorg> So, possibly a regression in what Virtualbox provides.
<apw> but if we are blacklisting for vbox video anyhow, it may well make sense to blacklist everything when vbox is found
<apw> which is what i assume the wildcard you added does
<flexiondotorg> apw, Yes.
<flexiondotorg> Although, AKAIK, vbox have only ever used one device I...

Colin Watson asked that I discuss this issue in #ubuntu-kernel. A log of the IRC discussion is below, as requested by Martin Pitt, and I'll attach a debdiff for 'grub-gfxpayload-lists' in due course:

Here is what we discussed:

<flexiondotorg> I been discussing https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/ with cjwatson in #ubuntu-devel
<ubot5> Ubuntu bug 1368784 in virtualbox (Ubuntu) "Vivid and Utopic Virtualbox guest gets only up to resolution of 640x480" [High,Confirmed]
<flexiondotorg> I've got the following work around - https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/comments/17
<flexiondotorg> cjwatson is prepared to update grub-gfxpayload-lists if someone here can confirm "fixing" this issue at a kernel level is hopeless.
<flexiondotorg> So, thoughts?
<apw> flexiondotorg, "fixing" at the kernel level, do we know what the issue is ?
<apw> flexiondotorg, the implication of the (admittedly older) comments is that you need virtualbox-guest-x11
<apw> flexiondotorg, and indeed i can confirm that installing the said package does sort things out, who knows what i has in it mind
<apw> seems it has a vbox specific video drivers
<apw> i wonder if they should be being installed by jockey
<flexiondotorg> apw, So the issue is the default resolution when virtualbox-guest-x11 is not installed.
<apw> the default resolution is that offered by the vesa settings i assume ?
<flexiondotorg> apw, The vmware video devices are already blacklisted by grub-gfxpayload-lists
<apw> ok, so then it sounds like whatever this is using now is a candidate for blacklisting ?
<flexiondotorg> apw, Must be. vesa is used by vbox when the guestadditions-x11 is absent.
<apw> so that is a vbox issue really, offering stupid resolutions by default
<flexiondotorg> apw, Since 14.04. Yes.
<flexiondotorg> apw, The 640x480 thing started sometime during 14.10.
<apw> and presumably it does that because they don't care about you if you don't install their video driver
<flexiondotorg> apw, I couldn't possibly comment ;)
<apw> i wonder why i makes a difference to blacklist it in grub though, vesa must be very broken
<apw> and so i would think rather than being a fallback option to blacklist more things in grub, it might
<apw> be the appropriate option instead
<flexiondotorg> apw, It is odd because when booting from the live media, resolution is 1024x768.
<flexiondotorg> But on first install, resolution is 640x480.
<apw> right, that doesn't use grub, nor initialise the display
<apw> it uses syslinux
<flexiondotorg> apw, Indeed.
<apw> grub initialises the display, because you know the vesa modes offered should be the preferred size of your display, so setting it up early makes sense and makes things prettier
<apw> unless your vesa config is spam
<apw> and has "1 1024x768 2 640x480 (default)" in it ... or equiv
<flexiondotorg> So, possibly a regression in what Virtualbox provides.
<apw> but if we are blacklisting for vbox video anyhow, it may well make sense to blacklist everything when vbox is found
<apw> which is what i assume the wildcard you added does
<flexiondotorg> apw, Yes.
<flexiondotorg> Although, AKAIK, vbox have only ever used one device ID for video.
<apw> flexiondotorg, not that i really know why one would use vbox if you had any other choice
<flexiondotorg> The other "work around" is to configure grub to use 'console' for all video output.
<flexiondotorg> apw, It is very popular with people who just want to test. Low barrier of entry.
<apw> flexiondotorg, i don't find virtmgr any more complex to drive, and it idoesn't have these issue at least
<flexiondotorg> apw, Agreed.
<apw> and i don't need 30k lines of random out of tree junk loaded into my kernle to make it work either
<flexiondotorg> But, people do use vbox.
<flexiondotorg> apw, So the question is. Is this fixable by the kernel team? Seems like a big fat "No" based on what we've discussed?
<apw> well they had much more ufn, they were just exploding in the host when they tried
<apw> flexiondotorg, i am not sure what we would fix, grub handed us a configured terminal, and we continued to use it as instructed
<apw> flexiondotorg, and presumably because vesa, it was at a stupid resolution
<apw> i'll try your workaround on that same gnome image in vbox and see how it looks
<flexiondotorg> apw, So I think that blacklisting the vbox video device in grub is the way forward.
<flexiondotorg> apw, OK. Thanks for testing.
<apw> flexiondotorg, and i think the behaviour with the blacklist seems more useful, and i assume if i install the -guest-x11 i'll get go faster stripes
<flexiondotorg> apw, Yes with guest-x11 install you get dynamic resizing and such.
<apw> flexiondotorg, but yes, i htink my prefrered option is this blacklist, and if it fixes the issues you have with locked disks that sounds liek a win
<flexiondotorg> apw, Agreed. Although the inability to enter encryption pass phrases affects actual hardware too. By blacklisting vbox for grub you get a text mode plymouth which always works.
<apw> flexiondotorg, yeah, i assume we have a lot of issues there now we have systemd fun to play with
<apw> i guess i ought to reinstall some of my kit with that to find out
<flexiondotorg> apw, systemd isn't to blame for passphrase entry. That was present in 14.10 also.
<flexiondotorg> apw, My "solution" was not to ship a graphical plymouth theme in 14.10. That way only text mode available and pass phrase entry worked.
<flexiondotorg> apw, Are you still testing this on an Ubuntu GNOME image or have we concluded that blacklisting is the solution?
<apw> i think we concur blacklisting is the way forward for the size issue
<apw> the plymouth not working is separate
<flexiondotorg> apw, Thanks for your time.
<apw> flexiondotorg, thanks for paying attention to it :)
<flexiondotorg> apw, I'll report back to cjwatson and he can make the blacklist change.
<flexiondotorg> apw, Most welcome :)
<apw> ack, thanks

Colin Watson (cjwatson) on 2015-03-27

Changed in grub-gfxpayload-lists (Ubuntu):
status:	Confirmed → Fix Committed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-03-28:

#19

This bug was fixed in the package grub-gfxpayload-lists - 0.7

---------------
grub-gfxpayload-lists (0.7) vivid; urgency=medium

  * Blacklist VirtualBox Graphics Adapter (thanks, Martin Wimpress;
    LP: #1368784).
  * Skip various backup files (LP: #1136592).
-- Colin Watson <email address hidden> Fri, 27 Mar 2015 17:52:29 +0000

Changed in grub-gfxpayload-lists (Ubuntu):
status:	Fix Committed → Fix Released

Revision history for this message

gravy45 (gravy45) wrote on 2015-04-17:

#20

The fix is that the resolution will be 1024x768 (max)?

Revision history for this message

John Przybytek (jprzybytek) wrote on 2015-04-18: Re: [Bug 1368784] Re: Vivid and Utopic Virtualbox guest gets only up to resolution of 640x480

#21

The fix would be that installer correctly recognizes the screen
resolution. 1024x768 would certainly be be better that 640x480 as you
could actually use the virtual installation.

On 04/16/2015 09:15 PM, gravy45 wrote:
> The fix is that the resolution will be 1024x768 (max)?
>

Revision history for this message

gravy45 (gravy45) wrote on 2015-04-22:

#22

Thanks @John P. Resolution in the 20150422 build of Ubuntu MATE is 1024x768. I'd prefer that it be able to go full screen like with past Ubuntu releases, and think that would be a true, final fix. That's the question for the folks working on this - what's the intention?

Ubuntu
grub-gfxpayload-lists package

Vivid and Utopic Virtualbox guest gets only up to resolution of 640x480

Bug Description

Related branches

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntugrub-gfxpayload-lists package

Vivid and Utopic Virtualbox guest gets only up to resolution of 640x480

Bug Description

Related branches

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
grub-gfxpayload-lists package