Opened 9 years ago
Closed 9 years ago
#15320 closed defect (fixed)
Ubuntu 14.04 doesn't boot correctly after VB upgrade
Reported by: | Stéphane Charette | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.0.18 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Linux |
Description
Ubuntu 14.04-32bit desktop installed as guest on Ubuntu 15.10-64 bit host.
Upgraded yesterday from VB 5.0.16 to 5.0.18. Since the upgrade, the guest no longer boots correctly. It goes to a completely black screen instead of the usual Ubuntu desktop.
Log file ends with this:
13:40:37.514254 Changing the VM state from 'SUSPENDED' to 'RESUMING' 13:40:37.514394 Changing the VM state from 'RESUMING' to 'RUNNING' 13:48:35.192950 VBVA: InfoScreen: [0] @0,0 800x600, line 0xc80, BPP 0, flags 0x5 13:48:35.192975 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f42081e2000 w=800 h=600 bpp=0 cbLine=0xC80 flags=0x5 13:48:35.193003 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=800x600, Sending to async-handler 13:48:35.193066 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=800x600 13:48:35.193077 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=800x600 13:48:35.193098 GUI: UIFrameBufferPrivate::performResize: Size=800x600, Using fallback buffer since no source bitmap is provided 13:52:59.965882 Changing the VM state from 'RUNNING' to 'SUSPENDING' 13:53:00.021278 PDMR3Suspend: 55 340 238 ns run time
Attachments (2)
Change History (14)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
I manually re-installed the 5.0.18 guest additions like this, but it didn't help:
sudo mount /dev/cdrom /mnt cd /mnt/ sudo ./VBoxLinuxAdditions.run sudo reboot
Also tried to toggle the "Enable 3D Acceleration" setting in the guest's machine settings, but it doesn't make a difference.
follow-up: 4 comment:3 by , 9 years ago
Which kernel do you have installed in your Ubuntu 14.04 guest?
comment:4 by , 9 years ago
Replying to frank:
Which kernel do you have installed in your Ubuntu 14.04 guest?
uname -a Linux 32bit-cross-compiler 3.19.0-58-generic #64~14.04.1-Ubuntu SMP Fri Mar 18 19:05:42 UTC 2016 i686 i686 i686 GNU/Linux
by , 9 years ago
machine log as requested when guest boots to a black screen
comment:6 by , 9 years ago
I have a Trusty guest with Linux 3.13 which works perfectly. Perhaps the different kernel version.
Oh, could you also attach the complete /var/log/Xorg.0.log?
comment:7 by , 9 years ago
Thanks. Now I updated my Trusty guest to the Vivid LTS stuff (kernel already was, now did X11) and it still works. I guess we need more debugging output in the vboxvideo driver.
follow-up: 9 comment:8 by , 9 years ago
Just a guess, but does increasing the VRAM make a difference?
comment:9 by , 9 years ago
Replying to michael:
Just a guess, but does increasing the VRAM make a difference?
Per Frank on the dev mailing list, I tried the 5.0.16 guest additions, and the problem has gone away. I have not tried increasing the VRAM which is currently set to the default 12 MB.
comment:10 by , 9 years ago
I seem to have reproduced this by installing the 5.0.18 Additions on a freshly installed and updated Ubuntu 14.04.3 32-bit machine.
comment:11 by , 9 years ago
The latest 5.0 Guest Additions test build (> revision 107107) contains a fix for 32-bit guests mentioned in the previous comment. Could you confirm?
Even though the guest boots to a black screen, I can still SSH to it. Looking at
/var/log/Xorg.0.log
, I see it ends with this:I'm a bit confused about what I'm seeing in the
/opt/
directory. I already have a VBoxGuestAdditions-5.0.18 directory, though I don't recall installing the 5.0.18 guest additions yet:Looking at running applications, I don't see the usual VBoxClients. All I have is: